Working cards #1
Comments
|
nvidia drivers 546,29, 1143:83F3 from xelafic seems to be 1043:83F3 from his screenshots btw |
|
I've posted in discussions |
|
Thank you for the info, can you also include CPU model ? Some AM4 motherboards only enable ReBAR with recent CPUs |
Edited to include CPU model. |
|
Please note GT640 is not supported by nvidia-smi but does appear to indicate full size by other means. Managed a few tests with 1660S 3DMark PCIE test results are clearly buggy so not included. 3DMark Timespy showed less than 1% gain with profiles of 1GiB, 1.5GiB so subjective. W10 and Linux GravityMark showed no gain, run with Vulkan MS Gears of War 5 which has been said to be favorable of resizable BAR showed no gain. Total War Three Kingdoms showed no gain on W10 but did show up to 15% on Linux. The W10 bench scored similar to the resizable BAR score on Linux. Standard 256MiB Resized to 8GiB Unlike W10, Linux nvidia settings shows the resizable flag, note that on my HW it requires resizable BAR to be set at least to the size of the VRAM, so in this case 8GiB and upwards. With W10, if resizable BAR is set to 8GiB and the card disabled in the OS and resizable BAR adjusted to 256MiB then enabled that the BAR is set back by W10 / nvidia driver to 8GiB. Under W10 the "nvidia-smi -q -d memory" always seems to show BAR1 memory of 2MiB in use. However under Linux we can see this value change with TWTK showing between 400MiB and 500MiB when running. |
|
Thank you for the report, table updated ! |
|
Works great for me, i did wrestle with some of the steps but eventually got there. Might make a video of my own.
Alan Wake 2 with ReBar set to Disabled in NVPI Alan Wake 2 with ReBar set to Enabled in NVPI (size limit 0x0000000200000000, ~8gb) Alan Wake 2 with ReBar set to Enabled in NVPI (size limit 0x0000000040000000, ~1gb) Seem like this is one of those games with very clear rebar-size-to-fps-boost ratios :) for testing I repeated them all a few times - clicking continue chapter from where I last saved, letting it load, and doing absolutely nothing. no movement, no adjustments, keeping it controlled. Close game, change NVPI setting, reload. It was consistent, repeatable and I didn't get any FPS fluctuations either so these are authentic snippets. I am having some issues however - my motherboard BIOS had two identical entries for the PCIE driver to add the .ffs file, and I added it to both. Now my PC will only start from cold, no reboots, no sleep resume, no hibernate resume. It'll not post, and the HDD light will remain on until i power off the PSU and restart. From full power down it works every time. I have a feeling this might be a potential hurdle for some users as we iron out the kinks of patching compatible BIOSes - I'll do some testing at some point of adding the .ffs to one entry, then the other, and see if ReBAR continues to work and it resolves my issues. For now I can deal with cold boot :P |
|
Motherboard model: Gigabyte AORUS X570 Elite |
|
is anyone else seeing errors in vulkan applications after enabling ReBAR? EDIT: Sorted, was a faulty DSDT patch |
|
Took me a day to get it to work - most troublesome was Gigabyte's "Invalid BIOS" protection. Many thanks @terminatorul
|
|
Thanks for adding my configuration! 😁@terminatorul For completion's sake my driver version is 551.23 and it's a GeForce Game Ready driver. I don't know what options in NvStrapsReBar.exe populate the Target BAR Size so I just left it blank. 😅 |
|
X570 not very easy to flash on ASROCK. I needed to downgrade to old AGESA version and flash modified BIOS using FLASHROM
|
|
|
Can you run |
Did I get all the information? |
|
|
@SuperCoolGuy855 This is the first time I see option 65 working (which happens to be the safe choice (and least intrusive) if users accidentally disable 4G Decoding or load the default settings in UEFI setup, but the option does not always work). Congrat'z and enjoy ! |
|
I had 65 working too initially but the new version of the program allows me to adjust the BAR size which I needed. 👍 |
|
The newer version allows both changing the BAR size on the GPU and using input value 65 for the PCI side. Please try option 65 and use it if it works for your system (you need to enable ReBAR in UEFI setup) Because it is the safe choice in case you accidentaly disable 4G decoding in UEFI setup, or you load the default UEFI settings, or the CMOS battery dies. So in this case you will not need to manually clear CMOS. I am thinking of a better failsafe for such cases, but it will be a while before I can implement anything about it. |
Option 65 is unavailable for P. Am I looking in the wrong spot for it? |
|
Oh, I forgot I made it the System default. It's really option 0 now :) |
Thank you! Failsafe is now in place and everything is working as intended. |
|
|
|
|
|
Thank you so much ♥. After fiddling around for a day i finally got it working. In Cyberpunk ~10% increase in performance: 3440x1440p; Ultra; RT Medium, No Upscale. PS: Obviously i don't play at these settings :D PS 2: In "Adding FFS module" it says to put the *.ffs file at the bottom of the volume. That didn't work for me. Scroll down a little until you see "NvramDXE", "PcdDXE" and the other thing which is too long for me to remember. I put it here on both entries and that did the trick. |
|
CPU: Intel Core i5-10400 @4.00Ghz
|
|
CPU: i7-10700K New BAR size (GPU-Z): New BAR size (nvidia-smi): |
|
CPU: Ryzen 5 5600x |
|
CPU: AMD Ryzen 5 5600 The BIOS Image is dumped, modified (w/ UEFITool), and then re-flashed with flashrom-DOS-port (through a bootable USB drive with FreeDOS on it) since ASRock's built-in Instant Flash reported
|
|
Works on "Asus ROG Rampage V Edition 10" + "Asus ROG Strix GeForce RTX 2080 Ti OC". Used "UEFITool.exe" + "NvStrapsReBar.ffs" + "UEFIPatch.exe" + "Asus USB BIOS Flashback" + 4G Decoding ON + CSM OFF + "NvStrapsReBar.exe" CPU: Intel Core-i7 6950X (Broadwell-E) |
|
CPU: Intel Core -2400 Q0NT |
|
|
|
CPU: i9 - 9900KF
|
|
@Addalyn I have the B550-f Wifi and when i use the UefiTool, I get 2 pcibus entries so I add teh NVStraps.ffs file to teh end of both those volumes. I then save the bios with the same name. When I run UefiPatch I always get the same error "no patch can be applied to your input file" Any help would be appreciated |
Intel 7 Series Chipset (B75/Z75/H77/Z77/Q75/Q77/C216) will additionally need to apply IvyUSB3.txt for functioning USB 3 ports in BIOS with 4G Decoding enabled. Use .\UEFIPatch YOURBIOS.bin.patched .\IvyUSB3.txt -o YOURBIOS.bin.patched after downloading and placing it in the same folder as UEFIPatch. Intel 8 Series Chipset (H81/B85/Q85/Q87/H87/Z87/C222/C224/C226) will additionally need to apply HswUSB3.txt for functioning USB 3 ports in BIOS with 4G Decoding enabled. Use .\UEFIPatch YOURBIOS.bin.patched .\HswUSB3.txt -o YOURBIOS.bin.patched after downloading and placing it in the same folder as UEFIPatch. Intel 9 Series Chipset (H97/Z97) will additionally need to apply BdwUSB3.txt for functioning USB 3 ports in BIOS with 4G Decoding enabled. Use .\UEFIPatch YOURBIOS.bin.patched .\BdwUSB3.txt -o YOURBIOS.bin.patched after downloading and placing it in the same folder as UEFIPatch. EXAMPLE: .\UEFIPatch rebar.rom .\BdwUSB3.txt -o rebar.rom Maybe this will help you. |
Thanks for the reply.... I'm not sure this is the applicable.. I'm not having issues with usb ports and my boards aren't in any of these chipset families? I can't get the uefipatch toll to work... Am I missing something? |
Yes, I think you need use this method. Please make a try and tell us it if worked. You don't get a rom like rebar.rom.patched is like the file is remplaced only. |
Im very sorry, I'm not sure I understand what you mean...can you explain exactly what I need to try? |
they are asking if you did the following : Was you able to complete this step? Of patching the bios with uefipatch? A) if you wasn’t able to complete it then you may have a problem? B) if you was then it might be something else |
|
Please watch the video carefully and make sure it lines up with what your system does to make the file |
|
I followed the video exactly, screenshot 235650 shows my bios file being opened, then the video shows the insertion of the .ffs file. finally the screen shot 235116 shows you what happens when I try and use uefipatch, i have the txt file and the bios file thats been saved with rebar added to its name and it saves it as a .rom not a .cap file.... any ideas? https://github.com/user-attachments/assets/d7a47273-82f5-459b-8043-4f1bfa9db9e7
|
something isnt adding up..... my board is the asus tuf z590 gaming plus wifi....follow the video and it doesnt work...see the screen shots and screen recorder clip i posted above.... |
The video was very helpful, it shows you aren’t scrolling all the way down till you see the last driver entry? are you sure where you stop and insert the rebar module is the last dxe driver entry? |
|
You could try using a older bios file, see if it gives the same behaviour |
Screen.Recording.2024-09-04.124534.mp4see new video this was my last attempt, is this the correct spot? in the youtube video you sent me, he scrolled to the end of the series of dxe drivers...there are more further down before you hit teh line volume free space, this is where i inserted it now.... unfortunately this is the same result.... thoughts? and once again i greatly appreciate your assistance and insights |
I believe with .cap files you might need to do something different, I believe you open the bios file as .cap format then you right click the 1st entry and save it, it should save as .rom, and then you follow on as normal from there you see with ASUS and some other manufacturers they checksum the bios file to make sure it’s genuine, if anything before the check some changes then it won’t flash and has to be forced, either with flashback (which doesn’t read the checksum or a executable that has ignores the checksum, worse case you have to use a tool that hooks up directly to the bios chip and flash it that way the problem is with this checksum thing, which is why it’s called a .cap and not a .rom, is the programs are probably getting caught up with the checksum, there’s even videos of people manually removing the checksum with a hex editor, look up convert .cap to .rom and it isn’t simply renaming it… there’s actually 2 to 3 bios files in that .cap file and you only need to edit the one, which is why your finding multiple entries, youll probably do all of this then find you can’t even flash it, you’ll need a tool to hook up directly to the board… so ask your self why your doing this? do you have a old gpu? The only time I found I needed to do this is when I was trying to unlock the chipset fan options on the ASUS board and I stopped the project because I would have to flash the file using a tool, (a peace of hardware that hooks up to it) example: 1st you need to do a hex edit I’m getting ahead of my self, again I’ll put the question to you is it really worth all this effort and investment in equipment |
|
Here’s a video about how you convert the file using hex edit it’s a right pain, and even the guy in the video does it wrong, as when I was messing about with it, I found 2 bios files with in 1 .cap this is seriously technical stuff and you may thank ASUS |
|
Thank you so much! |
|
I didn't have any luck getting this working with a Gigabyte Z170X Gaming 6 and a 6700K but I upgraded recently so I decided to try this mod again and it worked flawlessly. Thank you! Using v0.4-rc1
CPU: AMD Ryzen 7 3800X |
|
CPU: AMD 5800X3D Was moderate difficulty. Tried reverting to AGESA pre 1.2 but that actually did not work. Switched back to beta 5.63 taichi driver, used flashrom to make backup, used UEFI tool to add nvstraps ffs, flashrom to update modded bios, ran nvstraps.exe in admin mode and selcted (e) then (s) to save, rebooted and viola. |
|
My mobo had old bios ( 2.20 ). I used this guide to flash newest Asrock bios (with added ffs module using uefi tool [remember to add ffs module for each search occurence - 2 times]) using flashrom method: https://winraid.level1techs.com/t/guide-how-to-flash-a-modded-ami-uefi-bios/30627 CPU: Ryzen 5600x
|
|
@terminatorul Is it necessary to disable NvStraps before changing CPU? |
|
Everything seemed to work first try, thank you! I used v0.4-rc1. detailssystem information
|
|
|
I used v0.3 version. With v0.4-rc1 it doesn't works because configuration is not being saved.
|
|
CPU: i5-10400F Instructions for those who use a Gigabyte motherboard and a programmer (I have a CH341A):
|
and others
If you get ReBAR working you can post your system information in the below, if your motherboard and graphics card are not already listed in the table.
Use the following format to post a new result:
It may be easier to post screenshots instead, with:
nvidia-smi -q -d memoryIf you needed to apply more changes to make ReBAR work, post about them as well.
subsystem
@Xelafic
1043:83F3
@terminatorul
1462:3715
@Felty2562
1043:8747
(BIOS system with MBR)
@Xelafic
1458:4013
@UnidentifiedTag
1458:4014
@UnknownGuyzs
1462:3726
@pexcfequinnet
1043:1AB1
@Xelafic
1458:4013
@vig
1043:870F
@Sid127
1025:1336
@CptSchwifty
10DE:1435
@saveli
10DE:139F
@Maidvelia
1462:3734
@dakisback2
10DE:1435
@Pudent
3842:2589
@Cancretto
1B4C:A017
@SuperCoolGuy855
1462:C757
@ngrfgt
10DE:A027
@sociofall
1043:8667
@AliZf1d
19DA:5511
@T1m0th1
1462:3715
@ LLLLL MMMMM AAA OOO
1043:874F
@Aetopia
7377:2000
@traveeeeee
1458:37D9
@dahxka
7377:0000
@Pekls
10DE:1366
@rainbowjose
1458:37C2
@VartuloFN
196E:1345
@Akadem1kxz
1462:C757
@pabloalber84
1043:86BB
@alexpanetta
1043:868A
@dimka4996
19DA:3529
@lapist
10DE:1F08
@random-tek
19DA:5527
@whood
1462:8D90
@13pwn
1462:C724
@sunbyy
1D05:1096
@TheUntouchable
1458:3FEB
@TessellatedGuy
1043:8698
@readyact
1458:37C2
@AssKissStudio
10DE:139D
@Keigun-Spark
1458:3FF4
@TastyChimera
3842:3173
@fitsfer
1458:401A
@FreeTheTech101
19DA:1503
@woheede
1458:37A9
@Auglisters
17AA:3FFC
@Baruls
10DE:1F08
@BJTorgs
3842:3067
@Sachin-Garia
1458:401A
@WannaBeOCer
10DE:12A3
@Famebloody
1462:373E
@dduy1107
1043:86B7
@bebelllm
10B0:1E07
@Revenc7
10DE:139F
@ammarasyad
17AA:3FBC
@mitix67
10DE:12A6
@sandr1x
1462:375A
@Giperion
1458:37C0
@Addalyn
1458:4008
@Bakashii
1043:86B6
@NanoDrivee
(GV-N208SAORUS-8GC)
1458:3FF4
@Cise989
3842:2383
The text was updated successfully, but these errors were encountered: