KVM switch not sending image through usb

git000 · 2024-08-15 16:01:07

Hello,

I am having problems with my KVM switch. As subject says, It wont send any image through usb. I've done reaserch on the topic and contacted customer support of switch, with no success.

Hardware relevant to problem i am encountering:

KVM Switch: Unitek D1103A01
GPU: NVIDIA RTX3070ti

What is not exactly working:

On the Displaylink Arch Wiki site in paragraph 2.1 there is example output from 'dmesg' command, mine differs. Its the only thing i found.

What i tried:

I have successfully changed session type to Wayland
I did install DisplayLink, and enabled its service
Find anything about kernel error codes in dmesg command output
taking a look for Ubuntu driver available here : https://www.synaptics.com/products/disp … ads/ubuntu

I am attaching the log from mentioned command ( https://paste.rs/mcsz8 ). I hope it helps to troubleshoot the problem. Thanks in advance for your spent Time !

git000 · 2024-08-16 10:18:13

Hello Again!

I found additional info on producer's forum, that tells about porting their ubuntu software to other distributions.
Due to my limited knowledge, I don't really know what are those given files about, but it may help to solve the problem for some advanced users.\

If you want to help, please take a look here: https://support.displaylink.com/knowled … les/679060

Lone_Wolf · 2024-08-16 10:21:54

At first glance this didn't look like a displaylink device, but https://www.unitek-products.com/product … ng-station does have instructions to download a driver from displaylink .

So I looked at the log (which doesn't seen to be complete) and noticed :

[    0.039637] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=e24472aa-474c-4420-baba-7f54c65a2397 rw zswap.enabled=0 rootfstype=ext4 loglevel=3 nomodeset nvidia-drm.modeset=1 NVreg_PreserveVideoMemoryAllocations=1
[    0.039678] Booted with the nomodeset parameter. Only the system framebuffer will be available

nomodeset should only be used as a last resort to get to a console screen to troubleshoot .

To simplify the setup move the dock away and attach keyboard and monitor directly (mouse is optional) .
remove the kernel parameter nomodeset and append systemd.unit=multi-user.target .

In case this doesn't get you to a console login screen your setup has much bigger issues then a dock that doesn't function as intended.

git000 · 2024-08-16 22:31:01

So i did partly what you suggested, removed 'nomodeset' from kernel parameters and remade grub config. I couldn't notice any difference from previous state, dkmes still doesnt contain anything with word 'displaylink'.

Wasn't sure about systemd.unit part. Firstly i tried to add this to GRUB flags before compilation but it didn't work. As i was searching wiki to educate myself i noticed that it just simply sets graphical mode to cli and thus because i couldn't find how to apply it i skipped that part.

Is this second part crucial and should i attach any logs after that?
Please let me know, and thank you for your support!

Lone_Wolf · 2024-08-17 12:34:15

Wasn't sure about systemd.unit part. Firstly i tried to add this to GRUB flags before compilation but it didn't work. As i was searching wiki to educate myself i noticed that it just simply sets graphical mode to cli and thus because i couldn't find how to apply it i skipped that part.

How to add kernel parameters depends on the boot loader, for grub https://wiki.archlinux.org/title/GRUB#A … _arguments describes where to put them.

Is this second part crucial and should i attach any logs after that?

There are cases where systems don't succesfully reach graphical target and make users think their their systems are not booting correctly .

Very often (especially for systems with nvidia cards) the problem is in the graphical or display manager setup and booting works fine except that part.
People that lack understanding of the linux/systemd boot process search for nvidia+boot problems + linux and find lots of references to nomodeset .

Forcing a boot to cli by adding systemd.unit=multi-user.target as kernel parameters is then a useful troublehooting step to determine where the issue lies.

TL;DR : not critical/crucial , but very useful to narrow down possible causes and get access for troubleshooting .

Now that it is clear your system does boot to graphical target succesfully and (I assume) you can login, we can look further .

Many docks have their own firmware that can (and often needs to) be upgraded, but I can't find info on the unitek site if this is one of them.
Did support ask you to check the firmware version for your dock ?

Porting the driver to archlinux is not needed, as that's been done by others already .

For clarity:
Did you build & install the aur packages for latest evdi (1.14.5-0) and displaylink (6.0-0) ?

Please run the following command as root (or with root rights)

# journalctl -b | curl -F 'file=@-' 0x0.st

It will output a link, please post that link .

git000 · 2024-08-17 14:39:31

Thank You for Your explanation and link to wiki. It was very helpful to know how things work, especially for me as a beginner with arch.

I made sure through 'yay' command that I have in fact installed evdi 1.14.5-0 and displaylink 6.0-0.

Somehow log hosting that you proposed didn't work for me ( It says that my IP is banned due to recent abuse, but I don't remember using it at all and neither does my history command) but here is this same journal entry on other hosting recommended on wiki:
https://paste.rs/sW7x6 .
I had also contacted the person listed on 0x0.st website to deal with latter problem but i assume that it is not in the scope of this thread.

Lone_Wolf · 2024-08-17 15:02:21

Somehow log hosting that you proposed didn't work for me ( It says that my IP is banned due to recent abuse, but I don't remember using it at all and neither does my history command) but here is this same journal entry on other hosting recommended on wiki:
https://paste.rs/sW7x6 .
I had also contacted the person listed on 0x0.st website to deal with latter problem but i assume that it is not in the scope of this thread.

Correct, lately there was a post where a user from china mentioned they were blocked although they hadn't used 0x0.st before so it seems 0x0.st may be blocking ip-ranges .

Although the log does mention evdi, let's check the dkms setup.

You are using the linux-zen kernel , do you have linux-zen-headers installed ?
What is the output of (as root) dkms status ?

Assuming those check out :

boot without the dock attached
After logging in as user leave the system alone for a minute or 2 to allow things to setlle .

Attach the dock/kvm switch , wait a minute .
Post fresh journal .

edit : typos

Last edited by Lone_Wolf (2024-08-17 15:03:44)

git000 · 2024-08-17 15:41:12

I belive i had installed headers or had already installed. Here is the output of sudo dkms status:

evdi/1.14.4: added
evdi/1.14.5, 6.10.5-zen1-1-zen, x86_64: installed
nvidia/555.58.02, 6.10.5-zen1-1-zen, x86_64: installed

Also to be sure checked it through packet manager after boot and those header checks out.
I followed the procedure and here is a journal from given instructions https://paste.rs/DTJKb .
Dock is currently unoccupied, i disconnected microphone to not bloat the journal, i hope it was no mistake.

Lone_Wolf · 2024-08-17 16:23:49

sie 17 17:36:16 GainIT kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
sie 17 17:36:16 GainIT kernel: usb 3-1: New USB device found, idVendor=2109, idProduct=2822, bcdDevice= 1.34
sie 17 17:36:16 GainIT kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
sie 17 17:36:16 GainIT kernel: usb 3-1: Product: USB2.0 Hub             
sie 17 17:36:16 GainIT kernel: usb 3-1: Manufacturer: VIA Labs, Inc.         
sie 17 17:36:16 GainIT kernel: hub 3-1:1.0: USB hub found
sie 17 17:36:16 GainIT kernel: hub 3-1:1.0: 5 ports detected
sie 17 17:36:17 GainIT kernel: usb 3-1.4: new high-speed USB device number 3 using xhci_hcd
sie 17 17:36:17 GainIT kernel: usb 3-1.4: New USB device found, idVendor=2109, idProduct=2817, bcdDevice=90.14
sie 17 17:36:17 GainIT kernel: usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
sie 17 17:36:17 GainIT kernel: usb 3-1.4: Product: USB2.0 Hub             
sie 17 17:36:17 GainIT kernel: usb 3-1.4: Manufacturer: VIA Labs, Inc.         
sie 17 17:36:17 GainIT kernel: usb 3-1.4: SerialNumber: 000000000
sie 17 17:36:17 GainIT kernel: hub 3-1.4:1.0: USB hub found
sie 17 17:36:17 GainIT kernel: hub 3-1.4:1.0: 4 ports detected
sie 17 17:36:21 GainIT kernel: usb 3-1.5: new high-speed USB device number 4 using xhci_hcd
sie 17 17:36:21 GainIT kernel: usb 3-1.5: New USB device found, idVendor=2109, idProduct=8822, bcdDevice= 0.01
sie 17 17:36:21 GainIT kernel: usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
sie 17 17:36:21 GainIT kernel: usb 3-1.5: Product: USB Billboard Device   
sie 17 17:36:21 GainIT kernel: usb 3-1.5: Manufacturer: VIA Labs, Inc.         
sie 17 17:36:21 GainIT mtp-probe[5831]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.2/0000:20:04.0/0000:25:00.0/usb3/3-1/3-1.5"
sie 17 17:36:21 GainIT mtp-probe[5831]: bus: 3, device: 4 was not an MTP device
sie 17 17:36:21 GainIT mtp-probe[5833]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.2/0000:20:04.0/0000:25:00.0/usb3/3-1/3-1.5"
sie 17 17:36:21 GainIT mtp-probe[5833]: bus: 3, device: 4 was not an MTP device
sie 17 17:36:25 GainIT kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
sie 17 17:36:25 GainIT kernel: usb 4-1: New USB device found, idVendor=2109, idProduct=0822, bcdDevice= 1.34
sie 17 17:36:25 GainIT kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
sie 17 17:36:25 GainIT kernel: usb 4-1: Product: USB3.1 Hub             
sie 17 17:36:25 GainIT kernel: usb 4-1: Manufacturer: VIA Labs, Inc.         
sie 17 17:36:25 GainIT kernel: hub 4-1:1.0: USB hub found
sie 17 17:36:25 GainIT kernel: hub 4-1:1.0: 4 ports detected
sie 17 17:36:26 GainIT kernel: usb 4-1: USB disconnect, device number 2
sie 17 17:36:26 GainIT kernel: usb 4-1: Failed to suspend device, error -19
sie 17 17:36:47 GainIT kernel: usb 4-1: new SuperSpeed USB device number 4 using xhci_hcd
sie 17 17:36:52 GainIT kernel: xhci_hcd 0000:25:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
sie 17 17:36:52 GainIT kernel: usb 4-1: unable to get BOS descriptor set
sie 17 17:36:52 GainIT kernel: usb 4-1: unable to read config index 0 descriptor/start: -19
sie 17 17:36:52 GainIT kernel: usb 4-1: Device not responding to setup address.
sie 17 17:36:53 GainIT kernel: usb 4-1: Device not responding to setup address.
sie 17 17:36:53 GainIT kernel: usb 4-1: device not accepting address 5, error -71
sie 17 17:36:53 GainIT kernel: usb usb4-port1: attempt power cycle
sie 17 17:36:53 GainIT kernel: usb 4-1: new SuperSpeed USB device number 6 using xhci_hcd
sie 17 17:36:59 GainIT kernel: xhci_hcd 0000:25:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
sie 17 17:36:59 GainIT kernel: usb 4-1: device descriptor read/all, error -110

The lines starting with usb disconnect are what worries me.

The device 0000:25:00.0 is described elsewhere in the log :

sie 17 17:30:07 GainIT kernel: pci 0000:25:00.0: [1b21:3242] type 00 class 0x0c0330 PCIe Legacy Endpoint
sie 17 17:30:07 GainIT kernel: pci 0000:25:00.0: BAR 0 [mem 0xfc300000-0xfc307fff 64bit]
sie 17 17:30:07 GainIT kernel: pci 0000:25:00.0: PME# supported from D0 D3hot D3cold
sie 17 17:30:07 GainIT kernel: pci 0000:25:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:20:04.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)

The 4 Gb/s indicates this is a PCIe 4 device, but why would such a device be listed as PCIe legacy endpoint ?

Please post full lspci -tv and lsusb -tv output , with and without the dock attached .

git000 · 2024-08-17 16:30:24

Difference between logs where u indicates usb and 1indicates dock connected:

[git000@GainIT ~]$ diff d0p.txt d1p.txt 
[git000@GainIT ~]$ diff d0u.txt d1u.txt 
18a19,24
>     |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/5p, 480M
>         ID 2109:2822 VIA Labs, Inc. 
>         |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
>             ID 2109:2817 VIA Labs, Inc. 
>         |__ Port 005: Dev 007, If 0, Class=Billboard, Driver=[none], 480M
>             ID 2109:8822 VIA Labs, Inc.

Whole logs:
lspci -tv with dock connected:

-[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
           +-00.2  Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
           +-01.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-01.1-[01]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
           +-01.3-[03-28]--+-00.0  Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller
           |               +-00.1  Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller
           |               \-00.2-[20-28]--+-00.0-[21]--
           |                               +-01.0-[22]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
           |                               +-04.0-[25]----00.0  ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
           |                               +-05.0-[26]----00.0  Intel Corporation Wi-Fi 6 AX200
           |                               +-06.0-[27]--
           |                               \-07.0-[28]--
           +-02.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-03.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-03.1-[29]--+-00.0  NVIDIA Corporation GA104 [GeForce RTX 3070 Ti]
           |            \-00.1  NVIDIA Corporation GA104 High Definition Audio Controller
           +-04.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-05.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-07.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-07.1-[2a]----00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
           +-08.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-08.1-[2b]--+-00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
           |            +-00.1  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
           |            +-00.3  Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
           |            \-00.4  Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
           +-14.0  Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
           +-14.3  Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
           +-18.0  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
           +-18.1  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
           +-18.2  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
           +-18.3  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
           +-18.4  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
           +-18.5  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
           +-18.6  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
           \-18.7  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7

lspci -tv no dock:

-[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
           +-00.2  Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
           +-01.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-01.1-[01]----00.0  Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
           +-01.3-[03-28]--+-00.0  Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller
           |               +-00.1  Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller
           |               \-00.2-[20-28]--+-00.0-[21]--
           |                               +-01.0-[22]----00.0  Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
           |                               +-04.0-[25]----00.0  ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
           |                               +-05.0-[26]----00.0  Intel Corporation Wi-Fi 6 AX200
           |                               +-06.0-[27]--
           |                               \-07.0-[28]--
           +-02.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-03.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-03.1-[29]--+-00.0  NVIDIA Corporation GA104 [GeForce RTX 3070 Ti]
           |            \-00.1  NVIDIA Corporation GA104 High Definition Audio Controller
           +-04.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-05.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-07.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-07.1-[2a]----00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
           +-08.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
           +-08.1-[2b]--+-00.0  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
           |            +-00.1  Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
           |            +-00.3  Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
           |            \-00.4  Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
           +-14.0  Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller
           +-14.3  Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
           +-18.0  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
           +-18.1  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
           +-18.2  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
           +-18.3  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
           +-18.4  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
           +-18.5  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
           +-18.6  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
           \-18.7  Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7

lsusb -tv with dock :

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 003: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0c45:652f Microdia Backlit Gaming Keyboard
    |__ Port 003: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0c45:652f Microdia Backlit Gaming Keyboard
    |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
    |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
    |__ Port 005: Dev 004, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
    |__ Port 005: Dev 004, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 001: Dev 005, If 0, Class=Hub, Driver=hub/5p, 480M
        ID 2109:2822 VIA Labs, Inc. 
        |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 2109:2817 VIA Labs, Inc. 
        |__ Port 005: Dev 007, If 0, Class=Billboard, Driver=[none], 480M
            ID 2109:8822 VIA Labs, Inc. 
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub

lsusb -tv without dock :

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 003: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0c45:652f Microdia Backlit Gaming Keyboard
    |__ Port 003: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 0c45:652f Microdia Backlit Gaming Keyboard
    |__ Port 004: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
    |__ Port 004: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
    |__ Port 005: Dev 004, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
    |__ Port 005: Dev 004, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 20000M/x2
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub

Edit: formatting to make it more clear

Last edited by git000 (2024-08-17 16:36:31)

Lone_Wolf · 2024-08-19 10:48:30

So as kinda expected no changes in the pci setup, only the usb part.

Also no sign of the displaylink device in lsusb output .

The displaylink release notes have 2 interesting bits of info :

Supported Linux Kernel version range is from 4.15 to 6.8.

Device families supported:
- DL-7xxx
- DL-6xxx
- DL-5xxx
- DL-41xx
- DL-3xxx

Are any of those device families mentioned on the hardware ?

Try with the linux-lts kernel .

git000 · 2024-08-19 18:14:40

From curiosity i launched my old partition with windows 11 install, and tried to configure kvm from there with 'supported' driver. It seems it is not working on windows either. I will write to customer support in that matter, if anyone has idea why it could be, i am posting my hardware here : https://paste.rs/up1sW ( hwinfo --short at the beginning, later full hwinfo invocation).
I will also try writing to support once again, but they ghosted me last time so i do not expect much. Sorry that i am not following Your questions this time, tell me in case i still should, but i suppose that if it doesn't work on 2 different operating systems, it is no software issue. Also due to that plot twist i should probably remove old logs from paste.rs, is that correct? Anyway thanks for Your help and commitment also please let me know if i should close this thread, or since the problem still exists should I leave it open until i solve it?

Lone_Wolf · 2024-08-20 10:38:36

It does look to be hardware related, did it work in the past ?

Whether you keep the old pastes or remove them is a personal preference.
Does paste.rs allow removing them ?

I suggest you keep the thread open, there are people following this (number of views has gone up after every post)..

git000 · 2024-08-22 15:27:31

Alright, after contacting customer support and fixing some minor issues it works, but unfortunately on windows for now (since they don't officially support arch). In that case I guess we are still in this same point where we left debugging this. Gonna install second Kernel this evening hopefully.

git000 · 2024-08-22 21:50:29

Hi, I didn't install LTS kernel yet but i noticed something. Before installing new kernel i run 'pacman -Syu' to have things up to date, and noticed some wierd adnotations to evdi. It told me to check the log file and i found there something like this:

/var/lib/dkms/evdi/1.14.4/build/evdi_gem.c:319:25: error: implicit declaration of function ‘vmap’; did you mean ‘kmap’? [-Wimplicit-function-declaration]
  319 |         obj->vmapping = vmap(obj->pages, page_count, 0, PAGE_KERNEL);
      |                         ^~~~
      |                         kmap
/var/lib/dkms/evdi/1.14.4/build/evdi_gem.c:319:23: error: assignment to ‘void *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
  319 |         obj->vmapping = vmap(obj->pages, page_count, 0, PAGE_KERNEL);
      |                       ^
/var/lib/dkms/evdi/1.14.4/build/evdi_gem.c: In function ‘evdi_gem_vunmap’:
/var/lib/dkms/evdi/1.14.4/build/evdi_gem.c:355:17: error: implicit declaration of function ‘vunmap’; did you mean ‘kunmap’? [-Wimplicit-function-declaration]
  355 |                 vunmap(obj->vmapping);
      |                 ^~~~~~
      |                 kunmap
make[3]: *** [scripts/Makefile.build:244: /var/lib/dkms/evdi/1.14.4/build/evdi_gem.o] Błąd 1
make[3]: *** Oczekiwanie na niezakończone zadania....
make[2]: *** [/usr/lib/modules/6.10.6-zen1-1-zen/build/Makefile:1932: /var/lib/dkms/evdi/1.14.4/build] Błąd 2
make[1]: *** [Makefile:240: __sub-make] Błąd 2
make[1]: Opuszczenie katalogu '/usr/lib/modules/6.10.6-zen1-1-zen/build'
make: *** [Makefile:38: all] Błąd 1

Moreover i noticed that 2nd monitor (bcause i tested setup with one plugged directly into pc and other through kvm switch) is still like present but doesnt display anything, and what i mean by that is that i can switch browser windows or apps to 2nd monitor using shift+special+arrow combination, coursor also sinks into 2nd monitor, not limiting itself to the edge of 1st display. From curiosity i googled my way to list displays command and i found xrandr --listmonitors (below).

[git000@GainIT ~]$ xrandr --listmonitors
Monitors: 2
 0: +*DP-1 1920/530x1080/300+0+0  DP-1
 1: +DVI-I-1 1920/530x1080/300+1920+0  DVI-I-1

I hope that those remarks will lead us somewhere, I'm going back to the wiki & google to search how to install this second kernel.

git000 · 2024-09-02 11:05:33

Alright, i finally managed to spend some time on this issue again. What I did for now:

Installed linux-lts and linux-lts-headers and made new grub config with command grub-mkconfig -o /boot/grub/grub.cfg
Followed 3.7 debugging guide in displaylink since case described there is the situation i am currently in. ( https://wiki.archlinux.org/title/DisplayLink#Impossible_to_activate_displaylink's_screen )
Removed evdi 1.14.4 from zen because it was causing errors in the DKMS logs ( it was installed to linux lts tho and did not return any error messages, as i found on some evdi github site issue was fixed in 1.14.5)

None of those solutions are working, monitor is listed on xrandir i can throw windows at second screen but it stays inactive like it didnt have input given. 2nd Desktop I assume is rendered but image output not given to monitor connected no matter if used kernel is zen or lts.
Also i'd like to know what do you think about all AUR evdi modules? I have no idea what are the differences between those but if anyone has experience please share your knowledge.

I dont know what else should i try to do, any ideas?

EDIT:
Also i noticed that xrandr lists different output type depending on where i connect the cabel. Dock returns DVI-I-1 while cable HDMI-1. I wonder if that changes something

Last edited by git000 (2024-09-02 11:46:30)

Arch Linux

#1 2024-08-15 16:01:07

KVM switch not sending image through usb

#2 2024-08-16 10:18:13

Re: KVM switch not sending image through usb

#3 2024-08-16 10:21:54

Re: KVM switch not sending image through usb

#4 2024-08-16 22:31:01

Re: KVM switch not sending image through usb

#5 2024-08-17 12:34:15

Re: KVM switch not sending image through usb

#6 2024-08-17 14:39:31

Re: KVM switch not sending image through usb

#7 2024-08-17 15:02:21

Re: KVM switch not sending image through usb

#8 2024-08-17 15:41:12

Re: KVM switch not sending image through usb

#9 2024-08-17 16:23:49

Re: KVM switch not sending image through usb

#10 2024-08-17 16:30:24

Re: KVM switch not sending image through usb

#11 2024-08-19 10:48:30

Re: KVM switch not sending image through usb

#12 2024-08-19 18:14:40

Re: KVM switch not sending image through usb

#13 2024-08-20 10:38:36

Re: KVM switch not sending image through usb

#14 2024-08-22 15:27:31

Re: KVM switch not sending image through usb

#15 2024-08-22 21:50:29

Re: KVM switch not sending image through usb

#16 2024-09-02 11:05:33

Re: KVM switch not sending image through usb

Board footer