-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hang on reboot #35
Comments
It is possible the NVIDIA App behaves like the NVIDIA Control Panel, and always shows ReBAR disabled for Turing GPUs. Because ReBAR is officially supported only on Ampere (RTX 3000) and later GPUs. @xCuri0 do you know why the firmware would hang on reboot ? Is there a restart notification I can hook, and then de-configure GPU ReBAR at that time ? Is there another script like the S3 Resume one ? |
Thanks for the quick answer :) Regarding that reboot thing, @vigilant-hylian had the same:
But in my case I had only one entry in the UEFI file. |
@vigilant-hylian Did you try to add the NvStrapsReBar driver only once to the firmware image ? Can you try the new version v0.3 (which fixes sleep) and say if you still have the resume from sleep issue ? Do you have anything new about the reboot issue ? Are you stil dealing with it ? |
I haven't tried the new version, no! I should at some point. Will update
the thread if/when I do because I do still have this issue. No change.
…On Mon, 11 Mar 2024 at 11:43 PM, Timothy Madden ***@***.***> wrote:
@vigilant-hylian <https://github.com/vigilant-hylian> Did you try to add
the NvStrapsReBar driver only once to the firmware image ?
Can you try the new version v0.3 (which fixes sleep) and say if you still
have the resume from sleep issue ?
Do you have anything new about the reboot issue ? Are you stil dealing
with it ?
—
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2MJ4X5OSZBOIBXINFAOITYXWRFXAVCNFSM6AAAAABEQG3PLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGM2TINJRGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@terminatorul i dont think this relates to issues with the dxe driver. it's probably some corruption caused by UEFITool causing this, i think even rebaruefi does it on some AM4 systems |
@TheUntouchable can you try to modifiy the UEFI image using mmotool instead of UEFITool, and check if you still have the reboot problem ? Be sure to start from the original UEFI image file (from MSI) |
you should use MMTool V5 on recent motherboards like this btw, using MMTOOL V4 might cause issues |
I just flashed the image I created with the "MMTool Aptio 5.02.0024 Mod" and it is exactly the same behaivour. I also reset all settings and tried it without any changes, same thing. Previously I disabled BAR via "NvStrapsReBar.exe". |
Update: I just realized that the CPU error LED on my motherboard is lit while my PC is freezing up |
No, NvStrapsReBar does not modifiy the Setup variable. Can you flash the original version of UEFI the board had pre-installed ? Or some older version of the firmware ? |
Okay, I just had a really hard time 😄. Regarding your questions, I always flashed with M-Flash and a USB stick. My board can only hold one uefi version at the same time. |
Yes... I don't think it was my day... The PC is now running again, but the reboot problem is still there and the LED controller on my mainboard seems to be broken as well. |
So can you still flash an older version (with support for your CPU), then use MSI Live Update (instead of M-FLASH) to flash the latest version again ? |
I will try that out later :) |
Update: Ok, I installed an earlier version via M-FLASH without any problems. Nevertheless, the PC still freezes after/while a reboot with red CPU Led on. At least it seems that the LED controller is working again :) Unfortunately I can't flash the latest uefi version via Live Update as it has been marked as beta for 7 months :( EDIT: Ok, I just wanted to boot into the UEFI again to check some settings, and out of nowhere the reboot happend.. So it seems that this is fixed now again :D Will try to flash the latest UEFI now and see if its still working. |
Update: It seems that I got the UEFI and the LED Controlle fixed, everything is working like before I flashed the modified uefi version :) Question is now what happend.. |
At any point did you try to clear CMOS and then manually load default / optimized values ? |
My board has a dedicated button for that.. And I can't tell you how often I pressed it the last days :D Also I cleared the settings in the UEFI to default each time a did a flash. |
@TheUntouchable
The text was updated successfully, but these errors were encountered: