MX Linux Forum

Posted: **Sat May 10, 2025 4:54 pm**

Hello

I have a DisplayLink USB to VGA module .

I initially installed the Displaylink Driver - and got all the desired monitors up and running together perfectly . I then rebooted the system and the Display Link USB failed to work .

I then went onto Perplexity and followed instructions on how to get it running but now I have this error

"The following packages have unmet dependencies:
evdi : Conflicts: evdi-dkms but 1.12.0+dfsg-0.3 is to be installed
E: Unable to correct problems, you have held broken packages."

when I try and install the latest EVDI's from the repository .

This is another error I received early in the process

"dpkg: error processing package displaylink-driver (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
evdi
displaylink-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)"

Either way the EVDI and Displaylink Driver currently aren't compatible and I have broken packages. I know there is compatibility working solution out there as I did have everything up and running perfectly at one stage .

I need directions please in how to clean everything up and get the Displaylink driver and EVDI working together again .

Code: Select all

System:
  Kernel: 6.1.0-34-amd64 [6.1.135-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-34-amd64 root=UUID=<filter> ro quiet
    init=/lib/systemd/systemd
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto September 15  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Portable System: Dell product: Vostro 3550 v: N/A serial: <superuser required> Chassis:
    type: 8 serial: <superuser required>
  Mobo: Dell model: N/A v: A12 serial: <superuser required> BIOS: Dell v: A12 date: 02/18/2014
Battery:
  ID-1: BAT0 charge: 73.3 Wh (610.8%) condition: 12.0/12.0 Wh (100.0%) volts: 12.5 min: 11.1
    model: SMP DELL VXVK20B type: Li-ion serial: <filter> status: full
CPU:
  Info: model: Intel Core i5-2410M bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 954 high: 989 min/max: 800/2900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 976 2: 989 3: 877 4: 977 bogomips: 18359
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1,VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
  Device-2: Sunplus Innovation Laptop_Integrated_Webcam_FHD type: USB driver: uvcvideo
    bus-ID: 1-1.5:4 chip-ID: 1bcf:2809 class-ID: 0e02
  Device-3: DisplayLink Plugable UGA-165 type: USB driver: udl bus-ID: 3-1:5 chip-ID: 17e9:037a
    class-ID: 0000 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: intel
    dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x1792 s-dpi: 96 s-size: 362x475mm (14.25x18.70") s-diag: 597mm (23.51")
  Monitor-1: LVDS-1 mapped: LVDS1 pos: primary,bottom model: Chi Mei Opto 0x1570 built: 2008
    res: 1366x768 hz: 60 dpi: 99 gamma: 1.2 size: 350x190mm (13.78x7.48") diag: 398mm (15.7")
    ratio: 16:9 modes: 1366x768
  Monitor-2: VGA-1 mapped: VGA1 pos: top model: HannSpree/HannStar HX191D serial: <filter>
    built: 2007 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.2 size: 380x300mm (14.96x11.81")
    diag: 482mm (19") ratio: 5:4 modes: max: 1280x1024 min: 720x400
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Dell 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  API: ALSA v: k6.1.0-34-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active tools: pw-cat,pw-cli,wpctl
  Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Centrino Wireless-N 1030 [Rainbow Peak] driver: iwlwifi v: kernel modules: wl
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 8086:008a class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-1.2.4:13
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Intel Centrino Advanced-N 6230 Bluetooth adapter type: USB driver: btusb v: 0.8
    bus-ID: 1-1.4:3 chip-ID: 8086:0189 class-ID: e001
  Report: bt-adapter note: tool can't run ID: hci0 rfk-id: 1 state: down bt-service: N/A
    rfk-block: hardware: no software: no address: N/A
Drives:
  Local Storage: total: 238.47 GiB used: 81.41 GiB (34.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Fanxiang model: S101Q 256GB size: 238.47 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: D1.2 scheme: MBR
Partition:
  ID-1: / raw-size: 238.47 GiB size: 238.47 GiB (100.00%) used: 81.41 GiB (34.1%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 69.0 C mobo: 59.8 C
  Fan Speeds (RPM): cpu: 3724
Repos:
  Packages: 2271 pm: dpkg pkgs: 2265 libs: 1154 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/synaptics.list
    1: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable main
    2: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable non-free
Info:
  Processes: 273 Uptime: 2h 8m wakeups: 1 Memory: 7.66 GiB used: 3.29 GiB (42.9%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Much appreciated ...

Posted: **Sat May 10, 2025 10:11 pm**

Neither displaylink-driver or evdi are available in the Debian Bookworm or MX-23 repositories (a evdi-dkms package is), so I'm guessing the problem is the displaylink-driver package (and possibly the evdi package too) which I think apt is trying to install from these synaptics.com repos in your QSI report.

Code: Select all

 Active apt repos in: /etc/apt/sources.list.d/synaptics.list
    1: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable main
    2: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable non-free

The displaylink-driver package is available in Debian Trixie/testing (https://packages.debian.org/trixie/displaylink-driver).

Make a package request to see if displaylink-driver can be backported & added to the MX-23 repos. And if it can be, remove or disable the synaptics.com repos.

edit: maybe also request a backport of trixie evdi-dkms (1.14.8+dfsg-1)

Posted: **Sun May 11, 2025 5:05 am**

You want to avoid adding anything with Ubuntu in its name to MX becasue MX is built directly from Debain so as to be truly Debian compatible, whereas Ubuntu mixes 3 generations of Debian into their own "soup" which will contain inter-generational mixes of debianised packages specifically modified to fit their builds. The MX Packagers can often clean out the incompatible dependencies while retaining the raw content you really need and matching them to a proper Debain package that will not cause potential breakage, thereby making them safer for use with MX, but you certainly should not be looking outside of the approved repo pools.

When you pull content in like Debs made for Ubuntu, they will often come with incompatible library support files and/or dependencies that have the potential to royally muck up a clean Debian system. Ubunut are Debian-like, but their packages are not truly Debian compatible. It is for this reason that Debian flatly refused to allow Ubuntu packages to enter their pools and the Debian Wiki makes a clear distinction in their "Dont Break Debian" page. Look it up sometime, it'll change the way you think in the future about Debian-like packages.

Posted: **Sun May 11, 2025 8:41 am**

Thanks for that - the little I have picked up from the internet I thought MX was compatible with Ubuntu . Now that I know it is Debain based it will make it much easier .

I'm totally green when it comes to Linux systems . For me it is something that works well on an old laptop (that surprises me everyday by still running) and it's fun to play around with . I would like to get this issue resolved even if it means doing a fresh install as it's not a big deal if I have to do so . Preferably I would like to get all monitors working again with the Displaylink drivers, just to see how it can be done .

Posted: **Sun May 11, 2025 9:09 am**

kmathern wrote: Sat May 10, 2025 10:11 pm Neither displaylink-driver or evdi are available in the Debian Bookworm or MX-23 repositories (a evdi-dkms package is), so I'm guessing the problem is the displaylink-driver package (and possibly the evdi package too) which I think apt is trying to install from these synaptics.com repos in your QSI report.
Code: Select all
 Active apt repos in: /etc/apt/sources.list.d/synaptics.list
    1: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable main
    2: deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu stable non-free
The displaylink-driver package is available in Debian Trixie/testing (https://packages.debian.org/trixie/displaylink-driver).

Make a package request to see if displaylink-driver can be backported & added to the MX-23 repos. And if it can be, remove or disable the synaptics.com repos.

edit: maybe also request a backport of trixie evdi-dkms (1.14.8+dfsg-1)

Thanks - I see evdi 1.14.9-146 and evdi-dkms1.1.0+dfsg-0.3 in the repo .

to be honest I find all this very confusing "The displaylink-driver package is available in Debian Trixie/testing (https://packages.debian.org/trixie/displaylink-driver).

Make a package request to see if displaylink-driver can be backported & added to the MX-23 repos. And if it can be, remove or disable the synaptics.com repos.
"

I had everything up and running and working perfectly at one stage so I believe the compatible software is already out there but then I know very little . I literally had to do an internet search on pretty much everything you replied with .

I thought I would come on here , describe my issue and someone would be able to instruct me on how to clean up the existing broken packages and direct me to where the working ones are . I expect other people are running external monitors on MX using displaylink adaptors .

I'm not being ungrateful or looking for a quick solution , I'm just trying to articulate how little I know when it comes to Linux systems .

Posted: **Sun May 11, 2025 9:47 am**

To help ease your confusion, you should read this for an explanation for why your desire is not viable:
https://wiki.debian.org/DebianTesting

Posted: **Mon May 12, 2025 1:59 pm**

For what it's worth, I've backported displaylink-driver and evdi-dkms from Testing for the MX 23 test repository, and they should show up in a day or so.

Posted: **Mon May 12, 2025 4:35 pm**

I'm seeing that the backported displaylink-driver & evdi-dkms packages have now been added to the https://mxlinux.mirrors.uk2.net mx mirror repos
(https://mxlinux.mirrors.uk2.net/package ... nk-driver/)

Use MX Packager Installer to install them.
Start up MXPI and then click on the MX Test Repo tab and search for displaylink-driver (use the 'Refresh List' button if it doesn't find it).
It will then install displaylink-driver (6.1-2~mx23+1), and evdi-dkms (1.14.8+dfsg-1~mx23+1) & libevdi1 (1.14.8+dfsg-1~mx23+1) as it's dependencies.

The only issue I'm aware of right now is that evdi-dkms fails to build for the 6.14 kernel, but the o.p. (Moolalchemy) is using the 6.1 bookworm kernel.

Posted: **Sun May 18, 2025 7:52 am**

kmathern wrote: Mon May 12, 2025 4:35 pm I'm seeing that the backported displaylink-driver & evdi-dkms packages have now been added to the https://mxlinux.mirrors.uk2.net mx mirror repos
(https://mxlinux.mirrors.uk2.net/package ... nk-driver/)

Use MX Packager Installer to install them.
Start up MXPI and then click on the MX Test Repo tab and search for displaylink-driver (use the 'Refresh List' button if it doesn't find it).
It will then install displaylink-driver (6.1-2~mx23+1), and evdi-dkms (1.14.8+dfsg-1~mx23+1) & libevdi1 (1.14.8+dfsg-1~mx23+1) as it's dependencies.

The only issue I'm aware of right now is that evdi-dkms fails to build for the 6.14 kernel, but the o.p. (Moolalchemy) is using the 6.1 bookworm kernel.

Thank you for the instruction . I followed them and initially the setup did not work . I was then prompted to do updates through MX Installer which I did . Everything working perfectly now even after a a few reboots .

I did receive this warning message during the upgrade (I've highlighted with CAPITALS in the snippet of the report) but it does not appear to be an issue .

"Unpacking bash (5.2.15-2+b8) over (5.2.15-2+b7) ...
Setting up bash (5.2.15-2+b8) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
(Reading database ... 331841 files and directories currently installed.)
Preparing to unpack .../login_1%3a4.13+dfsg1-1+deb12u1_amd64.deb ...
Unpacking login (1:4.13+dfsg1-1+deb12u1) over (1:4.13+dfsg1-1+b1) ...
Setting up login (1:4.13+dfsg1-1+deb12u1) ...
(Reading database ... 331840 files and directories currently installed.)
Preparing to unpack .../displaylink-driver_6.1.1-17_amd64.deb ...
Unpacking displaylink-driver (6.1.1-17) over (6.1-2~mx23+1) ...
DPKG: WARNING: UNABLE TO DELETE OLD DIRECTORY '/VAR/LOG/DISPLAYLINK': DIRECTORY NOT EMPTY
(Reading database ... 331832 files and directories currently installed.)
Removing evdi-dkms (1.14.8+dfsg-1~mx23+1) ...
/usr/sbin/dkms.mx status -m evdi -v 1.14.8+dfsg
/usr/sbin/dkms.mx remove -m evdi -v 1.14.8+dfsg --all
Module evdi-1.14.8+dfsg for kernel 6.1.0-25-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

evdi.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-25-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....
Module evdi-1.14.8+dfsg for kernel 6.1.0-33-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

evdi.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-33-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....
Module evdi-1.14.8+dfsg for kernel 6.1.0-34-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

evdi.ko:
- Uninstallation
- Deleting from: /lib/modules/6.1.0-34-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....
Deleting module evdi-1.14.8+dfsg completely from the DKMS tree.........................................."

Again any instructions/help much appreciated .

Posted: **Sun May 18, 2025 7:54 am**

Stevo wrote: Mon May 12, 2025 1:59 pm For what it's worth, I've backported displaylink-driver and evdi-dkms from Testing for the MX 23 test repository, and they should show up in a day or so.

Great - has solved my issue and am extremely happy to have got it working . Much appreciation . !!

Posted: **Fri May 23, 2025 3:03 pm**

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)

Posted: **Fri May 23, 2025 4:32 pm**

@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.

Posted: **Fri May 23, 2025 5:59 pm**

Moolalchemy wrote: Fri May 23, 2025 3:03 pm 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.

Posted: **Sat May 24, 2025 6:20 am**

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?

Posted: **Sat May 24, 2025 7:02 pm**

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

Posted: **Sun May 25, 2025 6:15 am**

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 .

Posted: **Sun May 25, 2025 10:08 am**

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...

MX Linux Forum

DisplayLink Driver EVDI Issues

DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues [Solved]

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues

Re: DisplayLink Driver EVDI Issues