[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
talk:howtos:hardware:displaylink [2018/07/04 13:45 (UTC)] 76.30.40.253talk:howtos:hardware:displaylink [2020/02/03 18:14 (UTC)] (current) 104.124.60.87
Line 1: Line 1:
 ====== Discussion about DisplayLink support in Slackware ====== ====== Discussion about DisplayLink support in Slackware ======
 +Update February 03, 2020
 +
 +Slackware64-current with latest kernel (5.4.17) still working fine today.  After any kernel upgrade, I run grub-mkconfig -o /boot/grub/grub.cfg and after the reboot, press e and add 3 at the end of the line starting with "linux" I login and repackage evdi-kernel and nvidia-kernel, install and reboot.  Everything works fine after that, with the three monitors on the USB 3.0 docking station
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +Update December 30, 2019
 +
 +Slackware64-current with latest kernel (5.4.6) and nvidia-driver and nvidia-kernel using evdi, evdi-kernel and displaylink as listed below works fine with the latest versions of nettle, xorg-server, x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb
 +
 +All three external monitors work "off the shelf", without even running any scripts.  I did add some lines to /etc/rc.d/rc.local
 +
 +  # Load evdi after reboot
 +  modprobe evdi
 +  cd /usr/lib64/displaylink
 +  ./DisplayLinkManager &
 +
 +  # Create missing nvidia device nodes after reboot
 +  /usr/bin/nvidia-modprobe -c 0 -u
 +
 +More information on my "journey" with nvidia on Slackware64-current can be found here:  http://conoacum.blogspot.com/2019/12/nvidia-geforce-gtx-1050-in-slackware64.html
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +Update December 09, 2019
 +
 +Slackware64-current with latest kernel (5.4.2) needs a patch for evdi-kernel to be repackaged.  It can be found here: https://crazy.dev.frugalware.org/evdi-all-in-one-fixes.patch
 +
 +The whole thread where I found it can be found here: https://github.com/DisplayLink/evdi/issues/172
 +
 +All three packages can be repackaged using the SBo scripts:
 +  1) evdi-kernel:  https://www.slackbuilds.org/repository/14.2/system/evdi-kernel/
 +  2) evdi:  https://www.slackbuilds.org/repository/14.2/system/evdi/
 +  3) displaylink:  https://www.slackbuilds.org/repository/14.2/system/displaylink/
 +
 +I had to rename the .zip for DisplayLink to displaylink-driver-5.2.14.zip for it to be repackaged without any issues
 +
 +Download the latest compressed files from https://github.com/DisplayLink/evdi/releases/ (EVDI) and https://www.displaylink.com/downloads/ubuntu (DisplayLink)
 +
 +I can still not use the latest xorg-server, x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +Update August 16, 2019
 +
 +Same issue with the lastest version of the DisplayLink package and Slackware64-current.  The only way to have it working is with xorg-server 1.19.6
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +Update February 26, 2019
 +
 +DisplayLink package version 5.1.26 with Slackware64-current (kernel version 4.19.25) shows screen with lines of different colors and second monitor does not work with x-org-server packages on 1.20.3 (xorg-server, x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb)
 +
 +Updated to latest package for DisplayLink:  https://www.displaylink.com/downloads/file?id=1304
 +
 +Updated to latest version of EVDI:  https://github.com/DisplayLink/evdi/releases/tag/v1.6.0
 +
 +Downgraded to x-org-server packages 1.19.6
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +
 +Update December 11, 2018:
 +
 +DisplayLink package version 4.4.24 with Slackware64-current (kernel version 4.19.8) shows screen with lines of different colors and second monitor does not work with x-org-server packages on 1.20.3 (xorg-server, x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb)
 +
 +The package downloaded from DisplayLink did not install this time.  I had to repackage the packages using the ones from SBo and evdi packages for 1.5.1:
 +
 +https://www.slackbuilds.org/repository/14.2/system/evdi/
 +
 +https://www.slackbuilds.org/repository/14.2/system/evdi-kernel/
 +
 +https://www.slackbuilds.org/repository/14.2/system/displaylink/
 +
 +https://www.displaylink.com/downloads/file?id=1261
 +
 +https://github.com/DisplayLink/evdi/releases
 +
 +with a small modification for the displaylink.SlackBuild
 +
 +Downgrading all x-org-server packages to 1.19.6 did not work at first.  A workaround was to create a script to enable HDMI (without any HDMI monitor plugged in) and then enabling the two monitors, which then worked flawlessly
 +
 +Contents of HDMIMonitors.sh
 +  xrandr --listproviders --setprovideroutputsource 1 0
 +  xrandr --output DVI-I-1-1 --auto
 +  xrandr --output DVI-I-1-1 --pos 0x0 --output HDMI1 --pos 1920x0 --output eDP1 --pos 3840x312
 +
 +Contents of Monitors.sh
 +  xrandr --listproviders --setprovideroutputsource 1 0 --setprovideroutputsource 2 0
 +  xrandr --output DVI-I-1-1 --auto --output DVI-I-2-2 --auto
 +  xrandr --output DVI-I-1-1 --pos 0x0 --output DVI-I-2-2 --pos 1920x0 --output eDP-1 --pos 3840x312
 +
 +
 +I tried both of them, and rebooted after each change.  The one mentioning intel required to be Intel (capital I).  None of them yielded positive results.  In each case, once trying to activate the screen using xrandr I was logged out and kicked back to the gdm login screen
 +
 +The docking station I use is this one:  https://www.amazon.com/Lenovo-ThinkPad-Docking-Station-0A33970/dp/B008ABKADI
 +
 +It uses the DisplayLink chipset.  I have one at work.  At home I use a regular HDMI cable and an external monitor, which work, even with xorg-server 1.20.0
 +
 +Regards,
 +
 +F. Bobbio C. (a.k.a. Akileo)
 +
 +
 +Akileo, that page you link to contains two workarounds that //do not// require downgrading xorg-server. Have you tried them? What was the result? \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2018/07/05 17:55 (UTC)//
 +
 +
 Greetings, fellow Slackers, Greetings, fellow Slackers,
 I am running Slackware64-current with Plasma5.  Has anyone encountered issues with xorg-server 1.20.0 while running DisplayLink?  I have the same issues as listed here:   https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades I am running Slackware64-current with Plasma5.  Has anyone encountered issues with xorg-server 1.20.0 while running DisplayLink?  I have the same issues as listed here:   https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades
  
-I had to downgrade to xorg-server-1.19.6 with x-org-server-xephyr, xorg-server-xnext and xorg-server-xvfb also on the same version+I had to downgrade to xorg-server-1.19.6 with x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb also on the same version
  
 I had the same issues with Slackware64-current with KDE 4, by the way.  Any pointers/solutions/comments on how to fix the issue, if at all possible, while running xorg-server 1.20.0 would be more than welcome I had the same issues with Slackware64-current with KDE 4, by the way.  Any pointers/solutions/comments on how to fix the issue, if at all possible, while running xorg-server 1.20.0 would be more than welcome
 talk:howtos:hardware:displaylink ()