Got the dreaded /dev/sda1 clean message with no more screen output (black with only that text) and nothing on the secondary display port (VGA) on an AMD Radeon 540. This is on the Manjaro manjaro-kde-21.0.7-210614-linux510.iso build following a reboot after a system update on a fresh install. This appeared to be on a 5.10 kernel. I was able to ssh into the system, but it wouldn’t even reboot after I issued a sudo reboot. I had to hold the power in to kill it.
Postfixing amdgpu.dc=0 to the line GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (as per this) did not help.
After I installed the 5.4 LTS kernel (mhwd-kernel -i linux54 ) the system seemed to become textually responsive, but KDE and its KDM wouldn’t start up. startx resulted in errors. It didn’t seem that anything I did could get GUI to come back up and I had to basically boot with 3 postfixed to the GRUB command line to get into non-graphical mode.
After this insanity I did a reinstall with manjaro-kde-21.0.7-minimal-210614-linux54.iso which has the 5.4 LTS kernel by default and it seems to be functional even between updates and reboots.
After all of this I started noticing some odd behavior. The screen turned black at one point and I had to wait a few minutes and flip between the inputs of my monitor to which this and a couple other systems are attached. It finally came back and sshd remained active.
At one other point with a seemingly “stable” system the system hung again graphically. The time remained fixed over night for about 12 hours, but sshd was still active and so the kernel clearly did not hang, but the GPU driver apparently did.
Any thoughts on A) what’s going on with the 5.10 kernel series with this issue and B) anything I can do to track down the bug that could be causing the GPU/driver/module hang or is this a known issue?
I’m pretty leery right now since this is the second time within a year that I’ve been bitten hard by the “black screen” (device clean) symptom.
I do think Manjaro should consider making it easier to get a verbose boot + non-graphical access/control via GRUB. Perhaps an entry that makes debugging simpler vs having to modify the boot commands? Would make sense to have that living there beside Memtest86+…
Change quiet to text in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
Please read this: How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
And thanks for the tips re: REISUB, sadly this did not help in this situation at the time. I surely wish ctrl-alt-f* worked as well. I will keep it in mind thought for a future situation… that hopefully doesn’t strike.
Thanks, I had assumed that this was a known issue, but seemingly hard to find a core discussion about it to understand when/if it’s fixed.
I guess the big thing that SCARES THE CRAP OUTTA ME is that if I shift gears to a stable 5.10 kernel that supposedly fixes it, but doesn’t, then I’m going to perhaps end up with that issue where X doesn’t start again even after moving back to 5.4… It took a reinstall for that to resolve so yeah… very fearful to have that hit me without a strategy in place beforehand.