DisplayLink Forum - Displaylink on Fedora 22

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

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

- - Displaylink on Fedora 22 (https://displaylink.org/forum/showthread.php?t=64017)

Displaylink on Fedora 22

I got the new DisplayLink driver working for Fedora 22 with Kernel 4.1.3. Had to make a few changes to the install script. Here is the modified script.

It's working perfectly, but I have to re-run the install script to get the displaylink service running after every boot. I tried to use Fedora's built-in systemcl command to get it to run the service on startup, but it fails:

Code:

$ sudo systemctl enable displaylink.service                    

The unit files have no [Install] section. They are not meant to be enabled

using systemctl.

Possible reasons for having this kind of units are:

1) A unit may be statically enabled by being symlinked from another unit's

   .wants/ or .requires/ directory.

2) A unit's purpose may be to act as a helper for some other unit which has

   a requirement dependency on it.

3) A unit may be started when needed via activation (socket, path, timer,

   D-Bus, udev, scripted systemctl call, ...).

Anyone have any ideas?

I can confirm that this works on Fedora 22 with the 4.1.4 kernel. My system uses efi so I had to sign the kernel mod. There are a few guides on how to do it for Virtualbox, the same principles apply with this.

Quote:

Originally Posted by jkudish (Post 78084)

Code:

$ sudo systemctl enable displaylink.service                    

The unit files have no [Install] section. They are not meant to be enabled

using systemctl.

Possible reasons for having this kind of units are:

1) A unit may be statically enabled by being symlinked from another unit's

   .wants/ or .requires/ directory.

2) A unit's purpose may be to act as a helper for some other unit which has

   a requirement dependency on it.

3) A unit may be started when needed via activation (socket, path, timer,

   D-Bus, udev, scripted systemctl call, ...).

Anyone have any ideas?

I created my own rpm for Fedora 22, and added a udev rule so that the service is started when the device is plugged in, and stopped when plugged out. Also keeps dkms so that kernel updates won't break it.

http://nothen.com.ar/en/support-for-...ters-on-linux/

Eric