Arip that changelog is too big
Aone sec
Await
Kba is just fsync, beyond that
Kaffected stock fedora so fedora kenrel
Awhat was the previous kernel ver?
Amust have been 6.7.11
Aor was it ba? that build expired though
WWhich image did you use? How?
NWhere does deckyloader actually get installed?
A~/homebrew
PI used this
and then just replaced the gamescope binary with the one from chimeraOSv43-1
and then just replaced the gamescope binary with the one from chimeraOSv43-1
NI installed it using bazzite portal, but it did not create a desktop icon.
Ashouldnt i think
Ai think if you download it its a desktop icon
NOh ok, are we installing decky loader using homebrew then?
NStill getting used to switching over from traditional SteamOS to Bazzite 
Ano, they ship a .desktop file for normies
Athat executes under kde
Kwhat's the version of gamescope there?
Klast I checked we should be 1:1 unless they're testing the refactor
Achimera 43
Athats like summer times
PYes, its pretty old
Kah okay, this an intel handheld or smth?
Pand it is the last working version on gpd win2
PIt is intel
Kyeah OK that makes sense
Kthere's a fix for it in progress last I looked
Kintel is just in a rather unfortunate space w/ their GPUs atm
PDo you know which PR/issue is tracking that ?
PGPD win2 GPU is pretty old iirc is UHD 615
PI do have an iris Xe GPD win3 but I have not tested it yet
Aspeaking of win mini
A2024 lineup of gpd devices ships the same dmi
Abut win mini has the ally screen
Aso needs different quirks
Ahonjow is on it
K3466 doesn't work either :( I'll try 3200
KI don't understand
KI have the manual ram speed set to 3466 and the FLCK at 1733 because it's half of the speed right?
KWait
KGot it
KI can't get more than 3200 on this board
KEven tho it says it should support 3466 on those tech documents
WAfter typing in the terminal:
ujust enroll-secure-boot-key
It says key is already enrolled, but I don't see the blue screen with the option to ENROLL MOK.
Any ideas?
ujust enroll-secure-boot-key
It says key is already enrolled, but I don't see the blue screen with the option to ENROLL MOK.
Any ideas?
Kdid you reboot?
KMOK enrollment is through your BIOS
Kit'll ask on the next boot
Kinstaller works the same way
