Hello!
The machine is ASUS B1500C laptop, with Intel i5-1135G7, 16Gb RAM, Samsung 512 NVME SSD.
The system is freshly updated from 15.3 into 15.5., installed on USB SanDisk UltraFit 32Gb, UEFI, GRUB2, secure boot enabled. Prior to update system booted properly, but couldn’t detect NVME and audio device. The new kernel is 5.14.21-150500.55.19, DE is KDE with no tunes.
Boot hangs soon after taking the password to encrypted /home volume, and not responsible to any keys and combinations except power button hold. Still hangs with recovery mode or runlevel 3.
System boots into semi-working state using old kernel (5.3.18-150300.59.106) from GRUB boot menu: DE is broken (startKDE: could not start kdeinit5. Check your installation), TTY login succeseful.
Looking forward for you assistance, thanks in advance.
It seems you did not read the general rules for an successful upgrade:
Do not skip a release when upgrading! Example: do not upgrade from 15.1 to 15.4. Instead, from 15.1 upgrade to 15.2, then to 15.3, and only then from 15.3 upgrade to 15.4.
I have reinstalled root partition clearly, but it didn’t solve the problem, and now I can’t even boot into CLI with old kernel, because there aren’t any.
So I think the problem is not connected with ignoring the upgrade order. Maybe I can get some other suggestions?
There should be an advanced options menu in Grub containing rescue and/or failsafe boot selection(s). Did you try any of that? Those should result in boot messages that should spell out what happened last with clues to problems. Hitting ESC as soon as the Grub menu exits from the main selection also should give you messages. If you can’t read them due to tiny size you can append an option after striking the E key in the Grub menu, to the end of the linu line to specify a lower resolution screen mode that will result in larger framebuffer text, e.g.: video=1440x900 or video=1024x768 on a 1920x1080 or 1200 screen, or video=1920x1080 or video=2560x1440 on a 3840x2160 or 2400 screen.
Is this a hybrid graphics model? If yes, are NVidia’s proprietary drivers installed?
Are you able to boot 15.5 installation media sucessfully? If yes, are you able to use it to boot the installed system? If no, I would try to boot the media, chroot into the installed system, then install the OEM kernel 5.14.21-150500.53.2 to see if it will boot.
Will you please point me to instructions, how to do it correctly? Just before wiping root and reinstall I was trying to install KOTD, but it did bring me troubles with inproper filesystem, so I decided to reinstall. It will be better to read instruction first.
If it will help, I attach screenshot of messages, given prior to hang with recovery mode acpi=off option. In this case system is responsive to Ctrl+Alt+Del.
I wrote a Dracut in Chroot SDB 6 months ago, but can’t complete it myself due to lack of any experience with the default BTRFS filesystem. I don’t have any idea if anything needs to be different for those using it instead of EXT4. There may be no changes required. I just don’t know. Also, I have minimal experience with new Wiki page construction, which is an additional reason why you see strike-throughs instead of deletions there, besides not knowing what if any changes or additions are needed.
Once chroot is running, I would make the necessary adjustment previously explained to /etc/dracut.conf/ for adding nvme to initrd, then try rebuilding the installed 5.14.21-150500.55.19.1 initrd and try before assuming the further step of installing the older kernel is actually necessary.
Once you have a chroot running, installing an older kernel should be possible using SOP with zypper or YaST, but if that’s a problem, wget and rpm can do it:
I have successfully installed and booted kernel 5.14.21-150500.53-default thanks to your suggestion. And it normally detects nvme via lsblk.
I don’t know should I further research this bug or write to Bugzilla with current info?
5.14.21-150500.55.39.1 is current. 5.14.21-150500.53 is from May. Getting completely current by updating is highly recommended. The kernel changelog has 2,000+ entries since kernel-default-5.14.21-150500.53 release.
I think the time has come to report a bug. It may pay to first try the 15.6 6.4 kernel, or better a backport kernel. If that’s above your pay grade, report a bug, and consider to suggest you would try a newer kernel if instructed how.
If you’re game to try first, save this to /etc/zypp/repos.d/, do zypper ref && zypper in kernel-default-6.6.11 and reboot. Just be sure your 5.14.21-150500.53 is protected from disturbing or removal before you do.
S | Name | Type | Version | Arch | Repository
--+--------------------------------+------------+--------------------------+--------+---------------
v | kernel-default | package | 6.7.0-lp155.2.1.ge0612d9 | x86_64 | KernelStableBP
You waited too long to react. Either install 6.7.0 instead, or try the 15.6 kernel. If you copy your OSS repo file to another name, then change URL within it from $releasever to 15.6, you can install 15.6’s current 6.4 kernel with yast or zypper. If you go this latter path, disable or remove your extra repo before doing any other software updates or changes. Installing the 6.4 kernel may require one or more other packages automatically upgraded as well. You may consider also upgrading entirely to 15.6. 15.6 moves from alpha to beta in about 7 weeks. I have 9 installations of 15.6 so far, and will have several more long before its release in June.
Yes, unfortunately my daily job is not connected with Linux, so I can tinker only in spare time.
Installed, and it gets GRUB2 “bad shim signature”.
I have another USB-flash disk where I installed 15.6Alfa, and it successfully boots with 6.4.0-150600.4-default kernel (although very slow, because of bad RW speed of the disk).
Long story short, do not boot and hang:
5 .14.21-150500.55.19,
5.14.21-150500.55.39.1,
5.14.21-150500.13.27.2-rt.
Boot:
5.14.21-150500.53-default and 6.4.0-150600.4-default on 15.6A.
I appreciate your help very much, it’s the second time I install another kernel, after 5 or more years of ‘it’s just werks’ paradigm.
Well, I thought laptop from 2022 isn’t new. TW is not a good idea for install on USB drive?
Since I’ve submitted my last bug too long ago, now I can’t login into Bugzilla with “There is already an account with the login name …”. I wrote to bugzilla-admins 3 days ago, but received no reply.
