Skip to content

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

Closed

Description

@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

Activity

  1. JohnAZoidberg commented on Jan 27, 2026

    @JohnAZoidberg
    Member

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

  2. ziswiler commented on Jan 27, 2026

    @ziswiler
    Author

    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.

  3. ziswiler commented on Jan 27, 2026

    @ziswiler
    Author

    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.

  4. mamarley commented on Jan 27, 2026

    @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.

  5. ziswiler commented on Jan 27, 2026

    @ziswiler
    Author

    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.

  6. mamarley commented on Jan 27, 2026

    @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.

  7. Mathilu commented on Jan 27, 2026

    @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.

  8. Peter-Slump commented on Jan 28, 2026

    @Peter-Slump

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

  9. ai commented on Jan 28, 2026

    @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).

  10. jeffmaher commented on Jan 29, 2026

    @jeffmaher

    Adding on that I also started experiencing this issue this week after updating the BIOS to 3.18.

    I'll add my information below to help with debugging:

    System

    • Framework Laptop 13 AMD (Ryzen 5 7640U)
    • BIOS: 03.18
    • 64GB DDR5-5600 (2x32GB dual-channel)
    • Ubuntu 25.10

    Expansion cards:

    • Slot 1 (rear left): USB-C
    • Slot 2 (front left): USB-C
    • Slot 3 (rear right): USB-C
    • Slot 4 (front right): USB-A

    Affected devices (both cause the hang):

    (I've tried with these two dock or dock-like devices)

    • Dell WD22TB4 Thunderbolt dock (connected to rear left USB-C)
    • Dell U2719DC monitor via direct USB-C connection (non-Thunderbolt)

    Symptoms:

    • Power button LED lights up
    • Sometimes fans spin
    • No Framework logo, no POST, no display output on any screen (internal or external)
    • Unplugging the dock/monitor does not recover — requires holding power button to force shutdown
    • Also occurs on resume from suspend

    Working configurations:

    • USB-C power-only charger at boot — works fine
    • Boot undocked, plug in dock/monitor after login — works fine

    BIOS troubleshooting attempted (none resolved):

    • Disabled Quick Boot
    • Disabled boot from USB
    • Set firmware delay to 5 seconds
    • Restored BIOS to default settings

    This configuration worked correctly prior to the BIOS 3.18 update. Same dock and monitors were used without issue last year.

    One last note is that I did the 3.18 update while attached to a dock. Not sure if that's a relevant detail though.

  11. jeffmaher commented on Jan 29, 2026

    @jeffmaher

    Update: Downgrading to BIOS 3.17 resolved the issue.

    I downloaded the 3.17 EFI update package from Framework, flashed it via USB using the standard EFI shell method, and the dock boot hang is now fixed. I can boot and resume from suspend with my Dell WD22TB4 Thunderbolt dock connected without any issues.

    For anyone else experiencing this problem, the downgrade process is straightforward:

    1. Download the 3.17 EFI update: https://downloads.frame.work/bios/Framework_Laptop_13_Ryzen7040_BIOS_3.17_EFI.zip
    2. Extract to a FAT32 formatted USB drive
    3. Boot with F12 and select the USB drive
    4. Let startup.nsh run and follow the prompts
  12. 27 remaining items

  13. Travis-Snoozy commented on Feb 24, 2026

    @Travis-Snoozy

    Reporting that my dock ("no-name" https://www.amazon.com/dp/B0BNTHWWMY) also was impacted, when using the dock with port 4 (I did not try any other ports), and a monitor (ASUS MB166C) connected to port 1 (again, I did not try any other ports). I run my system standalone. With the dock plugged in, the system would not output any video to either the direct-connected or dock-connected monitors, and would give flash codes when I tried to use my dock-connected keyboard. Removing the dock, but leaving my external USB-C DP alt mode monitor connected to port 1 would come up only intermittently.

    Reverting the Framework Laptop 13 Ryzen 7040 from UEFI build 3.18 back to 3.17 resolved the issue.

  14. jandk commented on Feb 24, 2026

    @jandk

    Same issue here with two different Thinkpad docks

  15. lancatlin commented on Feb 26, 2026

    @lancatlin

    Same issue with Caldigit TS3 Plus. A Dell monitor, a keyboard, and a mouse are connected while booting. 100% reproducible. It works when you click "Reboot" in Fedora, but not if fully power off and on again.

    Framework Laptop 13 AMD Ryzen 7040Series
    Fedora: 43
    Linux: 6.18.10-200.fc43.x86_64

  16. quinchou77 commented on Mar 4, 2026

    @quinchou77

    After several days of debugging with the U2725QE monitor, we have successfully identified the root cause and verified a solution. The fix is slated for the upcoming release. The exact schedule is currently TBD, but I will provide an update as soon as the timeline is finalized.

  17. self-assigned this
    on Mar 4, 2026
  18. bmarinov commented on Apr 4, 2026

    @bmarinov

    I am experiencing the same issue with my WD22TB4. Updated to 3.18 and the laptop wont boot when connected to a dock.

  19. mamarley commented on Apr 4, 2026

    @mamarley

    @quinchou77 Any idea when the update to fix this might get released?

  20. zeaglee commented on Apr 10, 2026

    @zeaglee

    Pretty frustrating bug. I have to unplug my dock to run Fedora's near daily updates and reboot. If I forget to plug it back in it drains the battery. Latest time this happens Fedora/Windows no longer boot. Please release a downgrade procedure rolling back your bios or fix ASAP.

  21. jcrosshhpc commented on Apr 10, 2026

    @jcrosshhpc

    Pretty frustrating bug. I have to unplug my dock to run Fedora's near daily updates and reboot. If I forget to plug it back in it drains the battery. Latest time this happens Fedora/Windows no longer boot. Please release a downgrade procedure rolling back your bios or fix ASAP.

    @zeaglee the instructions to downgrade are listed above in this thread here:

    #170 (comment)

  22. hojjatabdollahi commented on May 7, 2026

    @hojjatabdollahi

    @quinchou77 are there other fixes being worked on for the next release? Is something holding up the release?

    [Sorry for the notification everyone, once a month comment should be fine though!]

  23. jeffmaher commented on May 29, 2026

    @jeffmaher

    FYI: Haven't tried it yet, but looks like a fix is on it's way via BIOS 3.19.

  24. dimitris-personal commented on May 29, 2026

    @dimitris-personal

    FYI: Haven't tried it yet, but looks like a fix is on it's way via BIOS 3.19.

    Running it here since yesterday, LGTM 👍. Dell WD25TB5 dock with USB keyboard attached.

  25. quinchou77 commented on Jun 1, 2026

    @quinchou77

    The solution has been implemented o 3.19. We are waiting for stable release process next week.

  26. ziswiler commented on Jun 1, 2026

    @ziswiler
    Author

    I can confirm that BIOS 3.19 fixes the issue. However, during the update, towards the end, I never saw the “Update Complete!!!” message, the display rather just went blank. I waited a minute and then rebooted using the power button, which worked. Just slightly scary.
    I am so looking forward to actually using a Framework Laptop motherboard with a fully open source boot chain incl. BIOS and everything, like DeepComputing's DC-ROMA RISC-V Mainboard III. Closed-source BIOS experience is just so really, really bad across the board!
    Anyway, you guys at least managed to fix it after just around 4 months. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

3.18BIOS UpdateA problem updating the BIOS or after updating itLaptop 13 - AMD Ryzen 7040Framework Laptop 13 (AMD Ryzen™ 7040 Series)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions