This beta BIOS was released a month ago. Any reason why it’s not updated to non-beta status yet?
@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.
Yes there was some vague words about working on PD issues for the next release but not specifically mentionning the Anker 737 powerbank model.
I did not realised that there was a topic with quite a lot of people using this model (or the newest one) currently:
https://community.frame.work/t/fw16-usb-pd-battery-issues
Thanks Ive already done that but somehow it keeps awaking randomly.
Everytime I tried the debugging script sl2idle from AMD I get nothing too …
I simply unziped the contents of the UEFI shell onto a fresh 8GB FAT32 usb drive as instructed. Given the layout comes from Framework, I’m assuming they know how large each directory should be or would at least provide additional directions if need be.
The last acknowledgment from Framework staff (apart from Destroya quoting Kieran_Levin’s post in question) that this BIOS was being held back to continue being worked on was 27 days ago. I don’t mean to rush anyone, as I know software development and especially troubleshooting and bug tracking are time consuming, but can we get more Framework communication on this? Maybe 1 post a week confirming things are still being worked on and possibly some vague status updates (eg. “bug seems to be related to USB controller, contacted the vendor/supplier/manufacturer and currently waiting to hear back from them” or something)?
Unfortunately, since the “we’re gonna do better” post/email, I don’t feel like communication has significantly changed or improved.
4 Likes
Yes, definitely, especially since one of the things being fixed is the compatibility with the dual drive bay. Seems kinda rude to show it off on the assembly line in an LTT video only to have to wait months to get it, when they’re probably sitting there ready to go in the warehouse.
Try double tapping the power button on the 737 (this enables trickle charge mode, shown on the screen with a green dot top left)
For me it can fully run and charge the Framework in that mode.
1 Like
It only disable the 140W power limiting output power to 100W.
You can use 100W cable to …
So yes it can be use in that mode and work like all other 100W power, but it do not allow to get the 140W power (28V/5A config) so for me not “fully”.
I guess this BIOS made it to lvfs-testing. I went ahead and updated (using Manjaro+KDE+Discover). I wasn’t really having any issues with 3.03, but I only use the framework power brick since nothing can compete in power output yet. I’ll check and see if any of my modules are acting up, but so far it all seems to be working fine.
I just came here to check up on the status of 3.04. I remember seeing the announcement of the BETA release 2 months ago, but surprised to not see it released yet.
I guess there is much work still to do?
1 Like
They said that it isn’t released due to one specific issue:
1 Like
Right. I guess I mean I was surprised to see that the issue hasn’t been resolved by now.
BIOS 3.04 seems to have regressed ito ability to charging over 3.02.
I used to be able to charge my notebook on a 25W PD charger before. It would charge slowly during use, but it would charge. This was on the 3.02 BIOS.
Now it says that the charger isn’t powerful enough and doesn’t try to charge.
If you then suspend the notebook before plugging in the 180W charger, it doesn’t charge.
When it wakes up it still refuses to charge.
If you then unplug the 180W charger, and then plug it back in again it starts to charge.
It seems that if it’s in an error state, it won’t recover until the OS is running and you unplug-re-plug the charger in.
1 Like
Any update? It’s been over two months now since the last official communication about this.
6 Likes
Any additional issues identified we can help test in order to get the GA version release speeded up?
4 Likes
I’ve not noticed any new issues that are specific to these BIOS. My issues stem from newer linux kernels acting wonky with USB C cable detection and inserting the framework DP card.
[ 987.954393] ucsi_acpi USBC000:00: unknown error 256
[ 987.954404] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 988.219657] usb 1-1: new full-speed USB device number 15 using xhci_hcd
[ 988.387738] usb 1-1: New USB device found, idVendor=32ac, idProduct=0003, bcdDevice= 0.00
[ 988.387754] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 988.387760] usb 1-1: Product: DisplayPort Expansion Card
[ 988.387765] usb 1-1: Manufacturer: Framework
[ 988.387770] usb 1-1: SerialNumber: 11AD1D00A49C40100C2F0B00
[ 988.455653] hid-generic 0003:32AC:0003.0011: hiddev97,hidraw2: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:c5:00.3-1/input1