Many issues with dual-boot setup on Lenovo Legion desktop (Intel CPU/Nvidia GPU)
Hey there! I was looking forward to using Bazzite. Got it installed and dual-booting, but I've run into a litany of problems. Most of them are minor but I also can't get games to play, so that's a relatively major one. 😅 Here's a list of what I'm experiencing. Maybe someone can chime in with ideas for how to overcome them.
1. Display settings reset on every reboot. I've only booted 3x so far, but each time I have to go into my display settings to set the scale to 200% and turn on HDR on every boot so far.
2. New entries in grub on most recent boot. On my first boot, I had two entries for Bazzite. (BTW, why two?) On my next boot, I had four. What does it mean?
3. Trouble installing 1Password. I downloaded an RPM for 1Password since that's what they recommend for Fedora. I was able to install it using DNF, but then it didn't work. Clicking the shortcut just brought up a message that it couldn't be found. I then suspected that maybe something about the nature of Bazzite meant that RPM was not the ideal installation method, but I don't think anything in the installer or onboarding said that explicitly. I wanted to remove the RPM and try another installation method, but the
remove sub-command tells me it's not implemented. I tried right-clicking on the shortcut and found an uninstall command which apparently does nothing. I'm not sure how to back out of this and what I should do as an alternative.
4. The Steam window flickers partially and reveals whatever is behind this. This is intermittent and it doesn't affect the entire Steam window. Parts of the window will disappear revealing whatever is behind them. It's very strange.
5. The biggest issue is that my games will not run. I launch them, which will sometimes trigger Steam to download things, but even after all the dependencies are downloaded, the game still won't launch. I click play. Steam says "Playing." The game never launches, and the play button is restored as if I never clicked it. (cont'd)15 Replies
Important note on games not launching: I'm trying to test the waters with Linux to see if it could become my daily driver on the gaming PC, so I resized my partition, and I've added my Steam libraries from a couple of NTFS partitions to my Bazzite Steam install. Maybe this is the issue, but this would be my ideal setup while I audition it so that's what I'd like to have working.
Corollary to this one: every time I boot, my libraries are gone. I have to re-add the libraries from the NTFS partitions.
What I did was add the drives to my /etc/fstab file so that they are mounted automatically and that they are mounted as my user (uid=1000,gid=1000). Be aware, that if you ever uncleanly shutdown, you'lly have to use ntfsfix to or else they won't mount, or will mount as read-only. If too much corruption happens you'll have to boot into windows have it it do a disk scan.
Hey,
This video should show you a safe way to have your drive automount so you don't have to keep remembering to mount it yourself.
https://youtu.be/JS0Jd_DNXdg
Chris Titus Tech
YouTube
How to Mount a Hard Drive in Linux on Startup
This video goes over how to mount a hard drive in Linux on startup and making it usable for your user. I simplified this so you don't have to remember a lot of different triggers for editing fstab and making it safer by having fewer things to go wrong with an fstab edit. I highly recommend doing it this way unless you have multiple users in your...
For point 2,
Bazzite is image based. You always keep two images, the current one and the previous one. This way, whenever you update your system you always have a working image you can revert back to and your system will always be able to boot. The fact that there are 4 entries might mean there are duplicates. In a terminal try running the following command in the terminal.
ujust configure-grub
For point 3,
Bazzite is based on Fedora Atomic. The main filesystem is read-only, thus you can't install packages to it so simply. You can (although it's not recommended) install RPMs using
rpm-ostree install package.rpm
This would then layer the package onto your image and make a new one and you then reboot. However, with immutable distributions like Bazzite it's recommended to install packages in an alternative way. Here's what you could try instead:
1. Make a Fedora distrobox container,
distrobox create --image registry.fedoraproject.org/fedora-toolbox:40 --name fedora40 --nvidia --init
2. Once you've created it, enter the toolbox
distrobox enter fedora40
3. This distrobox has access to your home directory. In this terminal, you can install the 1Password app exactly as they say on their website for Fedora using dnf
4. Once it's installed, you can now run 1Password from your regular system by running the command
distrobox-export 1password
You'll also need to run echo "xhost +si:localuser:$USER >/dev/null" >> ~/.distroboxrc on your home system and then restart the distrobox. Once you've created the distrobox you can use the application BoxBuddy and restart it easily if you don't like the command line too much.
This should now work!
To address point 4 and 5, the flickering in Steam is a bug with Nvidia graphics cards on the Wayland display server. It should be fixed really soon, just waiting on the update to enable explicit sync (see https://9to5linux.com/developer-explains-why-explicit-sync-will-finally-solve-the-nvidia-wayland-issues). When you login, in the bottom left you can click the Desktop button and change it to X11 and this will resolve the flickering bug.
No games launching is odd. Could you tell me which games? I can also show you some screenshots of things I regularly do to get Steam games working on Bazzite.
Marius Nestor
9to5Linux
Developer Explains Why Explicit Sync Will Finally Solve the NVIDIA/...
KDE developer Xaver Hugl explains why the explicit sync protocol will finally encourage the Wayland adoption among NVIDIA GPU users.
In the Steam settings you can try changing the 'Run other titles with' to some other version of Proton like Proton Experimental. You can also try installing other versions of Proton like the one I have here using the tool ProtonUp-Qt (you can get this from the software app)
The other thing you may find helpful is to go to https://www.protondb.com/, search your game and read what others have done to get it working.
Thank you for all of the help! I will try out some of this advice tomorrow.
I was trying to run Baldur's Gate 3 for starters, mostly because I wanted to see if HDR was working, and I know it has a decent example of it on the title screen. I checked that on protondb and found this that looks promising: https://www.protondb.com/help/troubleshooting-faq#games-stored-on-my-windows-partition-ntfs-wont-start
for me, in order to get my ntfs libraries to work with proton, I had to symlink my ~/.steam/steam/steamapps/compatdata to the steamapps folder in the Library on my ntfs drive. You can copy the symlink too multiple ntfs drives, it's tells steam where to store the wine/proton prefixes, and for some reason, they don't function well on ntfs
they dont function because
: is an illegal character for files and folders on ntfs and will cause filesystel corruption, the symlink workaround is also not really recommended as there have been reports (to valve) of that still causing issues and will invalidate any game issue reports to us.Please note that we literally cannot support you if you go out of your way to use NTFS
There's a reason it's not supported and it's a nightmare for us to deal with
@Kyle Gospo Do you have any ideas on my first issue? My display settings reset every time I restart, and I can't see that this would be related to my NTFS libraries at all.
dont know about that one, we answered about the 5th one since it is well documented
@RadDevon There seems to be a comment where someone also has a dual boot setup facing the same problem as you. Hope this helps! https://www.reddit.com/r/kde/comments/fnwn5l/dual_monitor_settings_reset_on_reboot/
Ah, wonderful. This looks promising. Thank you!
I tried to save from the NVIDIA control panel which was one of the suggestions in the thread @funky shared, but it didn't have all the display options. I found that this is the case on Wayland. I switched to X11, and the display settings are saved even if I use the system's panel. (BTW, "scale" isn't an option in the NVIDIA panel, and I'm not sure how to achieve it given the options that are available there. Not important since the system panel works fortunately.)
I tried making some changes directly to the X11 config in hopes that might lock in the scale for Wayland, but that left me unable to boot. I had to swap to a different session and delete my new config file in order to be able to boot back to the GUI. Any suggestions what else I might try here to get the display settings to save?