UniversalAMDFormBrowser has not options for steam deck in last bios version.

[l33tm4st3r]

Last update bios update (115) for steam deck, seems to disable or erase hiden options in bios. So UniversalAMDFormBrowser can't read it.

Any solution with a new UMAF or just we need to do a bios rollback ?

[Cederick]

Also just encounterd the issue. Would a BIOS dump help with figuring out what's going on?

[marcoand75]

Same problem with latest 115, downgraded back to 113, all work again, i hope someone fix it for 115

[bl4k1st]

Same problem with latest 115, downgraded back to 113, all work again, i hope someone fix it for 115

could you please post a link to BIOS 113?

[marcoand75]

F7A0113_sign.zip
https://gitlab.com/evlaV/jupiter-hw-support/-/commits/master/usr/share/jupiter_bios

[Cederick]

Isn't 115 necessary for the SMT fix?

[marcoand75]

Isn't 115 necessary for the SMT fix?

I use steam deck tools for disable when need SMT in this moment. I don't know the change log of 115 bios version.
I prefer to wait to go ahead and try to find more information on 115 because with TDP unlock and increase in CPU and GPU frequency I'm so happy 😊

[syberphunk]

Isn't 115 necessary for the SMT fix?

No. That's a linux kernel fix, not BIOS dependent.

[Cederick]

Well the big feature of 3.5 is fixing SMT so you don't have to disable SMT for the gain. You could just revert back to 3.4.6 then.

[marcoand75]

i forget to write it, i'm on win 11, i left steamOS after few days after i received the console.

[DavidS95]

See if the newest version of UMAF uploaded will solve the issue. If it still does not work I would recommend staying on an older bios.

[l33tm4st3r]

Not works for me. Thx anyway :)

[l33tm4st3r]

Also, RSEP.log

Welcome to SREP (Smokeless Runtime EFI Patcher) 0.1.4c
Opened SREP_Config

Config Size: 0x4E
Parsing Config

Stripping NewLine, Carriage and tab Return

Current Parsing Op LoadFromFS
OP Detected

Commnand LoadFromFS 
Current Parsing SuppressIFPatcher.efi
Found File SuppressIFPatcher.efi 
Current Parsing Op Exec
OP Detected

Commnand Exec 
Current Parsing Op LoadFromFS
OP Detected

Commnand LoadFromFS 
Current Parsing Loader.efi
Found File Loader.efi 
Current Parsing Op Exec
OP Detected

Commnand Exec 
Executing Load from FS

Loaded Image Success -> 6C778000
EXEC %r

Executing Load from FS

Loaded Image Success -> 6C777000

[Cederick]

Can report the same result

[BlankUserLing]

115.txt
113.txt
AMD CBS：
Offset has changed

[Cederick]

Hope that this is the nessesary information to create a fix.

[Haxorzz]

i wonder if anyone can create a pull request and fix it manually using this

[CryoByte33]

Has there been any progress on this? I'm hoping that we come up with a solution before it hits SteamOS stable 🙂

[Cederick]

So does reddit https://www.reddit.com/r/SteamDeck/comments/128nui6/steam_os_35_did_reset_bios_and_made_it_impossible

PS: Your CryoUtilities is unusuable when opened docked to a 1080p screen because it does not scale the window size correctly (waaay too large)

[CryoByte33]

Obviously, I was more asking if I can help 😅

As for CU, we're working on a fix, the issue should fix itself if you set the external monitor to primary, if not please open an issue!

[Mario-119]

Oh good I thought this was only me, hopefully this is fixable in due time

[ghost]

UPDATE:

The only addition to the steam Deck CBS/PBS Dxe in BIOS is:

  (*gBS->CreateEventEx)
                    (0x200,8,(EFI_EVENT_NOTIFY)&UnistallProtocollFunction,NotifyContext,
                     &EFI_EVENT_READY_TO_BOOT_GUID,&local_res10);
        }

Given that UMAF ofc is loaded after the READY_TO_BOOT, they used the READY_TO_BOOT event, to call a function that uninstall the form...

I could bypass this in varius way, by manually reinstalling the FORM, or by some other trick...
But for now I don't plan to...

I'm writing this here, just to make sure that no hope is created around an up-to-date UMAF..

[l33tm4st3r]

https://gist.github.com/SmokelessCPUv2/8c1e6559031e199d9a678c9fe2ebf7d4

@SmokelessCPUv2 Thanks dude. Works like a charm.

[JDGBOLT]

Only thing that I'm going to say is that Valve is most likely going to patch this out in the near future. This will be even more digestible to ordinary folks considering it's run this binary and you unlock the uefi, no need for even flashing a utility on a usb stick, just run binary and go into uefi.

I would request that everyone don't just go crazy making tons of youtube videos and guides on undervolting the deck using this as there can be a very real possibility of the uninitiated to break things by just seeing some youtube video going "Free Performance!" with just running the binary, messing with settings purely based off of what is going on in the video, and then rebooting their deck to have it be a brick unless you reflash the uefi chip on the board.

And you will have people who reach this point without accepting the very real risks by just following along in a guide inevitably reach out to Valve who has been good about RMA'ing decks, perhaps a bit too good on this front, so people view it as just an out in case they mess up, which it really shouldn't be. This then makes them try to lock things down in order to protect people from themselves and not have to deal with the headache of people crying to them when they break things.

Honestly within the binary itself there should be warnings and other messages that you use this at your own risk, don't go to valve if you mess up, and here be dragons essentially.

[ghost]

Also i would add to this,
@rnwgnr (or @DavidS95 if you have the permission )can you remove the binary please, i think that if someone is not able to follow the instrction on how compile it, shouldn't use it..
Or at least let's don't have binary so public...

Also i would this now is far off topic and not related to umaf anymore, so @DavidS95 i think you can close it.

[TarnishedWorker]

Thank you for the solution, and it works!

I noticed that for the settings and values that have already been presented in the factory BIOS menu, if I changed those in the CBS menu on my own, they will be overridden back by the factory settings.

For example, Steam Deck's factory BIOS allows us to change the TDP settings under the Advanced menu, up to maximum input of 15,000mw. Now if I go into the CBS menu and update the TDP settings (slow and fast) to go beyond 15,000mv, and when I hit "save & exit", it will actually save the Steam Deck's default maximum values (15,000mv) rather than the values I prefer (e.g., 25,000mv).

Is there any way we can solve this problem?

[rnwgnr]

Also i would add to this, @rnwgnr (or @DavidS95 if you have the permission )can you remove the binary please, i think that if someone is not able to follow the instrction on how compile it, shouldn't use it.. Or at least let's don't have binary so public...

I have removed the binary.

thanks for your efforts anyway 👍