Kit's "experimental"
Kbut we enable it OOTB
JOkay. I think I figured out why my monitors were not sleeping. I turned off VRR and it seemed to be fine
JI'm still testing it though
JI wonder why it would be causing sleep issues though.
JI don't know much about how VRR works entirely though
JI made an issue on the Bazzite GitHub but should I make one for GNOME?
Kyou'd need to test against stock GNOME, and yes
Kwe don't make the VRR for GNOME thing so that'd be the place
Kthat being said, I have VRR enabled and have no sleep issues
KI sincerely doubt this is the problem
JHmm. I'm not sure. VRR is the only thing I changed when I tested it, and it made my two monitors sleep. Before, the monitors would sleep for around 20minutes and turn on
KHad to reboot machine with HDR enabled, once I login I get a black screen. I’ve tried removing the json config files for displays but the only fix so far is to simply unplug the HDR monitor. If I plug it back in it blacks out both screens
KOk, going into tty and removing kwinoutputconfig.json, rebooting finally fixed it
RQuick question. Downloaded the newest bazzite-deck-stable ISO with the themed installer and fixed resolution. But, in the installer, it doesn't recognize the Wifi/BT chipset of my SD OLED. Does anyone know why that happens?
Kthe installer does not support BT, and does not have the OLED drivers for wifi
Kit's a fully offline installer so neither is an issue
Rbut it throws the -1 error after it tries to install. I'll try to remove all partitions from the SSD before I try to install Bazzite. Gonna do that real quick. Thanks though!
K-1 error can be a number of things
Kare you dual booting or anything like that?
Rno just one OS, but maybe SteamOS isn't completely removed
Ri am currently in the bazzite installer
RI'll repro the -1 error and tell you what exactly is happening
R"The command 'ostree container image deploy --sysroot=/mnt/sysimage --image=/run/install/repo/bazzite-deck-stable --transport=oci --no-signature-verification' exited with the code 1"
Kyeah, that's the generic error
Kmake sure you've wiped that drive
Rallright I'll try that
JI think you're right, yeah. I just looked and my monitors are on :dispair:
JDamn, I have zero clue what's happening. Fedora had no issues
M
Khow did you flash the ISO?
MISO mode rufus
KMight try balena etcher or fedora media writer instead
Kcould also be a corrupt download
Ri completely wiped the drive outside of bazzite and it now came up with the same error in the installer I had before. ISO is on ventoy btw.
Kventoy was recommended but is no longer required, it should work
KMaybe try fedora media writer as well
Kif the drive is truly empty there's not much else that can fail
Rhmm ok thanks for the quick help again
MIs checksum for KDE 6c546698171901f9985579c2d8d234a5d29c4818c3af09901bd17e0f5ed1998c ?
M
Kcan grab the checksum from the website
Knext to download button
Myeah I just cannot explain how I got borked iso
MI don't know can somebody help me out, bcz if it's correct checksum on website, then somehow I got broken iso twice
Ktry flashing with another tool then
WAnyone else running moonlight on Bazzite with a Rog ally?
Ri was just reading about moonlight but i have steam deck
KYeah this looks like a bad image/flash. If you've confirmed a good ISO image, you may want to reflash your ISO and confirm md5sum or sha256sum afterwards (Balena etcher should automatically do this)
KHuh looks like Lenovo is supporting the Legion Go til Oct 28, 2029. https://gaming.lenovo.com/legion-go/post/legion-go-update-08-09-2024-lD50griet21iYnZ
Legion Gaming Community
Hi Everyone, Thank you for your continued engagement and feedback, which have been invaluable in shaping the roadmap for Legion Go. I want to address some outstanding concerns that have been raised ...