ryanrudolfoba / SteamDeck-Clover-dualboot

Script to install Clover - a graphical boot manager for the Steam Deck.
https://www.youtube.com/watch?v=HDnxOw6j3EY&t=975s
496 stars 28 forks source link

clover doesn't load when the last booted os is steamos #59

Closed arvz closed 6 months ago

arvz commented 6 months ago

installed clover on my steam deck oled. I chose steamos as the default option.

after restarting the first time, clover appears, everything works great.

I load into steam os, restart again, this time there's no clover, just goes straight to steamos. even after shutting down, it always boots into steamos

if I choose clover from the boot menu, I can get clover back. now if I boot into windows after this, then when I restart or shut down, clover loads correctly.

seems to not work only when the last booted os is steamos?

also tried changing the default os to windows. still boots to steamos when the last os was steamos also tried re-running the script again, and same thing happens, first restart is good, then doesn't work anymore

image

the boot order in efibootmgr seems correct also:

image

ryanrudolfoba commented 6 months ago

Your second screenshot - the one that says BootNext 001. That is the culprit - it means on next reboot it will boot 001 which is assigned to SteamOS.

Do you have other scripts installed that could be interfering with the clover script?

Edit:

Try this to troubleshoot -

Uninstall Clover, reboot manually to SteamOS then run the efibootmgr command again. Take note if there is a BootNext item.

arvz commented 6 months ago

I've uninstalled clover, shut down, booted to steamos using the boot menu, run efibootmgr again:

image

the BootNext: 0001 is still there.

a while ago I did run a command that is supposed to make steamos the default os instead of windows - maybe that's why this is happening? I can't remember what the command was though. any suggestions?

arvz commented 6 months ago

I tried sudo efibootmgr --delete-bootnext which seems to remove the BootNext. then I run the script again, the BootNext comes back, but it is pointing to 0004 which is clover. restarted, and it boots to clover, but then I restart again, and we're back to the original problem, BootNext: 0001 (steamos)

ryanrudolfoba commented 6 months ago

Definitely there is a startup script that is causing that BootNext item to appear. If you have a link of the guide you followed prior to clover we can take a look at it and figure out how to remove it.

arvz commented 6 months ago

ok I found it, it was from this comment: https://www.reddit.com/r/WindowsOnDeck/comments/100puqr/comment/k1l9ti1/ it's just setting the BootOrder though, not a startup script. before I ran this command my steam deck would always default to restarting to Windows no matter which OS was the last one booted, and the command did work, it always goes to steamos after that.

I don't think there's any startup script other than clover - but is there a way to check this?

ryanrudolfoba commented 6 months ago

closing this issue as it is not related to the clover script. issue is caused by 3rd party script / tools messing with the BootNext parameter.