$ doas ryzenadj -a 43000
detected compatible ryzen_smu kernel module
Sucessfully set stapm_limit to 43000
$ doas ryzenadj -c 43000
detected compatible ryzen_smu kernel module
Sucessfully set slow_limit to 43000
$ doas ryzenadj --apu-skin-temp 43000
detected compatible ryzen_smu kernel module
Sucessfully set apu_skin_temp_limit to 43000
Did you select performance mode? This should set both stapm-limit and fast-limit to the maximum of 53W.
Happy to hear though that the slow limit still works. I don’t think its an intended feature to run the low power U skew at 43W instead of 28W all the time and it wouldn’t be the first time that a CPU manufacture takes away feature after purchase…
powerprofilesctl set performance sets stapm-limit and fast-limit to 46.0 for me. I was still unable to manually set it however.
Probably not. These were just his requested test settings from the last bios thread. I have unfortunately never had the time to look into putting together a set of ryzenadj configs for my purposes; I just have it installed from back when I discovered it and thought it useful.
Via the AMD PI update? That would be disappointing.
after running fwupdmgr update on my Framework 13 (AMD 7040 series) to upgrade to version 3.16, my external monitor stopped working correctly in Ubuntu 24.04.
The monitor now appears as “Unknown Display” in display settings.
It is limited to 640x480 resolution only.
This issue started immediately after the firmware update.
Kernel version: 6.14.0-28-generic
Has anyone else seen this problem after the latest firmware update? Does anyone know how I could address this issue?
Many thanks in advance for your help!
EDIT: I tried booting into the 6.8.0-1032-oem kernel, and with that version the external monitor works normally again — it is detected correctly and full resolution is available. So this seems to be a kernel/driver compatibility issue rather than a problem with the 3.16 firmware itself.
Argh! Only recently did I solve a problem whereby LibreOffice’s Impress would hard hang the system when displaying some particular slides onto an external monitor. (See here.) And now . . a BIOS update messes up external screens (and might also lock one out of the BIOS)? Lord above!
Currently I am on kernel 6.8.0-1032, non-OEM, on Linux Mint 22.1 (which is based upon Ubuntu . . 24.04). How, please, does one get the OEM kernels?
Thank you. I appreciate your taking the time to supply that information. Perhaps I will use that information at some point; for the moment, I shall wait in the hope that Framework provides a less buggy BIOS.
That’s odd, because support contacted me about my battery flipping ticket (which is still open) and suggested I try installing this BIOS to see if it fixes it.
However, I see that there’s a lot of issues with this BIOS (FN lock? Supervisor password breaking? USB-C display out breaking!?) so I am going to skip this one
That sounds a bit wrong to me. But I mainly learnt about these things before secure boot existed. Isn’t the kernel a part of your OS? Does the OS now always have to use the BIOS (aka UEFI) to load things securely? That sounds unlikely to me.
For Linux the bootloader would usually be grub and OS would be the Linux kernel who will detect and load the drivers for your hardware and then start the init system. The init system will in turn start the services required to bring up a graphical session.
The UEFI does do some device initialization and load a minimal set of drivers to get its UI running but AFAIK the drivers part gets thrown away when the Linux kernel starts and it will load its own drivers for any device found on the machine.
My external display stopped working with kernel 6.14.0-28-generic after updating the BIOS, but everything works fine with 6.8.0-1032-oem. My laptop’s internal display has always worked, so the problem only affects the external monitor. I think this suggests that it is mainly a kernel/display driver issue rather than a firmware issue—the firmware may have only exposed an incompatibility with the newer kernel’s display drivers. If you are stable on 6.12.15, it is probably best to stick with that for now. I’m no expert on BIOS or kernels, but if I can help in any way, please let me know.
