Did successful upgrade via lvfs on arch linux.
Fixed issue where I hat to start wayland session twice because of GPU problems.
Previously I could use my steam deck 45W charger to charge. Now it no longer works and I have to use Baseus 100W charger.
Yup, that did it. One risky forward-pushing partition resize and several boot-partition-reference fixes later, the Windows updater worked successfully, without the weird freezing I had before reboot. So Iâm good here 
1 Like
Same here.
Are you using an external monitor as well? How is it connected? I disconnected my external HDMI monitor, and the blanking problem seemed to go away (hard to be sure because itâs intermittent). After a few hours, I reconnected the monitor but instead of using the Framework HDMI expansion card, I connected to a USB-C expansion card using a USB-C/Thunderbolt to HDMI adapter. Itâs been about two hours and I havenât seen a whiteout yet. Iâm starting to think the HDMI expansion card might be a factor.
Interesting I noticed the same thing, the Steam Deck charger no longer works and it was working before.
I updated my Windows 11 system with no issues. Iâm planning to set up dual boot, but I waited until I had this BIOS upgrade installed before going ahead with that. My SSD has a partition of about 500 GB waitingâŚ
Yes, exactly: External monitor via HDMI.
But as this is my first new laptop in 10 years (Asus Zenbook ux32 
) I only recently discovered how versatile USB-C really has become and will switch over to USBc shortly anyway.
1 Like
Received and assembled my AMD 7040 Framework yesterday. Then
- updated to BIOS release 3.03 BETA using the EFI shell method. Worked fine (once I got the USB stick formatted properly, in particular without any grub boot sector remainders on it), and
- installed Kubuntu 23.10 without any problems.
Latest Kubuntu offers the choice between X11 and wayland sessions at login. Both work fine. As an alternative to fractional scaling I tried tuning font DPI setting from 97 to 140. Despite a popup notice saying that scaling is the recommended method, the result looks surprisingly good, so Iâll stick with it for now. It has to be done separately for X11 and wayland.
A strange issue surfaced when testing the HDMI card with an external monitor. In the right rear port the display failed every couple of seconds, just to reappear a few seconds later, fail again, and so on. Right front and left rear ports seemed to work normally with HDMI.
Same exercise, but connecting the monitor directly using USB-C worked properly on all three ports.
This morning, when I was about to submit a support request to Framework, I couldnât reproduce the issue any more, but found HDMI working happily in all three ports. Had that been a thermal issue? A faulty card or rather the main board? Or something solved for good with the next firmware update? Not sure what to ask at Framework support now.
The front left port doesnât drive any external monitor, neither via HDMI nor USB-C, but that is a known limitation, IIRC.
Suspend by closing the lid works fine, using s2idle, according to syslog.
3 Likes
Anyone else notice the âROPâ change between drivers? The âolderâ Framework drivers show more ROPs and the latest drivers bring it down, but the gaming/graphics have better numbers and response times for the newer drivers. Side note AIDA64 shows only 6 CUâs (no matter the driver version) though for the Ryzen 7 7840U chipsetâŚisnât it supposed to have 12 CUs?
1 Like
Reporting back from Kubuntu Mantic (23.10) with kernel 6.5.0-10-generic:
Used fwupdtool to do the update from lvfs-testing. Worked flawlessly. Took maybe 2 minutes longer on reboot than I took to make a pot of tea so⌠5-6 minutes?
Graphical setup:
kscreen-doctor -o reports:
$ kscreen-doctor -o
Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:2256x1504@60*! 1:2256x1504@48 2:1920x1200@60 3:1920x1080@60 4:1600x1200@60 5:1680x1050@60 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1280x720@60 10:1024x768@60 11:800x600@60 12:640x480@60 13:1600x1200@60 14:1280x1024@60 15:
1024x768@60 16:1920x1200@60 17:1280x800@60 18:1920x1080@60 19:1600x900@60 20:1368x768@60 21:1280x720@60 Geometry: 2439,2160 2256x1504 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:3840x2160@60*! 1:2560x1440@60 2:1920x1200@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60 6:1600x1200@60 7:1680x1050@60 8:1600x900@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x800@60 13:1152x864@75 14:1280x72
0@60 15:1280x720@60 16:1024x768@75 17:1024x768@70 18:1024x768@60 19:832x624@75 20:800x600@75 21:800x600@72 22:800x600@60 23:800x600@56 24:640x480@75 25:640x480@73 26:640x480@67 27:640x480@60 28:640x480@60 29:720x400@70 30:1600x1200@60 31:1280x1024@60 32:1024x768@60 33:2560x1600@60 34:
1920x1200@60 35:3200x1800@60 36:2880x1620@60 37:2560x1440@60 38:1920x1080@60 39:1600x900@60 40:1368x768@60 41:1280x720@60 Geometry: 0,196 3491x1964 Scale: 1.1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 3 DP-3 enabled connected priority 3 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@30 2:2560x1440@60 3:1920x1200@60 4:1920x1080@75 5:1920x1080@60 6:1600x1200@60 7:1680x1050@60 8:1600x900@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x800@60 13:1280x720@60 14:1280x72
0@60 15:1280x720@60 16:1280x720@50 17:1280x720@50 18:1024x768@75 19:1024x768@60 20:800x600@75 21:800x600@60 22:720x576@50 23:720x480@60 24:720x480@60 25:720x480@60 26:720x480@60 27:720x480@60 28:640x480@73 29:640x480@67 30:640x480@60 31:640x480@60 32:640x480@60 33:720x400@70 34:1600x1
200@60 35:1280x1024@60 36:1024x768@60 37:2560x1600@60 38:1920x1200@60 39:3200x1800@60 40:2880x1620@60 41:2560x1440@60 42:1920x1080@60 43:1600x900@60 44:1368x768@60 45:1280x720@60 Geometry: 3491,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Itâs a lot to read, so the summary is:
- Internal display, 1x scale
- Left 4k display, 1.1x scale
- Right 4k display, 1x scale
Iâm running Wayland (kwin-wayland from the package versioned 4:5.27.8-0ubuntu2).
Using Firefox from the snap. Importantly that means that Firefox is using Mesa version 23.0.4-0ubuntu1~22.04.1, so Iâve got gfx.blocklist.all set to -1 in about:config.
Results so far
- Firefoxâs renderer still occasionally crashes, bit this is most likely a mesa bug rather than hardware anything.
- On first boot after the update, my laptop recognised one external monitor (directly attached via USB-C-to-Displayport cable, back right port) but not the other (connected through a Cable Matters travel hub, model 201046. Iâm not entirely sure what happened there, but just disconnecting and reconnecting the DisplayPort cable didnât work. I had to disconnect & reconnect the entire hub (woe is me!
) This only happened on first boot, so itâs probably not something worth trying to solve. - TPM-backed FDE (using clevis) worked flawlessly. I didnât have to enter my backup passcode.
Side notes
- Battery charge limiting settings (still) arenât available through
tlp. (Not that I expected them to be, but just noting it in case anyone wonders.) (Neither version1.5.0-2ubuntu1from the Mantic repositories nor version1.6.1-2~mantic1from the official PPA) - I havenât had enough time to test the boot issues. Before it was only occasional that my laptop wouldnât boot in the first place (with Ubuntuâs 6.5 kernel.)
More to come as I find it, but honestly my experience so far with this laptop has been stellar. Massive kudos to the Framework team overall and a special shoutout to @Matt_Hartley and the others working on Linux support. Framework hiring Matt gave me a lot of confidence in your seriousness about Linux support, and still youâve wildly exceeded my expectations.
8 Likes
Third data point here; my OEM Steam Deck charger also no longer works. I see the orange LED on the side of the laptop light up extremely briefly, then it goes blank, and the OS doesnât seem to see the charger at all.
1 Like
A datapoint that might help narrow down the charging issues: My 45W ASUS Chromebook charger works on all ports on 3.03.
My 3.03 upgrade on W11 went flawlesssly.
Upgraded through fwupd on debian unstable, all the issues are gone and everything works flawlessly so far (previous issues â unable to start xorg with startx as a user and having to use login manager instead, launching firefox killed Xorg â I had to resort to disabling all video acceleration in xorg config).
Just updated my 7640u to 3.03 via LVFS on Elementary OS 7.1, great success!
Fourth data point: Can confirm. Something went wrong with USB PD in Bios 3.03.
- My Steam Deck Charger stopped working too.
- But the strangest thing is that my Framework sometimes shows a white charging LED, although my battery isnât even close to being full. (~ 60%)
Anyone else having those weird problems too?
Checking in here too. I never tried my Steam Deckâs charger until today (so I canât say it âstopped workingâ for me), but itâs not recognised by the laptop.
On the flip side, I was previously having intermittent issues with the laptop recognising other power supplies that now seem to be gone.
1 Like
Happens to me too, yesterday I left the laptop off to charge, white led, power on into Ubuntu22.04 (oem kernel), battery at 85%, led went back to orange.
However another issue seems to be solved with the new bios: the official charger (not others I tried among which an official macbook charger) would stop working when powering off the laptop from Linux (Ubuntu and kali), didnât happen on windows 11. To make it work again I had to unplug it from the wall first (I guess the charger equivalent of a reset).
Sounds similar. I âonlyâ needed to press the power button and the charging indicator went back to orange, when the password prompt for my disk encryption appeared.
For the statistics: I was using one of those ânewâ Anker Prime 100W GaN Plugs (Modell: 737 / A2343) and an Anker PowerLine III 100W USB-C cables attached to a USB-C expension card in the left rear port.
The steam deck charger also triggered the white charging indicator once. Without charging the Framework.
Iâm going to try some other chargers the next few days.
I canât apply the beta firmware on my Ryzen 7 DIY.
From Ubuntu 22.04 itâs hit and miss if it thinks the 100% charged battery is good enough to even start the upgrade from fwupdmgr, but on reboot 50% of the time it briefly displays something in the top left, then boots normally, the other 50% of the time the reboot just goes straight to GRUB.
Message when using fwupdmgr:
From a USB stick, all seems well, but it fails with error code 21. Icons in top right seem to show full charge. Doesnât seem to be a âdisable secure bootâ option, as hinted at in the main post.
Message from USB stick :
I believe they said there are issues if the battery charge state is 100%. They recommended to let the battery drain a few percent, then plug it in and try again.