You are not logged in.
Hi, I have a Gigabyte motherboard B560 AORUS PRO AX and with the latest kernel update to the latest kernels I can't do anymore password prompt for cryptsetup. I can choose between LTS and Mainline Kernel to boot but later the keyboard stop wroking. With a older USB stick it's working.
lsusb | nc termbin.com 9999journalctl -b | grep Microsoft | nc termbin.com 9999 With chroot the Keyboard is working...
How I can fix that?
Last edited by Morta (2022-02-10 17:22:22)
Offline
it sounds like your boot loader is not picking up a kernel version that is different from the kernel that is installed.
If you boot your system, do you have any way to get the output of
uname -a
pacman -Q linux
and
pacman -Q linux-lts
without a keyboard? Perhaps by using ssh to get into the system?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
it sounds like your boot loader is not picking up a kernel version that is different from the kernel that is installed.
If you boot your system, do you have any way to get the output of
uname -a
pacman -Q linux
and
pacman -Q linux-ltswithout a keyboard? Perhaps by using ssh to get into the system?
No because is crypted but I can chroot and do this command.
Have I to update the bootloader or is the hooks wrong with keyboard?
Offline
That is not all that helpful since we pretty much know what version is installed (which is what the pacman commands return). The uname command will return the name of the kernel provided by the chroot's host, not the one being loaded by your bootloader.
Let's try a different tack. Set up a chroot without having mounted your boot partition and enter it. Look in /boot and see if there are files. If there are, including the kernel, note the date on the file. Then exit, and set up a chroot with the boot partition mounted. Do the same. Compare the dates and report back.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Let's try a different tack. Set up a chroot without having mounted your boot partition and enter it. Look in /boot and see if there are files. If there are, including the kernel, note the date on the file.
file understands vmlinuz and will extract the kernel version
file /boot/vmlinuz-linuxOffline
Booting the fallback initrd may help in the case of a missing module from the autodetect initrd.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
file /boot/vmlinuz-linux | nc termbin.com 9999 pacman -Q linux linux-lts | nc termbin.com 9999 uname -a | nc termbin.com 9999 cat /etc/mkinitcpio.conf | nc termbin.com 9999 HOOKS=(base systemd autodetect modconf block keyboard sd-vconsole mdadm_udev sd-encrypt lvm2 filesystems fsck)It's this correct?
Without mount /dev/nvme0n1p1 /mnt/boot /boot is empty
Last edited by Morta (2022-02-10 14:32:04)
Offline
I fixed with this hooks
HOOKS=(base systemd keyboard autodetect modconf block sd-vconsole mdadm_udev sd-encrypt lvm2 filesystems fsck)The reason is
Note: For systems that are booted with different hardware configurations (e.g. laptops with external keyboard vs. internal keyboard or headless systems), this hook needs to be placed before autodetect in order to be able to use the keyboard at boot time, for example to unlock an encrypted device when using the encrypt hook is used.
I don’t know why it was working before
Offline