DisplayLink Driver EVDI Issues [Solved]

[Moolalchemy]

DisplayLink Driver is working perfectly but everytime I go to install or uninstall a program I get an error something similar to this . Is there a way to clean it up ?

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  lightdm
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
2 not fully installed or removed.
After this operation, 849 kB disk space will be freed.
(Reading database ... 331823 files and directories currently installed.)
Removing lightdm (1.32.0-3~mx23+1) ...
Setting up evdi (1.14.10-151) ...
/usr/sbin/dkms.mx status evdi/1.14.10
Removing old evdi/1.14.10 module.
/usr/sbin/dkms.mx remove evdi/1.14.10
Module evdi 1.14.10 is not installed for kernel 6.1.0-35-amd64 (x86_64). Skipping...
Module evdi 1.14.10 is not built for kernel 6.1.0-35-amd64 (x86_64). Skipping...
/usr/sbin/dkms.mx install /usr/src/evdi-1.14.10 -k 6.1.0-25-amd64 -k 6.1.0-34-amd64 -k 6.1.0-35-amd64 -a x86_64
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Processing triggers for man-db (2.11.2-2) ...
dpkg: error processing package evdi (--configure):
 installed evdi package post-installation script subprocess returned error exit status 3
dpkg: dependency problems prevent configuration of displaylink-driver:
 displaylink-driver depends on evdi (>= 1.14.9); however:
  Package evdi is not configured yet.
 displaylink-driver depends on evdi (<< 1.15.0); however:
  Package evdi is not configured yet.

dpkg: error processing package displaylink-driver (--configure):
dependency problems - leaving unconfigured
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Errors were encountered while processing:
evdi
displaylink-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)

[j2mcgreg]

@Moolalchemy
When you post long tracts (like above) please encase them in code tags which will make them easier to read and navigate here in the forums. I did it for you this time so that you can see how it's done.

[kmathern]

DisplayLink Driver is working perfectly but everytime I go to install or uninstall a program I get an error something similar to this . Is there a way to clean it up ?

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  lightdm
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
2 not fully installed or removed.
After this operation, 849 kB disk space will be freed.
(Reading database ... 331823 files and directories currently installed.)
Removing lightdm (1.32.0-3~mx23+1) ...
Setting up evdi (1.14.10-151) ...
/usr/sbin/dkms.mx status evdi/1.14.10 .....

That version (evdi/1.14.10) must be from some other attempt at installing displaylink-driver & evdi-dkms, the version of evdi-dkms in the mx repos is 1.14.8+dfsg-1~mx23+1.

Code: Select all

$ apt-cache policy evdi-dkms
evdi-dkms:
  Installed: (none)
  Candidate: 1.12.0+dfsg-0.3
  Version table:
     1.14.8+dfsg-1~mx23+1 1
          1 https://mxrepo.com/mx/testrepo bookworm/test amd64 Packages
          1 https://mxrepo.com/mx/testrepo bookworm/test i386 Packages
     1.12.0+dfsg-0.3 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian bookworm/main i386 Packages

In your sources do you still have the synaptics.com repos from the QSI in your first post in this topic? They should be removed or disabled.

[Moolalchemy]

Think I've broken the system.

Last thing I did was go into Repo Manager and deselected the two synaptic sources that were there . They had 'Ubuntu' in the address line .

I then rebooted and all I get now is Grub loads , then it looks like it's booting into system d , but all then that appears is a terminal like login . When I do login it says something like 'you have no mail' and mentions the last login .

Do I need a fresh install or can I repair?

[Stevo]

While those Ubuntu repos were active, you were not able to install the MX test repo versions. I backported a slightly older version from upstream Debian, 6.1, they had 6.1.1

Code: Select all

Preparing to unpack .../displaylink-driver_6.1.1-17_amd64.deb ...
Unpacking displaylink-driver (6.1.1-17) over (6.1-2~mx23+1) ...

You might be able to get back into a GUI if only lightdm was removed, try running

Code: Select all

startx

from your logged in terminal interface, and then reinstall lightdm.

or just

Code: Select all

sudo apt install lightdm

[Moolalchemy]

You might be able to get back into a GUI if only lightdm was removed, try running

Code: Select all

startx

from your logged in terminal interface, and then reinstall lightdm.

or just

Code: Select all

sudo apt install lightdm

[/quote]


Thanks for the direction.....

I did startx and got back in - reinstalled lightdm and now it will boot into the GUI .

I'm confused about these installations . I have managed to get Displaylink Driver working since the test repos were posted even though those Ubuntu sources were connected .

Also why does lightdm have a factor to play in this ? It wasn't running on the system until I installed it a day or so ago, and now removing it causes me to lose the GUI .

I have little knowledge about Linux systems so it really makes little sense to me . The one thing about these errors it that it is forcing me to learn a bit more .

Can I clean this system up so I won't be getting these errors when installing / uninstalling programs ?

I already have a fresh install running on another drive so might possibly migrate to that and start over again .

[Moolalchemy]

The MXUpdater prompted for an update so I followed the process . Everything okay until it started to run into errors in the end .

Code: Select all

Setting up linux-kbuild-6.1 (6.1.140-1) ...
Setting up mx-conky-data (20250524) ...
Setting up evdi (1.14.10-151) ...
/usr/sbin/dkms.mx status evdi/1.14.10
Removing old evdi/1.14.10 module.
/usr/sbin/dkms.mx remove evdi/1.14.10
Module evdi-1.14.10 for kernel 6.1.0-35-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

evdi.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-35-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod....
/usr/sbin/dkms.mx install /usr/src/evdi-1.14.10 -k 6.1.0-25-amd64 -k 6.1.0-34-amd64 -k 6.1.0-
35-amd64 -k 6.1.0-37-amd64 -a x86_64
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! DKMS tree already contains: evdi-1.14.10
You cannot add the same module/version combo more than once.
dpkg: error processing package evdi (--configure):
 installed evdi package post-installation script subprocess returned error exit status 3
Setting up lightdm (1.32.0-3~mx23+1) ...
Installing new version of config file /etc/apparmor.d/abstractions/lightdm ...
Installing new version of config file /etc/lightdm/lightdm.conf ...
Installing new version of config file /etc/pam.d/lightdm-autologin ...
Installing new version of config file /etc/pam.d/lightdm-greeter ...
Setting up linux-headers-6.1.0-37-amd64 (6.1.140-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-37-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-37-amd64
dkms: autoinstall for kernel: 6.1.0-37-amd64.
Setting up linux-source (6.1.140-1) ...
Setting up linux-image-amd64 (6.1.140-1) ...
dpkg: dependency problems prevent configuration of displaylink-driver:
 displaylink-driver depends on evdi (>= 1.14.9); however:
  Package evdi is not configured yet.
 displaylink-driver depends on evdi (<< 1.15.0); however:
  Package evdi is not configured yet.

dpkg: error processing package displaylink-driver (--configure):
 dependency problems - leaving unconfigured
Setting up linux-headers-amd64 (6.1.140-1) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for gnome-menus (3.36.0-1.1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-37-amd64
Errors were encountered while processing:
 evdi
 displaylink-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)

full upgrade complete (or was canceled)

this terminal window can now be closed

Press any key to close...