evdi-amd-vmap-texture is outdated and shouldn't be an option.

If you have AMD graphics, ignore the AUR helper's suggestion and go with evdi-dkms.

@php4fan is the installed version of evdi built for your running kernel? Try running: find /lib/modules -name "evdi.ko" as root.

Installed on Manjaro Linux.

$ systemctl start displaylink.service Job for displaylink.service failed because the control process exited with error code. See "systemctl status displaylink.service" and "journalctl -xeu displaylink.service" for details.

journalctl -xeu displaylink.service                                  1 ✘ 
may 11 20:48:01 teo-bmax modprobe[48483]: modprobe: FATAL: Module evdi not found in directory /lib/modules/6.12.25-1-MAN>
may 11 20:48:01 teo-bmax systemd[1]: displaylink.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStartPre= process belonging to unit displaylink.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
may 11 20:48:01 teo-bmax systemd[1]: displaylink.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit displaylink.service has entered the 'failed' state with result 'exit-code'.
may 11 20:48:01 teo-bmax systemd[1]: Failed to start DisplayLink Manager Service.
░░ Subject: A start job for unit displaylink.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit displaylink.service has finished with a failure.
░░ 
░░ The job identifier is 5479 and the job result is failed.
may 11 20:48:06 teo-bmax systemd[1]: displaylink.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ Automatic restarting of the unit displaylink.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
may 11 20:48:06 teo-bmax systemd[1]: Starting DisplayLink Manager Service...
░░ Subject: A start job for unit displaylink.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit displaylink.service has begun execution.
░░ 
░░ The job identifier is 5584.

NOTE: evdi IS installed.

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?

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