Arch Linux

esskayesss

Member

Registered: 2023-05-05

Posts: 3

[SOLVED] rEFInd randomly stopped using my keyboard

I just completed a fresh installation, opting for rEFInd with secure boot. However, I'm experiencing some issues with my backlit keyboard and the rEFInd boot menu. As soon as the rEFInd screen appears, the keyboard lights turn off, and the keys become unresponsive, making it impossible to choose a boot option. Additionally, the UEFI settings menu was being skipped, forcing me to remove the disk and boot from a different target. This happened multiple times during my installation tests, especially since rEFInd tried to mount an empty address as the root device. I had to run refind-install repeatedly to resolve the issue.

Previously, I've only had to customize rEFInd themes, but this time I'm facing several challenges:

1. Failure to mount the correct root device initially

2. Unresponsiveness in the rEFInd menu (although it successfully boots into my Linux installation)
   Also note that it doesn't seem like it's stalled either because the timeout clock still updates. judging by the backlight of my keyboard, it seems like the keyboard itself is just inactive.

3. Disappearance of the Windows boot option after the first Linux boot

I also need help ensuring that the Windows Boot Manager and rEFInd don't skip the BIOS screen, as I faced this issue earlier as well.

To sum up, here are the main problems I'm facing:

• Inactive keyboard during the rEFInd menu

• Windows boot option not showing up after the first boot

In addition to these issues, I would prefer not to have my computer bypass the BIOS menu screen. This makes it quite challenging to access when needed.

Any suggestions or solutions for these issues would be greatly appreciated!

Last edited by esskayesss (2023-05-05 19:07:33)

esskayesss

Member

Registered: 2023-05-05

Posts: 3

Re: [SOLVED] rEFInd randomly stopped using my keyboard

SOLVED

in my BIOS settings, the fastboot was set to ultra-fast. while you would still expect rEFInd to activate the keyboard on it's own, it apparently did not. now that I've set fastboot to just enabled instead of ultra-fast, it works!