Can’t log into the system after updating

[BraisonCrece]

System details

AMD Ryzen 5 5600X, GTX 1080Ti, 32 RAM DDR4, 500GB Nvme.

What's wrong?

I updated Omarchy through the built-in system updater. When I tried to log in again after the required restart, I couldn’t.

My keyboard works fine, since on the partition selection screen (GRUB) I can select any entry without issues.

Once I select Arch Linux, I reach the password input screen (to unlock the encrypted volume) with the OMARCHY letters, but I can’t type the password or do anything. The system doesn’t respond, I can’t open a new TTY, nothing works.

Expected Behavior

Be able to enter the password and unlock the encrypted volume to boot the system.

Actual Behavior
• Keyboard does not respond on the OMARCHY password screen.
• Cannot type the password.
• Cannot switch to another TTY.
• System is completely unresponsive.

Impact

For me, and maybe other people affected, this is a critical bug

[dhh]

What kind of keyboard are you using?

[BraisonCrece]

I'm using a Keychron K10 pro connected by cable.

On second thought, there is something else that could cause this issue. between applying the system update and rebooting, I attempted to connect my keyboard via Bluetooth.

This is the Wifi and Bluetooth device I use:

Asus PCE-AX58BT WiFi 6 AX3000, Bluetooth 5.0

The keyboard was discoverable and would pair, but it failed to maintain a connection. The root cause might not be a bug in the system updater itself.

[BraisonCrece]

I have managed to solve the problem and want to share the solution in case it helps others or in diagnosing the root cause.

The issue was resolved by manually regenerating the initramfs.

Here are the steps I followed to do it:

1. I booted using the "Arch Linux (linux-fallback)" option from the GRUB menu. This provided a root shell.
2. To make changes, I ensured the filesystem was writable.

mount -o remount,rw /

3. I executed the mkinitcpio command with the -P preset flag to rebuild the initramfs for all installed kernels.

mkinitcpio -P

This command completed without errors.

After rebooting, the keyboard worked perfectly at the LUKS password prompt, and the system booted as expected. 👏

The root cause might not be a bug in the system updater itself. It is highly likely that my attempts to set up a Bluetooth device right after the update process were the actual trigger for the faulty initramfs generation.

I'm going to try to connect the keyboard via bluetooth again to see what happens, I'll keep adding info here.

I hope this is useful!

[dhh]

Thanks for sharing, @BraisonCrece!

[BraisonCrece]

Note

I have tried to connect my keyboard using bluetooth, and still didn't work. Then, I restarted the system and I was able to log in without issues, everything was working perfectly. The keyboard still wouldn't pair. I decided to update the firmware provided by the manufacturer, and after restarting again, the keyboard connected via Bluetooth, and everything is working fantastically

• Asus PCE-AX58BT WiFi 6 AX3000, Bluetooth 5.0 firmware link: https://www.asus.com/es/networking-iot-servers/adapters/all-series/pce-ax58bt/helpdesk_download?model2Name=PCE-AX58BT