Forum › Forums › New users › New Users and General Questions › Trying to use a displaylink adapter to add a 2nd external screen
- This topic has 18 replies, 5 voices, and was last updated Oct 10-4:52 pm by hughtmccullough.
-
AuthorPosts
-
August 27, 2024 at 6:20 pm #152851
BobC
ModeratorThanks for the help. I need to be careful messing with the I7-7559 as it’s used all day long on weekdays . I’ve been fortunate so far. I now have a backup system for it’s day to day use, which also gives me the 3rd screen at the cost of needing to power 2 machines, but at least I’m up and running .
I’ll give the displylink a try again next weekend.
Here is the link to SEARCH THE FORUM >> http://www.antixforum.com/search-forums
October 1, 2025 at 6:17 am #186537hughtmccullough
MemberI know this topic is rather old but it was left open-ended and I thought I would add some comments for anyone trying to get the DisplayLink driver to work on a SysVinit system, in my case with antiX 23.2 on a Lenovo P1 Gen 4 laptop and a Lenovo DK1523 dock.
I used the Debian install script created by Adnan Hodzic mentioned in the second post on this topic. However, there were two changes I had to make pre-install and one post-install.
Issues:
1) antiX isn’t one of the listed distributions for the displaylink-debian.sh script. So, I hard coded the distribution to Devuan which is the only one in the list that uses SysVinit. I did this by adding the line
lsb=Devuan
at the end of the section starting# globalvars2) The official DisplayLink driver script that is downloaded as part of the install process doesn’t recognise SysVinit as a valid init system and crashes out with a message to that effect. To get round this I just commented out the
exit 1
line that exits the code at that point. It is OK to bypass this as Adnan Hodzic’s script goes on to install the SysVinit code after the official install script has run.This can’t be done directly as the driver script isn’t downloaded until during the install process. However, the displaylink-debian.sh script modifies the driver script once it has been downloaded using a patch and I just added this change to the patch.
3) After the installation and reboot, the driver wasn’t properly detected on my system that uses an Intel graphics card with the i915 driver. To get round this I had to change the file /etc/X11/xorg.conf.d/20-displaylink to the following:
Section "OutputClass" Identifier "DisplayLink" MatchDriver "evdi" Driver "modesetting" Option "AccelMethod" "none" EndSectionand reboot.
I eventually managed to attach the modified install script and also the patch file that needs to go in the resources directory one level below the displaylink-debian directory.
This is a worthwhile upgrade if you need an extra HDMI or DisplayPort output. The docks can be purchased for next to nothing on the second hand market, e.g. your favourite auction site.- This reply was modified 12 months ago by hughtmccullough.
- This reply was modified 12 months ago by hughtmccullough.
- This reply was modified 12 months ago by hughtmccullough.
Attachments:
October 1, 2025 at 6:29 am #186543BobC
ModeratorThanks for taking the time to post that.
If you zip the scripts into a .zip file, you should be able to add it to your post above.
I have some displaylink adapters that I never got to work with Linux. In desperation, I bought an extra laptop to solve the problem. It would be nice to be able to add an additional screen to each, as I use them for charting a lot. I used to use the displaylink adapters back when I ran Windows for work back before I retired a year ago.
Here is the link to SEARCH THE FORUM >> http://www.antixforum.com/search-forums
October 10, 2025 at 4:52 pm #187258hughtmccullough
MemberI had to revisit this to make one more change. Everything was working fine except it took over 30s for my computer to shut down.
I reported the details in another thread with the conclusion in post http://www.antixforum.com/forums/topic/long-shutown-time/#post-187256
Basically the file displaylink.sh which appears in the /etc/init.d directory has to be changed to the one in the attachment and the file
/opt/displaylink/DisplayLinkManager has to be renamed to DisplayLinkMan.
Attachments:
-
AuthorPosts
- You must be logged in to reply to this topic.