[SOLVED] Issues connecting to USB-C Monitor (AMD Ryzen AI 350)

Framework Laptop 13 Linux
1

Which Linux distro are you using?
OpenSUSE Tumbleweed

Which release version?
Up to date (today)

Which kernel are you using?
6.14.4

Which BIOS version are you using?
3.03

Which Framework Laptop 13 model are you using? (AMD Ryzen™ AI 300 Series, AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
AMD Ryzen AI 300

I received my laptop as part of Batch 1 and everything works great except connecting to my BenQ RD280U monitor over USB-C. It appears to be a charging issue as the charging LED will flash briefly and go off. Also, if the laptop is powered off, plugging in will not illuminate the charging LED.

This monitor/cable works fine with 2 other laptops (one Windows, one linux). I did try other cables just to be sure.

Here is a syslog of plugging the cable into the laptop, then unplugging. It does see the Logitech dongle connected to the monitor’s usb, so something is working right.

Please let me know if there is more information needed, or if anyone has any ideas.

Thanks!

Apr 29 18:06:01 rsp-framework kernel: pcieport 0000:00:08.3: PME: Spurious native interrupt!
Apr 29 18:06:01 rsp-framework kernel: xhci_hcd 0000:c3:00.4: Refused to change power state from D0 to D3hot
Apr 29 18:06:02 rsp-framework kernel: usb 7-1: new high-speed USB device number 2 using xhci_hcd
Apr 29 18:06:02 rsp-framework kernel: usb 7-1: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.18
Apr 29 18:06:02 rsp-framework kernel: usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:02 rsp-framework kernel: usb 7-1: Product: USB2.1 Hub
Apr 29 18:06:02 rsp-framework kernel: usb 7-1: Manufacturer: Generic
Apr 29 18:06:02 rsp-framework kernel: hub 7-1:1.0: USB hub found
Apr 29 18:06:02 rsp-framework kernel: hub 7-1:1.0: 6 ports detected
Apr 29 18:06:02 rsp-framework boltd[1582]: probing: started [1000]
Apr 29 18:06:02 rsp-framework kernel: ucsi_acpi USBC000:00: unknown error 0
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.4: new full-speed USB device number 3 using xhci_hcd
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.4: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.07
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.4: Product: USB Receiver
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.4: Manufacturer: Logitech
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.6: new high-speed USB device number 4 using xhci_hcd
Apr 29 18:06:03 rsp-framework kernel: usb 7-1.6: New USB device found, idVendor=0bda, idProduct=1100, bcdDevice= 1.01
Apr 29 18:06:04 rsp-framework kernel: usb 7-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:04 rsp-framework kernel: usb 7-1.6: Product: HID Device
Apr 29 18:06:04 rsp-framework kernel: usb 7-1.6: Manufacturer: Realtek
Apr 29 18:06:04 rsp-framework mtp-probe[2873]: checking bus 7, device 4: “/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.6”
Apr 29 18:06:04 rsp-framework mtp-probe[2874]: checking bus 7, device 3: “/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4”
Apr 29 18:06:04 rsp-framework mtp-probe[2874]: bus: 7, device: 3 was not an MTP device
Apr 29 18:06:04 rsp-framework mtp-probe[2873]: bus: 7, device: 4 was not an MTP device
Apr 29 18:06:04 rsp-framework kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.0/0003:046D:C52B.0004/input/input16
Apr 29 18:06:04 rsp-framework kernel: hid-generic 0003:046D:C52B.0004: input,hidraw3: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input0
Apr 29 18:06:04 rsp-framework kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.1/0003:046D:C52B.0005/input/input17
Apr 29 18:06:04 rsp-framework kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.1/0003:046D:C52B.0005/input/input18
Apr 29 18:06:04 rsp-framework kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.1/0003:046D:C52B.0005/input/input19
Apr 29 18:06:04 rsp-framework kernel: hid-generic 0003:046D:C52B.0005: input,hiddev96,hidraw4: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input1
Apr 29 18:06:04 rsp-framework kernel: hid-generic 0003:046D:C52B.0006: hiddev97,hidraw5: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input2
Apr 29 18:06:04 rsp-framework kernel: hid-generic 0003:0BDA:1100.0007: hiddev98,hidraw6: USB HID v1.11 Device [Realtek HID Device] on usb-0000:c3:00.4-1.6/input0
Apr 29 18:06:04 rsp-framework kernel: usbcore: registered new interface driver usbhid
Apr 29 18:06:04 rsp-framework kernel: usbhid: USB HID core driver
Apr 29 18:06:04 rsp-framework mtp-probe[2895]: checking bus 7, device 3: “/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4”
Apr 29 18:06:04 rsp-framework mtp-probe[2896]: checking bus 7, device 4: “/sys/devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.6”
Apr 29 18:06:04 rsp-framework mtp-probe[2896]: bus: 7, device: 4 was not an MTP device
Apr 29 18:06:04 rsp-framework mtp-probe[2895]: bus: 7, device: 3 was not an MTP device
Apr 29 18:06:04 rsp-framework kernel: usb 7-1: USB disconnect, device number 2
Apr 29 18:06:04 rsp-framework kernel: usb 7-1.4: USB disconnect, device number 3
Apr 29 18:06:04 rsp-framework kernel: logitech-djreceiver 0003:046D:C52B.0006: hiddev96,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input2
Apr 29 18:06:04 rsp-framework kernel: logitech-djreceiver 0003:046D:C52B.0006: usb_submit_urb(ctrl) failed: -19
Apr 29 18:06:04 rsp-framework kernel: logitech-djreceiver 0003:046D:C52B.0006: logi_dj_probe: logi_dj_recv_switch_to_dj_mode returned error:-19
Apr 29 18:06:04 rsp-framework kernel: usb 7-1.6: USB disconnect, device number 4
Apr 29 18:06:04 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:04 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:05 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:05 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:05 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:05 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:06 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:06 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:06 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:07 rsp-framework boltd[1582]: probing: timeout, done: [2975850] (2000000)
Apr 29 18:06:20 rsp-framework kernel: usb 7-1: new high-speed USB device number 5 using xhci_hcd
Apr 29 18:06:21 rsp-framework kernel: usb 7-1: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.18
Apr 29 18:06:21 rsp-framework kernel: usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:21 rsp-framework kernel: usb 7-1: Product: USB2.1 Hub
Apr 29 18:06:21 rsp-framework kernel: usb 7-1: Manufacturer: Generic
Apr 29 18:06:21 rsp-framework kernel: hub 7-1:1.0: USB hub found
Apr 29 18:06:21 rsp-framework kernel: hub 7-1:1.0: 6 ports detected
Apr 29 18:06:21 rsp-framework boltd[1582]: probing: started [1000]
Apr 29 18:06:21 rsp-framework kernel: ucsi_acpi USBC000:00: unknown error 0
Apr 29 18:06:21 rsp-framework kernel: usb 7-1.4: new full-speed USB device number 6 using xhci_hcd
Apr 29 18:06:21 rsp-framework kernel: usb 7-1.4: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.07
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.4: Product: USB Receiver
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.4: Manufacturer: Logitech
Apr 29 18:06:22 rsp-framework kernel: logitech-djreceiver 0003:046D:C52B.000A: hiddev96,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input2
Apr 29 18:06:22 rsp-framework kernel: input: Logitech Wireless Device PID:4069 Keyboard as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.2/0003:046D:C52B.000A/0003:046D:4069.000B/input/input21
Apr 29 18:06:22 rsp-framework kernel: input: Logitech Wireless Device PID:4069 Mouse as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.2/0003:046D:C52B.000A/0003:046D:4069.000B/input/input22
Apr 29 18:06:22 rsp-framework kernel: hid-generic 0003:046D:4069.000B: input,hidraw4: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4069] on usb-0000:c3:00.4-1.4/input2:1
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.6: new high-speed USB device number 7 using xhci_hcd
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.6: New USB device found, idVendor=0bda, idProduct=1100, bcdDevice= 1.01
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.6: Product: HID Device
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.6: Manufacturer: Realtek
Apr 29 18:06:22 rsp-framework kernel: hid-generic 0003:0BDA:1100.000C: hiddev97,hidraw5: USB HID v1.11 Device [Realtek HID Device] on usb-0000:c3:00.4-1.6/input0
Apr 29 18:06:22 rsp-framework kernel: usb 7-1.3: new full-speed USB device number 8 using xhci_hcd
Apr 29 18:06:22 rsp-framework kernel: usb 7-1: USB disconnect, device number 5
Apr 29 18:06:23 rsp-framework kernel: usb 7-1-port3: attempt power cycle
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:23 rsp-framework kernel: usb 7-1.4: USB disconnect, device number 6
Apr 29 18:06:23 rsp-framework kernel: usb 7-1.6: USB disconnect, device number 7
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:23 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:24 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:24 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:24 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:25 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1113: core_link_write_dpcd (DP_DOWNSPREAD_CTRL) failed
Apr 29 18:06:25 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1118: core_link_write_dpcd (DP_LANE_COUNT_SET) failed
Apr 29 18:06:25 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpcd_set_link_settings:1146: core_link_write_dpcd (DP_LINK_BW_SET) failed
Apr 29 18:06:25 rsp-framework kernel: amdgpu 0000:c1:00.0: [drm] enabling link 3 failed: 15
Apr 29 18:06:25 rsp-framework kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: Unknown ELD version 0
Apr 29 18:06:26 rsp-framework boltd[1582]: probing: timeout, done: [2671846] (2000000)
Apr 29 18:06:39 rsp-framework kernel: usb 7-1: new high-speed USB device number 12 using xhci_hcd
Apr 29 18:06:39 rsp-framework kernel: usb 7-1: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.18
Apr 29 18:06:39 rsp-framework kernel: usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:39 rsp-framework kernel: usb 7-1: Product: USB2.1 Hub
Apr 29 18:06:39 rsp-framework kernel: usb 7-1: Manufacturer: Generic
Apr 29 18:06:39 rsp-framework kernel: hub 7-1:1.0: USB hub found
Apr 29 18:06:39 rsp-framework kernel: hub 7-1:1.0: 6 ports detected
Apr 29 18:06:39 rsp-framework boltd[1582]: probing: started [1000]
Apr 29 18:06:39 rsp-framework kernel: ucsi_acpi USBC000:00: unknown error 0
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: new full-speed USB device number 13 using xhci_hcd
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.07
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: Product: USB Receiver
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: Manufacturer: Logitech
Apr 29 18:06:40 rsp-framework kernel: logitech-djreceiver 0003:046D:C52B.000F: hiddev96,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:c3:00.4-1.4/input2
Apr 29 18:06:40 rsp-framework kernel: input: Logitech MX Master 2S as /devices/pci0000:00/0000:00:08.3/0000:c3:00.4/usb7/7-1/7-1.4/7-1.4:1.2/0003:046D:C52B.000F/0003:046D:4069.0010/input/input26
Apr 29 18:06:40 rsp-framework kernel: usb 7-1: USB disconnect, device number 12
Apr 29 18:06:40 rsp-framework kernel: logitech-hidpp-device 0003:046D:4069.0010: input,hidraw4: USB HID v1.11 Keyboard [Logitech MX Master 2S] on usb-0000:c3:00.4-1.4/input2:1
Apr 29 18:06:40 rsp-framework kernel: usb 7-1.4: USB disconnect, device number 13
Apr 29 18:06:43 rsp-framework boltd[1582]: probing: timeout, done: [2601780] (2000000)

2

To follow up on this, I was playing around a bit more and found that swapping ends of my USB cable resulted in things working fine. So I’m guessing there is some cable defect that doesn’t cause problems with other laptops. I’m going to buy a new Thunderbird 4 rated cable and see how that goes.

3

I was able to get a USB4 cable and everything is working fine. Marked as solved.

4

I’m with AI 370 and the same monitor and also have the same problem, already tried 2 cables with no success, although they work fine with 2 other laptops. Your posts gave me hope, and tomorrow I’ll try to buy a new usb4 cable.. Thanks for the follow-ups..

5

This is what I got.

Hopefully the issue will not return

1 Like
6

Would note that this might be related to USB C is not compatible with iPhone 15 / Pro / Pro Max - #129 by JenJ as some people also complained their USB monitor is not usable.

7

It looks like my issue is related to the same PD bugs in AMD FrameWork laptops from the thread. Unfortunately on my side no cable was able to fix the issue as the OP. But I noticed that charging the laptop from one USB-C cable and connecting the monitor USB-C cable to another USB-C port of the laptop works fine, except for the fact that I have to use 2 cables and a charger. Unplugging the charging cable may keep the screen on for half a minute or so, but eventually it turns off.

8

I don’t seem to be able to remove the SOLVED tag, but this issue is still present.

It seems if I plug the monitor in with the laptop fully charged (white LED when charging), everything works fine, but if I plug in with the battery below 85%, it does not work. The last time I tried, I must have had the laptop fully charged. This is consistent with all 3 cables I have.

For now I have a USB-C to Display Port dongle that works fine. I’ll just need to charge separately until a fix is available.

9

That is a little worrying, I’ve just replaced my Samsung M7 monitor with a BenQ RD320U, mostly for USB-C compatibility reasons (and so far every device worked with it). Hope it will be fully compatible with the Framework Laptop 12.

10

FW12 is with intel CPU which should not be affected by this issue.

1 Like
11

There’s a Redditor experiencing the same issue with the AI 370 and a Dell U2725QE, which suggests the problem isn’t specific to BenQ monitors. I really hope this isn’t a hardware limitation and that a fix can be provided in the future.

Is there anyone who’s been able to connect their new AI-series laptop to a USB-C monitor successfully?

12

I actually don’t have problem with Samsung M7 (1st gen), what was the actual problem you encounter?

13

It is the 32" version of the Samsung M7, not sure which revision because it’s now packed up in a box. But my Mac and handheld were never able to output video over USB-C, it only worked on Linux for the first couple of days, then stopped. I cannot even use the USB-C port to charge anything, the charging indicator goes on and off all the time. I have tried updating the firmware and using a different cable, to no avail. There are various threads about USB-C being wonky with this monitor, mostly from Mac users, so I assumed that’s just how it is.

All is wonderful with the BenQ RD320U so far, I hope it stays that way. It was silly of me to worry about the FL12 because that is indeed an Intel machine, but I have also ordered a Framework Desktop, so I hope the RD320U will work with that too.

14

Just adding another data point: BenQ RD280U with FW 13 AMD Ryzen AI 370. Had the same issues - charging light just briefly flashes, but nothing happening - no charging no monitor over USB C / DP.
Tried Ubuntu 24.04 LTS (Kernel 6.11). Could not get 6.13 to run and stopped messing around after a while.
Tried Windows 10 with official driver package and noticed, that the USB devices were missing drivers, so no big surprise here that it did not work. Not sure why they were missing, did not bother to try with Windows 11.

Same monitor works flawlessly with FW 13 AMD Ryzen 7840U.