Left Middle port. Which has been working fine for me until that newer BIOS. 
@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?
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.
@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.
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.
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.
2 Likes
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
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.
I have unplugged and reinserted the audio jack and have also turned off and disconnected from AC power for 2-3 minutes.
The random disconnection of USB SSD drives seems to be better but is still occuring with this BIOS version. That’s in port 4, rear right.
Just want some clarity of this statement. Does this mean until the issue is resovled or will it always be a Beta release and there will be another once that particular issue is resolved?
Tried to update using the UEFI shell method. I’ve previously used this method to update both this machine to 3.03 and for all my Framework 13 updates but I get the same error in the pictures with and without an NVME plugged in. Tried with and without power from a Framework 16 charger. Nothing else is plugged in besides the usb and the expansion card it’s connected too. I’m a bit confused by the error message as you can see files are there and there more than enough space left over on the usb if needed. Any suggestions as to what I may be doing wrong?
I’m also getting an error on my uploaded images that I think is causing corruption in the post. Had to open the pictures in my browser and screenshot them to have them show up.
Not related to the other questions but any plans to include more or really any cpu features to the BIOS it’s a bit bare-bones especially when compared to the Intel counterparts or other vendors offering the same cpu?
Trying this out and both my issues still are the same if not worse - the laptop still refuses to charge through a Anker 737 powerbank (140W) entirely (it tries, over and over, but never keeps it going - and the cpu crashes to lowest performance for ~100ms each time) and reports in dmesg (Fedora 40):
Note: “Trickle Charge” Mode on the 737 seems to make it work, but other Laptops do not need it so…
[ 520.390492] ucsi_acpi USBC000:00: unknown error 256
[ 520.390509] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 520.527319] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
While on a Ugreen Nexode Charger on the 140W port performance entirely tanks (now worse than before), while the same charger on 100W works completely fine, like my 65W Anker Chargers (just dipping much harder into the battery).
Please, PLEASE do some tests on common (140W usually) chargers and powerbanks and fix your PD handling.
Not a single of my other PD capable devices has so consistently locked up charging entirely, or shown such weird behaviour.
Its a gamble each time i plug into any thirdparty charger that is >= 100W.
I emphatically second this request to get some more PD device testing and fixing. I suspect it would only take analysis of one or two known-incompatible devices to find and fix whatever bugs in the EC/PD firmware are causing incompatibilities with most/all of the devices that are currently broken and it would be really nice!
@Woof, the performance issues you mention with that charger, you mention they were already happening with 3.03 and no change or worse with 3.04, is that right? PD passthrough even to the Framework adaptor doesn’t work with my hub, and between kernel 6.7 and 6.8 it went from merely “not working” (6.7) to “not working, and also, CPU performance tanks until I unplug the adaptor” (6.8), which sounds like what you describe, but I just wanted to confirm my understanding (to commiserate, mostly :-)).
Yes, they were happening ever since i got the machine in Batch 9 (Loaded 3.03 and Fedora 40 beta on it day 1)
https://community.frame.work/t/extremely-weird-dgpu-power-behaviour-on-140w-chargers-moved
They tend to show as the massive performance swings and frametimes being out of whack every time it tries to use the charger - which makes me almost nauseous - however 3.04 seems to limit far more, and i am now stuck at the lower performance level entirely as long as one of the affected chargers is connected.
Worse than on battery only, even.
Waiting for Anker 747 (140w) powerbank support here too.
I was in a 15 hours flight with broken outlet on the seats nearby and having my powerbank just charging my phone … oh boy … this was frustrating and really long flight…
Edit: Ignore me, I was hitting F12 and then going to setup which is apparently not the right place (even though it has a secure boot section) and I needed to hit F2 and go to the Secure Boot Administration section of the main menu.
Is anyone else having issues with secure boot / TPM setup? When I choose to erase the TPM and reboot with this bios version, sbctl tells me that secure boot is still enabled and not in setup mode. There’s an odd menu for doing things to the TPM that I’m afraid to touch so as not to really break things, but maybe something in there needs to be configured to put the TPM in setup mode?
Did you check if your EFI Partion has enough space? I (and others) had this problem when updating BIOS from 3.02 to 3.03.
Have the same problem. Kubuntu 24.04, Kernel 6.8.0-40-generic (64-bit), BIOS 3.03
I’ve got the same lsusb -v problem with OpenSuse Tumbleweed, kernel 6.10.4-1-default
$ sudo dmesg -H
[17. Aug 18:02] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,330068] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,206637] [ T189593] usb 2-2: device not accepting address 2, error -62
[ +5,340128] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,333345] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,206689] [ T189593] usb 2-2: device not accepting address 2, error -62
[ +5,343437] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,330013] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,206637] [ T189593] usb 2-2: device not accepting address 2, error -62
[ +5,340088] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,333438] [ T189593] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,209938] [ T189593] usb 2-2: device not accepting address 2, error -62
[ +0,020024] [ T181127] usb 2-2: USB disconnect, device number 2
[17. Aug 18:03] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,336724] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,206643] [ T181127] usb 2-2: device not accepting address 3, error -62
[ +5,336761] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,333397] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,209973] [ T181127] usb 2-2: device not accepting address 4, error -62
[ +0,006725] [ T181127] usb usb2-port2: attempt power cycle
[ +5,546697] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,330063] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,206630] [ T181127] usb 2-2: device not accepting address 5, error -62
[ +5,343436] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +5,330052] [ T181127] xhci_hcd 0000:c2:00.3: Timeout while waiting for setup device command
[ +0,209980] [ T181127] usb 2-2: device not accepting address 6, error -62
[ +0,006823] [ T181127] usb usb2-port2: unable to enumerate USB device
After using “sudo lsusb -v” does your fingerprint-reader work as expected?
Are your USB-Ports working as expected? My external USB 3.2 SSD (Samsung T7) when connected to USB-Port 5 (right, middle) only has USB 2.0 (480 MBit) speed. System-Info shows it under an USB 2.1-Hub.