![]() |
|
|||||||
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#9 |
|
Junior Member
Join Date: Mar 2016
Posts: 3
|
dkms autoinstall does not fix for me either
Verifying archive integrity... All good. Uncompressing DisplayLink Linux Driver 1.0.335 100% DisplayLink Linux Software 1.0.335 install script called: install install Distribution discovered: Ubuntu 15.10 WARNING: Kernel version 4.2.0-34-generic is not supported. Highest supported version is 3.19. 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 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, ...). Job for displaylink.service failed because the control process exited with error code. See "systemctl status displaylink.service" and "journalctl -xe" for details. The computer I'm trying to get it working on is a NUC - not sure if that matters. http://www.intel.com/content/www/us/...nuc6i5syk.html |
|
|
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|