My Deck doesn't respond at all on this black screen
My Deck doesn't respond at all on this black screen
ITry holding volume down and pressing power button to turn on. Or maybe ... and power? Idea being to find the boot or grub menu to be able to select the older image.
RHow can I tell what's the older image?
ICouldn't tell you. Try one then the other? :p
RBoth boot to the same black screen.
IHave you been able to boot in successfully at all yet?
RI was booting just fine since I initially installed in October.
RJust restarted and...black screen
IAh, no idea then. :\
RThanks anyway.
RHopefully a dev sees soon.
KJust updated both my devices, no black screen
KGonna need more info, logs especially
RWas using my Deck in desktop mode, decided to restart, it powers on and shows the bazzite logo and wheel, but afterwards shows the little words when it's booting things and it shows the the CUPS scheduler failed to start. Then the screen goes black with a text cursor. It doesn't blink and pressing anything on my keyboard doesn't do anything.
KControl+alt+f4 on your keyboard
KThen you should have a terminal to get logs
RNone of the function key combinations do anything.
RTried Ctrl+AltF1-6
RReally 1-12
ISame.
IWould they be accessible to me somewhere since I can boot the older image?
KYeah, same as usual
ISorry, where's that?
KAre you on latest or testing?
ITesting.
RI'm on Latest
KSame here. LCD?
Iamd/radeon desktop
KI see
RI'm on an LCD
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 status lists sha256: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 though