Jso uhh
nothing useful
nothing useful
Anice, just wanted to make sure
Athanks for the quick work on the fix 
Jif you have anything else
Jshare it before i'm done installing Metal Gear Online
Jfeel free to judge the cables
this is my test desk
this is my test desk
Awhen urn not on bazzite and you dont upgrade for a century
Almao
Aill update when i want dammit
Qis there some kernel parameter for amdgpu or something that can just completely disable HDR display support?
Aw console of its time lol
JI dont think there is one
Jthe day they port MGS4 to PC
Jit will go back into the closet
Joh my god
they recommend linux-fsync-nobara-bin for HDR on Arch
they recommend linux-fsync-nobara-bin for HDR on Arch
Jwhich isn't even nobara
KHAHAHA
Ahey that kernel works, but man that integrity check come on 
JI am tempted to log in and inform them that its not the nobara kernel
T
Momg they list valve's neptune 6.5 kernel now too 
Mthat was there last time i checked
Mwasn't**
Mi was told to definitely not use that kernel which is pretty amusing
Qhttps://github.com/ValveSoftware/gamescope/blob/3.14.0/src/steamcompmgr.cpp#L2958 wow I really do run into all the fun gamescope fail states don't I
Mhardware specs? and on bazzite's gamescope or gamescope-git?
Msince that’s the same error I get on Gamescope-git with all AMD hardware
KBazzite scope
KAnd AMD GPU, yea
Qalso AMD GPU here - with bazzite's gamescope, also looks like that is in the latest stable release
VQuestion for you all... Getting a SD inspired me to get back into Linux after being away for like 15 years. I've got light development background but not with Linux specifically. Reading through much of this chat over the past few days, I find that I can't follow the nuances of the discussion and I'd like to fix that.
Where would you all suggest I start if I want to begin learning uBlue/Bazz in a way where I'll be able to effectively troubleshoot things once I make the switch over to Bazzite on my SD OLED?
Where would you all suggest I start if I want to begin learning uBlue/Bazz in a way where I'll be able to effectively troubleshoot things once I make the switch over to Bazzite on my SD OLED?
MIt’s spreading :frog_sweat:
KOLED has issues with frame control and a random audio driver crash, id hold off a bit
KLCD Deck works perfectly
VI'm aware of the bugs, I just want to learn
Qaudio on the OLED deck seems pretty quirky even on SteamOS lol
KBoth bugs should be in the kernel, hard start but gathering logs is always helpful
KThe frame control thing is an issue in DRM, which has very verbose logging if explicitly enabled
KAnd it broke around kernel 6.2
Teven on the LCD on the beta branch with SteamOS for me
Ti put my deck to sleep the other day and woke it up to garbled and double speed audio
QI've had garbled audio too occasionally, and also the way they are doing volume control is terrible and/or broken
Qjust bit crushes the audio to hell if the volume is too low
Mjoshua even told me there's nothing special about sd oled drm which makes things more confusing
KWell Joshua is about to find out what it is with that 6.5 port
KCan't wait
MSame, it’ll be nice to not feel like I’m taking crazy pills
MI’ve been waiting for the drm refactor to be completed before pinging again about gamescope-git failing (if it still does by that point)
MI checked last week after pt. 1 and there was no change in stacktrace
Qlol I can’t read, that commit was a different thing
