Bug 2363927 - TH3P4G3 eGPU with AMD RX5700 Doesn’t work in Fedora 42 on Intel Framework 13
Summary: TH3P4G3 eGPU with AMD RX5700 Doesn’t work in Fedora 42 on Intel Framework 13
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-04 02:27 UTC by ericcorp
Modified: 2026-06-08 17:04 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 17:04:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
journalctl logs from boot with 6.14.5-300.fc42.x86_64 (205.34 KB, text/plain)
2025-05-12 11:19 UTC, ericcorp
no flags Details

Description ericcorp 2025-05-04 02:27:33 UTC
1. Please describe the problem
eGPU doesn't work after update.  The eGPU is connected via USB-C to the laptop, the eGPU chassis has a USB-C out for a monitor and the GPU itself is connected via Display Port ot a monitor.  The USB-C monitor works, but the display port doesn't. The graphics card it self is never detected or loaded.

2. What is the Version-Release number of the kernel:

kernel-6.14.4-100.fc40.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes, it workles fine in  kernel-6.8.5-301.fc40.x86_64, with Fedora 40.  It also fails in 6.13 version, I haven't tested all the others as it's 

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Connect eGPU and it doesn't work

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes, with the latest 6.15 rawhide it fails as well

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Relevant snippet here, I can get the rest of it if necessary but I have to rebuild the device.

```
Apr 30 20:19:57 fedora kernel: amdgpu 0000:81:00.0: amdgpu: get invalid ip discovery binary signature
Apr 30 20:19:57 fedora kernel: [drm:amdgpu_discovery_reg_base_init [amdgpu]] *ERROR* amdgpu_discovery_init failed
Apr 30 20:19:57 fedora kernel: amdgpu 0000:81:00.0: amdgpu: Fatal error during GPU init
Apr 30 20:19:57 fedora kernel: amdgpu 0000:81:00.0: amdgpu: amdgpu: finishing device.
Apr 30 20:19:57 fedora kernel: amdgpu 0000:81:00.0: probe with driver amdgpu failed with error -22
```
lscpi and lsmod:
```
eric@fedora:~$  lspci |grep -i amd
7f:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1)
80:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
81:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1)
81:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
eric@fedora:~$ lsmod|grep -i amd
amdgpu              20312064  0
amdxcp                 12288  1 amdgpu
drm_ttm_helper         16384  2 amdgpu,xe
drm_exec               12288  3 drm_gpuvm,amdgpu,xe
gpu_sched              65536  2 amdgpu,xe
drm_suballoc_helper    16384  2 amdgpu,xe
drm_panel_backlight_quirks    12288  1 amdgpu
i2c_algo_bit           20480  3 amdgpu,xe,i915
ttm                   122880  4 amdgpu,drm_ttm_helper,xe,i915
drm_buddy              28672  3 amdgpu,xe,i915
drm_display_helper    307200  3 amdgpu,xe,i915
cec                   102400  4 drm_display_helper,amdgpu,xe,i915
video                  81920  3 amdgpu,xe,i915
eric@fedora:~$
```
```
eric@fedora:~$ inxi -Fzxx
System:
  Kernel: 6.14.4-300.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.0.1
  Desktop: GNOME v: 48.1 tk: GTK v: 3.24.49 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 42 (Workstation Edition)
Machine:
  Type: Laptop System: Framework product: Laptop (12th Gen Intel Core) v: A6
    serial: <superuser required>
  Mobo: Framework model: FRANGACP06 v: A6 serial: <superuser required>
    part-nu: FRANDACP06 UEFI: INSYDE v: 03.08 date: 12/25/2023
Battery:
  ID-1: BAT1 charge: 48.5 Wh (100.0%) condition: 48.5/55.0 Wh (88.2%)
    volts: 17.2 min: 15.4 model: NVT Framewo serial: <filter>
    status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) status: discharging
CPU:
  Info: 12-core (4-mt/8-st) model: 12th Gen Intel Core i7-1260P bits: 64
    type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.1 MiB L2: 9 MiB
    L3: 18 MiB
  Speed (MHz): avg: 1024 min/max: 400/4700:3400 cores: 1: 1024 2: 1024
    3: 1024 4: 1024 5: 1024 6: 1024 7: 1024 8: 1024 9: 1024 10: 1024 11: 1024
    12: 1024 13: 1024 14: 1024 15: 1024 16: 1024 bogomips: 79872
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Framework
    driver: i915 v: kernel arch: Xe ports: active: DP-3,eDP-1 empty: DP-1,
    DP-2, DP-4, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46a6
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600
    OEM/5600 XT / 5700/5700 XT] vendor: Micro-Star MSI driver: N/A
    arch: RDNA-1 pcie: speed: 16 GT/s lanes: 16 bus-ID: 81:00.0
    chip-ID: 1002:731f
  Device-3: Anker PowerConf C200
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 5-2.4:6 chip-ID: 291a:3369
  Display: wayland server: Xwayland v: 24.1.6 compositor: gnome-shell
    driver: gpu: i915 display-ID: 0
  Monitor-1: DP-3 model: Philips PHL 346E2C res: 3440x1440 dpi: 110
    diag: 864mm (34")
  Monitor-2: eDP-1 model: BOE Display 0x095f res: 2256x1504 dpi: 201
    diag: 343mm (13.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.0.4 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Iris Xe Graphics (ADL GT2)
    device-ID: 8086:46a6 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Framework
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:51c8
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 81:00.1 chip-ID: 1002:ab38
  Device-3: Microsoft USB Link driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 5-2.3:5
    chip-ID: 045e:083c
  Device-4: Anker PowerConf C200
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 5-2.4:6 chip-ID: 291a:3369
  API: ALSA v: k6.14.4-300.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: a6:00.0 chip-ID: 8086:2725
  IF: wlp166s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-10:3 chip-ID: 8087:0032
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12
Drives:
  Local Storage: total: 931.51 GiB used: 4.63 GiB (0.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 42.9 C
Partition:
  ID-1: / size: 487.28 GiB used: 4.23 GiB (0.9%) fs: btrfs dev: /dev/nvme0n1p6
  ID-2: /boot size: 973.4 MiB used: 363.3 MiB (37.3%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-3: /boot/efi size: 96 MiB used: 45.7 MiB (47.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 487.28 GiB used: 4.23 GiB (0.9%) fs: btrfs
    dev: /dev/nvme0n1p6
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2976
Info:
  Memory: total: 32 GiB note: est. available: 31.05 GiB used: 4.89 GiB (15.7%)
  Processes: 429 Power: uptime: 2h 4m wakeups: 6 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
    v: 5.2.37 running-in: ptyxis-agent inxi: 3.3.38
eric@fedora:~$
```



Reproducible: Always

Comment 1 ericcorp 2025-05-07 19:30:14 UTC
So I did some more testing, and it looks like it started with the 6.10 kernel.  If I rollback to before that it works normally.

Comment 2 ericcorp 2025-05-12 11:19:04 UTC
Same thing on 6.14.5-300.fc42.x86_64

journalctl output from the last boot attached, but same error:
```
May 12 07:14:15 fedora kernel: amdgpu 0000:81:00.0: amdgpu: get invalid ip discovery binary signature
May 12 07:14:15 fedora kernel: [drm:amdgpu_discovery_reg_base_init [amdgpu]] *ERROR* amdgpu_discovery_init failed
May 12 07:14:15 fedora kernel: amdgpu 0000:81:00.0: amdgpu: Fatal error during GPU init
May 12 07:14:15 fedora kernel: amdgpu 0000:81:00.0: amdgpu: amdgpu: finishing device.
May 12 07:14:15 fedora kernel: amdgpu 0000:81:00.0: probe with driver amdgpu failed with error -22
May 12 07:14:15 fedora kernel: pci 0000:81:00.1: D0 power state depends on 0000:81:00.0
```

Comment 3 ericcorp 2025-05-12 11:19:46 UTC
Created attachment 2089474 [details]
journalctl logs from boot with 6.14.5-300.fc42.x86_64

Comment 4 ericcorp 2025-06-04 00:36:19 UTC
Just checking in on this. It's still broken in the latest updates.

Comment 5 ericcorp 2025-08-07 17:43:23 UTC
Heyo so just to close the loop on this. I spent a lot of time fooling with this, updating etc. I finally got it working today.

I added this kernel options: `amdgpu.aspm=0` and it didn't' fix it, but then read that Kernel DMA can interfer with this, so I researched what that is and I found that it's also called Intel VT-d, which I disabled and it worked immediately fine right after. I don't want to roll back the kernel change since that seems to be required to, but for anyone looking for an answer it's the VT-d setting.

Comment 6 Fedora Release Engineering 2026-05-06 12:50:07 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Aoife Moloney 2026-06-08 17:04:00 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.