AMD Ryzen 7040 Series BIOS 3.03 and Driver Bundle Release

I had to have the computer plugged in, but be below 100% full, so the system would recognize that it was charging. I let the computer sit, unplugged until it was at 90% or so, plugged it in and ran the update and it worked. I can’t say for sure if that’s what you are running into, but it’s something to be aware of.

Yeah, I saw that folks were running into this. With some even trying different chargers and/or cables and/or USB-C modules. I only have the one charger that’s rated high enough for this, and perhaps the same for my USB-C cable (all the same brand and variant).

I got my laptop down to 96% and tried it, but still had that error. Perhaps that’s not low enough? I do see the light on the module flicker right before I get the error. Wondering if there’s some interruption there.

I also notice some folks mentioned their light being red. Mine is a whitish-green, if that matters. I have seen the red light before, but haven’t since I started paying attention to it.

UPDATE 01
Got it down to about 87%, the light’s now red / orange, but still getting error code 21

UPDATE 02
I’ve now tried a different USB drive and the 1 TB storage module. Neither has worked. I’m at a loss, because I don’t have access to any other chargers / cables, and I’d rather not purchase one hoping it works.

UPDATE 03
I tried my Anker 537 PowerCore 24K power bank (65 W) and it worked! I was able to do the update. Unlike with my Anker 737 wall wart, which took a 2 or 3 seconds to negotiate(?), the light was immediately solid when using the power bank.

I think, perhaps, we could benefit from the BIOS updater waiting a beat before checking for AC power, or before deciding it’s not available?

Because, if it wasn’t plugged in, we wouldn’t even get to the screen that throws the error code. If I remember correctly.

Chassis intrusion protection doesn’t appear to work for me – I asked on Discord and someone said that the red lights that flash indicate that chassis intrusion has tripped, but the machine happily boots (without asking for the BIOS password) despite having opened the device!

Edit: As I say that, I just got the password prompt on my last test, so I’m going to need to try and reproduce this.

Does anyone know if there is an option to disable AMD PSP?

The intrusion detection switch not meant to prevent you from booting up the laptop, merely to inform you that you’re operating on live circuits.

4 Likes

@mackncheesiest @ClaudiuIO @Rufo_Sanchez @Bumblebee @lengau @Matt_Hartley @Maxr1998
I didn’t see that this charging issue was already being discussed in this thread, I had the same issue and already opened my own thread (with a more detailed analysis) about this here:

According to current information, only chargers with less than 3A should be affected (so 60W and above chargers should work reliably).

As of now, it is unclear if it’s actually related to the BIOS/EC/PD controller firmware up-/downgrade, as the issues are intermittent (sometimes it just works, sometimes it works after a few retries), so reports of chargers working before and not working now may be influenced by other factors like state of charge and it just randomly working / not working.

Though no matter if it was broken or not before, this is something that will have to be fixed in future versions.

(Also, funny how the “Steam Deck charger” seems to be a very common PD PSU that Framework owners seem to have :grinning:)

5 Likes

Well, the audience might overlap quite a bit. At the end of the day the Steam Deck is just another repair-friendly Computer in a slightly different form factor. :wink:

This, and also maybe higher chance of an overlap than some random model Anker or whatever else charger found on Amazon :slight_smile:

So half of my RAM is missing. It only shows 8 of my 16 gig. Does anyone else has the same issue?

Check the physical contacts maybe

4 Likes

@LA-MJ Just did by removing the ram and adding it gain and now it does detect the 16 gb :blush:. Weird…

2 Likes

The memory pin layout for the AMD mainboard will result with one memory chip facing up and one memory chip facing down.

I did the AMD mainboard install (Friday-over weekend). I almost the same mistake with putting the memory on the left side of the mainboard.

Hi all, just received the AMD Ryzen 13, loving it so far. However… I’ve not been able to upgrade the BIOS to 3.03. Currently on 3.02.

When the machine reboots to do the upgrade, it gives me an error code “21” Additionally, whenever I reboot the machine the charge that came with the laptop no longer works. I have to unplug it from the wall and then plug it back in for it to register that power is being delivered to the device.

Is it possible this is causing the error (as the BIOS instructions say the device must remain plugged in - which it is, it just does not accept power when it’s been reboot).

Any help or advice gratefully received.

I just received my batch 4 AMD Framework. It shipped with 3.02 and I thought I would try updating the BIOS with the UEFI Shell option before installing an OS. However when I try it says “upgrade completed” and on reboot gives an error code “15” “Invalid Image”

Anyone else encountering this error? I have tried a couple different flash drives and fresh formatted them to FAT32 and secure boot is disabled, but no luck. In a bit I will try installing Arch and using the Linux/LVFS method. I don’t understand why the UEFI method is not working.

UPDATE: I tried another flash drive because why not and it worked! Not sure what the issues was, but error code 15 could be caused by the flash drive?

iirc this was in connection with charger compatibility. for some using a different charger helped, for others letting the battery deplete a little (to 90% or so) and then plugging in and doing the bios upgrade worked :slight_smile:

Is the 3.03 stable release, the same build as the beta release?
Or should I downgrade to 3.02 stable and then up to 3.03 stable.

The 3.03 stable release is the same as the beta release.

3 Likes

Just wanted to say, I was having frequent AMDGPU errors on Arch:

  • GDM Wayland failing at boot and falling back to X11
  • severe screen flickering when running games
  • display lockup when opening Steam or alacritty or anything else that used GPU resources
  • slow / unreliable video encoding

Updating to 3.03 via LVFS fixed all those problems. Thanks for releasing this update!

5 Likes

Thanks @Johannes_Hedtrich I’ll try a different charger and see how I get on!

Questions:
a. is it possible to configure the keyboard such that the function keys work as functions keys without pressing the Fn key?
b. is it possible to configure the BIOS such that the laptop powers on when opening the lid?