Stuck at Linux Boot Loader

[gabitoesmiapodo]

Hi guys, I'm currently having the following issue:

• I could install ChimeraOS no problem in my ROG Ally. The system boots, I logged in on Steam, downloaded some games, etc., everything went super smooth.
• At some point I had to reboot the device and got the following (I took the image from this reddit post because I can't seem to know how to take a decent picture, just replace the first option with ChimeraOS' current version):

This wouldn't be a huge problem if I could just select the first option, but it seems there's no way to select anything unless there's a keyboard plugged in. None of the ROG Ally's controls work, except the power and volume buttons.

• Is this boot screen expected? (I don't remember seeing it the first few times the system rebooted)
• Can I just default to ChimeraOS somehow and avoid it? I'm not interested in selecting anything, I just want to boot into ChimeraOS.

As a workaround on the ROG Ally I found I could do the following:

• Boot into the firmware setup / utility mode (power on + volume down button when the ROG Ally logo appears).
• Go down, select the "Boot Menu" option. Press A.
• Select "Linux Boot Manager". Press A.
• The boot menu from the screenshot will appear, but this time the ROG Ally's controls will work. Just select the first option and boot into ChimeraOS.

[gabitoesmiapodo]

Just for future reference, I could finally fix this...

It turns out it may not be a ChimeraOS bug, or maybe it is but I don't know why...

So, I first edited the options in boot/loader/loader.conf until it looked like this:

timeout 0
default frzr.conf
auto-firmware no

But nothing happened, still stuck, except that the "Reboot into firmware interface" disappeared. So: some of the options were being detected, and some of the options were not.

After some further research I found out that EFI vars overwrite loader.conf vars if they exist.

If you write efivar --list | grep -i Timeout on your Linux console and get one or more results, then your configuration is being overwritten. And that's what for some reason was happening to me.

The fix:

Write this on your console sudo bootctl set-timeout 0 (pass: gamer)

And then reboot and it should be fixed.