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.
I don’t use the fingerprint reader, so can’t answer that.
Port one (docking station with ethernet and 3 monitors) is not affected, and neither is port 6 (bottom right) with the audio expansion card. The other ports are not in use. Ports 3 and 5 are equipped with USB-A cards and were both able able to mount a 8GB USB drive I’ve got lying around. So I can’t tell if anything is amiss (other than the timeout and error messages in dmesg).
I also have no problems with Port 1 and 4 (USB 4) because there are not connected to the Genisys Logic USB-Hub.
Some proper indication that shows when the laptop went to sleep. It’s no good when you arrive at home and find it running hot when you get it out of your backpack.
I’m still running 3.03, and haven’t tried updating yet. I’m running Windows 11 Pro installed by Framework. Lately, I’ve been experiencing more and more issues with the computer waking itself up from sleep.
When logged in and using the device, going to the start → power setting and selecting sleep will put the machine to sleep and then immediately wake back up, but now locked.
Selecting sleep from the power options on the locked login screen will often put it to sleep for a variable period.
When the laptop is asleep and open, closing the lid often wakes the laptop.
When the laptop is asleep and plugged in, unplugging it often wakes the laptop.
When the laptop is asleep and unplugged, plugging it in often wakes the laptop.
When the laptop is asleep, closed, and plugged in, it often wakes randomly.
When the laptop is asleep, closed, and unplugged, it often wakes randomly (this often happens in my bag).
My go to lately has been to unplug the laptop, put it to sleep, and hope that if it does wake itself up, that it will hibernate until I get back, just so that it doesn’t bake itself to death.
The only hardware change I’ve made recently was receiving the LED Matrix spacer, and installing it to the right of the keyboard (and the color shift spacer to the left). I doubt it’s related, but as a USB device 
. I’ve also updated Windows and installed updated drivers from AMD as prompted by AMD Adrenaline.
1 Like
This beta BIOS was released a month ago. Any reason why it’s not updated to non-beta status yet?
Hope this helps.
3 Likes
@Kieran_Levin any hope to have a working usb PD with Anker 737 powertank on next update ? I’m deseperate to not be able to rely on a powersource on the go while the laptop always drains during sleep or even worst, wakes up while being in my bag T-T
1 Like
I saw somewhere that was being worked on for the next update.