You are not logged in.
I have a functional 5.11.22-161-tkg-upds kernel running with no issues. I'm testing a Bluetooth patch with 5.4 kernel(can't apply it to a more recent kernel), but I can't boot into it and I can't figure out why.
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-partuuid/2d283d04-c170-9644-82f4-9d03dbef3e64 ...
ERROR: device 'PARTUUID=2d283d04-c170-9644-82f4-9d03dbef3e64' not found. Skipping fsck.
:: mounting 'PARIUUID=2d283d04-c170-9644-82f4-9d03dbef3e64' on real root
mount: /new_root: can't find PARTUUID=2d283d04-c170-9644-82f4-9d03dbef3e64.
You are non being dropped into an emergency shell.
sh: can't access tty: Job control turned off
[rootfs ]#First I had to change the initramfs compression to gzip, since 5.4 didn't support zsdt yet, and then run mkinitcpio -p linux54-tkg-bmq in order to update it with the new compression algorithm. I'm using BTRFS.
Bootloader(rEFInd) is fine. I created a separate entry for the 5.4:
menuentry "Arch Linux 5.4" {
icon /EFI/refind/icons/os_arch.png
volume archlinux
loader /ROOT/boot/vmlinuz-linux54-tkg-bmq
initrd /ROOT/boot/initramfs-linux54-tkg-bmq.img
options "root=PARTUUID=2d283d04-c170-9644-82f4-9d03dbef3e64 rw rootflags=subvol=ROOT initrd=ROOT\boot\intel-ucode.img initrd=ROOT\boot\initramfs-linux54-tkg-bmq.img audit=off mitigation=off nowatchdog"
}The PARTUUID is absolutely right. I tried specifying the UUID too..
[SOLVED]
It seems my .config/modprobed.db wasn't popupated enough. I missed some module. All good compiling the kernel with all modules.
Last edited by lucasrizzini (2021-05-29 14:08:48)
Offline
What distro is this about? Those kernels don't seem to be related to Arch kernels. "linux54" makes me think Manjaro?
Offline
What distro is this about? Those kernels don't seem to be related to Arch kernels. "linux54" makes me think Manjaro?
I'm on pure Arch, but using TKG's Kernel(https://github.com/Frogging-Family/linux-tkg).
I put the solution for my case at the bottom.
Last edited by lucasrizzini (2021-05-29 19:16:59)
Offline