ryanrudolfoba / steamdeck-bios-manager Goto Github PK

When messing with memory overclocking I might have to clear CMOS/Reset a few times and re-do the process of unlocking the BIOS over and over again. Some users might already have their BIOS Backed up, so it'd be nice to not have to go through the process every time you flash the BIOS or everytime you unlock it.

Through H20UVE It's easy to see there's much more options inside "Advanced" menu, like setting NumLock on by default on boot and so on
Is there any possibility to expose these options out for tweaking? (Really need NumLock on by default)

Hi, I created a shortcut on my desktop to start the bios manager according to your comment on Youtube and it works fine. Can the script be modified so that I don't have to enter the password or so that it is entered automatically?

When selecting the different bios versions in the flash window, the program doesn't list the version numbers.
Every file just reads "BIOS" in the program, even though the files are properly named on the system.
So, at the end, it fails with the error: Open file failed. (path="/home/deck/bios/SteamDeck-BIOS-Manager/BIOS/BIOS")

I've just experienced a BIOS write failure. [EDIT: the deck has become responsive again on its own about an hour and a half later and completed the BIOS installation.]

The deck was on stable channel OS 3.5, BIOS 119 as of yesterday. Followed the steps outlined in the youtube video, with no issues until the final step. (Cloned SteamDeck-BIOS-Manager from git, made script executable, ran script, performed manual backup out of habit, downloaded BIOS files, blocked auto-updates, selected BIOS v116 to flash.)

Upon starting the write command, the script began backing up the BIOS. I was looking at another screen when progress hit 100%, but I did notice the screen turn off after a reasonable period. At this point, the steam deck remained turned off - the charging indicator remained lit, but all plugged in peripherals (a mouse and keyboard) remained dark, and there was no audible fan or system activity. After ten minutes of silence I tried prompting it to wake up with the power button without success. I also tried the CMOS reset key combination, just in case, and did hear the three tone chime but noticed no other activity from the deck.

Possible contributing factors: I have reflashed the BIOS with a chip programmer in the past, using the methods described here, although it has been stable for months and recently updated to 119 successfully. Undervolt settings at the time of the issue were adjusted through the setup menu to -50/-40/-40 (they were -60/-40/-40 before the 116-119 update.) VRAM was set to 4G, but all other BIOS settings were stock, presuming the 119 update overwrote all the now-inaccessible settings. No other bootable media was connected to the deck. The only other system settings altered are those collected here, except for the retbleed mitigations. The only hardware modification is the Jsaux Vented Backplate.

Not sure if I've done something incorrectly, or if there's a sneaky conflict in here somewhere, but I hope this feedback helps. I'm just going to go ahead and flash in my backup manually. I'll be doing this overseen by the same expert who walked me through it the first time, but for RL reasons it might not be soon. I'll attempt to reproduce these steps while I've still got the case open and the clamps handy to see if it happens again.

EDIT: I am at an absolute loss as to what's happening. I was about to put the deck away and thought to hit the power button one more time, and the deck turned on and the update is progressing. It is two hours and several attempts later. Update complete, 116 is installed.

This was certainly strange. I did time it to ten minutes of unresponsiveness, and I did attempt to power it on several times after that, so something weird was happening, but I'm at a loss.

Root user password check doesn't work on Bazzite.

Running the script on Bazzite fails with Sudo password is blank! Setup a sudo password first and then re-run script! providing a password here does seem to work, but upon running the script again it is still unable to detect that a sudo password has been set.

Removing the password sanity check section before running the script results in a normal superuser prompt, followed by the script working as expected.

What's New (as of February 10 2024)
Added BIOS F7A0121 for LCD model. This BIOS version allows for overclocking!

This appears to mean that the F7A0121 BIOS supports Overclock.
However, your program's SMOKELESS menu says it only allows BIOS 110 to 116.
How do I unlock 121 Bios?