I downloaded displaylink-rpm from https://github.com/displaylink-rpm/displaylink-rpm
Looking at displaylink.specs I just changed Requires: libusbx to libusb1.0_0 and xorg-server-x11 to accomodate to mageia names as shown below.
Fits; I wonder if it's possible to add both so othat specs file would be compatible with mga and others. Something like shown below.
- Code: Select all
Requires: libusbx or libusb1.0_0
Requires: xorg-x11-server-Xorg or x11-server-xorg >= 1.16
Conflicts: mutter < 3.32
Conflicts: x11-server-xorg = 1.20.1
If not, that s ok, I can just modify them to the correct mageia names.
Now, I already changed the names to the correct mageia names and ran the make file, the rpm if created and while installing I get this.
- Code: Select all
SECURITY: The following package is _NOT_ signed (OK ((none))): displaylink-1.11.0-1.x86_64.rpm
installing displaylink-1.11.0-1.x86_64.rpm
Preparing... ###############################################################################################################################
1/1: displaylink ###############################################################################################################################
Job for displaylink-driver.service failed because the control process exited with error code.
See "systemctl status displaylink-driver.service" and "journalctl -xeu displaylink-driver.service" for details.
warning: %post(displaylink-1.11.0-1.x86_64) scriptlet failed, exit status 1
ERROR: 'script' failed for displaylink-1.11.0-1.x86_64
systemctl status displaylink-driver.service
● displaylink-driver.service - DisplayLink Driver Service
Loaded: loaded (/usr/lib/systemd/system/displaylink-driver.service; static)
Active: activating (start-pre) since Wed 2022-07-27 10:22:30 PDT; 4ms ago
Cntrl PID: 373601
Tasks: 1 (limit: 28514)
Memory: 256.0K
CPU: 165us
CGroup: /system.slice/displaylink-driver.service
Jul 27 10:22:30 localhost systemd[1]: Starting DisplayLink Driver Service...
Jul 27 10:22:30 localhost modprobe[373601]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.18.14-desktop-2.mga9
Jul 27 10:22:30 localhost systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=1/FAILURE
Jul 27 10:22:30 localhost systemd[1]: displaylink-driver.service: Failed with result 'exit-code'.
Jul 27 10:22:30 localhost systemd[1]: Failed to start DisplayLink Driver Service.
journalctl -xeu displaylink-driver.service
░░
░░ A stop job for unit displaylink-driver.service has finished.
░░
░░ The job identifier is 38585 and the job result is done.
Jul 27 10:23:54 localhost systemd[1]: Starting DisplayLink Driver Service...
░░ Subject: A start job for unit displaylink-driver.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit displaylink-driver.service has begun execution.
░░
░░ The job identifier is 38585.
Jul 27 10:23:54 localhost modprobe[376490]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.18.14-desktop-2.mga9
Jul 27 10:23:54 localhost systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartPre= process belonging to unit displaylink-driver.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 27 10:23:54 localhost systemd[1]: displaylink-driver.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit displaylink-driver.service has entered the 'failed' state with result 'exit-code'.
Jul 27 10:23:54 localhost systemd[1]: Failed to start DisplayLink Driver Service.
░░ Subject: A start job for unit displaylink-driver.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit displaylink-driver.service has finished with a failure.
░░
░░ The job identifier is 38585 and the job result is failed.
...skipping...
░░
░░ A stop job for unit displaylink-driver.service has finished.
░░
░░ The job identifier is 38585 and the job result is done.
Jul 27 10:23:54 localhost systemd[1]: Starting DisplayLink Driver Service...
░░ Subject: A start job for unit displaylink-driver.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit displaylink-driver.service has begun execution.
░░
░░ The job identifier is 38585.
Jul 27 10:23:54 localhost modprobe[376490]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.18.14-desktop-2.mga9
Jul 27 10:23:54 localhost systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartPre= process belonging to unit displaylink-driver.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 27 10:23:54 localhost systemd[1]: displaylink-driver.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit displaylink-driver.service has entered the 'failed' state with result 'exit-code'.
Jul 27 10:23:54 localhost systemd[1]: Failed to start DisplayLink Driver Service.
░░ Subject: A start job for unit displaylink-driver.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit displaylink-driver.service has finished with a failure.
░░
░░ The job identifier is 38585 and the job result is failed.
lines 6537-6571/6571 (END)
I see it complains about evdi.so not being available but it is suppose to be bundled in the package.
What this makefile does is that it downloads the ubuntu zip drivers from https://www.synaptics.com/products/disp ... letype=exe and makes a fedora rpm out of it.
On the original ubuntu .sh file I did some changes to make it work with dnf instead of apt, but I got stuck with a dkms error, I guess commands are different. But this is another story.
Any Ideas?
This is a displaylink dock driver for many Lenovo and HP Thunderbolt Dock drivers.
Regards
ZekeMX