On 27/05/2021 14:50, jarmo wrote:
Wed, 26 May 2021 22:44:49 -0700 Samuel Sieb samuel@sieb.net kirjoitti:
It works ok? Then which kernel doesn't work? Does pressing the power button go to suspend? (Just a click, not holding it to power off.) So the same thing for you. After booting the not-working kernel, boot a working one and run "sudo journalctl -b -1" and see if there's anything at the end of the log that is relevant.
In my desktop ALL works fine, but those tested 2 laptops didn't. Removed allready (yesterday) after malfunctions, 5.12.6 kernels, so can't test them. At the moment, time limited to test...
Well, you could do "journalctl --list-boots" and then find which once most recently would correspond with failed episodes. Then use the number associated with those boots to exam the journal output to see if there is anything suspicious when compared with good boots.
The first few lines in the journal will tell you what kernel is being booted to.
For example....
[egreshko@meimei ~]$ journalctl -b -123 | more -- Journal begins at Sun 2020-12-27 18:33:37 CST, ends at Thu 2021-05-27 15:10:06 CST. -- Dec 27 18:35:30 meimei.greshko.com kernel: microcode: microcode updated early to r evision 0xa, date = 2018-05-08 Dec 27 18:35:30 meimei.greshko.com kernel: Linux version 5.9.15-200.fc33.x86_64 (m ockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 10.2.1 20201125 (Red Hat 10. 2.1-9), GNU ld version 2.35-15.fc33) #1 SMP Wed Dec 16 19:14:35 UTC 2020 Dec 27 18:35:30 meimei.greshko.com kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/v mlinuz-5.9.15-200.fc33.x86_64 root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 ro rd .driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nomodese t