Open ClaudeLib opened 1 week ago
Have you tried connecting your Deck to a charger first, and then using the button combination to reset the CMOS?
I think it only works that way now, possibly to prevent bricking the Deck when on low battery or something...
Compared to older BIOS versions, I noticed that you also have to hold down the button combo slightly longer for the bootup chime.
I did try resetting CMOS while plugged in, with a full battery, tried holding the buttons down for up to five seconds, no luck. Would be nice to have the release notes for BIOS updates, see which changes are intentional and which are not.
EDIT: I should've mentioned that the other button combos, like Vol- and Power button to enter the boot menu, or Vol+ and Power button (or holding Esc on an external keyboard) to enter the BIOS settings worked just fine on 131.
Your system information
Please describe your issue in as much detail as possible:
Unfortunately I cannot provide exact Steam Client and SteamOS versions, as I reimaged my LCDeck just yesterday (that was actually when I got the issue), but I checked for updates in the settings every morning when I was on Preview. The issue is that after I try to clear the CMOS by pressing the Vol-, ***, Power button combination, my LCDeck refuses to start. The white diode blinks, but the ascending three note bootup chime does not play and the whole device stays dead, until I plug it in (or if it's already plugged it, disconnect the changer and reconnect it again), at which point it starts up automatically. At first I thought this has to do with the battery, so I tried charge cycling it, I even tried disconnecting it from the motherboard to drain the capacitors and whatnot, nothing helps. In fact, out of curiosity, i tried doing the procedure with battery disconnected, it exhibits the same behaviour. Only when I tried manually downgrading BIOS to version F7A0121, the issue went away, my Deck would properly start up after clearing CMOS. Just to make sure, I flashed BIOS F7A0131 again and the issue popped back up again.
Steps for reproducing this issue: