Replies: 368 comments 22 replies
-
|
You need to disable CSM
I'm also using the same GPU and GOP doesn't work when using modded VBIOS unless you use "magic GOP" which is incompatible with secure boot. So try with stock VBIOS and if it works then you can try magic GOP if you need modded |
Beta Was this translation helpful? Give feedback.
-
|
Yeah i already reverted to the stock bios. Forgot to mention, obviously the CSM is off. |
Beta Was this translation helpful? Give feedback.
-
|
Try setting these BIOS settings: 4G Decode: On |
Beta Was this translation helpful? Give feedback.
-
|
I did already try all of them, i even tried changing mmioh size from 64gb to 128gb but with no results. |
Beta Was this translation helpful? Give feedback.
-
|
@Raziel49 are you able to boot a linux live usb with 4g decoding ? |
Beta Was this translation helpful? Give feedback.
-
|
@xCuri0 I will try now, will let you know |
Beta Was this translation helpful? Give feedback.
-
|
Just tried 3 different linux distros, ubuntu, xubuntu and kali linux, but i can't boot in any of them. The bootloader works, but as soon as one selects "install linux" or "try linux without installing" i get the same black screen as if i was trying to boot windows 10. |
Beta Was this translation helpful? Give feedback.
-
|
Of course all of this is with Above 4G option enabled, with the option disabled i can boot no problem. I think that there is some problem with the motherboard bios and the Above 4G function, maybe it was not well implemented, there has to be a reason if it was hidden by default. |
Beta Was this translation helpful? Give feedback.
-
|
@Raziel49 try to get a log of the kernel output somehow |
Beta Was this translation helpful? Give feedback.
-
|
Ok, do you have any suggestion? How can i record that output? |
Beta Was this translation helpful? Give feedback.
-
|
@Raziel49 try adding kernel option Also can try disabling acpi to see if it fixes with worst cause u will need to debug over serial port if no other way gives you early kernel output |
Beta Was this translation helpful? Give feedback.
-
|
These asus x79 motherboards have a hidden MMIOH setting that defaults to 64GB, it might be a factor and need restricting to lower in order to support ReBar on this platform. You need to enable the hidden system agent settings (IOH config) panel in a bios editor to access it.
|
Beta Was this translation helpful? Give feedback.
-
|
@Squall-Leonhart is that the MMIOH size or base ? Either way it should be fine unless you have 64GB+ RAM or a GPU with 32GB+ BAR. There is no need for BIOS editing you can just use setup_var as described here Enabling hidden 4G decoding |
Beta Was this translation helpful? Give feedback.
-
|
I remember trying all of these different MMIOH values but with no result. Sadly i can't continue trying things as i don't own the board anymore. |
Beta Was this translation helpful? Give feedback.
-
Hello squall-leonhart my shore card is configured on mmioh 64g by default. when I decrease the value at 32G, there is a black screen while when I put it on 128G, my pc starts correctly. do you have any idea of the cause? |
Beta Was this translation helpful? Give feedback.
-
|
I've finally found a solution for BIOS bug where neither MMtool or UEFItool would successfully add modified ffs/body. What you have to do is to find the value with hex editor, change it accordingly (you can use patched bios and just copy values) but then checksum fails.
Finally, now I can finish the guide ... |
Beta Was this translation helpful? Give feedback.
-
|
Continuation of a prior conversation on zoxzx's guide: Requested link to asus 4701 driver: https://www.asus.com/uk/supportonly/sabertooth%20x79/helpdesk_bios/ Points where errors occured and no work around has been achieved: amiboardinfo.ffs injection during dsdt patching causes padding errors |
Beta Was this translation helpful? Give feedback.
-
|
@ZOXZX thanks for figuring this out, I'll update the wiki with it |
Beta Was this translation helpful? Give feedback.
-
|
I had an experiment with another ASUS (Gene) board, and this time amiboardinfo caused padding error. By comparing DSDT from last two BIOS versions, there was change at the end. Method (_SB._OSC, 4, NotSerialized) // _OSC: Operating System Capabilities Creating amiboard info with old DSDT or with this lines removed from new one, solved the padding problem. |
Beta Was this translation helpful? Give feedback.
-
|
You need to use \AMIBCP-4.53.0050, open bios find what you search, you need to activate it like extended user, not a regular user. If you activate it as the first option, after activating 4g x.m.p, it stops working. https://github.com/xCuri0/ReBarUEFI/wiki/Unlocking-hidden-BIOS-menus#uefi-editor... worket perfect. setup_Var not help to me... Im with rampage 4 extreme...#24 |
Beta Was this translation helpful? Give feedback.
-
|
in this patch, original value is 00100000760B48B8 and it was patched to FF000000760B48B8 ? or other way round ? PciBus | Increase 256 byte configuration space limit to 4096 byte allowing access to PCIe extended configuration space3C1DE39F-D207-408A-AACC-731CFB7F1DD7 10 P:FF000000760B48B8:00100000760B48B8 |
Beta Was this translation helpful? Give feedback.
-
|
This patch is broken don't use it, and the only use case for it was some specific Hackintosh configurations. |
Beta Was this translation helpful? Give feedback.
-
|
How did you enable the "Above 4G" feature in BIOS? Mine doesn't have that option. How can I enable it or unhide it? Thanks in advance, |
Beta Was this translation helpful? Give feedback.
-
|
Hello. What IS the model of your motherboard.? |
Beta Was this translation helpful? Give feedback.
-
|
It's a ASUS P9X79 PRO. I don't know how to unhide the "PCI Subsystem Settings" menu from BIOS settings |
Beta Was this translation helpful? Give feedback.
-
|
ok. I have activated the "pci subsystem settings" menu.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot. Does it have the "Decode 4G" patch to have it enabled and working? I need it to use NvStrapsReBar.ffs |
Beta Was this translation helpful? Give feedback.
-
|
no I have not applied a patch to make the "decode 4g" work. these are modifications that take time but I can look. |
Beta Was this translation helpful? Give feedback.
-
|
I see. The issue is that I'm trying to get it working with the "Above 4G Decoding" feature enabled in my P9X79 PRO motherboard. But it seems that as soon as I use your modded UEFI BIOS and enable that in the menu the system resets all the time and I must restore the original BIOS to get it working again. |
Beta Was this translation helpful? Give feedback.
-
"Hello Franckythebest, whatever I did before with DSDT patching, no matter which versions I used, it always broke the BIOS file structure. Anyway, I managed to run it with an error, but SpeedStep technology stopped working... After your DSDT, does the structure stay intact for you? As far as I remember, you're also on Rampage4? For me, one option is with a slightly broken BIOS after DSDT, and the other option is with a normal, much more stable BIOS, just with 4G unlocked and the REBAR element added... If everything is fine for you after DSDT, would you be willing to share your BIOS pleeeese :)?" |
Beta Was this translation helpful? Give feedback.
-
In your post you said that "The issue above has been fixed by a new UEFIPatch" but there is no reference to that patch. I have the same mainboard than you and I'm having the same issue with "Above 4G Decode" enabled. In my case, when I enable it the system resets all the time. So I can't get it working in enabled state. That's why I'm asking for that patch. I suppose that it's a needed modification into the CAP file but I can't find the info about how to do it. |
Beta Was this translation helpful? Give feedback.
-
|
Well, finally I made some progress. I've managed to patch the BIOS cap file with AMIBCP 4.55 to add the enabled status for "Above 4G Decode" feature into the saved optimized settings. This way it boots with no problem and when loading optimized defaults into the BIOS setup it puts the enabled flag to the 4G thing. I attach the modded file ready to be programmed just in case that anyone needs it. P9X79PRO.zip (Thanks @franckythebest ) It also has the NvStrapsReBar.ffs added because my graphic card is a GTX 1660 SUPER. However now I have the problem with NvStrapsReBar.exe because even with CSM disabled and Above 4G also enabled (see atached pic)
it seems that the config is not being saved or whatever. I've no idea by now about what it happens. |
Beta Was this translation helpful? Give feedback.
-
|
hello test this bios. sub system menu and correction of dsdt. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again. I've finally solved by installing the previous release of NvStrapsReBar. It seems that the latest one is not working. See here. Now I have the ReBAR working with no issues.
|
Beta Was this translation helpful? Give feedback.
-
|
Good morning dimitrogen yes for me everything works correctly no apparent bug. my xeon e5 2697 v2 even takes 114MHZ on the bus with a relatively low voltage. I am attaching my bios. |
Beta Was this translation helpful? Give feedback.
-
|
"Hello, thank you so much, franckythebest. I have no words to express my gratitude. I dare say that I understand these kinds of things, but I couldn't figure out why it's not working... the moment I enter AmiBoardInfo, everything disappears, it goes into a "pad row, pad row" state, and I've tried everything. There is even someone on the forum who made a video with several options to prevent the structure from breaking. I paused the video at every step, and it worked for him, but not for me. I don't know why... But thank you so much, I'll test it now. Thank you!"And I will now unlock and enable 4G decoding Edit: works perfect no bad padding but how in my case speedstep not working...But all other is perfect manage to go to 4.7- very very thanks again |
Beta Was this translation helpful? Give feedback.
-
|
" There is even someone on the forum who made a video with several options to prevent the structure from breaking. I paused the video at every step, and it worked for him, but not for me. I don't know why... " Because you probably didn't bother to look at the second part where errors were corrected on a uncooperative BIOS ;-) |
Beta Was this translation helpful? Give feedback.
-
|
i try this way i try other way i try all the ways in video without rushing anywhere always broke padding...After transferring the modified BIOS to a new, clean BIOS, the padding still breaks |
Beta Was this translation helpful? Give feedback.
-
|
I seem to have read in a discussion that above 4.5ghz the speedstep is deactivated because much more power is required. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I mentioned that I reached a stable 4.7, but I didn't say that I stay there :)... By the way, a long time ago when I was setting cpu at -126* (that's where the cold boot was) at 5.1 GHz and the video at -86*+ with various my made volt mods, the processor still maintained the speed step unless I set it to "High" or "Ultra Performance" in power management... Even the BIOS, which was done without patching and only with the added ReBAR element and unlocked 4G, shows this address: 0x0000000420000000-00003FFFFFFFFFFF: PCI root complex, while after the patch it's 0x0000380000000000-00003FFFFFFFFFFF: PCI root complex. Theoretically, starting from lower address spaces allows PCI devices to have fewer limitations on memory access and more address space. This can lead to better performance, especially with new technologies like ReBAR, which enable the GPU to have better access to system memory... In the pached BIOS, after patching, when you try to run the speed step under default in the save menu, where it shows what you’ve changed, two identical lines with this command appear and it doesn't activate... For you, it's constantly at 114 and you didn’t notice... I generally set it to 4.5, adjust the power management in balance mode so it can range from 1.2 to 3.6, and then when I set it to ultra, it stays stable at 4.5. https://ibb.co/Nt5by8Y |
Beta Was this translation helpful? Give feedback.
-
|
[franckythebest] So, after seeing that my BIOS was also like that, but with broken padding (though I had copied all the files where the AMI BIOS made changes after inserting the element and restored them back, and the BIOS worked even with the broken padding), I decided to return to the other BIOS configuration—only with 4G decoding enabled and the REBAR element imported. This gives me the following address range: 0000000420000000-00003FFFFFFFFFFF: PCI Root Complex (after BSDT, it becomes 380000000000-00003FFFFFFFFFFF). I want to note that after I applied your BIOS, when I booted into Windows, REBAR was reset, or rather, it somehow requested it from another source. After a reset, switching to the first BIOS config, it boots into Windows with the REBAR set again. The idea here is that something is drastically changing. TODAY – I discovered that the padding breaks (at least for me) not after patching, but after the USB patch for Ivy Bridge. So I decided to try again—just patched it, now with the added REBAR element, and the difference is that I’m now using this 0000000420000000-00003FFFFFFFFFFF address range (which, according to most info, is better). I can tell something changed because it once again prompted me (as mentioned earlier) to enter a REBAR value. I set it to 32GB, reset the system, switched to the other BIOS (without the patch), booted into Windows, and it shows 16GB (the value I had set in Windows when I used that BIOS).and again switch to other and show me 32gb So, something definitely changed dramatically, and now SpeedStep and all USB are working, and I’m on the better address space.TRY how i say without bsdt even stable here what AI said: Higher Address Space: 0x0000000420000000 – 0x00003FFFFFFFFFFF This is the better address space. Lower Address Space: 0x0000380000000000 – 0x00003FFFFFFFFFFF It’s less ideal because it uses address space closer to system resources, which can lead to conflicts or inefficiencies, especially with memory mapping and PCIe devices. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone know which bios/settings I'd need for a P9X79PRO with 64GB ram and Intel ARC? From reading comments I don't need NvStrapsReBar and I plan on using linux but can't get to BIOS after enabling Above 4G. Here is a recording: https://files.catbox.moe/jwrvo3.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
If you are using an Intel GPU How did you expected that this going to work with a BIOS driver designed to work with nVidia cards ONLY? Just use the original ReBarUEFI or remove from my attached CAP file the NvStrapsReBar module. Delete it and save again before flasing it to the BIOS. Without the NvStrapsReBar module it should work for sure because you have the same ASUS P9X79 PRO. |
Beta Was this translation helpful? Give feedback.
-
|
Well I thought NvStrapsReBar was an extra module that needed to be added in for nvidia cards. My experience with software is that extra drivers for different hardware don't do much besides take up space. I expected to Intel Arc to work using the base module in this repo and the nVidia one to just sit around and do nothing. ¯\_(ツ)_/¯ |
Beta Was this translation helpful? Give feedback.
-
|
It's not. It's the reBAR fixup itselt. So you can't have that feature without it IF YOU HAVE A NVIDIA GPU. Any other case, this reBAR repository should work, but I've no any experience with Intel GPUs. And yes, NvStrapsReBar is a fork from the original, created for nVidia cards only. |
Beta Was this translation helpful? Give feedback.
-
|
NvStrapsRebar is only for Nvidia Turing GPUs because they don't support Resizable BAR officially, anything newer works fine with regular ReBarUEFI or modern OEM firmware. Also I think you can have both modules in the BIOS without any issue |
Beta Was this translation helpful? Give feedback.
-
|
You should disable the CSM boot and also allow the UEFI boot. Both things. If you can't boot with my BIOS after having removed the NvStrapsReBar there must be any other problem with your computer or may be you are not using the defaults after settings "optimal settings" only. |
Beta Was this translation helpful? Give feedback.
-
Hi there,
I have a ASUS P9X79 PRO motherboard with an i7-4930K and 32GB of ram, gpu is a Sapphire RX 580 Nitro+ 8GB.
The issue is that, after having successfully added your .ffs module to the bios, and also enabled the bios submenu for Above 4G Decoding, and having enabled the 4G Decoding itself, the board POSTs just fine but it doesn't boot anything, it just stucks to a black screen.
If i disable the Above 4G option, i can boot to windows just fine. Also another thing is that adding your module to the bios, breaks the sata contoller somehow (it gives code 10 in device manager, sata controller is a Marvell 91xx, but this is not a problem as i am booting from a NVMe drive).
I didn't do the UEFIPatch part, and the program said that it cannot find anything to patch.
Also i didn't do the DSDT patching step as you indicated in the guide that HEDT boards do not need it.
(But i still tried to look in the extracted DSDT file from the AmiBoardInfo module if i could find any of the lines you pointed to in the guide, and i couldn't find anything that matched)
I tried also updating the GOP in the vga bios to the last version, but to no avail.
UPDATE by xCuri0:
The issue above has been fixed by a new UEFIPatch (make sure to uncomment it) and DSDT patch, however there have been some reports of NVIDIA GPUs still not working on Windows.
UPDATE from @nefh:
dmesg_2GPU_KWin.txt
Since you've renamed the topic, I thought about some summary that could be pasted into first post.
I've recorded also some boot comparison videos for illustration, hope it's easier to get it this way.
All of the following issues happen only with ReBAR>1GB, only when RTX is receiving 64bit address space for BAR1.
In all cases ended in successful boot, the ReBAR works correct.
1. Boot to Windows - bad case
a) If RTX is connected to any display, even as a secondary input, then booting stops after POST, when Windows bootloader starts. The PC responds with instant turn off for power button push.
b) With Radeon connected alone or with no cables attached at all, the boot proceeds without any problems:
WindowsBoot.mp4
2. Boot to Linux - better case
Connecting display to RTX results in visibility problems during booting.
a) When display shows output from Radeon with secondary input connected to RTX, there is black screen instead of bootloaders UI. Any graphics seems to be a problem, even AMI logo is missing in POST screen. The visibility comes back during text mode.
b) When display shows output from RTX, the screen stays entirely black for whole boot sequence.
However, in all cases we have successful boot and proper display in desktop mode.
LinuxBoot.mp4
3. Misc info
The issue is independent to bootloaders. No matter if boot goes through rEFInd, GRUB or straight to Windows, the behavior is the same. Removing Radeon entirely and keeping only RTX also gives no effect - issues stays the same. RTX3090 VBIOS is the newest one.
Thanks for all your support and great work!
Beta Was this translation helpful? Give feedback.
All reactions