KWhen is the last time you updated?
RThrough the terminal? Not positive, but maybe some time last week?
RI get the feeling the cursor is normally supposed to blink, but it's not, which makes me think it's freezing when it gets to the black screen.
KNot seeing many changes on main in that timeframe, seems suspect two different devices on two different builds are affected
KI'll try and reproduce it here, but so far both my decks are fine
RNot sure if an update caused it. I was just using the Deck normally and decided to restart This just started an hour ago.
RDidn't use any rpm-ostree commands
RManaged to get what it says before it goes black
RThen it just looks like this afterwards. Cursor not blinking.
KHave you made any changes recently?
RNot that I know of. I was copying files over to another hard drive as a backup
II wonder if I set the default uefi boot target to the wrong entry.. I've got two for some reason, one that just gives a blinking cursor (like the above, just.. blinking) and one that boots fedora properly.
rpm-ostree statussha256:814cefa14e134b6c5b9fb57fb1b6a6db46ce70d7f771e88b2676d8cc031eeeb6 (with a dot, is that active?) and sha256:61f2d030e03d45430d249039e235e2b3ad83e77c4a153dfd172ca270b69b4f29
RSpam the three lines button.
RThat's the escape key in the controller.
RThat will bring up the grub menu.
I@rogerlovesyou
RThe three lines button.
RTo be clear in Deck terms XD
IShould’ve turned off reply ping for that one but oh well
RNo that’s helpful I’ll give it a try.
IYeah looks like that was it. I am getting
/etc/sudoers.d/nix-sudo-env: spam on sudo again thoughRTHAT WORKED. I was able to get into some other selection on grub
RGuess I'll keep backing my stuff up and get ready for a reinstall or something...
RThanks @rodoma92
IIf it was still bazzite, I think you should be able to use rpm-ostree to remove the one that won't boot and try again later?
RYeah it's still bazzite
ITheoretically that's one of the big upsides of this, if a new image won't boot it doesn't super matter because the previous one still does
RAhhhh, handy
RWell at least I know how to access it now
RIs this what you're referring to? That there's two of these?
RWhen anyone sees how do I get rid of the one that isn't working (assuming it's the one that says 11-21)?
RAnd should I update?
ROr will that just break it again?
RI only ask because I figure maybe something went wrong the first time it did.
IYep, but I don't know how to get rid of the new one though, or if you need to :p
HIs there a way to calibrate the joysticks on the legion go? I know there's a terminal command you can run in steam os, does it work on bazzite? Already tried adjusting the dead zone sliders and it seems to have helped a little but feel like it could be tighter.
TIs steam-patch broken again? I tried using PowerControl too and it seems that it hasn't been fixed yet either for Non-Deck devices
Ahow is Ally support coming along?
VNew kernel soon which should fix the controllers (afaik)
MTrying out bazzite. Retired my work desktop and setting it up as an htpc. Rebasing is awesome.
ROut of curiosity, which desktop is everyone using? KDE or GNOME?
KControllers work in :testing
KAudio needs a fix
Aon the deck image?
A@nielsjuh01 ^^^^^
Dis :testing ahead of :latest?
KYes
Kbazzite-ally:testing
KThat does work in bazzite but as far as I'm aware it's specifically for valve hardware
KAnd it's written to the firmware itself
