I am going to guess that the usb bus in question does not have enough allocated bandwidth. On usb2 that was a big problem that limited the number of web-cams usually to 1 per actual usb bus. I would suspect that removing the SSD may let the video device work. use the gui tool usbview and it should let you drill down and will tell you what other devices on the bus have allocated (assuming usb3/usb-c acts like usb2 for bandwidth), and make sure the SSD is not allocating the BW. On Mon, Jan 6, 2020 at 3:39 PM S.Bob <sbob@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > On 1/6/20 1:43 PM, Samuel Sieb wrote: > > On 1/6/20 12:14 PM, S.Bob wrote: > > On 1/6/20 2:29 AM, Samuel Sieb wrote: > > On 1/5/20 2:19 PM, S.Bob wrote: > > When I plug an external monitor into the USB-C port I usually see something like this via dmesg: > > > Is this a USB display device or is it a thunderbolt/displayport over USB-C device? Searching on the USB id suggests that it's probably the latter. > > > Not sure, how can I tell? If it's the latter do I need any added packages for it to work? > > > Do you have a link to the device? I'm a little fuzzy on how these things work, but I believe that there has to be support by the graphics card and driver to route the video output through the port. > > > I do not, see my journalctl output below > > > > > > [100335.446405] usb 1-3: new high-speed USB device number 11 using xhci_hcd > [100335.919043] usb 1-3: New USB device found, idVendor=2109, idProduct=0100, bcdDevice= 6.03 > [100335.919046] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [100335.919048] usb 1-3: Product: USB-C dongle > [100335.919050] usb 1-3: Manufacturer: VIA Technologies Inc. > [100335.919051] usb 1-3: SerialNumber: 0000000000000001 > [100340.101375] usb usb2-port3: Cannot enable. Maybe the USB cable is bad? > [100344.156355] usb usb2-port4: Cannot enable. Maybe the USB cable is bad? > > > $ lsusb > Bus 002 Device 003: ID 04e8:61f3 Samsung Electronics Co., Ltd Portable SSD T3 (MU-PT250B, MU-PT500B) > Bus 002 Device 002: ID 2109:0715 VIA Labs, Inc. VectoTech > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 04f2:b64a Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam > Bus 001 Device 028: ID 1038:120a SteelSeries ApS > Bus 001 Device 027: ID 05e3:0608 Genesys Logic, Inc. Hub > Bus 001 Device 026: ID 047d:1020 Kensington Expert Mouse Trackball > Bus 001 Device 025: ID 2109:2813 VIA Labs, Inc. > Bus 001 Device 024: ID 2109:2813 VIA Labs, Inc. > Bus 001 Device 023: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub > Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller > Bus 001 Device 006: ID 8087:0aaa Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > I don't see the device that was mentioned in the original logs you posted. It should be "ID 2109:0100". Can you run "journalct -fa" as root in a terminal, plug the device in, and copy the resulting logs? > > > # journalctl -fa > > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: new high-speed USB device number 41 using xhci_hcd > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: New USB device found, idVendor=2109, idProduct=0100, bcdDevice= 3.00 > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: Product: USB-C dongle > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: Manufacturer: VIA Technologies Inc. > Jan 06 14:36:24 Fedora31Host kernel: usb 1-3: SerialNumber: 0000000000000001 > Jan 06 14:36:25 Fedora31Host baloo_file[1437]: UdevQt: unhandled device action "bind" > Jan 06 14:36:25 Fedora31Host org_kde_powerdevil[1490]: UdevQt: unhandled device action "bind" > Jan 06 14:36:25 Fedora31Host plasmashell[1431]: UdevQt: unhandled device action "bind" > Jan 06 14:36:26 Fedora31Host kernel: usb usb2-port3: Cannot enable. Maybe the USB cable is bad? > Jan 06 14:36:30 Fedora31Host kernel: usb usb2-port4: Cannot enable. Maybe the USB cable is bad? > > > > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx