It is my daily driver but I primarily use Windows 11 (for my job).
The root cause is a pretty critical systemd/linux kernel oversight that has always existed. Its a race condition. Linux kernel passes off control to the init system (systemd) before all the drivers have initialized. That part is normal. Hardware is so fast now that systemd ends up finishing all pre-GUI services and starts sddm (I use KDE Plasma) before the amdgpu kernel driver has finished initializing. This results in a black screen the lasts forever as sddm doesnāt see the amdgpu driver available to start on. This wonāt happen on GDM as it waits for the display drivers to finish initializing before attempting to start. More detail at the bug report Bug #2063143 āFrequent boot to black displayā : Bugs : Linux and the other bug reports linked there.
This issue can occur on any device and I also experience the same issue on my HP Spectre x360 (Intel i7-6500U). For whatever reason the issue became exacerbated in ubuntuās linux kernel 6.8.
Correct! Thermal protection is effectively completely unaffected by the kernel version.
I doubt itās critical enough be to backported, although it is technically a regression so maybe, but I feel like it wouldāve happened already if it was.
Iām experiencing this same problemā¦ itās really concerning. Fedora 40, happens with both KDE and GNOME. It happens after a few hours of usage usually.
Concerningly, nothing weird gets logged to journald. Also, at some point, I had a swapfile, and in one of these freezes I got to a TTY and it read Read-error on swap-device. Considering the abstence of journald logs, this swap error and the fact that it would seem as I lost a few minutes of stuff on the next boot, it would seem that thereās an issue with the SSD. Iāll roll back to 3.03 and report back (otherwise, feel free to ping me.)
I also didnāt see anything in the logs. Iām scared to try again, so Iāll probably stay on 3.03 for the time being since thereās no compelling reason to upgrade - 3.03 works just fine.
For me was the same, laptop shut down and stayed on black screen. I did not dare to reboot it for more than -10h. After reading your comment, I pressed the power button for quite a long time to reboot it. It was error 2 decompress failed as well.
I probably will read more comments here before I decide whether to upgrade to BIOS 3.05.
well, iāve just had it happen again in 3.03. Iāve tried disabling the NVMe/PCIe sleep setting in the BIOS, but it still happens. Iāve managed to get a picture of the error by having a terminal open with dmesg -w, and running the amd_s2idle.py script.
nvme 0000:02:00.0: Unable to change power state from D3cold to D0, device inaccessible
I can consistently reproduce it. At this point, I donāt know what to do, because it makes the laptop pretty unusableā¦ should I try Windows?
With the last of my college exams finished, I did the bios reset today by accessing the mainboard switch, as instructed.
However, now the system aways requires the boot password at boot, not just when trying to access bios. This is new behavior and I now canāt use the system at all.
I tried the old password and some basic ones in case there was a default. I also redid the reset a few more times, but no change
As a workaround, you could try echo 0 > /sys/bus/pci/devices/0000\:02\:00.0/d3cold_allowed from a root shell, which should temporarily disable the SSD sleeping, but Iām not sure how that will interact with sleep.
What SSD are you using, are you able to upgrade itās firmware too?
UPDATE: After further review of the support pages and in spending more time on searching for similar issues in other threads, I was able to try again today and finally succeed in doing the reset.
Instructions followed (Specific to FW13 AMD and a few edits Iāve starred.):
Plug in the system to AC. *
Remove the Input Cover.
Press the chassis open switch in the center [top] of the Mainboard 10 times, you must press it slowly, so press for 2 seconds. Release, wait for the red blink on the Mainboard LEDs *. repeat.
Yesterday I experienced a strange issue. Under heavy load, the CPU went up to about 97 degrees (Celsius) but fan did not turn on. Shut down the laptop completely, turned it back on, and fans immediately kicked on to full speed (even during the EFI POST).
FW Version: 0.3.5
I donāt think that it matters, as fans should be controlled by the EC, but:
Ubuntu 24.04
kernel 6.8.0-31-generic
If you couldnāt reset the bios password when you forget it or donāt know what you set, then how would you ever use your laptop again? There has to be a way to reset it or it would create even more e-waste - throwing the whole laptop away and replacing it.
Iāve been having a similar issue since 3.03. Sometimes apps will just crash, the DE will start showing visual bugs, and shutting down will result in an error, making me have to hard reset. Sometimes everything freezes. I think the filesystem is going into read only, hence why no logs are showing up. I reported this a while ago [RESPONDED] SSD Does not Wake up After Suspend - AMD. But I never figured it out. I have been running dmesg constantly in hopes of seeing any logs when it occurs.