---
title: "Ubuntu : Module evdi not found in directory for displaylink-driver.service"
url: https://www.cyber-neurones.org/2023/09/ubuntu-module-evdi-not-found-in-directory-for-displaylink-driver-service/
date: 2023-09-14
modified: 2023-09-14
author: "Frederic"
description: "J'ai vu que j'avais en boucle dans syslog : sh[30354]: modprobe: FATAL: Module evdi not found in directory /lib/modules/6.2.0-10018-tuxedo sh[30396]: Kernel preparation unnecessary for this kernel. Skipping... sh[30396]: Building module:..."
categories:
  - "Ubuntu"
tags:
  - "Ubuntu"
word_count: 292
---

# Ubuntu : Module evdi not found in directory for displaylink-driver.service

J'ai vu que j'avais en boucle dans syslog :

sh[30354]: modprobe: FATAL: Module evdi not found in directory /lib/modules/6.2.0-10018-tuxedo
sh[30396]: Kernel preparation unnecessary for this kernel. Skipping...
sh[30396]: Building module:
sh[30396]: cleaning build area...
sh[30396]: make -j16 KERNELRELEASE=6.2.0-10018-tuxedo all INCLUDEDIR=/lib/modules/6.2.0-10018-tuxedo/build/include KVERSION=6.2.0-10018-tuxedo DKMS_BUILD=1...(bad exit status: 2)
sh[31025]: ERROR (dkms apport): binary package for evdi: 1.10.1 not found
sh[31099]: Error! Bad return status for module build on kernel: 6.2.0-10018-tuxedo (x86_64)
sh[31099]: Consult /var/lib/dkms/evdi/1.10.1/build/make.log for more information.
systemd[1]: displaylink-driver.service: Control process exited, code=exited, status=10/n/a
systemd[1]: displaylink-driver.service: Failed with result 'exit-code'.
systemd[1]: Failed to start DisplayLink Driver Service.
systemd[1]: displaylink-driver.service: Consumed 7.320s CPU time.
systemd[1]: displaylink-driver.service: Scheduled restart job, restart counter is at 16.
systemd[1]: Stopped DisplayLink Driver Service.
systemd[1]: displaylink-driver.service: Consumed 7.320s CPU time.
systemd[1]: Starting DisplayLink Driver Service...

J'ai donc essayé manuellement avec plusieurs versions mais sans succès :

$ sudo dkms install -m evdi -v 1.12.0
Error! Could not find module source directory.
Directory: /usr/src/evdi-1.12.0 does not exist.

Donc j'ai du me résoudre à prendre sur git et à faire le build :

$ git clone https://github.com/DisplayLink/evdi.git
Cloning into 'evdi'...
remote: Enumerating objects: 3065, done.
remote: Counting objects: 100% (1631/1631), done.
remote: Compressing objects: 100% (482/482), done.
remote: Total 3065 (delta 1253), reused 1294 (delta 1148), pack-reused 1434
Receiving objects: 100% (3065/3065), 6.21 MiB | 2.07 MiB/s, done.
Resolving deltas: 100% (2146/2146), done.

$ python3 -m pip install pybind11

$ make

$ sudo make install

make -C module install
make[1]: Entering directory '/home/arias/GIT/evdi/module'
make -C /lib/modules/6.2.0-10018-tuxedo/build M=$PWD INSTALL_MOD_PATH= INSTALL_MOD_DIR=/kernel/drivers/gpu/drm/evdi modules_install
make[2]: Entering directory '/usr/src/linux-headers-6.2.0-10018-tuxedo'
INSTALL /lib/modules/6.2.0-10018-tuxedo//kernel/drivers/gpu/drm/evdi/evdi.ko
SIGN /lib/modules/6.2.0-10018-tuxedo//kernel/drivers/gpu/drm/evdi/evdi.ko
DEPMOD /lib/modules/6.2.0-10018-tuxedo
Warning: modules_install: missing 'System.map' file. Skipping depmod.
make[2]: Leaving directory '/usr/src/linux-headers-6.2.0-10018-tuxedo'

Ensuite j'ai fait l'installation manuellement ... et maintenant j'ai le displaylink-driver.service qui se lance et le display port qui fonctionne à nouveau.