You can just pin your other deployment and boot from that
You can just pin your other deployment and boot from that
KOr
rpm-ostree rollback
KOkay, I'll google how to do that. I was trying to get into GRUB but couldn't figure out how
Pif I used
rpm-ostree usroverlay --hotfix to test a different gamescope version, how can I revert to locked install + update to latest gamescope ?
Cside note, 555 is on
:stable
WThat's right.
WErr, sorry I'm using :latest. Not :stable.
WBut that might still answer your question?
CProbably
K@Kyle Gospo is there some way I can collect a log or something to file a bug on github? Cause something broke between last build and this one, or I had some weird error - I guess, if someone else has a Legion Go and could test booting into Game Mode plugged into an external display it'd quickly determine if it's just me or the build I suppose
KAll I know is got home, powered on my Go, and had 3 black screens til I unplugged my USB dock. I rebooted twice, same issue both times.
KDoes the same thing happen on the desktop?
KNope desktop mode is fine
KI'm on it right now, all 3 (2 ext, 1 internal) are working.
KSo I can get to a usable state desktop or handheld, but if I switch to game mode I can't use my big display to game on 'docked'.
Kin docked game mode only 1 of my external displays normally works anyways (and the Go's internal one shuts down) - so that's fine, but for some reason the Go's display is turning off but netiher of the externals are coming on. Also, they ARE both on during boot, it's only after game mode starts that the issues happen.
PDoes latest from bazzite have this ?
AThe latest bazzite gamescope ver is too recent
AWhy do you need to know the ver
KQuestion: is there any way to "factory reset" bazzite? I have a mini PC i need to send in for service and I dont want to send it with any of my Steam data still lingering on it
AJust nuke the drive
AUnfortunately no
KDelete your user
KNo we don't ship an option for that
KBest thing to do is just remove the drive
KOr to be more exact, make a new user first than delete your user
KBazzite is on the latest tag of gamescope
KWith patches from Chimera OS and some homegrown ones
PI replaced the old gamescope version I had installed on my win2, as per previous bazzite, it didnt work.
I want to update to latest one to see if the default now works of if I still need to use an outdated one
I want to update to latest one to see if the default now works of if I still need to use an outdated one
ATry the latest tah
PI replaced it by doing
sudo rpm-ostree usroverlay --hotfix
curr_gamescope=$(which gamescope)
path=$(echo "$curr_gamescope" | sed 's/\/gamescope//')
cmd=$(echo "cp ./gamescope ${path}/")
echo "Replacing gamescope to working one v43-1"
sudo $cmd
PAnd now, I tried
but it still uses my version, not bazzite one
rpm-ostree resetbut it still uses my version, not bazzite one
AImpressive
ARebase to the latest ver
Kwait , you did
usroverlayUse a different level if you have to
Kthat only applies until you reboot
Kit's a temporary overlay
Photfix makes it permanent
A*pabel
A*label
AStroke
Kew
KI have no idea how to undo that
AMakes too much sense @j0rge nice
ABazzite when
Prebasing to latest (40-stable-20240630 ) will check once it finishes
Ahuh, i had no idea about the --hotfix flag. that'll be useful to know about 
PYeah, I found it to make my device work 
Jif you get me that json thing I filed in main so we have structured versions of packages we can just wire it up to the website
Jso that the bazzite on can show hhd, mangohud, gamescope versions, etc.
