Replies: 357 comments
-
|
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.
-
|
As I can see, CSM is left enabled and Above 4G is disabled ... |
Beta Was this translation helpful? Give feedback.
-
|
thank you for your efficiency. But I don't understand because I manually change CSM bios to "disabled" and above4g to "enabled". |
Beta Was this translation helpful? Give feedback.
-
|
I just compared the patches.txt file that I used to patch my bios "uefipatch" and I notice that yours has an additional value "# PciBus | Increase 256 byte configuration space limit to 4096 byte allowing access to PCIe extended configuration space |
Beta Was this translation helpful? Give feedback.
-
|
finally I succeeded. I used your patches.txt file. The one contained in the file you sent me. However, it is impossible to make the RAM work faster. see photos. |
Beta Was this translation helpful? Give feedback.
-
|
@franckythebest did you read common issues and fixes wiki page these issues are caused by using UEFITool and/or UEFIPatch directly on the BIOS image. And some have even reported unusually high voltages on X79 when this happens. You need to do it the proper way using MMTool (read the wiki page if u need help with it) |
Beta Was this translation helpful? Give feedback.
-
|
hmmm ... I was just recording a guide based on Rampage 4 extreme and I stumbled across a difficulty. |
Beta Was this translation helpful? Give feedback.
-
|
With the holidays, I didn't have time to worry about this problem. Indeed, I integrated "amiboardinfo.uefi" with uefitool and not mmtool. I will check that tomorrow. |
Beta Was this translation helpful? Give feedback.
-
|
hello xcurio. I noticed that in your comment of November 21, you recommended the modification of these lines QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, . which I didn't do. Do you think it should also be modified and explained to me the reason? THANKS. |
Beta Was this translation helpful? Give feedback.
-
|
Just follow the guide... |
Beta Was this translation helpful? Give feedback.
-
What I mean is to make the "Above 4G" option appear in BIOS interface. |
Beta Was this translation helpful? Give feedback.
-
It won't work with any display options (user/etc). |
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.
-
|
@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.
-
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