[SOLVED] kernel issues with 6.4.7

othersamo_ · 2023-10-09 19:45:58

hello,
I am using thinkpad p50 and am unable to update to a newer kernel than 6.1.39-1-lts. Each time I try to update to a new kernel, my system panics and is unable to mount the efi partition:
https://i.imgur.com/NpQq6l2.png

I am able to jump into tty and do some commands but the functionality is very limited and the kernel does not even upgrade:
https://i.imgur.com/bxuRDAv.jpg
(see that kernel is 6.4.6 but before reboot I upgraded it to 6.5.6. I also have to keep some another packages back such as nvidia drivers. I originally thought this was a bug in 6.4.7 but considering this happens also in 6.5.6, I do not believe this is the case anymore.

Update: After yesterday's update, kernel 6.4.6 no longer works correctly with my system as lightdm cannot be started. Same for XFCE session. My guess would be some incompatibility with the integrated intel graphics card occured:
http://ix.io/4ICv
^^ This was the output of the xorg log.

Ideal case would be to update the kernel and the Nvidia drivers, as well but the error above the "Update" section is happening.
Thank you

Last edited by othersamo_ (2023-10-13 18:19:10)

loqs · 2023-10-09 19:59:40

Please post the full system journal for a boot with the issue.

seth · 2023-10-09 20:37:36

Remove "quiet" and " lsm=landlock,lockdown,yama,integrity,apparmor,bpf" but w/

see that kernel is 6.4.6 but before reboot I upgraded it to 6.5.6

and the failed module loads you're most likely just forgetting to mount the /boot partition before the update?

othersamo_ · 2023-10-10 11:16:28

Thank you for the support, here is the complete log from the boot session with the newest kernel 6.5.6: http://ix.io/4IEY

Last edited by othersamo_ (2023-10-10 11:16:41)

othersamo_ · 2023-10-10 11:18:53

seth wrote:

and the failed module loads you're most likely just forgetting to mount the /boot partition before the update?

Sorry, but I am not necessarily sure what you mean. I did not manually mount the efi partition but at the same I never had to do that. Updates of the kernel were so far pretty much seamless when running pacman update was enough.

Lone_Wolf · 2023-10-10 11:43:16

Please don't post several times in a row (especially if the time between posts is so short) , just edit the already existing post.

Oct 09 18:52:26 archlinux kernel: Linux version 6.1.39-1-lts (linux-lts@archlinux) (gcc (GCC) 13.1.1 20230714, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Wed, 19 Jul 2023 17:58:31 +0000

Oct 09 18:52:28 Samo-PCTP systemd-modules-load[267]: Failed to find module 'crypto_user'
Oct 09 18:52:28 Samo-PCTP systemd-modules-load[267]: Failed to find module 'dm-multipath'
Oct 09 18:52:28 Samo-PCTP systemd-modules-load[267]: Failed to find module 'nvidia-uvm'

Oct 09 18:52:28 Samo-PCTP ufw-init[316]: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.1.39-1-lts
Oct 09 18:52:28 Samo-PCTP ufw-init[315]: iptables-restore v1.8.9 (legacy): iptables-restore: unable to initialize table 'filter'
Oct 09 18:52:28 Samo-PCTP ufw-init[315]: Error occurred at line: 1

You appear to be booting linux-lts 6.1.39 , but it's modules are missing .

There are some signs in the log you are not booting but resuming .
While I doubt that can cause this, please perform a cold boot to verify it.

seth · 2023-10-10 12:20:42

othersamo_ wrote:

Sorry, but I am not necessarily sure what you mean.

You're (now) clearly booting
- a dated kernel
- from a boot partition (that's not the same as the ESP that you fail to mount at /efi)
- w/o any attempt to boot the boot partition in the journal

lsblk -f

othersamo_ · 2023-10-10 14:54:03

I removed the linux stuff from IgnorePkg and upgraded linux to 6.5.7. Because I also have LTS kernel, it was updated too. I probably forgot to mention it earlier but I am using systemd-boot with UEFI.
Unfortunately, I cannot post it as text because wifi does not work, usb ports do not work, so I cannot copy it anywhere from the PC. It should be possible to read though. If you have any idea how to transfer it elsewhere, please lmk and I will re-upload it. Sorry for that

I ran the upgrade and this was the output.:
https://imgur.com/a/9X9P1vy
Despite upgrading, I can only boot to the previous kernel: https://imgur.com/a/8TQ9D8g

Output of lsblk -f (I am booting from the nvme0n1p1):
https://imgur.com/a/lSD6Tyf

Journal from the current boot:
https://imgur.com/a/X984ABg

Thank you.

EDIT: This was a boot where all apparmor modules were NOT turned on.

Last edited by othersamo_ (2023-10-10 14:58:28)

seth · 2023-10-10 15:27:25

Boot some live distro or the install iso, mount nvme0n1p1 and nvme1n1p1 somewhere and check their contents.
If there're vmlinuz-linux* and initramfs* around, that's probably your boot partition.

othersamo_ · 2023-10-10 18:30:51

Okay, so my boot partition seems to be nvme0n1p1 where initramfs* and vmlinuz-linux* files are. nvme1n1p1 is for timeshift where I do my backups, so that is not very important right now. However, my main partition (nvme0n1p2 [my system is there] contains in /boot very similar set of files.
Here is how it looks:
https://imgur.com/a/hgEfCTG

seth · 2023-10-10 19:33:27

Don't post pictures, check "file /boot/vmlinuz-linux" and "file /mnt/vmlinuz-linux" to see which holds the kernel you actually end up booting but I'll spoil this and tell you that it's the one on nvme0n1p1, so mount that to /boot and re-install the kernel (you can do that from the chroot off the install iso)

othersamo_ · 2023-10-12 16:50:20

Yes, you were right. I am booting from the one in nvme0n1p1.

Maybe do you have any source of how can I upgrade the kernel from the iso? I am asking especially because despite downloading the newest iso, it uses 6.4.12-arch1-1 kernel.

V1del · 2023-10-12 17:02:24

The ISO kernel doesn't matter, once you have the partitions mounted and chroot properly the next pacman invocation will download the latest kernel from the repositories/your sync DB and you can just install with pacman -S linux like normal.

so

mount /dev/nvme0n1p2 /mnt
mount /dev/nvme0n1p1 /mnt/boot
arch-chroot /mnt
pacman -Syu linux

And fix your /etc/fstab so nvme0n1p1 is mounted to /boot in the future -- use UUIDs however!

And read https://wiki.archlinux.org/title/Chroot to know what and why we are doing that, and https://wiki.archlinux.org/title/Persis … ice_naming while you're at it.

Last edited by V1del (2023-10-12 17:10:06)

othersamo_ · 2023-10-13 18:17:01

Yes, I installed the archiso via chroot.
Fixing fstab was done via:

genfstab -U /mnt/p2 >> /mnt/p2/etc/fstab.new

Then I checked, edited swap and rewrote the actual fstab and booted normally.

Thank you for help.

othersamo_ · 2023-10-13 18:18:25

Yes, I installed the archiso via chroot.
Fixing fstab was done via:

genfstab -U /mnt/p2 >> /mnt/p2/etc/fstab.new

Then I checked, edited swap and rewrote the actual fstab and booted normally.

Thank you for help.

seth · 2023-10-13 18:19:38

Edit: yes he can and he did…

Last edited by seth (2023-10-13 18:19:58)

Arch Linux

#1 2023-10-09 19:45:58

[SOLVED] kernel issues with 6.4.7

#2 2023-10-09 19:59:40

Re: [SOLVED] kernel issues with 6.4.7

#3 2023-10-09 20:37:36

Re: [SOLVED] kernel issues with 6.4.7

#4 2023-10-10 11:16:28

Re: [SOLVED] kernel issues with 6.4.7

#5 2023-10-10 11:18:53

Re: [SOLVED] kernel issues with 6.4.7

#6 2023-10-10 11:43:16

Re: [SOLVED] kernel issues with 6.4.7

#7 2023-10-10 12:20:42

Re: [SOLVED] kernel issues with 6.4.7

#8 2023-10-10 14:54:03

Re: [SOLVED] kernel issues with 6.4.7

#9 2023-10-10 15:27:25

Re: [SOLVED] kernel issues with 6.4.7

#10 2023-10-10 18:30:51

Re: [SOLVED] kernel issues with 6.4.7

#11 2023-10-10 19:33:27

Re: [SOLVED] kernel issues with 6.4.7

#12 2023-10-12 16:50:20

Re: [SOLVED] kernel issues with 6.4.7

#13 2023-10-12 17:02:24

Re: [SOLVED] kernel issues with 6.4.7

#14 2023-10-13 18:17:01

Re: [SOLVED] kernel issues with 6.4.7

#15 2023-10-13 18:18:25

Re: [SOLVED] kernel issues with 6.4.7

#16 2023-10-13 18:19:38

Re: [SOLVED] kernel issues with 6.4.7

Board footer