DisplayLink Forum - Modified script Debian Friendly

DisplayLink Forum (https://displaylink.org/forum/index.php)

- Linux and Open Source (https://displaylink.org/forum/forumdisplay.php?f=29)

- - Modified script Debian Friendly (https://displaylink.org/forum/showthread.php?t=64043)

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

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.

Quote:

Originally Posted by stuguy909 (Post 78231)

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 ;-)

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

Quote:

Originally Posted by stuguy909 (Post 78239)

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

Quote:

Originally Posted by guerrierk (Post 78241)

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.

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

Quote:

Originally Posted by stuguy909 (Post 78259)

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 ;-)

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?

Quote:

Originally Posted by stuguy909 (Post 78262)

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