Problem when firmware bootnum is not a number

[upirons]

Hi,

First of all, many thanks for your program, for your work and for helping the Steam deck community.
I'm using reFind and I am understanding better its behaviour, and how Steam Os works. Many thanks for the info on your GitHub page.
After the last Steam Os update (I'm using the preview channel), I had problems starting Steam Os from reFind. When I selected Steam, after a few seconds, the refind menu appeared again. The only way to start Steam Os was using the Vol + & power option, and then selecting the steam file.

After many tests, I think there is a little issue in refind. In my case, the firmware bootnum for my Steam OS is 000C. When I use the reFind GUI version and I select the "Firmware_bootnum" option, when the config file is created and I open it, I can see that the bootnum appears as '000', without the 'C'. I added the 'C' to the bootnum in the refind.conf file, (000C), and then the Steam Os starts without any problem.

Many thanks again.

[jlobue10]

Well C technically is a number in hex. I plan on one more major release for this repo and I'll add fixing this to that list. Out of curiosity, what does your efibootmgr look like if you're up to 000C?

[upirons]

Yes, C is technically a number in hex. I didn´t do anything for myself to get that num (000C). I think as I had to reinstall Steam OS, then I had to reinstall Windows 11 over my installation of Windows 11, I had to reinstall reFInd several times, and also launched the restore efi entries script.

[jlobue10]

Yeah, I should update the code to support the full range of Hex numbers. I appreciate the heads up. You can manually clean-up older EFI entries with efibootmgr if you want.

[upirons]

I use the '-B' option of efibootmgr to delete older entries, but I currently have only one Steam Os entry. I would like to change its boot num, but I don´t know if it's possible to do it.

[jlobue10]

Yes, you can safely delete that SteamOS EFI entry. Then either restore the EFI entry manually or with the script, or next boot, use the boot from file BIOS option for SteamOS and the systemd service will replace the missing entry (assuming the service is running). There are multiple ways to get this done, in other words.