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 |
I did manage to recover my laptop by using the novo button on the right side, it self-healed. I'm just trying to figure out what I missed before attempting another reflash. I'm thinking I did something wrong when I used the UEFIpatcher, but I'm not sure. Should it be in .ROM format when flashed or .BIN? |
|
中央处理器：I5-13600KF |
|
CPU: RYZEN 5-5600 VRAM size: 4 GB Who will flash the bios on GIGABYTE motherboards - just flash it through q-flash plus, the other methods did not work for me |
hello, for q-flash plus you have to put the bios modified with UEFITool in .rom or modified in .f16 as is the default bios? |
|
Hi! My question is how exactly are we supposed to modify bios file if on my laptop both GPU and UEFI are both on the same chip (i think) Let me know if the guide I mentioned here is usefull for anyone, I could post it here |
|
CPU: AMD Ryzen 7 5800x |
|
CPU: Intel Core i7-8700
|
|
This page is for confirmed working, if you don’t see you’re manufacturer / motherboard listed. Then you should assume it hasn’t been done. please scroll the list above, if it isn’t listed and you are having issues, open an issue. Otherwise unless you have a working board you wish to add to the list above please do not comment. |
System
GPU-Z
nvidia-smi
CPU-Z
Note:To flash the modded BIOS on this board, you'll have to use the ASUS BIOS Flashback feature, because EZ Flash will say "Selected file is not a proper BIOS!" and not allow you to flash it, so it seems to me that there's a check that's run on the image, a check that BIOS flashback can't run because of how "simple" it has to be, either that or it just wasn't implemented by ASUS. |
Bro, how were you able to get the Asus laptop to work? After flashing the BIOS and enabling ReBar on the RTX2060 I just get a constant blue screen error "gpu video scheduler", maybe I'm doing something wrong? Asus FX506IV |
|
Finally, here it is !
As I am on a "capsule bios" from Gigabyte, I had to follow this flashing method : https://winraid.level1techs.com/t/flashing-gigabyte-while-avoiding-invalid-bios-image/31185/305 |
|
|
GPU-Z: GPU page + ReBAR page CPU-Z: CPU page + MB page console output from nvidia-smi -q -d memory Done via CH341A Programmer and Flashrom on Linux. |
System
GPU-Z
nvidia-smi
CPU-Z
Notes:
Commands to disable the "BIOS Lock" and other stuff using GRUB:
|
System information
nvidia-smi
GPU-Z
CPU-Z
|
I'm interested. I've got an ASUS G732LXS device and currently researching on how to enable ReBar on it. |
|
I had to use flashrom from FreeDOS (Rufus) to flash the modified bios:
|
|
I think I got it. The BIOS was easily reflashed using the standard bios update procedure. |
|
Somebody has test with ROG CROSSHAIR VIII HERO(WI-FI) BIOS 4805? |
|
CPU: Core i7-12700K
Haven't tried maxing out the BAR size just yet; going with 2GB and moving up throughout the week |
|
I used these steps to flash the modded BIOS I couldn't find my GPU PCI subsystem ID. maybe this could be in part due to me using a PCI-E x1 to x16 riser to use the card? On another note, I hate 1366x768 monitors.
EDIT: oh god, I accidentally switched to the sensors tab... |
|
CPU: Ryzen 5800X3D Completely smooth process with no unexpected issues. I'm unclear, however, as to why I don't get the 'unsupported GPU' message in GPU-Z. It just shows everything as working with no error messages. Obviously that's not a problem, but curious all the same as everybody else seems to have it.
|
|
CPU:Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz I successfully started ReBAR according to the tutorial. No abnormalities have been found so far. The graphics card has modified the video memory.
|
|
CPU: Core i5-9400f
|
|
CPU: 12-Core Intel Xeon E5-2690 v3, Unlock Turbo Boost, 3500 MHz
What to do with the previous DXE driver BIOS ReBarUEFI? I didn't delete it, but added NvStrapsReBar.ffs. It seems they work together, you can install a video card with ReBar support and not have to reflash the BIOS again. In benchmarks I noticed an increase of 0.5-5%. But most importantly, the friezes and stators in Dakar Desert Rally disappeared, otherwise it was impossible to play! Now I’ll try again in BF5, there are freezes even in DX11, but it’s somehow buggy, it won’t start today. Also, the YouTube video “Japan in 8k” is now available without friezes. Used version v0.3. |
|
CPU: Ryzen 2400G |
|
Here are my results.
|
|
CPU: Intel Core i7 8086K |
and others
If you get ReBAR working please post your system information in the below format
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
The text was updated successfully, but these errors were encountered: