I'd be curious to see what the EDID information of your monitor is
I'd be curious to see what the EDID information of your monitor is
TThe crashing, that is.
KCould? Though, if you did it would also apply to game mode once setup
Salienware aw3423dwf
SI know thats not the edid, but I thought I'd give you the model num
KToss your game mode logs here, they get made in your home directory
T@Kyle Gospo good news, the Game Mode session launched! This is a +1 for Bazzite-Polaris.
KBoth hidden
Sgamescope-stdout.log17.08KB
KKwithout a doubt gamescope thinks your monitor is 60hz
Kare you using HDMI?
Mthats the highest modeset for the aw3423dw
M3440x1440@175 is second
Mi would not be shocked if the dwf is the same but 165
Mi have to uncheck the automatically select resolution option and choose 3440x1440@175hz manually in the drop down list
KThis is without a doubt one of the dell moments of all time
Mi have the one you literally cannot update the firmware on
Mlike not even dell can
Mwhoops
LHi I just switched from windows to Bazzite. Is it normal that the bottom bar will just freeze when I have an app maximized?
KNvidia on KDE?
LYes
LAnd now it froze just because I opened the status and notification tray, and it doesn't seem to stop freezing (like before).
KNvidia is still a little buggy on Wayland
KFrom the login screen, select X11
KShould be in the bottom left
KI suspect you'll find that so much better experience in the short term
Tone day nvidia drivers on linux won't be garbage
Tand that day will probably come when the reverse engineered drivers are matured
Mhuh, dont think ive run into that one yet on kde
Mdoes it depend on theming?
Ta good way to test is if a nvidia user chooses the breeze theme instead of the default which is vapor
Tvapor shouldn't change that much to be causing this though?
TIt's funny, back about 12 years ago, they were the best experience because their drivers worked well on X11 and the others just kinda sucked.
Tyeah they were like the only ones who had proper driver support on linux lol
Tbut now that the other vendors have open source drivers, its the total opposite experience
TAnyone had issues with sleep recently? I’m running Bazzite-Polaris with the older Gamescope version, and immediately after entering sleep my fans will ramp up and the PC wakes again. There’s a good chance it’s a hardware problem on my end, i figured I’d ask first though.
QI have a slightly more philosophical question, since everything I've tried so far has mostly just worked. How are people managing machine configs long term, especially across updates? I've been using NixOS on my home lab servers for a while, and now every time I manually edit something on my new Bazzite gaming machine, a little part of my soul dies. It's only been a week and I already feel like I couldn't get back to the exact same state again if I reinstalled.
Achezmoi work pretty good for me, also usually update unless major wont break config right?
QI'm still using home-manager and nix to manage my personal home environment, but I meant system level things. Everything from hostname, to sshd and tailscale configs, automounts for my NAS shares, etc. All those little things you slowly build up over time. With NixOS, all that's described in a (set of) config file(s) that's built into a system, and the only way to "apply" it is to build a new generation and switch to it, so you inherently have a full description of what changes exist from the system defaults.
Afor that you can create your own custom image i think?
Ayou can just base it off bazzite and add things you need like package, configs, service, and such
QWould that be something that can sit atop the standard Bazzite
just updateif you fork you need to pull our changes
Kif you make an image FROM then every time it builds (shcheduled in github) your changes are applied on top of our latest
KBazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
QHrm. That's not quite the sort of workflow I was envisioning, but it might work. I'd have to use standard shell scripting or some other similar tool in the context of the Containerfile to put the various changes in place. I suppose what I was looking for was a ublue/bazzite sort of equivalent to Arch's aconfmgr.
Aif you dont like using containerfile directly you can use bluebuild and have your config almost declaratively
QOh, it wasn't really a problem with containerfiles. It's just the suggestion solves the problem at a different level than I had originally thought about approaching it. I was thinking of a tool that I would run on top of an existing Bazzite build to ensure that the things I wanted configured. A bazzite-aware Ansible role or as I mentioned, aconfmgr for ublue-based distros, or similar. I hadn't thought of making the image itself custom.
Acustom image in atomic/immutable distro are kinda equivalent to aconfmgr i think? because the normal distro way and atomic distro way are kinda different
