[SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

fakirinho · 2022-06-03 12:25:56

Hi,

I've been looking through many (definitely not all, that's not possible) topics like mine but to no avail. One of the differences between mine setup and the setup from "others' issues" is that I have my root ("/") encrypted with looks. Currently I run on linux-5.17.9:

$ uname -a
Linux PLPCLPD-1035 5.17.9-arch1-1 #1 SMP PREEMPT Wed, 18 May 2022 17:30:11 +0000 x86_64 GNU/Linux

and after I upgrade to linux-5.18.1 (with no obvious pacman bugs) after reboot I'm not immediately prompted for a key to open my encrypted /dev/nvme0n1p2, but instead a wall of text is presented. After ~2 minutes I'm asked for key to open the encrypted partition and after some more time (~1-2 minutes, don't remember) I get info that it was not possible to load kernel modules and I'm unable to switch to another tty (well, from the beginning I'm unable to switch to any other tty).

The only way I have now to make my system usable once again is to live-boot Arch USB stick, open my drive (cryptsetup), mount it ("mount /dev/mapper/luks /mnt") together with boot partition ("mount /dev/nvme0n1p1 /mnt/boot") and then arch-chroot to /mnt. Afterwards I can manually downgrade my linux package specifying version 5.17.9 from pacman's cache.

Few commands below are from "arch-chrooted" environment:

$ blkid
/dev/nvme0n1p5: LABEL="DELLSUPPORT" BLOCK_SIZE="512" UUID="F440CCAE40CC78BE" TYPE="ntfs" PARTUUID="a7e95252-fe6d-496d-8a1b-8eb989c1dbe8"
/dev/nvme0n1p1: UUID="F49D-4E12" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="b553c6ff-08b6-412c-bf8f-64d4bd25536b"
/dev/nvme0n1p4: LABEL="WINRETOOLS" BLOCK_SIZE="512" UUID="2AD0D22AD0D1FBCF" TYPE="ntfs" PARTUUID="f9d146c1-f788-4215-94e1-c84070e27233"
/dev/nvme0n1p2: UUID="a5397d34-27ff-4fd5-9874-78531b7564e7" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="7919298a-e914-41ec-bc34-4b1e79b0b735"
/dev/loop0: TYPE="squashfs"
/dev/mapper/luks: UUID="27666750-75c2-452f-a588-5d5905fe97ab" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="878C-7E2D" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bf3c4bb4-02"
/dev/sda1: BLOCK_SIZE="2048" UUID="2022-04-05-16-02-52-00" LABEL="ARCH_202204" TYPE="iso9660" PARTUUID="bf3c4bb4-01"

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
loop0         7:0    0 666.6M  1 loop  
sda           8:0    1  29.3G  0 disk  
|-sda1        8:1    1   746M  0 part  
`-sda2        8:2    1    78M  0 part  
sdb           8:16   1     0B  0 disk  
nvme0n1     259:0    0 953.9G  0 disk  
|-nvme0n1p1 259:1    0   299M  0 part  /boot
|-nvme0n1p2 259:2    0 951.2G  0 part  
| `-luks    254:0    0 951.2G  0 crypt /
|-nvme0n1p4 259:3    0   990M  0 part  
`-nvme0n1p5 259:4    0   1.4G  0 part

$ fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: PM9A1 NVMe Samsung 1024GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6C3433C7-3D20-4821-A27D-63FD8F1A1B64

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     614399     612352   299M EFI System
/dev/nvme0n1p2     614400 1995476991 1994862592 951.2G Linux filesystem
/dev/nvme0n1p4 1995476992 1997504511    2027520   990M Windows recovery environment
/dev/nvme0n1p5 1997506560 2000377855    2871296   1.4G Windows recovery environment


Disk /dev/sda: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk model: Flash Disk      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbf3c4bb4

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 1527807 1527744  746M  0 Empty
/dev/sda2       1527808 1687551  159744   78M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 666.63 MiB, 699011072 bytes, 1365256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/luks: 951.21 GiB, 1021352869888 bytes, 1994829824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/luks_root
UUID=27666750-75c2-452f-a588-5d5905fe97ab	/         	ext4      	rw,relatime	0 1

# /dev/nvme0n1p1
UUID=F49D-4E12      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

$ file /boot/vmlinuz-linux
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 5.18.1-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Mon, 30 May 2022 17:53:11 +0000, RO-rootFS, swap_dev 0XA, Normal VGA

$ pacman -Qi linux
Name            : linux
Version         : 5.18.1.arch1-1
Description     : The Linux kernel and modules
Architecture    : x86_64
URL             : https://github.com/archlinux/linux/commits/v5.18.1-arch1
Licenses        : GPL2
Groups          : None
Provides        : VIRTUALBOX-GUEST-MODULES  WIREGUARD-MODULE
Depends On      : coreutils  kmod  initramfs
Optional Deps   : wireless-regdb: to set the correct wireless channels of your country
                  linux-firmware: firmware images needed for some devices [installed]
Required By     : bbswitch  nvidia
Optional For    : base
Conflicts With  : None
Replaces        : virtualbox-guest-modules-arch  wireguard-arch
Installed Size  : 174.92 MiB
Packager        : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date      : Mon May 30 19:53:11 2022
Install Date    : Fri Jun  3 13:35:20 2022
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

$ efibootmgr -v
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0000,0005,0006,0007,0008,0003,0001,0002,0004
Boot0000* GRUB	HD(1,GPT,b553c6ff-08b6-412c-bf8f-64d4bd25536b,0x800,0x95800)/File(\EFI\GRUB\grubx64.efi)
Boot0001* USB NIC (IPV4)	PciRoot(0x0)/Pci(0xd,0x0)/USB(3,0)/USB(3,0)/MAC(0892045fa361,0)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
Boot0002* USB NIC (IPV6)	PciRoot(0x0)/Pci(0xd,0x0)/USB(3,0)/USB(3,0)/MAC(0892045fa361,0)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
Boot0003* Arch_Linux	HD(1,GPT,5ddbc067-c011-7643-977f-87b8310d088b,0x22,0x967de)/File(\EFI\Arch_Linux\grubx64.efi)
Boot0004* UEFI HTTPs Boot	PciRoot(0x0)/Pci(0xd,0x0)/USB(3,0)/USB(3,0)/MAC(0892045fa361,0)/IPv4(0.0.0.00.0.0.0,0,0)/Uri()N.....YM....R,Y.
Boot0005* UEFI Generic Mass Storage B3DD8818	PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/USB(1,0)/HD(2,MBR,0xbf3c4bb4,0x175000,0x27000)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
Boot0006* UEFI Generic Mass Storage B3DD8818	PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/USB(1,0)/HD(2,MBR,0xbf3c4bb4,0x175000,0x27000)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
Boot0007* UEFI Generic Mass Storage B3DD8818	PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/USB(1,0)/HD(2,MBR,0xbf3c4bb4,0x175000,0x27000)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
Boot0008* UEFI Generic B3DD8818	PciRoot(0x0)/Pci(0x14,0x0)/USB(4,0)/USB(1,0)/CDROM(1,0x175000,0x27298)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.

Any ideas what I have messed up during my installation? Whole system was setup around ~1-1.5 months back if that makes any difference, already with kernel 5.17.x...

Last edited by fakirinho (2022-06-03 14:19:17)

seth · 2022-06-03 12:55:15

Required By     : bbswitch  nvidia

Add "ibt=off" to the kernel parameters, https://www.google.com/search?q=ibt%3Do … hlinux.org

fakirinho · 2022-06-03 13:10:51

how on earth have you reached this conclusion?! it works. but I guess it's more of the workaround rather then proper solution, right? should I wait more for newer nvidia package to get this properly solved or what?

Edit: and most importantly - thank you

Last edited by fakirinho (2022-06-03 13:23:27)

seth · 2022-06-03 13:36:08

Did you check the google link? This came up pretty often recently.
The workaround disables a feature that didn't exist before - you can use it until nvidia ships a driver w/ ENBDR support.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

fakirinho · 2022-06-03 14:17:45

I've quickly looked at the linked google search but it was not obvious from that at the time I wrote my comment. Then while being AFK I've searched about it bit more and got some understanding. And I guess my own google-lookup (prior to this topic) still might have been to "fresh" and older issues came in search results - my learning from this is to sometimes filter search results to most recent ones, like one week old.

I've also found some more detailed explanation about what "ibt=off" disables and that it's actually nvidia not keeping up to date with releasing the drivers. But if you are a regular user as I am and not really living on "arch/kernel/nvidia/other-geekish fuel" there is literally no chance to keep up with the news and not bump into such problems.

To finish with - I wanted to first understand bit more on the topic and maybe adjust the title before marking as "solved", so that title is bit more precise.

Anyway, thanks again for all the help!

Arch Linux

#1 2022-06-03 12:25:56

[SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

#2 2022-06-03 12:55:15

Re: [SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

#3 2022-06-03 13:10:51

Re: [SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

#4 2022-06-03 13:36:08

Re: [SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

#5 2022-06-03 14:17:45

Re: [SOLVED] Another "can't boot" after linux update - nvidia & linux-5.18

Board footer