The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request. Rene
On Wed, 26 May 2021 at 16:13, René Harder Olsen rehol4@gmail.com wrote:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request.
Can you login on the text console? 5.12.6 "works for me" on an elderly desktop with an old nVidia graphics card running under nouveau.
As soon I come to the login screen where the blue square is then screen freeze up under kernel .5.12.6 & 5.12.5 where as everything is working as expected under kernel 5.11.21 and both kde and Gnome René
ons, 26 05 2021 kl. 16:46 -0300, skrev George N. White III:
On Wed, 26 May 2021 at 16:13, René Harder Olsen rehol4@gmail.com wrote:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request.
Can you login on the text console? 5.12.6 "works for me" on an elderly desktop with an old nVidia graphics card running under nouveau.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Wed, 26 May 2021 at 17:30, René Harder Olsen rehol4@gmail.com wrote:
As soon I come to the login screen where the blue square is then screen freeze up under kernel .5.12.6 & 5.12.5 where as everything is working as expected under kernel 5.11.21 and both kde and Gnome
I've encountered bugs that broke video or network drivers. Invariably others had reported the bugs by the time I looked them up. I had to stick with an older kernel until a fix was available. With buggy video drivers the text console is usually still available to view dmesg for errors.
I also encountered errors with network drivers on the new kernels. I was using this [rtl88x2bu](https://github.com/cilynx/rtl88x2bu) which broke after the update. I eventually got [this one](https://github.com/RinCat/RTL88x2BU-Linux-Driver) to work, but it threw me for a loop for a while.
I've encountered bugs that broke video or network drivers. Invariably others had reported the bugs by the time I looked them up. I had to stick with an older kernel until a fix was available. With buggy video drivers the text console is usually still available to view dmesg for errors. --
George N. White III
-- Trevor McKay
On 26/05/2021 13:12, René Harder Olsen wrote:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request. Rene
Just a comment
No video issues here but issues with USB3 external drives taking minutes to mount. 3 different drives. Get error messages with dmesg that don't show up with the older kernel on this computer.
I spent over an hour to test hardware to ensure that it was good.
This was after an update very late last night.
More testing needed on my part.
Robin
Hello. Here is the system info: Operating System: Fedora 34 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.21-300.fc34.x86_64 OS Type: 64-bit Graphics Platform: Wayland Processors: 2 × Intel® Core™2 Duo CPU P8700 @ 2.53GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Mobile Intel® GM45 Express Chipset
It is running a Lenovo T400 René
ons, 26 05 2021 kl. 14:19 -0700, skrev Samuel Sieb:
On 2021-05-26 1:30 p.m., René Harder Olsen wrote:
As soon I come to the login screen where the blue square is then screen freeze up under kernel .5.12.6 & 5.12.5 where as everything is working as expected under kernel 5.11.21 and both kde and Gnome
What is your video card? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Wed, 26 May 2021 21:12:56 +0200 René Harder Olsen rehol4@gmail.com kirjoitti:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request. Rene
Tested two laptops, both quite old, Lenovo t61 and Toshiba Satelite, both stopped working when updated into 5.12.6. 5.11.21 works fine, anyway...
Jarmo
On 27/05/2021 12:12, jarmo wrote:
Wed, 26 May 2021 21:12:56 +0200 René Harder Olsen rehol4@gmail.com kirjoitti:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request. Rene
Tested two laptops, both quite old, Lenovo t61 and Toshiba Satelite, both stopped working when updated into 5.12.6. 5.11.21 works fine, anyway...
FWIW, I've an Acer Aspire 5920 purchased sometime in 2007 or 2008.
[egreshko@acer ~]$ uname -r 5.12.6-300.fc34.x86_64
Working just fine.
On 2021-05-26 9:12 p.m., jarmo wrote:
Wed, 26 May 2021 21:12:56 +0200 René Harder Olsen rehol4@gmail.com kirjoitti:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request. Rene
Tested two laptops, both quite old, Lenovo t61 and Toshiba Satelite, both stopped working when updated into 5.12.6. 5.11.21 works fine, anyway...
I have a Lenovo Thinkpad T510 from around 2010. It has different Intel graphics and it works fine with that kernel.
On 2021-05-26 12:12 p.m., René Harder Olsen wrote:
The new kernel begin with version 5.12.5 and 5.12.6 refuses to continue after login request.
Does the mouse move? Are you able to switch to a text console (CTRL-ALT-F3)? If you can, then try logging in and check the log. Otherwise, after trying the new kernel, then boot into an older kernel and run "sudo journalctl -b -1" and see if there's anything useful in the log.
Wed, 26 May 2021 21:57:30 -0700 Samuel Sieb samuel@sieb.net kirjoitti:
Does the mouse move? Are you able to switch to a text console (CTRL-ALT-F3)?
Mine freezes totally, nothing than hard boot works... But, 5.11.21 works.. And it's both F33 and F34. My desktop i7 and intel craphics works ok with 5.12.6 F34...
Jarmo
On 5/26/21 10:14 PM, jarmo wrote:
Wed, 26 May 2021 21:57:30 -0700 Samuel Sieb samuel@sieb.net kirjoitti:
Does the mouse move? Are you able to switch to a text console (CTRL-ALT-F3)?
Mine freezes totally, nothing than hard boot works... But, 5.11.21 works.. And it's both F33 and F34. My desktop i7 and intel craphics works ok with 5.12.6 F34...
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.
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...
Jarmo
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
Hoi Rene,
I'm also running into "hard freezes", although somewhat later. Can't figure out the cause, made a ticket though: https://bugzilla.redhat.com/show_bug.cgi?id=1965809 At one point I saw a crash message related to nvme scrolling over my console, but wasn't able to capture it completely. Ik could scroll the console output up and down with my keyboard, but details were "scrolled out".
My system is based on an Asus PRIME B250M-A motherboard, with an Intel i5-7400 CPU CPU and 16GB RAM. Other details:
[root@home07 ~]# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0) 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) 00:1c.7 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #8 (rev f0) 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (B250) 00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio 00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) [root@home07 ~]#
Rolf
-
Ed Greshko -
George N. White III -
jarmo -
René Harder Olsen -
Robin Laing -
Rolf Fokkens -
Samuel Sieb -
Trevor McKay