You are not logged in.
Pages: 1
I have arch installed on an external SSD (I dual boot with windows), and for now everything seems to be working fine except for when I shutdown arch.
There are no errors, it appears to exit everything and shutdown successfully except that the PC itself does not shut down, the screen remains on and blank, until I manually power off.
I would not mind powering it off manually, the problem is that when I do so, it doesn't turn off, instead it reboots back into arch and I have to login and shut it down again.
Shutting it down the second time seems to always work.
I have read that turning off 'fast boot' in windows is supposed to help, so I have done this, but unfortunately I get the same result.
Would appreciate some help. Thanks.
Offline
read that turning off 'fast boot' in windows is supposed to helpMandatory
Then reboot windows and linux twice or thrice for voodo reasons (to "unconfuse" the BIOS)
Does the system properly shut down/power off from the multi-user.target (2nd link below)?
Does it from a live distro like eg. grml?
Offline
Issues like these are often UEFI related, do you have a relevant firmware update available?
Offline
What are your specs? The issue hasn't happened for me since a few kernel patches ago but a lot of people with AMD 7 series GPUs were reporting this very issue when shutting down. Basically you'd get a black screen and your PC wouldn't actually power off without you pressing the power button.
Ryzen 7 9850X3D | AMD 7800XT | KDE Plasma
Offline
read that turning off 'fast boot' in windows is supposed to helpMandatory
Then reboot windows and linux twice or thrice for voodo reasons (to "unconfuse" the BIOS)
Does the system properly shut down/power off from the multi-user.target (2nd link below)?
Does it from a live distro like eg. grml?
I will experiment with these and get back to you.
Issues like these are often UEFI related, do you have a relevant firmware update available?
I'm not sure, how do I check this with arch? Also: I don't use UEFI to boot, its MBR, not sure if that makes a difference?
What are your specs? The issue hasn't happened for me since a few kernel patches ago but a lot of people with AMD 7 series GPUs were reporting this very issue when shutting down. Basically you'd get a black screen and your PC wouldn't actually power off without you pressing the power button.
Not AMD, it's Geforce GTX.
These are my specs:
https://www.notebookcheck.net/Asus-G752 … 140.0.html
Thanks everyone for the help
Last edited by mrconfused (2024-03-08 09:17:50)
Offline
There's an ongoing issue w/ nvidia 550xx (and possibly a numa bug), https://bbs.archlinux.org/viewtopic.php?id=293543
Offline
Does the system properly shut down/power off from the multi-user.target (2nd link below)?
Does it from a live distro like eg. grml?
Yes to both. (BUT see below)
There's an ongoing issue w/ nvidia 550xx (and possibly a numa bug), https://bbs.archlinux.org/viewtopic.php?id=293543
Ok this seems most like what kind of problem I have been having. Like this person, my arch will shutdown normally if the system has only been running for a short while (Which is probably why the above two tests worked ok).
I have read the quoted threads, but I am still a bit confused. As far as I can tell, I dont have nvidia drivers installed.
Using lspci to check my GPU, it says my kernel driver in use is "nouveau." If I search for nvidia packages with 'pacman -Qs nvidia' nothing is returned.
Am I doing something wrong? If I am wrong and I do have nvidia drivers installed, should I then downgrade? Unlike the person in the above thread, I plan on using my GPU, so I don't want to just uninstall everything.
What should I try/do next?
Offline
"lspci -k", nouveau and nvidia will both show up but only nvidia is in use (iff you're using that)
But my comment was pure speculation based on nothing more than
Not AMD, it's Geforce GTX.
and that bug being around.
If you're using nouveau, it might however be a good idea to test the nvidia driver to begin with, the nouveau driver is on frequent record for stalling the PCI.
If that doesn't help, please post your complete system journal for the boot:
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.stafter the accidental reboot.
Offline
Pages: 1