Arch Linux User Repository

I installed the package as follows:

Kernel 6.12.18-1-lts

evdi 1.14.8-1 (because this appeared to be more up to date than evdi-git?)

displaylink 6.1-1

Enabled and started the displaylink.service

Rebooted

Disconnected+reconnected the displaylink docking station/hub

On the displaylink side, nothing happens, at least as far as I can tell.

The USB hubs and Ethernet controller in the dock are recognised, so the USB connection to the dock is ok.

The systemd journal shows displaylink.service starting and stopping as normal during shutdown and reboot. No other activity.

dmesg shows connect/disconnect info on USB hubs and the Ethernet adapter, but nothing about displays.

Although I am using Wayland, xrandr still seems to work. It only shows the main monitor, which is on a Displayport connector.

I'm not sure exactly what i'm supposed to be seeing, or how to diagnose the fault from here?

Also curious if wake on lan works on linux? I dual boot with windows and WOL works when my laptop is in sleep mode. On linux, the laptop fails to wake up.

Wake on LAN will wake the PC from an S3 (suspend or sleep) state. It may fail if the PC turns off the USB connection during S3 on battery power. It will not wake the PC from an S4 (Hibernate) or S5 (Off) state.

Reference: https://support.displaylink.com/knowledgebase/articles/613455-how-to-configure-displaylink-ethernet#wol

This package should be renamed displaylink-bin, since the driver is not built from source.

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.

https://wiki.archlinux.org/title/AUR_submission_guidelines

@MaKaNu Setup is currently usb-c to ASUS display.. BUT for future reference I will just use standards HDMI/miniHDMI, etc.. one of the reasons is: if you put a video on the external display or move your most a lot on the display the driver will hog 25%, open a processmanager and have a look.

I just rebooted and tried to reconnect displaylink, long behold it just works® again. Thank you! evdi: 1.14.8-1, displaylink: 6.1-1, uname -a: 6.12.4-arch1-1

Works well for me with evdi 1.14.8 on kernel 6.12.4. Thank you very much! :)

Working(patch as per comment):

kernel: 6.12.3-arch1-1 and 6.12.4-arch1-1
displaylink: 6.0-0
evdi-git: 1.14.7.r0.ge41240c-1

Not working(tried the above mentioned patch as well):

kernel 6.12.4-arch1-1
displaylink 6.1-1
evdi-git 1.14.7.r0.ge41240c-1 or 1.14.8.r0.g3a82424-1

@LinaM, Yeah, thanks. I can confirm, works with evdi-git-1.14.7.r12.g398f065

6.1-1 works fine for me with evdi 1.14.7.r3.g59a3a86-1 (Manjaro, KDE, Kernel 6.6.63) Thx. :-)

A script DLSupportTool.sh was included in the 6.1 release.

I don't think the changelog/release notes can be done dynamically. makepkg fails if the file defined in $changelog is not present at the start.

Also, the evdi is regularly failing to build with new kernels. I was looking for a way to express package dependency upon specific kernel versions, but it doesn't seem possible.

PS. Sorry for the delay. I got busy with a new job.