DisplayLink Forum - View Single Post

PlusMinus · 02-03-2016, 01:15 PM

The way I see it, the problem with the current installer is that no init daemon is defined in the installation script.

The way I did it (IIRC) was to install the file you downloaded like you normally would

Code:

./displaylink-driver-1.0.335.run

then I unpacked this file

Code:

./displaylink-driver-1.0.335.run --keep --noexec

and opened the displaylink-installer.sh and changed line 9 to match the daemon I wanted to use (upstart worked, didn't try systemd).

Code:

SYSTEMINITDAEMON=upstart

And ran the extracted script

Code:

displaylink-installer.sh install

02-03-2016, 01:15 PM	#3
PlusMinus Junior Member Join Date: Feb 2016 Posts: 3	The way I see it, the problem with the current installer is that no init daemon is defined in the installation script. The way I did it (IIRC) was to install the file you downloaded like you normally would Code: ./displaylink-driver-1.0.335.run then I unpacked this file Code: ./displaylink-driver-1.0.335.run --keep --noexec and opened the displaylink-installer.sh and changed line 9 to match the daemon I wanted to use (upstart worked, didn't try systemd). Code: SYSTEMINITDAEMON=upstart And ran the extracted script Code: displaylink-installer.sh install Last edited by PlusMinus; 02-04-2016 at 09:41 AM.