SteamOS 3.5 boot into Windows when SteamOS selected in rEFInd

[johnlietzke]

Updated to SteamOS 3.5 beta today to play Starfield.

rEFInd loads properly but when Steam is selected it boots into Windows.

I may be daft and missing something obvious to remedy this. Any ideas why?

I did notice it updated the firmware after the update rebooted. I did not realize it was going to do this in my haste to try Starfield on the Deck. Is there a simple fix after the fact like downgrading to Stable and selecting Sysd Off then redo the upgrade.

Thanks, John

[jlobue10]

Manually boot into Steam OS from its efi file on the esp partion.

[johnlietzke]

I did manually boot into Steam from ESP and tried using the GUI to reinstall REFInd.

I was wondering how to fix rEFInd so I can use it as a boot manager where both SteamOS and Windows work.

When the Steam icon is selected it boots into Windows and when the Windows icon is selected it boots in the Windows UEFI.

[jlobue10]

Please show me the output of efibootmgr and sudo nano /esp/efi/refind/refind.conf.

[johnlietzke]

# GUI generated refined.conf Config File
timeout 5
use_nvram false
hideui singleuser,hints,arrows,label,badges
banner background.png
banner_scale fillscreen
resolution 3
enable_touch
#enable_mouse

[jlobue10]

That looks completely wrong (missing boot entries). Can you recreate and reinstall the config? Are you just running SteamOS and Windows both from the NVMe?

[johnlietzke]

I completely uninstalled rEFInd. When attempting to reinstall the GUI, I get this error:

sudo steamos-readonly disable

[error: linux-api-headers: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/linux-api-headers-6.3-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: glibc: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/glibc-2.37-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: lib32-glibc: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/lib32-glibc-2.37-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: libx86emu: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/libx86emu-3.5-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-encode-locale: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-encode-locale-1.05-10-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-http-date: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-http-date-6.05-6-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-file-listing: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-file-listing-6.15-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-html-tagset: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-html-tagset-3.20-13-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-clone: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-clone-0.46-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-io-html: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-io-html-1.004-3-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-lwp-mediatypes: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-lwp-mediatypes-6.04-3-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-uri: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-uri-5.19-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-http-message: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-http-message-6.44-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-html-parser: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-html-parser-3.81-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-http-cookies: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-http-cookies-6.10-3-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-http-daemon: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-http-daemon-6.16-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-http-negotiate: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-http-negotiate-6.01-11-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-net-http: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-net-http-6.22-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-try-tiny: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-try-tiny-0.31-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-www-robotrules: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-www-robotrules-6.02-11-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-libwww: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-libwww-6.67-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-xml-parser: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-xml-parser-2.46-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: perl-xml-writer: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/perl-xml-writer-0.900-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: hwinfo: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/hwinfo-22.2-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: qt5-base: signature from "GitLab CI Package Builder <ci-package-builder-1@steamos.cloud>" is unknown trust
:: File /var/cache/pacman/pkg/qt5-base-5.15.9+kde+r155-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Project ERROR: Cannot run compiler 'g++'. Output:
===================
===================
Maybe you forgot to setup the environment?
./install-GUI.sh: line 31: make: command not found

GUI compile failed. Please try again after ensuring that your cloned repo is up to date and your pacman config is normal.](z)

[jlobue10]

Please try the standalone versions. Immutability of SteamOS has become a huge pain in the ass for me (sorry but been asked these same questions countless times).

[johnlietzke]

For your own future development, when re-enabling readonly I get this message

Warning: The rootfs is already read-only!
         Nothing is performed.

Looks like disabling readonly is not working properly.

[jlobue10]

No it is working, I believe. It's dependency package signature problems which is wreaking havoc with pacman installing them properly.

The precompiled versions hopefully work in your case. There are 2 versions. The prepackaged tarball which still uses all system dynamic libraries, and the more "standalone" package which uses some static libraries at compile time. Both are precompiled. Instructions for those are on the GUI page.

[johnlietzke]

I went back to the old school way of installing rEFInd and now it works. git clone https://github.com/jlobue10/SteamDeck_rEFInd/ cd SteamDeck_rEFInd chmod +x SteamDeck_rEFInd_install.sh ./SteamDeck_rEFInd_install.sh Thanks for the help. You are the most response Git devs I seen.

[jlobue10]

No worries. I'm happy the old script works. Please let me know if one of the precompiled GUI versions work for you or not. I've personally been spending more time with ROG ALLY (running Nobara) these days.

I have some repo improvements (background randomizer and sudoless config install) that I could push out as well. I just need to find the time.

[johnlietzke]

I am struggling with deciding whether to buy an Ally or not. Is it a meaningful upgrade to the Deck? I canceled my pre order give the abundance of availability. First hand experience from someone who tinkers and pushes hardware to the limit would be helpful.

Use ChimeraOS on my PC and Mini PC a 2nd, sometimes 5th operating system depending on what OS I am trying out at the time. May try Nobara in the coming days.

I wanted a console like gaming experience in the living room so got the Beelink GRT7 Pro (7940hs) Mini PC about 6 weeks ago. Stock 65 watt TDP but boosted it to 85 watts and OC the GPU to 3000mhz. Outstanding performance for an APU in such a small form factor. Have not had time to try Starfield yet on it. But given how well it runs on the Deck, I suspect I will be getting close to a stable 60fps.

[jlobue10]

To me the ALLY is just better in every single way that matters (for what I want). It's more powerful, it's lighter, and I actually like the RGBs around the sticks too. If you feel that you can live without the trackpads, then I'd seriously consider getting an ALLY. I have both the ALLY and Steam Deck and the Deck has been relegated to a paper weight for now (even though it's still great). The ChimeraOS devs put a lot of work in to get it in great shape on the ALLY, which it is. The reasons that I chose to go with Nobara (Steam Deck edition) instead of ChimeraOS are my dislikes of immutability (since I am comfortable in Linux and know what I'm doing) and my preference of KDE Plasma over Gnome. I've also personally gone to a lot of effort tracking down relevant kernel patches to fix the hardware on ALLY in Nobara (Linux in general). And in the one case where a patch didn't exist yet for the audio, I actually contributed to getting an original patch into the early working stages. We're still waiting for a response here.

TL:DR; even with the SD card reader issue, I think the ROG ALLY is 100% worth getting and enjoying.

[johnlietzke]

I may pick one up in the coming days. Was considering a OneXPlayer Fly but support and updates are an ongoing issue OneNetBook devices. Plus the Ally has FreeSync which gives smoother performance at higher FPS.

Another big holdup was the lack of Hall Effects sticks. Now there upgrades available that barrier is gone. Love the Hall on the Deck.

Linux is not my daily driver. MacOS Sonoma and Windows 11 are my primary uses. Use MacOS most of the time and Windows for gaming, but always like to have options. There are somethings you can do in Linux when setting up multiple operating systems on a single drive that are just not possible with Apple and Microsoft.

[jlobue10]

I think the one thing to keep in mind with hall effect sticks on the ALLY is that some shielding is needed so that hall effect triggers and sticks don't interfere with each other.

The more I use Nobara, the more I am falling in love with Linux. Sure it can be a bit of a pain to setup, but once it's good to go, it's basically rock solid.

Plus SteamOS just made me fall in love with that UI. I know you can do big picture mode in Windows, but it's just not the same without Decky and other under the hood differences. I'm honestly just happy that Valve kicked off this "golden age" of handhelds.

[jlobue10]

Closed on accident.

[johnlietzke]

No question the gaming UI was a game changer. The clunky Windows UI with Steam Big Picture is the biggest turnoff to Windows for me.

There is always something that needs to be done with Windows when you sit down to play.

Have you been able to get noticeable performance boost overclocking the Ally with Universal X86 Tuning Utility? I use it on the Mini PC with an 8-10FPS increase in newer AAA games.

[jlobue10]

I haven't tried. There's lots of good info available in the ROGALLY subreddit and discord.

I've honestly spent more time tracking down all the relevant fixes than actually playing. Oh there's also one huge nice thing that ALLY can do that the Steam Deck cannot. You can dual boot Nobara and W11 (my use case) with secure boot enabled (with local keys). This allows you to play games that require that in W11 like Valorant, Fifa 23, FC 24, and Madden 24. I've confirmed that it works on mine.

[johnlietzke]

That is really nice. Leaning more and more to getting an Ally. Just was looking at some OC videos.

I would just take the 2TB out of the deck for the Ally and put the old 1TB back in the deck without a dual boot.

Easiest way I found to dual boot ChimeraOS was to install it on to an 64GB flash drive and clone the partitions to the empty space left after shrinking Windows to 100GB. The remaining space is a Btrfs partition accessible by both Windows and ChimeraOS. Add WinBTRFS to Windows and you are good to go.

[jlobue10]

Yeah dual booting ChimeraOS is not "easy" on the same NVMe. There's a way like you mention with installing to USB and then cloning over with snapshots. I've had a good experience with Nobara Steam Deck edition and dual booting alongside W11.

One intriguing thing with ALLY is the available 90 degree adapter for the NVMe which opens 4TB up as a reasonable, not too difficult option. I've ordered that adapter and will probably clone my 2TB setup to that, and split 50/50 between the OSes.

[johnlietzke]

I hate having the operating system partitions so large. Having to put games on separate partitions often leaves unused space on each partition as they get fuller.

That is why I use the BTRFS "game" partition. Plus you play and update the games from either OS.

[jlobue10]

Yeah, true. That's probably a better way of doing it.

[smtdev]

I went back to the old school way of installing rEFInd and now it works. git clone https://github.com/jlobue10/SteamDeck_rEFInd/ cd SteamDeck_rEFInd chmod +x SteamDeck_rEFInd_install.sh ./SteamDeck_rEFInd_install.sh Thanks for the help. You are the most response Git devs I seen.

Thanks! It has worked for me as well.

[jlobue10]

Yes, it seems that something has broken with the script that the GUI calls for the "Install rEFInd" step. I will need to debug why. For future release versions, I may just hard code it into the C++ functions on what exactly to do, with a popped up xterm. This is annoying that something that has worked for months now doesn't when I have changed nothing recently...

[jlobue10]

It actually seems to be a pacman related issue. While this is ongoing, I'd recommend that people use the Sourceforge installation method.

[jlobue10]

Please try the updated installer if you're still having issues. Sourceforge will be the recommended rEFInd installation method moving forward.

[johnlietzke]

Thanks for the update. Just this week deleted windows from the deck. Got a Legion go yesterday, don’t really know how I feel about it yet. There are a lot of incredible things about the Go but also a lot of half baked innovations, and an even worse UI than the ally.

[jlobue10]

Yeah I personally have been using the ALLY and really enjoy using Nobara on it. I know the ChimeraOS devs and community are working on fixing certain things up for the GO with regards to Linux. I was thinking about possibly getting a Legion GO and then the OLED Steam Deck was announced, so I decided to just go for the OLED Steam Deck.

[johnlietzke]

I will be returning the Go tomorrow. Placing my OLED order in a few minutes. On Nov 19, 2023, at 2:00 PM, jlobue10 @.***> wrote: Yeah I personally have the ALLY and really enjoy using Nobara on it. I know the ChimeraOS devs and community are working on fixing certain things up for the GO with regards to Linux. I was thinking about possibly getting a Legion GO and then the OLED Steam Deck was announced, so I decided to just go for the OLED Steam Deck.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>