Framework Laptop 13 Ryzen 7040 BIOS 3.18 Breaks Booting With Dock Connected

[ziswiler]

Device Information

System Model or SKU

Please select one of the following

• Framework Laptop 13 (AMD Ryzen™ 7040 Series)

BIOS VERSION

03.18 (JFP30.03.18)

Port/Peripheral information

If you are experiencing an issue with a peripheral or an expansion card/port please fill out the following information:

• Peripheral vendor and name: Lenovo ThinkPad USB-C Dock Gen 2 (40AS)
• Port the Peripheral was connected to: 1 via USB-C expansion card
• Device or expansion card attached to the Adjacent port to the port that is having the issue.

1. USB-C
2. micro SD
3. HDMI
4. USB-A

Standalone Operation (Laptop Only)

Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?

• Yes
• No

Describe the bug

If I power the framework laptop on with the Lenovo ThinkPad USB-C Dock Gen 2 (40AS) connected, it does not boot but rather sits there idle forever. Pressing the power button will immediately power it off again.

If I power it on without the dock, all is fine.

With my on-desk setup, I do have to plug the dock in after I get the Linux disk encryption prompt, and the USB keyboard starts working, and it then even shows the prompt on my external screen as well, after which I close the lid. Just slightly a little bit annoying TBH.

But what was most scary was during BIOS update itself, when it just went black and died! Had me worry just a little there hahaha.

Steps To Reproduce

Steps to reproduce the behavior:

1. Connect Lenovo ThinkPad USB-C Dock Gen 2 (40AS) to USB-C expansion on slot 1.
2. Hit the power button (on the framwork laptop that is).
3. Power button light lights up.
4. Internal laptop screen seems to activate its backlight slightly.
5. No further reaction whatsoever.

Expected behavior

I would expect it to just boot as it did with any previous BIOS version.

Screenshots

N/A

Operating System (please complete the following information):

• OS/Distribution: Fedora Silverblue
• Version: 43
• Linux Kernel Version: Linux fedora 6.18.6-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jan 18 18:57:00 UTC 2026 x86_64 GNU/Linux

Additional context

N/A

[JohnAZoidberg]

Did this only happen on the first boot, or also afterwards? Is everything ok now?

[ziswiler]

Did this only happen on the first boot, or also afterwards? Is everything ok now?

No, this is 100% reproducible on every boot since the update.

[ziswiler]

BTW: Another user actually reported it before me.

https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-18-release-stable/79967/34

However, in my case, I don't think it has anything to do with Power on AC attach. At least I never activated any such and use the regular power button on the framework laptop itself to power it on/off.

[mamarley]

I've got this issue too, but it actually doesn't even have anything to do directly with USB4/Thunderbolt docks (though I did initially experience it with one). The real issue is that the laptop won't POST if you have a USB mouse plugged into a daisy-chained USB hub.

I was able to reproduce the issue by daisy-chaining 2 Anker 4-port USB3 A hubs (with the first plugged directly into the laptop) and then plugging a mouse into the second hub, no dock required. The reason docks cause the issue is because they have a Thunderbolt controller (which acts as a USB hub, among other things) and then they have another USB hub internally daisy-chained from that one for the USB ports on the dock. And then, of course, everyone who has a dock has a mouse plugged into it.

[ziswiler]

I don't think it has anything to do with a USB mouse, as mine is connected via Bluetooth 😏. However, I can confirm that it even happens if my dock is plugged into the USB-A extension on port 4, of course, with a USB-C to USB-A adapter. So it indeed seems to be a USB issue of sorts.

[mamarley]

OK, it may not be specific to mouses then, but it certainly seems like it has something to do daisy-chained hubs, and it can be reproduced without having a dock. That definitely means it isn't directly caused by USB4/Thunderbolt and should make it easier to reproduce for Framework.

[Mathilu]

I had the same problem with a Lenovo ThinkPad Universal Thunderbolt 4 Dock (40B0), after going back to 3.17 everything works again.

I also lost my internal speaker and microphone, Realtek audio completely disappeared on Windows 11 Device Manager. But I don't think this is related.

[Peter-Slump]

I can confirm this bug. Same laptop (Ryzen 7040) and a Thinkpad Docking station (40A9).

[ai]

I have the same case with DELL UltraSharp U2725QE (monitor with Thunderbolt hub).

When I connect it via Thunderbolt cable (official, with the logo) and reboot the laptop, the button shines, but screen is blank. Nothing is happening.

If I disconnect cable, press On the laptop reboots normally. Then I can connect cable again and everything works normal.

I have Framework 13 7840U with Fedora 43. I start to see the error pretty consistency only after the BIOS update.

If I press On (and do not reboot) it works (but I tried only 2-3 times, maybe it is flunky issue).

[NRaiders]

@JohnAZoidberg this is definitely a BIOS issue with the FW13 AMD 7040 laptops running 3.18

https://community.frame.work/t/framework-13-7840u-hanging-on-post-when-a-mouse-is-plugged-into-a-daisy-chained-usb-hub-and-an-unacceptable-support-experience/80142