get boot loops after changing bar size #13
Replies: 26 comments 19 replies
-
|
Comparing with other screenshots, the root port looks normal. On my AMD motherboards it shows "PCIe GPP Bridge", don't know what it means. And your screenshot shows "Device Class: PCI-to-PCI Bridge" for the root port. Your LocalPciGpu.h header file looks fine. I can't tell what's wrong to cause the boot loop. What values did you use in NvStrapsReBar ? Can you show a screenshot (before the first reboot) ? Can you try latest version from the bleed branch ? |
Beta Was this translation helpful? Give feedback.
-
|
I tried down to 1GB Bar size, but same boot loop until I clear cmos and reset the driver. Going to try the bleed branch now. |
Beta Was this translation helpful? Give feedback.
-
|
still getting the hang during post after first reboot "no video" with bleed |
Beta Was this translation helpful? Give feedback.
-
|
Can you make an USB stick with a Linux installer, for example Fedora or openSUSE ? You don't have to install it, only use the USB drive to start Linux, and then show the output of Or can you still boot Windows in safe mode ? That way you can just show the output from |
Beta Was this translation helpful? Give feedback.
-
|
boots and runs fine until a set a bar size.. I'm typing on it right now. booting to linux to get the info now. BTW thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
|
got em |
Beta Was this translation helpful? Give feedback.
-
|
There should be more then one EFI variable starting with NvStraps. Did you collect the .dmp after you enabled ReBAR with When you get the boot loop again, you can recover the system if you manually set back the current year in UEFI Setup to a value before 2023, and reboot. You can change back the year to the correct value after the reboot.
After you enable ReBAR (with NvStrapsReBar.exe) and trigger the boot loop in Windows, you should see both Also you should try the latest version from the github repository, it no longer uses hard-coded values in LocalPciGpu.h header. |
Beta Was this translation helpful? Give feedback.
-
|
Also, maybe your Xeon is for productivity or office use and you have the NVIDIA Studio drivers instead of GameReady drivers ? Can you check ? |
Beta Was this translation helpful? Give feedback.
-
|
when I said boot loop what I really meant is just a constant POST reset without video.. no OS load at all. Sorry, bad terminology. Normally video initializes right after POST code 98 on the boards diag display.. after enabling/sizing the BAR it reaches 98 then immediately jumps to 9C then 87 and hangs now.. if I power cycle it then just starts the POST loop. And no, no office or pro work with this machine so its using standard gameready driver.. was built 4 years ago to be the cheaper threadripper alternative |
Beta Was this translation helpful? Give feedback.
-
|
Oh, man, you have a dual-CPU server motherboard ... should have led with that. This hardware is ... intimidating to me. I do have an old Threadripper, but only because AMD marketed 1st gen Threadripper as a gaming computer (for lack of a better HEDT). I think somehow I get the PCI bus or domain wrong, for such a system. Can you check what the boot CPU is ... and what PCI slot leads to what CPU ... ? Maybe just switch the GPU to a slot belonging to the other CPU ? @xCuri0 can you help please: how do I make sure I am using the right PCI bus from the right CPU, on a dual-CPU server motherboard (Asus Z10PE-D8) ? Output from @Black6spdZ can you attach again the output from |
Beta Was this translation helpful? Give feedback.
-
|
Can you check what slot you GPU is in ? Maybe you need to switch it from CPU2 to CPU1
|
Beta Was this translation helpful? Give feedback.
-
|
it's in slot 1 for sure system sidenote, I almost decided to go with the Ryzen 3950x but could see the writing on the wall, AM4 was long in the tooth and physically just too small to have the PCIe and MEM I/O as the older HEDT Xeons at the time.. besides the turbo-boost unlock was just icing on the cake |
Beta Was this translation helpful? Give feedback.
-
|
PCI bus looks fine. This motherboard does not have ReBAR, and your PCI BAR size in the screenshot is set to 0 (System Default) Did you set PCI BAR size for the GPU in |
Beta Was this translation helpful? Give feedback.
-
|
yes, but once I set them system no longer POSTS or boots.. so I can't get anything meaningful.. should I try something very small? 256MB? |
Beta Was this translation helpful? Give feedback.
-
|
someone with the same board also can't use ReBarUEFI xCuri0#26 @terminatorul seems like there's nothing wrong with your module kinda weird a server board has trouble with large BAR tho because usually they are paired with GPUs that require it like Nvidia Tesla / RTX A-series. maybe it's just a wrong bios setting |
Beta Was this translation helpful? Give feedback.
-
|
so, maybe new version is going somewhere.. I flashed it and it looks like everything was detected properly and set the recommended BAR size "8gb" in this case for my 2080S with 8gb and rebooted with fingers crossed.. it POSTS and booted fine! BUT it looks like it's not enabled? I do see a new file from the linux efi firmware folder though so maybe it's just a windows / driver issue? |
Beta Was this translation helpful? Give feedback.
-
|
Also add screenshot with the status code in NvStrapsReBar.exe |
Beta Was this translation helpful? Give feedback.
-
|
you got it |
Beta Was this translation helpful? Give feedback.
-
|
does this mean anything to you? some hidden options in bios hardcoded to certain values regarding MMIO |
Beta Was this translation helpful? Give feedback.
-
|
look what I found hidden away |
Beta Was this translation helpful? Give feedback.
-
|
The status code from the driver is good. But the motherboard does not enable ReBAR out of the box, even if GPU advertises ReBAR support on the PCI bus. Can you find the right port in your screenshot here for the GPU in slot 1 (CPU 1) ? Do you see the same settings when you enter UEFI setup ? Looks like they allow you to manually set the BAR size for each PCI device ! But it might be for integrated devices only (from the chipset) |
Beta Was this translation helpful? Give feedback.
-
|
so I had to move my GPU to get it into that Port3A "PCIe Slot 3 on mobo" because only that port and socket 2 port 3A "slot 7" have those BAR size adjustments.. who would have known, not documented anywhere and had to spend hours digging through bios to find and unhide it. I haven't made any bios adjustments yet but just swapping slots I still get same problem, system boots but no bar size change.. nvstrapsrebar shows: UEFI DXE driver status: GPU-side ReBAR Configured with PCI confirm (0x0300000000000064) |
Beta Was this translation helpful? Give feedback.
-
|
I was hoping you can find a BAR1 size or BAR12 size option... What are NTB BARs, can you show the Control Help String at the buttom ? |
Beta Was this translation helpful? Give feedback.
-
|
@Black6spdZ sounds like you're still using the old bridge config which won't work in the new slot |
Beta Was this translation helpful? Give feedback.
-
|
yeah, that gave me a hang until I cleared CMOS.. was strange that it initially booted to windows fine.. I did what I thought was clearing the old config and resetting the bar size again, rebooted and it hung. gave it a CMOS clear and it was fine but back to it's old ways, BAR is stuck at 256MB |
Beta Was this translation helpful? Give feedback.
-
|
NTB is a mechanism for direct PCIe networking between servers! https://www.dolphinics.com/products/pcie_Intel_NTB_networking.html |
Beta Was this translation helpful? Give feedback.
-
|
Non-Transparent Bridge. I've tried everything there: disable NTB bridge bars, enable/disable split bars, changed the sizes.. no change. Still in the same boat :( maybe it just wasn't meant to be. I'm not sure what else I can do |
Beta Was this translation helpful? Give feedback.
-
|
what about a UEFI based driver? would that load after system initialization? |
Beta Was this translation helpful? Give feedback.
-
|
Amazingly, I don't know what a UEFI based driver is (other then the DXE driver in NvStrapsReBar, but it looks like you want something different) |
Beta Was this translation helpful? Give feedback.
-
|
Also maybe there is a support forum for this, or other forum like win-raid... |
Beta Was this translation helpful? Give feedback.
-
|
yep, an efi file is included with your compile. going to do this: Use EFI Shellx64 or other suitable UEFI shell to set automatic load (and execution) of NvStrapsReBar.efi during system boot. Use cmd ' bcfg driver add 0 fs1:\EFI\Boot\NvStrapsReBar.efi "NvStrapsReBar" ' where 'fs1:\EFI\Boot\NvStrapsReBar.efi' is path to DXE driver file on UEFI boot partition |
Beta Was this translation helpful? Give feedback.
-
|
does it matter where it gets placed in the bios? |
Beta Was this translation helpful? Give feedback.
-
|
removed the bios ffs driver, then used the UEFI shell to copy over and add efi the driver.. it appears it worked.. at least no freezes or bsod's but still stuck with 256MB BAR but did get a different diag code in nvstrapsrebar.exe UEFI DXE driver status: Configured (0x0000000000000014) if this method works it would be a safer way for others to load the patch without flashing bios |
Beta Was this translation helpful? Give feedback.
-
|
@Black6spdZ that method of bcfg does not work with NvStrapsRebar or ReBarUEFI Because the module has to be loaded before PCI enumeration. In this case it's running after because the firmware needs all that stuff initialized in order for it to load a module from storage. |
Beta Was this translation helpful? Give feedback.
-
|
oh.. well damn, wishful thinking on my part |
Beta Was this translation helpful? Give feedback.
-
|
would doing a boot with my asus q-code logger offer any useful information? |
Beta Was this translation helpful? Give feedback.
-
|
I'm confused with HWInfo's output here |
Beta Was this translation helpful? Give feedback.
-
|
would this switch cause issues?? |
Beta Was this translation helpful? Give feedback.
-
|
That affects PCIe lanes, not BAR1 size. Your device manager pic before shows BAR1 in 32-bit space, with above 4G decoding it should be above 4G unless a 4G display patch is in place. What is Load RT32 Image ? Would you try disabling it in BIOS setup and see if BAR1 address moves. Do it without setting Rebar first, ie 256MB BAR's. |
Beta Was this translation helpful? Give feedback.
-
disabled "Load RT32 Image".. I'm not seeing any change at all. what do you mean by 4G display patch?
|
Beta Was this translation helpful? Give feedback.
-
|
I guess some display adapters / OS don't play well above 4G so an option is available to use them with 64-bit addressing but below 4GiB. Example on my X99 with 2696 v3 With 4G and patch enabled And with patched disabled addressing for 64-bit BAR1 and BAR2 are moved to 1TiB address range while 32-bit BAR0 remains below 4GiB Your device manager pic is not clear as it appears to show multiple entries. There can be old records but usually these are a lighter shade but yours look the same? Maybe need to DDU (Display Driver Uninstaller) and start again without Rebar and get above 4G working with your single RTX card? |
Beta Was this translation helpful? Give feedback.
-
|
I don't have that "above 4G decoding patch" option.. searched bios with UEFITool |
Beta Was this translation helpful? Give feedback.
-
|
rebar 4Gb => boot, but no bios display until windows seems I am late to this party xCuri0#4 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
eyelids are getting heavy.. if anyone wants to doublecheck my searching.. maybe I've overlooked something. I can't even find what that "patch" does, but it plagues many boards that don't have it as well from the searches |
Beta Was this translation helpful? Give feedback.
-
I did everything according to instructions, everything compiled OK but if I set any size for BAR I get a boot-loop. One thing with my system is I don't have a PCI-to-PCI bridge on the same bus as the GPU, just a CPU root port?
Motherboard: Asus Z10PE-D8
CPUs: Xeon E5-2696v3
GPU: 2080 Super FTW3
LocalPciGPU.h.txt
MONOLITH.txt
Beta Was this translation helpful? Give feedback.
All reactions