Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 08-26-2015, 01:19 PM   #1
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Smile Modified script Debian Friendly

Hi all,

I'm using Debian Jessie 8.1 with External HP EliteDisplay S140u.

I had to modify the installer to correctly use it due to bad detection of kernel headers and system init daemon.

If it can help someone, you should find the updated installer in attachment.

You must unzip the file
Code:
saian@n5110:displaylink$ unzip dl_installer_debian.zip 
Archive:  dl_installer_debian.zip
   creating: displaylink-driver-1.0.68/
  inflating: displaylink-driver-1.0.68/firefly-monitor-release.spkg  
   creating: displaylink-driver-1.0.68/x86/
  inflating: displaylink-driver-1.0.68/x86/DisplayLinkManager  
  inflating: displaylink-driver-1.0.68/x86/libusb-1.0.so.0.1.0  
  inflating: displaylink-driver-1.0.68/x86/libevdi.so  
  inflating: displaylink-driver-1.0.68/LICENSE  
   creating: displaylink-driver-1.0.68/x64/
  inflating: displaylink-driver-1.0.68/x64/DisplayLinkManager  
  inflating: displaylink-driver-1.0.68/x64/libusb-1.0.so.0.1.0  
  inflating: displaylink-driver-1.0.68/x64/libevdi.so  
  inflating: displaylink-driver-1.0.68/displaylink-installer.sh  
  inflating: displaylink-driver-1.0.68/ella-dock-release.spkg  
 extracting: displaylink-driver-1.0.68/evdi-1.0.68-src.tar.gz
saian@n5110:displaylink$ cd displaylink-driver-1.0.68/
and then as root, you can install it by the same way that original
Code:
root@n5110:displaylink-driver-1.0.68# ./displaylink-installer.sh install
DisplayLink Linux Software 1.0.68 install script called: install
Distribution discovered: Debian GNU/Linux 8.1 (jessie)
Init daemon detected : systemd
Linux Headers found : linux-headers-3.16.0-4-amd64
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
Starting DLM systemd service
after reboot, you should see the new provider with
Code:
root@n5110:displaylink-driver-1.0.68# xrandr --listproviders 
Providers: number : 2
Provider 0: id: 0x43 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:Intel
Provider 1: id: 0xe9 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
and activate it with
Code:
root@n5110:displaylink-driver-1.0.68# xrandr --setprovideroutputsource 1 0
The new screen is now available in the screen configuration.

Thanks to DisplayLink Members to this driver ;-)

EDIT :
The script should be more efficient to detect the system init daemon. Thanks to @runejuhl for his patch.
It seems that many users have problem to download the file. It could be useful that some admin talk about it. Waiting for that, I share the file with Drive.
The link for the current version is : https://drive.google.com/file/d/0B5q...ew?usp=sharing
Attached Files
File Type: zip dl_installer_debian_v1-1.zip (5.68 MB, 0 views)

Last edited by guerrierk; 09-02-2015 at 08:33 AM. Reason: Archive v1.1 / Drive link
guerrierk is offline   Reply With Quote
Old 08-26-2015, 07:32 PM   #2
stuguy909
Member
 
Join Date: Aug 2015
Posts: 37
Default

can't download - insufficient permissions.

Edit1: I found a work around for the kernel headers problem without modifying the installer. However, it won't install and start the dlm service. Is that issue related to the system init daemon you mentioned?

Edit2: It is. You created some work around to plug in the displaylink.service in the /lib/system.d/system/ Care to share what it is? I have a debian 8.1 install thread and I would like to have a full procedure created without having to modify any downloads. CLI progressions only.

Last edited by stuguy909; 08-26-2015 at 09:06 PM. Reason: #1 might as well #2 confirmed my question
stuguy909 is offline   Reply With Quote
Old 08-26-2015, 09:14 PM   #3
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Default

Quote:
Originally Posted by stuguy909 View Post
can't download - insufficient permissions.

Edit: I found a work around for the kernel headers problem without modifying the installer. However, it won't install and start the dlm service. Is that issue related to the system init daemon you mentioned?
Hi stuguy909,
I don't know why you can't download this file. I wil upload it to another server and post the link tomorrow.

The problem with the system init deamon is thay the installer create the service only on ubuntu system. I modified the test that where it is checked and initialized, but you can simply specify "systemd" to the value of SYSTEMINITDAEMON.

Currently I have a problem with the udev rules because it doesnt match with my EliteDisplay and the displaylink services doesnt start automatically. I had to run (as root) systemctl start displaylink.service before to set the new provider with xrandr.

Tell me if that help you ;-)
guerrierk is offline   Reply With Quote
Old 08-26-2015, 09:25 PM   #4
stuguy909
Member
 
Join Date: Aug 2015
Posts: 37
Default dlm installed...but

That certainly installed DLM, and crashed the PC. I rebooted and did as you said, the service failed to start because it is masked.

Code:
# systemctl start displaylink.service
Failed to start displaylink.service: Unit displaylink.service is masked.
Edit: kicked off:

Code:
# systemctl -a
UNIT                                                                        LOAD      ACTIVE   SUB       DESCRIPTION
● display-manager.service                                                     not-found inactive dead      display-manager.service

Last edited by stuguy909; 08-26-2015 at 09:43 PM. Reason: found why
stuguy909 is offline   Reply With Quote
Old 08-26-2015, 09:43 PM   #5
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Default

Quote:
Originally Posted by stuguy909 View Post
That certainly installed DLM, and crashed the PC. I rebooted and did as you said, the service failed to start because it is masked.

Code:
# systemctl start displaylink.service
Failed to start displaylink.service: Unit displaylink.service is masked.
Have you uninstall the previous installation before modify the script and re-run install ?

Does the installer has terminated correctly before thé PC crashed ?

I don't know what the message "service is masked" mean... I will search about it and reply to you asap.

Does anyone has this problem too ?

Thx all
guerrierk is offline   Reply With Quote
Old 08-27-2015, 02:46 PM   #6
stuguy909
Member
 
Join Date: Aug 2015
Posts: 37
Default

Quote:
Originally Posted by guerrierk View Post
Have you uninstall the previous installation before modify the script and re-run install ?

Does the installer has terminated correctly before thé PC crashed ?

I don't know what the message "service is masked" mean... I will search about it and reply to you asap.

Does anyone has this problem too ?

Thx all
I didn't uninstall the old installation. The old installer wasn't technically working correctly. It couldn't load the DLM service and start it. Nothing was actually getting put into systemd. As for the crash, the script finished and the system sat fine for a few seconds at the # prompt, then everything froze. I will try to uninstall and reinstall.
stuguy909 is offline   Reply With Quote
Old 08-27-2015, 02:58 PM   #7
stuguy909
Member
 
Join Date: Aug 2015
Posts: 37
Default re-install

I uninstalled, rebooted, and reinstalled. I seem to be getting errors now with the modified script.

Code:
displaylink-driver-1.0.68# ./displaylink-installer.sh install
DisplayLink Linux Software 1.0.68 install script called: install
Distribution discovered: Debian GNU/Linux 8.1 (jessie)
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64/DisplayLinkManager
Installing libraries
chmod: cannot access ‘/usr/lib/displaylink/DisplayLinkManager’: No such file or directory
chmod: cannot access ‘/usr/lib/displaylink/libevdi.so’: No such file or directory
chmod: cannot operate on dangling symlink ‘/usr/lib/displaylink/libusb-1.0.so’
chmod: cannot operate on dangling symlink ‘/usr/lib/displaylink/libusb-1.0.so.0’
Installing firmware packages
mv: cannot stat ‘*.spkg’: No such file or directory
chmod: cannot access ‘/usr/lib/displaylink/*.spkg’: No such file or directory
Installing license file
mv: cannot stat ‘LICENSE’: No such file or directory
chmod: cannot access ‘/usr/lib/displaylink/LICENSE’: No such file or directory
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
Starting DLM systemd service
stuguy909 is offline   Reply With Quote
Old 08-27-2015, 03:06 PM   #8
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Default

Quote:
Originally Posted by stuguy909 View Post
I didn't uninstall the old installation. The old installer wasn't technically working correctly. It couldn't load the DLM service and start it. Nothing was actually getting put into systemd. As for the crash, the script finished and the system sat fine for a few seconds at the # prompt, then everything froze. I will try to uninstall and reinstall.
OK. That could explain some crash of your system... To uninstall correctly, you can re-execute
Code:
# ./displaylink-driver-1.0.68.run --keep --noexec
to have a good script and run
Code:
# cd DisplayLink-Ubuntu-1.0.68/
# ./displaylink-installer.sh uninstall
after you done that, you can restart and search some file about displaylink with
Code:
# updatedb
# locate displaylink
It should have only the installer's files into the results...

To reinstall, you can use my installer (I updated the archive few minutes ago).

Tell us what the result is ;-)

Last edited by guerrierk; 08-27-2015 at 03:07 PM. Reason: bugfix
guerrierk is offline   Reply With Quote
Old 08-27-2015, 03:29 PM   #9
stuguy909
Member
 
Join Date: Aug 2015
Posts: 37
Default some left overs

I uninstalled as you said, I still have some left overs:

Code:
/lib/systemd/system/displaylink.service
/var/tmp/kdecache-sanderson/favicons/displaylink.org.png
/var/tmp/kdecache-sanderson/favicons/support.displaylink.com.png
/var/tmp/kdecache-sanderson/favicons/www.displaylink.com.png
/var/tmp/kdecache-sanderson/favicons/www.displaylink.org.png
Should I manually delete them?
stuguy909 is offline   Reply With Quote
Old 08-27-2015, 03:33 PM   #10
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Default

Quote:
Originally Posted by stuguy909 View Post
I uninstalled as you said, I still have some left overs:

Code:
/lib/systemd/system/displaylink.service
/var/tmp/kdecache-sanderson/favicons/displaylink.org.png
/var/tmp/kdecache-sanderson/favicons/support.displaylink.com.png
/var/tmp/kdecache-sanderson/favicons/www.displaylink.com.png
/var/tmp/kdecache-sanderson/favicons/www.displaylink.org.png
Should I manually delete them?
Yes you must delete the /lib/systemd/system/displaylink.service (as root)
The tmp files are not important. You can leave them...

After that, can you use my installer and give us the results ?

Thx
guerrierk is offline   Reply With Quote
Reply

Tags
debian

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:51 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.