Stuck getting displaylink drivers to work.

bmarkey · 2016-10-03 10:08:29

Bought a plugable usb 3.0 displaylink adapter. ( I'm on hydrogen just fyi) They have a ubuntu driver http://www.displaylink.com/downloads/ubuntu.

Downloaded that, changed the install file to it thought I was running debian jessie. Failed.

Then I found:

https://github.com/AdnanHodzic/displaylink-debian

That gets it installed but after can't find the actual service.

:~$ systemctl status displaylink.service
● displaylink.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
:~$ systemctl start displaylink.service
Failed to start displaylink.service: Unit displaylink.service not found.

Can anyone point me in the right direction. The debian installer should work.

Thanks

iMBeCil · 2016-10-03 13:17:17

I'm not in position to test this driver, but first correction you should make is to run 'systemctl' with 'sudo':

$ sudo systemctl start displaylink.service

And, please, use 'code' tag for the code ...

bmarkey · 2016-10-03 13:31:26

I had tried that, same issue.

Also there is a bug filed on the github page for the debian installer. Same issue,though he doesn't state distro so I assume straight debian. Either way the ubuntu drivers "should" work, though in trying the straight installer you end up with a constant error that it can't find the headers even though they've been downloaded.

So currently I'm not sure where the issue lies. The debian install script looks pretty straight forward. Either there, something different with BL over straight debian , or something else.

( sorry about the code tag, I was on 4 space indent auto pilot)

Last edited by bmarkey (2016-10-03 13:31:58)

iMBeCil · 2016-10-03 14:31:06

Well, sorry ...

Anyway, I would try to go backward. Yes, the script doesn't seem to be particularly difficult to decipher. I suggest checking existence of the 'displaylink' unit:

$ find /etc/systemd -iname "displaylink*" -print

and/or

$ find /lib/systemd -iname "displaylink*" -print

Other idea is that you try to do the installation manually ... in effect, what script does -> do it manually. Obviously, don't do OS checks and other stuff .... simply try to replicate 'install()' function in script. Perhaps it will spill some errors or something useful?!?

Head_on_a_Stick · 2016-10-03 17:58:35

If the systemd unit files are not there (they should be under /lib/systemd/, as iMBeCil notes) then it may be worth reporting this issue at the github page.

bmarkey · 2016-10-03 18:21:42

Ok I sort of know whats going on but not sure how to fix.

First:

358 detect_init_daemon()
359 {
360     INIT=$(readlink /proc/1/exe)
361     if [ "$INIT" == "/sbin/init" ]; then
362         INIT=$(/sbin/init --version)
363     fi
364     [ -z "${INIT##*upstart*}" ] && SYSTEMINITDAEMON="upstart"
365     [ -z "${INIT##*systemd*}" ] && SYSTEMINITDAEMON="systemd"
366 
367     if [ -z "$SYSTEMINITDAEMON" ]; then                                                
368         echo "ERROR: the installer script is unable to find out how to start DisplayLin            kManager service automatically on your system." >&2
369         echo "Please set an environment variable SYSTEMINITDAEMON to 'upstart' or 'syst            emd' before running the installation script to force one of the options." >&2
370         echo "Installation terminated." >&2
371         exit 1
372     fi
373 }

Neither readlink /proc/1/exe nor /sbin/init --version return anything. Readlink returns nothing, the other returns --version unrecognized option.

Second:

Still saying no headers.

334 check_requirements()
335 {
336   # DKMS
337   which dkms >/dev/null || missing_requirement "DKMS"
338   
339   # Required kernel version
340   KVER=$(uname -r)
341   KVER_MIN="3.14"
342   version_lt "$KVER" "$KVER_MIN" && missing_requirement "Kernel version $KVER is too ol      d. At least $KVER_MIN is required"
343   
344   # Linux headers
345   [ ! -f "/lib/modules/$KVER/build/Kconfig" ] && missing_requirement "Linux headers for       running kernel, $KVER"
346 }

There is no Kconfig file there

bmarkey@Lappie:/lib/modules/3.16.0-4-amd64/build$ ls -lah
total 1.3M
drwxr-xr-x 4 root root 4.0K Oct  3 13:57 .
drwxr-xr-x 4 root root 4.0K Oct  2 15:35 ..
drwxr-xr-x 3 root root 4.0K Oct  2 15:35 arch
-rw-r--r-- 1 root root 155K Sep  3 04:57 .config
drwxr-xr-x 4 root root 4.0K Oct  2 15:35 include
lrwxrwxrwx 1 root root    8 Oct  2 15:42 Kbuild -> Makefile
-rw-r--r-- 1 root root  245 Sep  3 04:57 .kernelvariables
-rw-r--r-- 1 root root  306 Sep  3 05:33 Makefile
-rw-r--r-- 1 root root 1.1M Sep  3 05:29 Module.symvers
lrwxrwxrwx 1 root root   35 Sep  3 05:33 scripts -> ../../lib/linux-kbuild-3.16/scripts

The kbuild link is from here, http://www.displaylink.org/forum/showthread.php?t=64041. I tried that and am still stuck.

I should have stated I'm working from this http://support.displaylink.com/knowledg … -other-lin to extract the files and the above code is from the displaylink-installer.sh file.

I'm not sure how to create a kconfig. Also not sure how to force it to use systemd.

Thanks

Last edited by bmarkey (2016-10-03 18:24:46)

Head_on_a_Stick · 2016-10-03 18:38:10

bmarkey wrote:

Still saying no headers.

Perhaps a silly question but have you installed the headers?

https://packages.debian.org/jessie/linux-headers-amd64

If you haven't installed the header metapackage and have instead installed a single header package and the kernel has since been updated then the headers won't match.

I will test that init stuff later, I'm booted with busybox at the moment, but `readlink /proc/1/exe` should output "systemd"

For example:

alpine:~# readlink /proc/1/exe
/bin/busybox
alpine:~#

bmarkey · 2016-10-03 18:46:28

Fair question, yes I've installed the headers.

bmarkey@Lappie:~$ sudo apt-get install linux-headers-3.16.0-4-amd64 
[sudo] password for bmarkey: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-3.16.0-4-amd64 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
bmarkey@Lappie:~$

Also looks like I never ran readlink as sudo (duh) and it does in fact return systemd.

That leave a missing Kconfig.

iMBeCil · 2016-10-04 07:42:28

^^Indeed, as HoaS says:

$ sudo readlink /proc/1/exe
[sudo] password for user: 
/lib/systemd/systemd

Note: 'sudo' seems to be mandatory, as empty string is returned without it ... don't forget 'sudo' if you are running it as ordinary user.

bmarkey · 2016-10-05 14:08:30

No I checked that. It's the lack of that kconfig that is causing it to fail the check for headers even though they are there.

So at this point after googling kconfig a bit I think since I know nothing about ( I don't mind learning but I have 0 interest in mucking about with kernels) that I might just spin up a vanilla debian and see if the drivers load. If so I'll install openbox and go from there.

#1 2016-10-03 10:08:29

Stuck getting displaylink drivers to work.

#2 2016-10-03 13:17:17

Re: Stuck getting displaylink drivers to work.

#3 2016-10-03 13:31:26

Re: Stuck getting displaylink drivers to work.

#4 2016-10-03 14:31:06

Re: Stuck getting displaylink drivers to work.

#5 2016-10-03 17:58:35

Re: Stuck getting displaylink drivers to work.

#6 2016-10-03 18:21:42

Re: Stuck getting displaylink drivers to work.

#7 2016-10-03 18:38:10

Re: Stuck getting displaylink drivers to work.

#8 2016-10-03 18:46:28

Re: Stuck getting displaylink drivers to work.

#9 2016-10-04 07:42:28

Re: Stuck getting displaylink drivers to work.

#10 2016-10-05 14:08:30

Re: Stuck getting displaylink drivers to work.

Board footer