Framework 16 BIOS update 4.03 PD error screen and half USB ports stopped working

Community Support
, ,
1

I just updated the BIOS to 4.03.
My machine is a Laptop 16 (AMD Ryzen 9 7940HS w/ Radeon 780M Graphics) with an AMD Radeon RX 7700S GPU unit.

I followed the steps in the linux guide:
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update

Upon rebooting the machine shows a screen saying that I need to manually update the bios because the PD version is not the expected one. I can press the power button to boot the machine. However, none of the USB ports on the left side works at all.

The screen saying my PD version does not match has a QR code leading to the same instructions I already followed. When I try to update the bios agian it says it is already on the latest version and there is nothing to do.

No matter how many power offs I do I can’t get rid of the screen saying my PD version is wrong, the GPU does not work, the USB ports on the left side (all of them) does not work and I can’t update.

Please help, my laptop is only half working :frowning:

2

Have you tried disconnecting all devices on the left side and repeating the fwupdmgr update step?

3

Thanks for the tip but I tried that. The fwupdmgr update just says that my devices either have no updates available or are already up to date.

However, I powered off and removed the USB modules several times and suddenly they started working :person_shrugging: I literally did nothing else than remove them and reinsert them in different slots. Power on and try again several times.

I still get the annoying boot screen saying my FD2 firmware is not the expected version and that I need to install the bios manually. Which I don’t know how to do other than fwupmgr which does nothing.

4

The EFI update method is probably what is needed in this case. There is a description in the BIOS page for the latest version on how to perform it. Try reaching out to support for additional assistance as this is a partially applied BIOS update gone wrong. There may be a bug in how it is scripted in the fwupmgr.

5

Thanks for the tip! I have contacted support. I’ll update this thread if I hear from them or if the EFI method works

1 Like
6

After some back and forth with support, cleaning interposer contacts and resetting the mainboard, they also suggested the EFI Shell Method. It ran the update but seems to not have been able to update the PD2 Firmware, basically it just reinstalled what fwupdmgr already did but I still get the error screen on boot saying that the PD2 version is 0.0.1e but it was expecting 0.0.21
Waiting to hear back from support about what possible next steps can be taken.

7

It is getting an abnormal result and the script for installing the PD2 is getting bypassed in their default script file.

Maybe ask them to write a special script that you can put on the EFI drive that will involve the PD2 and force the update manually. It is seeing a version mismatch but it is not executing the upgrade to that side of the mainboard.

8

That is a good idea and I wish it could become reality. This is the latest I got back from support:

“Thank you for patiently waiting.
To better understand what’s happening with your Linux installation, we need to gather logs”

They obviously do not know how to fix it, nor do they care. They are bouncing my support ticket around hoping I will give up :frowning:

9

Oh no. Yeah it is not really an OS issue (well it was caused by however the fwupmgr called the BIOS update to get it into its current state)

There is a batch fiile on the EFI boot USB that can be carefully taken apart or modified to at least get into the command prompt. There it should be possible to issue the same command as in the script to update that side of the controller. (Remember power it and plug the USB on the opposite side!)

Then it should try to update the firmware on that side of the board for the controller. Someone with better understanding of the script and commands might have some better input here.