Skip to content

FW16 7040 Firmware update 0.0.3.7 -> 0.0.4.2: egpu support broken (RTX4080) #132

Open

Description

@raldone01

Device Information

System Model or SKU

Framework Laptop 13 (AMD Ryzen™ 7040 Series)

BIOS VERSION

0.0.4.2 or 4.0.2 or 04.02

DIY Edition information

If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.

Memory: Stock
Storage: SSD 980 PRO 2TB

Standalone Operation

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

  • Yes
  • No

Describe the bug

Booting and plugging in the egpu causes errors in dmesg and the gpu nor any of the docks usb devices are recognized.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Update to 04.02
  2. Plug in egpu enclosure
  3. The egpu is not recognized and there are errors in dmesg.

Expected behavior

The egpu dock enumerates and the gpu is recognized as in 03.07.

Operating System (please complete the following information):

  • OS/Distribution: arch
  • Version: Rolling
  • Linux Kernel Version: Linux Elizabeth 6.17.8-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 14 Nov 2025 06:54:07 +0000 x86_64 GNU/Linux

Additional context

[  +8.402013] ucsi_acpi USBC000:00: unknown error 256
[  +2.813577] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +2.835546] ucsi_acpi USBC000:00: unknown error 256
[  +4.286381] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +1.846004] ucsi_acpi USBC000:00: unknown error 256
[  +4.516567] ucsi_acpi USBC000:00: unknown error 0
[  +0.000332] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[  +1.694123] ucsi_acpi USBC000:00: unknown error 256
[  +2.730960] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +1.171132] cros-ec-dev cros-ec-dev.1.auto: Some logs may have been dropped...
[Nov20 13:52] ucsi_acpi USBC000:00: unknown error 0
[  +0.000054] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[  +1.302551] ucsi_acpi USBC000:00: unknown error 256
[  +6.827117] ucsi_acpi USBC000:00: unknown error 256
[  +9.928329] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +2.738106] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +6.970762] ucsi_acpi USBC000:00: unknown error 256
[  +1.870900] ucsi_acpi USBC000:00: unknown error 256
[  +5.008311] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[  +9.324300] ucsi_acpi USBC000:00: unknown error 256
[  +0.131565] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)

Activity

  1. changed the title [-]FW16 7040 Firmware update 0.0.3.7 -> 0.0.4.2 breaks egpu support (RTX4080)[/-] [+]FW16 7040 Firmware update 0.0.3.7 -> 0.0.4.2: egpu support broken (RTX4080)[/+] on Nov 20, 2025
  2. JohnAZoidberg commented on Nov 20, 2025

    @JohnAZoidberg
    Member

    What devices are you plugging into which ports?

  3. raldone01 commented on Nov 20, 2025

    @raldone01
    Author

    I always plug the egpu dock into port 1 though 4 also works.
    The dmesg error happens on 1, 4 and 5.
    It just keeps repeating the error in dmesg until I unplug.
    The gpu always starts to spin up and the speakers make a clicking sound.

    I am now back on 3.07 with the egpu dock plugged in and working:

    main@Elizabeth ~> lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card
    Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
    Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
    Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
    Bus 001 Device 006: ID 32ac:0014 Framework Laptop 16 Numpad Module
    Bus 001 Device 007: ID 8087:0032 Intel Corp. AX210 Bluetooth
    Bus 001 Device 008: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint USB Device
    Bus 001 Device 009: ID 32ac:0012 Framework Laptop 16 Keyboard Module - ANSI
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 002: ID 05e3:0625 Genesys Logic, Inc. USB3.2 Hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 009 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
    Bus 009 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
    Bus 009 Device 005: ID 1532:005c Razer USA, Ltd DeathAdder Elite
    Bus 009 Device 006: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
    Bus 009 Device 007: ID 046a:b090 CHERRY Keyboard
    Bus 009 Device 008: ID 0020:0b21 Generic USB Audio
    Bus 009 Device 009: ID 3302:29e3 TTGK Technology USB Audio
    Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 010 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
    
    main@Elizabeth ~> lspci
    00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Root Complex
    00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Phoenix IOMMU
    00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge
    00:01.5 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix GPP Bridge
    00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge
    00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix GPP Bridge
    00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix GPP Bridge
    00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge
    00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel
    00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge
    00:04.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 19h USB4/Thunderbolt PCIe tunnel
    00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Host Bridge
    00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Internal GPP Bridge to Bus [C:A]
    00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Internal GPP Bridge to Bus [C:A]
    00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Internal GPP Bridge to Bus [C:A]
    00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
    00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
    00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 0
    00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 1
    00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 2
    00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 3
    00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 4
    00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 5
    00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 6
    00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Phoenix Data Fabric; Function 7
    01:00.0 Non-Volatile memory controller: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) (rev 01)
    02:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
    03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO
    63:00.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
    64:01.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
    64:02.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
    64:04.0 PCI bridge: Intel Corporation JHL7440 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06)
    65:00.0 VGA compatible controller: NVIDIA Corporation AD103 [GeForce RTX 4080] (rev a1)
    65:00.1 Audio device: NVIDIA Corporation AD103 High Definition Audio Controller (rev a1)
    93:00.0 USB controller: Intel Corporation JHL7440 Thunderbolt 3 USB Controller [Titan Ridge DD 2018] (rev 06)
    c2:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev c2)
    c2:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Radeon High Definition Audio Controller [Rembrandt/Strix]
    c2:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Phoenix CCP/PSP 3.0 Device
    c2:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b9
    c2:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15ba
    c2:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor (rev 63)
    c2:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller
    c3:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Function
    c3:00.1 Signal processing controller: Advanced Micro Devices, Inc. [AMD] AMD IPU Device
    c4:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Phoenix Dummy Function
    c4:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15c0
    c4:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15c1
    c4:00.5 USB controller: Advanced Micro Devices, Inc. [AMD] Pink Sardine USB4/Thunderbolt NHI controller #1
    c4:00.6 USB controller: Advanced Micro Devices, Inc. [AMD] Pink Sardine USB4/Thunderbolt NHI controller #2
    

    If you need any additional information, let me know.

  4. quinchou77 commented on Dec 30, 2025

    @quinchou77

    When the issue occurs, are the affected ports still capable of charging via the adapter? I want to confirm if the power negotiation fails entirely.
    We are investigating a known issue where PD functionality may fail following the v4.02 BIOS update. We have confirmed that when this occurs, the affected ports stop charging entirely (negotiation failure).
    While we are still working on a reliable reproduction case, we have identified two recovery paths:

    1. BIOS Reflash: Forces a re-initialization of the PD firmware.
    2. G3 Hardware Reset: Disconnecting both AC and the internal battery to completely drain the standby power rails.
  5. raldone01 commented on Dec 30, 2025

    @raldone01
    Author

    I am not 100% sure of what I should test for you.
    I have had issues before v4.02 with charging from the egpu dock. Sometimes it would charge from the dock sometimes it wouldn't. I always plugged in another usb charger in another port because of this annoying issue.


    So for v4.02 do you want me to:

    1. Flash v4.02
    2. Disconnect the battery and ac.
    3. Test if the laptop can charge via usbc?
    4. Plug in the dock see if it charges from the dock
    5. Unplug the dock see if it can be charged from the port where I just unplugged the port?
      If you write step by step instructions for me I can test and protocol the results for you in the new year.

    Otherwise you can get: TH3P4G3 PD 60W 85W on aliexpress or similar and plug in some gpu to test yourself.

  6. raldone01 commented on Jan 2, 2026

    @raldone01
    Author

    Updated to 4.03 BETA.
    Plugging in the egpu repeatedly yields error 256 and sometimes UCSI_GET_PDOS failed with various error codes.
    If I unplug the egpu again and plug in a charger it charges fine.

    [Jan 2 12:46] ucsi_acpi USBC000:00: unknown error 256
    [  +2.860972] ucsi_acpi USBC000:00: unknown error 256
    [  +4.051242] ucsi_acpi USBC000:00: unknown error 256
    [  +4.106089] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
    [ +14.662961] ucsi_acpi USBC000:00: unknown error 256
    [Jan 2 12:47] ucsi_acpi USBC000:00: unknown error 256
    [  +9.385292] ucsi_acpi USBC000:00: unknown error 256
    [  +6.093542] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
    [  +7.426429] ucsi_acpi USBC000:00: unknown error 256
    

    Replugging the battery does not change anything. I get the same errors and the egpu dock is not detected properly.

  7. raldone01 commented on Jan 15, 2026

    @raldone01
    Author

    Even on v3.7 power negotiation sometimes fails.
    So when I plug it in, the charge symbol appears on the battery for a second and then fails and doesn't charge.

    When the egpu is detected correctly, no charging happens and I have to use another power cable to also charge my laptop.

    Can you reproduce the problem with other EGPU docks?

  8. raldone01 commented on Jun 1, 2026

    @raldone01
    Author

    @JohnAZoidberg This is still an issue with the latest 4.04 and a clear regression. 3.07 is the last version that works. I would like to be able to use my egpu as before with newer versions of the firmware. This is quite frustrating and disappointing as this worked flawlessly in the past.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions