[SOLVED] SW kernel-5.10.37 breaks 5.10.x compatibility to date
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
SW kernel-5.10.37 breaks 5.10.x compatibility to date
SW kernel 5.10.37 installed identically as 5.10.1-36 versions (kernel-generic + kernel-modules + initrd) exhibits many woes compared to all priors. Boot time to console prompt is minutes versus earlier 10s of seconds. Boot messages have long pauses. Sys does eventually give a prompt. Reboot / halt fails with kvm notes; needs hard reset. Behavior same on 2 different machines.
On screen boot messages show problems with TPM & udevd.
Revert to 5.10.36 or earlier & all functions well. No problem with 5.12.x either.
I'm seeing the same(?) problem -- using kernel-huge with no initrd. Haven't had any problems in ages. 5.10.36 and earlier worked great. I upgraded to 5.10.37, and my laptop refused to boot (or maybe it was just *really* slow, dunno). Downgraded to 5.10.36 and all is well.
This is on a ThinkPad X1C8. I'll be happy to provide more info it it would be helpful.
My laptop (Lenovo T460 with Intel GPU) and my desktop (Nvidia GeForce GTX 1050 Ti with the binary blob driver) both run Slackware64-current up-to-date with the 5.10.37 kernel and I don't experience any issue at all.
Both running the generic kernel (as is advised for daily use) with an initrd. The laptop is a UEFI model and there I use elilo as the bootloader; the desktop is BIOS based and it uses good old lilo.
For the desktop I generate my initrd as follows:
Code:
KERNELVERSION=5.10.37 ; /usr/share/mkinitrd/mkinitrd_command_generator.sh -r -k $KERNELVERSION -a "-o /boot/initrd_$KERNELVERSION.gz" |bash
For my laptop, I also add LVM and LUKS to the mix but that should not make a difference; I also use 'mkinitrd_command_generator.sh' there.
I'm seeing the same(?) problem -- using kernel-huge with no initrd. Haven't had any problems in ages. 5.10.36 and earlier worked great. I upgraded to 5.10.37, and my laptop refused to boot (or maybe it was just *really* slow, dunno). Downgraded to 5.10.36 and all is well.
This is on a ThinkPad X1C8. I'll be happy to provide more info it it would be helpful.
I had a problem with 5.10.37 as well. My computer would just stop after the log in. The screen font also goes back to the bigger font as well. I had plenty of errors but they came by so fast I don't know what they were.
I did a complete re-install with a -current.iso which still had the 5.10.36 kernel and everything is working. I've been updating my kernel with slackpkg for quite some time. I know many don't recommend this.
My question for you is - how did you downgrade the kernel to 5.10.36? This would be a much better than a complete reinstall. I'm running the huge kernel.
Thanks.
Last edited by NakedRider; 05-19-2021 at 11:25 AM.
Does your system use original rc.d scripts (sysvinit-scripts) or modified ones in lxc?
Using huge or generic kernel?
If you build initrd, could you post the mkinitrd command line args (especially modules to load) in build?
Thnx.
generic kernel,
mkinitrd -c -k $KVER -m ext4:nvme -f ext4 (+ LUKS stuff)
original rc.d scripts.
The only relevant difference is that I use rEFInd boot manager, chain loading the EFI stub loader of the Linux kernel.
My laptop (Lenovo T460 with Intel GPU) and my desktop (Nvidia GeForce GTX 1050 Ti with the binary blob driver) both run Slackware64-current up-to-date with the 5.10.37 kernel and I don't experience any issue at all.
Both running the generic kernel (as is advised for daily use) with an initrd. The laptop is a UEFI model and there I use elilo as the bootloader; the desktop is BIOS based and it uses good old lilo. For the desktop I generate my initrd as follows:
Code:
KERNELVERSION=5.10.37 ; /usr/share/mkinitrd/mkinitrd_command_generator.sh -r -k $KERNELVERSION -a "-o /boot/initrd_$KERNELVERSION.gz" |bash
For my laptop, I also add LVM and LUKS to the mix but that should not make a difference; I also use 'mkinitrd_command_generator.sh' there.
kernel-huge 5.10.37 will rapidly boot my Lenovo P15v with both elilo & grub! (But, I never use 'huge'.) It must be a an initrd problem & one which I have not encountered in decades of use. I used your suggested mkinitrd_command_generator.sh; it boots as a snail moves. I then added a lot of extras to the module list: ehci-hcd:ehci-pci:ext4:fat:hid:hid-generic:hid-lenovo:hid-multitouch:i2c-core:i2c-hid:irqbypass:jbd2:kvm:kvm-intel:mbcachehci-hcdhci-pci:thinkpad-acpi:tpm:uhci-hcd:uhci-pci:xhci-hcd:xhci-pci:xhci-plat-hcd:uas:usbhid:usb-storage:vfat
No improvement at all. During boot, there is a long pause as it looks for the TrackPoint & an even longer wait as udevdadm trigger searches. And it will not reboot!
This is all paradoxical. Identical slow behavior on my Lenovo X390. My initrd.gz's are never a problem. All the earlier 5.10.x (1<x<37) kernel-generic are perfect. So are the early 5.12.x versions.
I had a problem with 5.10.37 as well. My computer would just stop after the log in. The screen font also goes back to the bigger font as well. I had plenty of errors but they came by so fast I don't know what they were.
I did a complete re-install with a -current.iso which still had the 5.10.36 kernel and everything is working. I've been updating my kernel with slackpkg for quite some time. I know many don't recommend this.
My question for you is - how did you downgrade the kernel to 5.10.36? This would be a much better than a complete reinstall. I'm running the huge kernel.
Thanks.
No need to re-install, just download the kernel that worked for you and run upgradepkg
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
hci-hcd
