Laptop 16 AMD Ryzen 7040 BIOS 3.04 BETA Release

Dustin_Knecht · July 25, 2024, 7:41am

For clarification, the Ethernet port was seemingly disabled. It was registering something was there in that port (I don’t remember what screen I was in where it was telling me this, I can check tomorrow), like a disabled driver and I think it had the name of the driver it was referring to, but the driver wasn’t appearing in Control Panel or Device Manager (even with showing hidden enabled).

Even when I reverted back to 3.03, the Ethernet adapter still wasn’t showing up in neither my Device Manager nor Control Panel.

I was able to get it working again in 3.03 by clean reinstalling the Driver bundle and doing a couple restarts and winsh resets. Not sure what exactly fixed it, or if I was supposed to reinstall the Drivers after the BIOS update or not. Maybe that would’ve solved my problem.

I can try and recreate the problem again to gather more information and to try to solve it without reverting to 3.04 tomorrow if you’d like.

Destroya · July 25, 2024, 7:09pm

thank you for the additional information, I’d appreciate it you could try again tomorrow.

knipp30 · July 26, 2024, 5:22am

I did some testing this AM and the issue was on the USB C dock… it works just fine in this bios.

~~This isnt quite what is in the known issues thread.~~

But after installing the update, my usb-c dock does not work in port #4. It works in port #1 though.

My charger works in 1 or 4…and my usb c headset works in port #4 as well.

James3 · July 26, 2024, 8:40am

@knipp30
It is strange regarding the usb problems because the new bios did not mention making any changes to the usb parts.

I have not bothered updating to BIOS 3
0.4 because it did not mention any usb fixes.

After upgrading BIOS it is a good idea to reset the bios to “optimized defaults”.

Dustin_Knecht · July 26, 2024, 11:00am

It’ll be 2-3 days because I’m out of town without my Framework, but I will definitely try again and give your more useful information about it when I get back.

Djip · July 27, 2024, 10:06am

hop this will be the same issues as this one FW16 refusing to properly charge on 140W charger

And nice job, I realy love my FW16!

Darius_C · July 28, 2024, 9:01pm

I had an issue where the dGPU was completely missing from both Windows and NixOS, so I downgraded back.

knipp30 · July 30, 2024, 2:28am

So, after a few days running 3.04, I can confirm that it caused instability with my usb-c dock.

No matter what port, it would not connect.

Rolled back to 3.03 and it worked as expected.

Kieran_Levin · July 30, 2024, 11:49pm

Could you provide more information about your dock? Also what port the dock is connected to. Model number and brand? We would like to see if we can reproduce your issue.

Kieran_Levin · July 30, 2024, 11:53pm

Can you tell us what port your ethernet adapter was connected to? Upper middle lower, right, left.

knipp30 · July 31, 2024, 1:39am

Sure thing - its the following dock:

I tried in both ports 1 and 4.

I’m willing to roll the bios forward if you need/want some logs if you cannot reproduce the issue.

I have other issues with the dGPU port stability on both the 3.03 and 3.04 bios - and that seems to be something yall are working on seperately.

Dustin_Knecht · July 31, 2024, 3:18pm

Left Middle port. Which has been working fine for me until that newer BIOS.

James3 · July 31, 2024, 4:04pm

@Kieran_Levin
Hi,
I think some clarification is needed. The release notes for BIOS 3.0.4 did not say that anything in relation to USB had changed at all. But some people here have seen USB changes with the BIOS upgrade.
Are the release notes wrong?

Arazil · July 31, 2024, 5:30pm

I reverted back to 3.03 after getting constant GPU resets while visiting certain websites on Firefox.

Each crash would generate a “amdgpu timeout” error similar to:

Jul 31 12:10:31 artemis kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=737896, emitted seq=737898
Jul 31 12:10:31 artemis kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 3625 thread firefox:cs0 pid 3729
Jul 31 12:10:31 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: GPU reset begin!
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Jul 31 12:10:33 artemis kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Jul 31 12:10:33 artemis kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: MODE2 reset
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: GPU reset succeeded, trying to resume
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resuming...
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: SMU is resumed successfully!
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:223
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:231
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:239
Jul 31 12:10:33 artemis kernel: amdgpu 0000:c4:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:247
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: recover vram bo from shadow start
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: recover vram bo from shadow done
Jul 31 12:10:34 artemis kernel: amdgpu 0000:c4:00.0: amdgpu: GPU reset(10) succeeded!
Jul 31 12:10:34 artemis kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Kernel version: Linux artemis 6.10.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 27 Jul 2024 16:49:55 +0000 x86_64 GNU/Linux

I have the dedicated GPU expansion card installed.

James3 · July 31, 2024, 6:25pm

@Arazil
Whether a GPU works or not is pretty much independent of any BIOS.
This is more likely to be a GPU driver bug. I would raise a bug with the linux kernel amdgpu / mesa. They should be able to help.
It might also be helpful to describe to them how to reproduce the problem.
Maybe provide details which web sites you went to on firefox that reproduce the problem. If someone else can reproduce the problem, it will get fixed quicker.

Bruce_McLachlan · July 31, 2024, 7:06pm

I just installed the Beta Release, and my Ethernet would not connect after the reboot.
I rebooted and it is working, I am running Win 11 and Ethernet is in the middle port LH side.

Kieran_Levin · August 1, 2024, 1:16am

I have been able to reproduce the device connectivity issues after the update. We are debugging the issue at the moment.

Generally this looks like if a device is plugged in during the update, all USB3/DP functionality will be lost until the device is removed and reinstalled.

I can see the following issues:

After updating, HDMI output will not work until the HDMI cable is unplugged and replugged on HDMI V3 expansion cards. On HDMI V1 expansion cards the card needs to be removed and reinstalled.
Using a cable matters MFD dongle, after updating the HDMI output does not work until the dongle is unplugged and replugged.
If a usb3 flash drive is attached, it will be recognized as usb2 after the update until it is unplugged and replugged.

We will keep this bios release in beta while we investigate these issues further.

You can work around this after the update by unplugging and re-plugging any device attached, or doing a full shutdown, remove all power sources, waiting 2 minutes, and then powering on the system.

sinatosk · August 1, 2024, 4:11pm

I’m using a FW16 with 7840HS, Arch Linux ( Linux 6.10.2 ) and KDE Plasma 6.1.3

When using the command

$ sudo lsusb -v

it starts probing all the USB ports but then when it gets to “Genesys Logic, Inc. USB3.2 Hub”

it timeouts reading and then the USB port ( port 6 ) is no longer working (reboot fixes it) and the errors from the kernel are

[ 6750.227885] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6755.859920] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6756.067862] usb 2-2: device not accepting address 2, error -62
[ 6761.491906] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6767.123898] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6767.331815] usb 2-2: device not accepting address 2, error -62
[ 6772.755538] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6778.388389] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6778.595862] usb 2-2: device not accepting address 2, error -62
[ 6784.019879] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6789.651893] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6789.859351] usb 2-2: device not accepting address 2, error -62
[ 6789.884672] usb 2-2: USB disconnect, device number 2
[ 6795.283513] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6800.915370] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6801.123814] usb 2-2: device not accepting address 3, error -62
[ 6806.547939] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6812.179496] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6812.387872] usb 2-2: device not accepting address 4, error -62
[ 6812.396715] usb usb2-port2: attempt power cycle
[ 6818.323719] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6823.955712] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6824.163813] usb 2-2: device not accepting address 5, error -62
[ 6829.587889] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6835.219404] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ 6835.427860] usb 2-2: device not accepting address 6, error -62
[ 6835.436215] usb usb2-port2: unable to enumerate USB device

The port works fine until I run the “lsusb -v” command, then that’s when port eventually stops. After the port fails, I suspend the system and resume to see if it works, it doesn’t. Rebooting is the only fix.

and the “lsusb” output is

Bus 002 Device 002: ID 05e3:0625 Genesys Logic, Inc. USB3.2 Hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.20
  bDeviceClass            9 Hub
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         3 
  bMaxPacketSize0         9
  idVendor           0x05e3 Genesys Logic, Inc.
  idProduct          0x0625 USB3.2 Hub
  bcdDevice           34.04
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001f
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 [unknown]
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes           19
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Feedback
        wMaxPacketSize     0x0002  1x 2 bytes
        bInterval               8
        bMaxBurst               0

then I have to reboot my FW16 for the port to work again it to work again.

I don’t remember if this issued happened in 3.02 but in 3.03 ( didn’t get round to reporting the issue ) I saw it and it still here in 3.04

Also in BIOS 3.03 and again 3.04 ( this issue didn’t happen in 3.02 ) when running the command

$ fwupdmgr security

in one entry it shows

✘ TPM PCR0 reconstruction: Invalid

This was valid in 3.02. I’ve not made any use of the TPM yet though so it’s empty as far as I know

the output from

$ fwupdmgr security

Host Security ID: HSI:1! (v1.9.22)

HSI-1
✔ BIOS firmware updates:         Enabled
✔ Fused platform:                Locked
✔ Supported CPU:                 Valid
✔ TPM empty PCRs:                Valid
✔ TPM v2.0:                      Found
✔ UEFI bootservice variables:    Locked
✔ UEFI platform key:             Valid
✔ UEFI secure boot:              Enabled

HSI-2
✔ SPI write protection:          Enabled
✔ IOMMU:                         Enabled
✔ Platform debugging:            Locked
✘ TPM PCR0 reconstruction:       Invalid

HSI-3
✔ SPI replay protection:         Enabled
✔ CET Platform:                  Supported
✔ Pre-boot DMA protection:       Enabled
✔ Suspend-to-idle:               Enabled
✔ Suspend-to-ram:                Disabled

HSI-4
✔ SMAP:                          Enabled
✘ Processor rollback protection: Disabled
✘ Encrypted RAM:                 Not supported

Runtime Suffix -!
✔ fwupd plug-ins:                Untainted
✔ CET OS Support:                Supported
✔ Linux kernel:                  Untainted
✘ Linux kernel lockdown:         Disabled
✘ Linux swap:                    Unencrypted

This system has HSI runtime issues.
 » https://fwupd.github.io/hsi.html#hsi-runtime-suffix

The TPM PCR0 differs from reconstruction.
 » https://fwupd.github.io/hsi.html#pcr0-tpm-event-log-reconstruction

Host Security Events
  2024-06-01 04:48:38:  ✔ Secure Boot enabled
  2024-05-31 15:09:40:  ✘ Secure Boot disabled
  2024-05-30 11:24:38:  ✔ Secure Boot enabled
  2024-05-29 17:48:08:  ✘ Secure Boot disabled
  2024-05-29 17:46:50:  ✔ CET OS Support changed: Not supported → Supported
  2024-05-21 16:01:15:  ✘ CET OS Support changed: Supported → Not supported
  2024-05-21 16:01:15:  ✔ Secure Boot enabled
  2024-05-21 14:08:39:  ✔ CET OS Support changed: Not supported → Supported
  2024-05-20 12:02:19:  ✘ CET OS Support changed: Supported → Not supported
  2024-05-20 11:29:33:  ✘ UEFI secure boot changed: Not found → Disabled
  2024-05-20 11:29:33:  ✔ BIOS firmware updates changed: Disabled → Enabled

I did take a look at here but didn’t help and I did find reading directly from the TPM event log, it returned empty

I’ve been experencing the same issues as @Arazil with amdgpu crashes since 3.04

David_Mellor · August 1, 2024, 10:58pm

With 2.0.3 there is a querk with the audio expansion card not fully initialising correctly such that error beep on command prompt filename completion with tab key does not produce a sound and the Windows API Beep(freq, duration) call does not work.
It could take up to 4 reboots or a couple of shutdowns to get it to work.
With 3.0.4 it’s not working at all no matter how many times I reboot or shutdown.
This doesn’t affect other aspects of the audio. mp3 players and visually impaired speech for example are okay.

David_Mellor · August 1, 2024, 11:13pm

I have unplugged and reinserted the audio jack and have also turned off and disconnected from AC power for 2-3 minutes.