Issues with USB-C alt mode dock

Bidski · 2025-10-23 21:50:40

seth wrote:

nouveau loads fine but doesn't see any outputs.

It is interesting that nouveau doesn't see any outputs. Is Gnome Display settings just showing the monitors as being there because of previous configuration?

seth wrote:

swap to a tty and
sudo systemctl restart gdm
and the external monitors will start then become active.
still works (w/ nouvau or nvidia)?
Do you have a journal from such a run?

I have not needed to try this since I first reported this. I will see if I can replicate this next week

seth · 2025-10-23 21:58:52

They're stored in ~/.config/monitors.xml but you also want to check https://man.archlinux.org/man/gdctl.1

Bidski · 2025-11-26 22:58:02

Sorry for the lengthy delay, it has been a hectic couple of weeks.

seth wrote:

swap to a tty and
sudo systemctl restart gdm
and the external monitors will start then become active.
still works (w/ nouvau or nvidia)?
Do you have a journal from such a run?

I think now, we have progressed passed this point and I no longer run into this issue in the same way that I did when I reported that. If I have the dock plugged in at boot I usually have the laptop monitor and 1 external monitor active. Swapping to a tty and restarting gdm doesn't affect this.

I tried doing this with nvidia blacklisted and using nouveau. This also doesn't seem to have any affect. Here are the logs for this boot http://0x0.st/K4z2.txt

These logs are from the same boot, but are from after I tried to re-enable the monitors. Not sure if these have captured anything, but this is one of those weird scenarios where I can move the mouse around the screen, but I can't interact with any applications http://0x0.st/K4z9.txt

Because I couldn't interact with anything, I had to force power off the laptop (holding down the power button). This appeared to leave the dock in an inconsistent state, this boot had to wait for 1m 30s for devices to enumerate (I believe the boot was waiting on "Rule-based Manager for Device Events and Files") and the dock never came up properly (no keyboard and mouse) http://0x0.st/K4zt.txt

Finally, based on this other thread (https://bbs.archlinux.org/viewtopic.php … 2#p2268262) I tried module_blacklist=nvidia_uvm,ucsi_cc (I don't have wl on this system). This also did not appear to help with anything. I also just realised I had a typo and was meant to blacklist ucsi_ccg, not usci_cc, either way usci_ccg does not appear in lsmod anyway http://0x0.st/K4z3.txt

seth · 2025-11-28 21:25:35

blacklisting uvm and ucsi_ccg is moot if using nouveau didn't change anything.

Nov 27 09:04:47 archlinux kernel: usb usb3-port1: attempt power cycle
Nov 27 09:04:56 archlinux kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:05:04 archlinux kernel: usb usb3-port1: attempt power cycle
Nov 27 09:05:12 archlinux kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:05:20 archlinux kernel: usb usb3-port1: attempt power cycle
Nov 27 09:05:23 archlinux systemd-udevd[262]: usb3: Worker [285] processing SEQNUM=2481 is taking a long time.
Nov 27 09:05:29 archlinux kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:05:37 archlinux kernel: usb usb3-port1: attempt power cycle
Nov 27 09:05:45 archlinux kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:05:53 archlinux kernel: usb usb3-port1: attempt power cycle
Nov 27 09:05:57 4AISLT001 mtp-probe[619]: checking bus 3, device 6: "/sys/devices/pci0000:80/0000:80:14.0/usb3/3-8"
Nov 27 09:05:57 4AISLT001 mtp-probe[685]: checking bus 3, device 6: "/sys/devices/pci0000:80/0000:80:14.0/usb3/3-8"
Nov 27 09:06:01 4AISLT001 kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:06:10 4AISLT001 kernel: usb usb3-port1: attempt power cycle
Nov 27 09:06:18 4AISLT001 kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:06:26 4AISLT001 kernel: usb usb3-port1: attempt power cycle
Nov 27 09:06:34 4AISLT001 kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:06:43 4AISLT001 kernel: usb usb3-port1: attempt power cycle
Nov 27 09:06:50 4AISLT001 kernel: usb usb3-port1: unable to enumerate USB device
Nov 27 09:06:50 4AISLT001 mtp-probe[7245]: checking bus 3, device 6: "/sys/devices/pci0000:80/0000:80:14.0/usb3/3-8"
Nov 27 09:06:58 4AISLT001 kernel: usb usb3-port1: attempt power cycle
Nov 27 09:07:07 4AISLT001 kernel: usb usb3-port1: unable to enumerate USB device

Did you attempt to power cycle the dock (ie. unplug every cable, wait, replug and retry)?

Because I couldn't interact with anything, I had to force power off the laptop (holding down the power button).

Avoid that at all costs, https://wiki.archlinux.org/title/Keyboa … el_(SysRq) or ssh into the system.

Nov 27 09:02:04 4AISLT001 kernel: ACPI: PM: Waking up from system sleep state S3
Nov 27 09:02:04 4AISLT001 kernel: ACPI: EC: interrupt unblocked
Nov 27 09:02:04 4AISLT001 kernel: nouveau 0000:01:00.0: Enabling HDA controller
Nov 27 09:02:04 4AISLT001 kernel: ACPI: EC: event unblocked
Nov 27 09:02:04 4AISLT001 kernel: xhci_hcd 0000:00:0d.0: xHC error in resume, USBSTS 0x401, Reinit
Nov 27 09:02:04 4AISLT001 kernel: usb usb1: root hub lost power or was reset
Nov 27 09:02:04 4AISLT001 kernel: usb usb2: root hub lost power or was reset
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0051: Failed to write b = 0: -6
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0051: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0051: PM: failed to resume async: error -6
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0053: Failed to write b = 0: -6
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0053: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Nov 27 09:02:04 4AISLT001 kernel: spd5118 20-0053: PM: failed to resume async: error -6
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.53.0
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.53.0
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
Nov 27 09:02:04 4AISLT001 kernel: nvme nvme0: 24/0/0 default/read/poll queues
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
Nov 27 09:02:04 4AISLT001 kernel: i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads
Nov 27 09:02:04 4AISLT001 kernel: usb 3-8: reset high-speed USB device number 3 using xhci_hcd
Nov 27 09:02:04 4AISLT001 kernel: r8152 4-1.1:1.0 enp128s20f0u1u1: carrier on
Nov 27 09:02:04 4AISLT001 kernel: nouveau 0000:01:00.0: [drm] *ERROR* Sending link address failed with -5
Nov 27 09:02:04 4AISLT001 kernel: mei_gsc_proxy 0000:80:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915])
Nov 27 09:02:04 4AISLT001 kernel: OOM killer enabled.
Nov 27 09:02:04 4AISLT001 kernel: Restarting tasks: Starting
Nov 27 09:02:04 4AISLT001 kernel: Restarting tasks: Done
Nov 27 09:02:04 4AISLT001 kernel: random: crng reseeded on system resumption
Nov 27 09:02:04 4AISLT001 kernel: video LNXVIDEO:00: Restoring backlight state
Nov 27 09:02:04 4AISLT001 kernel: PM: suspend exit
Nov 27 09:02:04 4AISLT001 systemd[1]: nvidia-resume.service: Deactivated successfully.

You had the nvidia VRAM preservation services active along nouveau, might have botched the framebuffer update (ie. you're actually interacting, but looking at a frozen frame)

Yazore · 2025-12-03 06:57:59

I faced a similar issue and found not quite a solution, but rather a workaround.

I have noticed that if I set the grub timer to be 1 or 2 seconds, it boots in time to avoid some kind of "loss" of the external monitor's connection that would otherwise happen if the boot sequence were to take too long for the monitor to go on power saving mode.

I still face issues, though. For instance, sleeping and turning of the screens to save power seem to affect the connection. Hibernation, however, works without problems.

It's an LG monitor, is that the same case for you Bidski?

Arch Linux

#26 2025-10-23 21:50:40

Re: Issues with USB-C alt mode dock

#27 2025-10-23 21:58:52

Re: Issues with USB-C alt mode dock

#28 2025-11-26 22:58:02

Re: Issues with USB-C alt mode dock

#29 2025-11-28 21:25:35

Re: Issues with USB-C alt mode dock

#30 2025-12-03 06:57:59

Re: Issues with USB-C alt mode dock

Board footer