Debian 8.1 driver install

[stuguy909]

I installed DKMS but I am getting the error:
Unsatisfied dependencies. Missing component: Linux headers for running kernel, 3.16.0-4-amd64

whenever I run the displaylink-driver-1.0.68.run script. I am doing UEFI boot, so do I have to edit my kernel somewhere to bipass this? Ubuntu instructions has a signed kernel available in the Ubuntu repo for UEFI boots, but debian is a little different. Any thoughts?

kernel 3.16.0-4-amd64

[mlukaszek]

The installer script is looking for /lib/modules/$(uname -r)/build/Kbuild to ensure that kernel headers are available for a running kernel. Ensure the headers are indeed installed, then change or remove the line to match files available on Debian.

Hope this helps.
Michal

[stuguy909]

It is indeed installed.

sudo apt-get install linux-headers-$(uname -r)
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.

However, there is no Kbuild file:

/lib/modules/3.16.0-4-amd64/build# ls
arch include Makefile Module.symvers scripts


Do you know of some alternative I can create a symbolic link to?

Edit:
the Makefile.

[stuguy909]

/lib/modules/3.16.0-4-amd64/build# ln -sf Makefile Kbuild

linking the Makefile to Kbuild seemed to allow me to install the drivers without error.


# ./displaylink-driver-1.0.68.run
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.0.68 100%
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
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices


I rebooted and now I guess I need to run some more commands? If the above output looks correct, do you have a link to a thread or directions on how to load my screens or check if the driver is working?

Edit: lsmod and lsusb outputs

# lsmod
Module Size Used by
binfmt_misc 16949 1
pci_stub 12429 1
vboxpci 23078 0
vboxnetadp 25443 0
vboxnetflt 27648 0
vboxdrv 375481 3 vboxnetadp,vboxnetflt,vboxpci
bnep 17431 2
snd_hda_codec_hdmi 45118 1
nfsd 263032 2
auth_rpcgss 51211 1 nfsd
oid_registry 12419 1 auth_rpcgss
nfs_acl 12511 1 nfsd
nfs 188136 0
lockd 83389 2 nfs,nfsd
fscache 45542 1 nfs
sunrpc 237402 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
nls_utf8 12456 1
nls_cp437 16553 1
vfat 17135 1
fat 61986 1 vfat
cdc_mbim 12825 0
cdc_wdm 17427 1 cdc_mbim
hid_sensor_als 12639 0
hid_sensor_incl_3d 12667 0
hid_sensor_rotation 12667 0
hid_sensor_gyro_3d 12667 0
hid_sensor_accel_3d 12674 0
hid_sensor_magn_3d 12667 0
hid_sensor_trigger 12521 12 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
industrialio_triggered_buffer 12417 6 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
kfifo_buf 12834 1 industrialio_triggered_buffer
hid_sensor_iio_common 12795 6 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
iTCO_wdt 12831 0
industrialio 42405 9 hid_sensor_trigger,hid_sensor_gyro_3d,industrialio _triggered_buffer,hid_sensor_incl_3d,hid_sensor_ac cel_3d,hid_sensor_rotation,hid_sensor_als,kfifo_bu f,hid_sensor_magn_3d
joydev 17063 0
iTCO_vendor_support 12649 1 iTCO_wdt
cdc_ncm 26618 1 cdc_mbim
snd_usb_audio 135354 2
usbnet 30844 2 cdc_mbim,cdc_ncm
mii 12675 1 usbnet
snd_usbmidi_lib 23388 1 snd_usb_audio
snd_rawmidi 26806 1 snd_usbmidi_lib
snd_seq_device 13132 1 snd_rawmidi
ecb 12737 1
btusb 29721 0
hid_sensor_hub 17310 8 hid_sensor_trigger,hid_sensor_gyro_3d,hid_sensor_i ncl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid _sensor_als,hid_sensor_magn_3d,hid_sensor_iio_comm on
uvcvideo 79005 0
wacom 59529 0
bluetooth 374429 21 bnep,btusb
videobuf2_vmalloc 12816 1 uvcvideo
videobuf2_memops 12519 1 videobuf2_vmalloc
videobuf2_core 47787 1 uvcvideo
6lowpan_iphc 16588 1 bluetooth
v4l2_common 12995 1 videobuf2_core
videodev 126451 3 uvcvideo,v4l2_common,videobuf2_core
hid_multitouch 17057 0
media 18305 2 uvcvideo,videodev
x86_pkg_temp_thermal 12951 0
intel_powerclamp 17159 0
intel_rapl 17356 0
coretemp 12820 0
iwlwifi 96547 0
kvm_intel 139116 0
rtsx_pci_ms 16898 0
kvm 388635 1 kvm_intel
efi_pstore 12805 1
memstick 13696 1 rtsx_pci_ms
cfg80211 405538 1 iwlwifi
i915 837138 6
pcspkr 12595 0
efivars 17257 1 efi_pstore
psmouse 99249 0
i2c_i801 16965 0
snd_hda_codec_conexant 17841 1
lpc_ich 20768 0
wmi 17339 0
snd_hda_codec_generic 63181 1 snd_hda_codec_conexant
evdev 17445 31
serio_raw 12849 0
thinkpad_acpi 69119 1
nvram 13034 1 thinkpad_acpi
rfkill 18867 4 cfg80211,thinkpad_acpi,bluetooth
snd_hda_intel 26327 5
snd_hda_controller 26646 1 snd_hda_intel
battery 13356 0
ac 12715 0
drm_kms_helper 49210 1 i915
snd_hda_codec 104463 5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_ codec_generic,snd_hda_intel,snd_hda_controller
snd_hwdep 13148 2 snd_usb_audio,snd_hda_codec
snd_pcm 88662 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd _hda_intel,snd_hda_controller
drm 249955 5 i915,drm_kms_helper
snd_timer 26614 1 snd_pcm
mei_me 17941 0
snd 65244 27 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hd mi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_ hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,sn d_hda_intel,thinkpad_acpi,snd_seq_device
video 18096 1 i915
i2c_algo_bit 12751 1 i915
soundcore 13026 2 snd,snd_hda_codec
mei 74977 1 mei_me
i2c_core 46012 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2 _common,videodev
shpchp 31121 0
button 12944 1 i915
processor 28221 0
fuse 83350 1
autofs4 35529 2
ext4 473802 3
crc16 12343 2 ext4,bluetooth
mbcache 17171 1 ext4
jbd2 82413 1 ext4
algif_skcipher 13008 0
af_alg 12988 1 algif_skcipher
hid_generic 12393 0
usbhid 44460 0
hid 102264 4 hid_multitouch,hid_generic,hid_sensor_hub,usbhid
dm_crypt 22595 1
dm_mod 89405 12 dm_crypt
sg 29973 0
sd_mod 44356 4
crc_t10dif 12431 1 sd_mod
crct10dif_generic 12581 0
crct10dif_pclmul 13387 1
crct10dif_common 12356 3 crct10dif_pclmul,crct10dif_generic,crc_t10dif
crc32_pclmul 12915 0
crc32c_intel 21809 0
ghash_clmulni_intel 12978 0
rtsx_pci_sdmmc 21105 0
mmc_core 102374 1 rtsx_pci_sdmmc
aesni_intel 151423 3
aes_x86_64 16719 1 aesni_intel
lrw 12757 1 aesni_intel
gf128mul 12970 1 lrw
glue_helper 12695 1 aesni_intel
ablk_helper 12572 1 aesni_intel
cryptd 14516 4 ghash_clmulni_intel,aesni_intel,ablk_helper
ahci 33291 3
libahci 27158 1 ahci
libata 177457 2 ahci,libahci
ehci_pci 12512 0
xhci_hcd 148881 0
ehci_hcd 69837 1 ehci_pci
scsi_mod 191405 3 sg,libata,sd_mod
rtsx_pci 37719 2 rtsx_pci_ms,rtsx_pci_sdmmc
mfd_core 12601 3 lpc_ich,rtsx_pci,hid_sensor_hub
usbcore 195340 13 btusb,wacom,snd_usb_audio,uvcvideo,snd_usbmidi_lib ,ehci_hcd,ehci_pci,usbhid,usbnet,cdc_mbim,cdc_ncm, cdc_wdm,xhci_hcd
thermal 17559 0
usb_common 12440 1 usbcore
thermal_sys 27642 5 video,intel_powerclamp,thermal,processor,x86_pkg_t emp_thermal
# lsmod | grep usb
snd_usb_audio 135354 2
usbnet 30844 2 cdc_mbim,cdc_ncm
mii 12675 1 usbnet
snd_usbmidi_lib 23388 1 snd_usb_audio
snd_rawmidi 26806 1 snd_usbmidi_lib
btusb 29721 0
bluetooth 374429 21 bnep,btusb
snd_hwdep 13148 2 snd_usb_audio,snd_hda_codec
snd_pcm 88662 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd _hda_intel,snd_hda_controller
snd 65244 27 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hd mi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_ hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,sn d_hda_intel,thinkpad_acpi,snd_seq_device
usbhid 44460 0
hid 102264 4 hid_multitouch,hid_generic,hid_sensor_hub,usbhid
usbcore 195340 13 btusb,wacom,snd_usb_audio,uvcvideo,snd_usbmidi_lib ,ehci_hcd,ehci_pci,usbhid,usbnet,cdc_mbim,cdc_ncm, cdc_wdm,xhci_hcd
usb_common 12440 1 usbcore
# lsusb
Bus 003 Device 004: ID 056a:00ec Wacom Co., Ltd
Bus 003 Device 003: ID 0483:91d1 STMicroelectronics
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 17e9:4302 DisplayLink
Bus 002 Device 003: ID 2109:0811
Bus 002 Device 002: ID 2109:0811
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f2:b39f Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 04f3:0254 Elan Microelectronics Corp.
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 008: ID 2109:3431
Bus 001 Device 007: ID 04f2:0112 Chicony Electronics Co., Ltd KU-8933 Keyboard with PS/2 Mouse port
Bus 001 Device 006: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 002: ID 2109:3431
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[stuguy909]

$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x46 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 0 name:Intel


I can only see my default monitor. The two ACER monitors are on and plugged into the USB dock firmly.

[stuguy909]

I was reading the other post about the gentleman with the custom display-link driver for debian 8.1. His installer seems to have started the dlm service, where as, mine did not. I do not appear to have DLM in my services list.


# service --status-all
[ + ] acpid
[ - ] alsa-utils
[ - ] anacron
[ + ] atd
[ + ] avahi-daemon
[ + ] bluetooth
[ - ] bootlogs
[ - ] bootmisc.sh
[ - ] checkfs.sh
[ - ] checkroot-bootclean.sh
[ - ] checkroot.sh
[ + ] console-setup
[ + ] cron
[ - ] cryptdisks
[ - ] cryptdisks-early
[ + ] dbus
[ + ] ebtables
[ + ] exim4
[ + ] hdparm
[ - ] hostname.sh
[ - ] hwclock.sh
[ + ] kbd
[ + ] kdm
[ + ] keyboard-setup
[ - ] killprocs
[ + ] kmod
[ + ] libvirt-guests
[ + ] libvirtd
[ - ] lvm2
[ - ] motd
[ - ] mountall-bootclean.sh
[ - ] mountall.sh
[ - ] mountdevsubfs.sh
[ - ] mountkernfs.sh
[ - ] mountnfs-bootclean.sh
[ - ] mountnfs.sh
[ + ] network-manager
[ + ] networking
[ + ] nfs-common
[ + ] openvpn
[ - ] pppd-dns
[ + ] procps
[ ? ] qemu-system-x86
[ + ] rc.local
[ - ] rmnologin
[ + ] rpcbind
[ + ] rsyslog
[ + ] saned
[ - ] sendsigs
[ + ] speech-dispatcher
[ + ] ssh
[ - ] sudo
[ + ] udev
[ + ] udev-finish
[ - ] umountfs
[ - ] umountnfs.sh
[ - ] umountroot
[ - ] unattended-upgrades
[ + ] urandom
[ ? ] vboxautostart-service
[ + ] vboxballoonctrl-service
[ + ] vboxdrv
[ + ] vboxweb-service
[ - ] x11-common
[ + ] xen
[ + ] xendomains


Edit: Upon further research. This is a common occurrence because the install script only supports Ubuntu and its /lib/system.d/system hierarchy. There are work-arounds available. Searching....

[stuguy909]

A temporary work around to at least get a step further in the process:

run the displaylink-driver-1.0.68.run file with the --keep --noexec options to unpack the files into a directory. cd into that driver directory. edit the displaylink-installer.sh file. Edit the line with SYSTEMINITDAEMON= to be SYSTEMINITDAEMON=systemd

run


displaylink-installer.sh -install


With my symbolic link work around and editing this file, the driver installs and dlm is installed and started. HOWEVER, on my computer, my system crashed. After reboot, I am unable to start the displaylink.service because it is masked.


# systemctl start displaylink.service
Failed to start displaylink.service: Unit displaylink.service is masked.


Edit: kicked off:


# systemctl -a
UNIT LOAD ACTIVE SUB DESCRIPTION
● display-manager.service not-found inactive dead display-manager.service

[guerrierk]

Hi stuguy909,

Could you post results for
# dmesg
# lsusb

when your display is connected please.

Thx.

PS : I test on another system and I had to blacklist udlfb to work correctly (it's not done by the installer). I have specify it into /etc/modprobe.d/blacklist-framebuffer.conf

blacklist udlfb

I will update my installer and re-upload it.

[stuguy909]

dmesg: http://stuartanderson.info/dmesg.txt


# lsusb
Bus 003 Device 004: ID 056a:00ec Wacom Co., Ltd
Bus 003 Device 003: ID 0483:91d1 STMicroelectronics
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 17e9:4302 DisplayLink
Bus 002 Device 003: ID 2109:0811
Bus 002 Device 002: ID 2109:0811
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f2:b39f Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 04f3:0254 Elan Microelectronics Corp.
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 008: ID 2109:3431
Bus 001 Device 007: ID 04f2:0112 Chicony Electronics Co., Ltd KU-8933 Keyboard with PS/2 Mouse port
Bus 001 Device 006: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 002: ID 2109:3431
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[stuguy909]

Hi stuguy909,


PS : I test on another system and I had to blacklist udlfb to work correctly (it's not done by the installer). I have specify it into /etc/modprobe.d/blacklist-framebuffer.conf

blacklist udlfb

I will update my installer and re-upload it.

the udlfb was already blacklisted on my system. I didn't do it personally, however. My procedure may have been slightly different than yours.

[guerrierk]

Thanks,

Your dmesg have no problem. Your ThinkPad USB 3.0 Dock is correctly detected...

Could you post the result of lsmod please ?

[stuguy909]

new dmesg: http://stuartanderson.info/dmesg.txt


# lsmod
Module Size Used by
evdi 32278 0
pci_stub 12429 1
vboxpci 23078 0
vboxnetadp 25443 0
vboxnetflt 27648 0
vboxdrv 375481 3 vboxnetadp,vboxnetflt,vboxpci
bnep 17431 2
nfsd 263032 2
auth_rpcgss 51211 1 nfsd
oid_registry 12419 1 auth_rpcgss
nfs_acl 12511 1 nfsd
nfs 188136 0
lockd 83389 2 nfs,nfsd
fscache 45542 1 nfs
sunrpc 237402 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
snd_hda_codec_hdmi 45118 1
nls_utf8 12456 1
nls_cp437 16553 1
vfat 17135 1
fat 61986 1 vfat
hid_sensor_incl_3d 12667 0
hid_sensor_accel_3d 12674 0
hid_sensor_rotation 12667 0
hid_sensor_als 12639 0
hid_sensor_gyro_3d 12667 0
hid_sensor_magn_3d 12667 0
hid_sensor_trigger 12521 12 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
industrialio_triggered_buffer 12417 6 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
kfifo_buf 12834 1 industrialio_triggered_buffer
hid_sensor_iio_common 12795 6 hid_sensor_gyro_3d,hid_sensor_incl_3d,hid_sensor_a ccel_3d,hid_sensor_rotation,hid_sensor_als,hid_sen sor_magn_3d
industrialio 42405 9 hid_sensor_trigger,hid_sensor_gyro_3d,industrialio _triggered_buffer,hid_sensor_incl_3d,hid_sensor_ac cel_3d,hid_sensor_rotation,hid_sensor_als,kfifo_bu f,hid_sensor_magn_3d
joydev 17063 0
iTCO_wdt 12831 0
iTCO_vendor_support 12649 1 iTCO_wdt
cdc_mbim 12825 0
cdc_wdm 17427 1 cdc_mbim
cdc_ncm 26618 1 cdc_mbim
usbnet 30844 2 cdc_mbim,cdc_ncm
x86_pkg_temp_thermal 12951 0
intel_powerclamp 17159 0
mii 12675 1 usbnet
snd_usb_audio 135354 2
intel_rapl 17356 0
snd_usbmidi_lib 23388 1 snd_usb_audio
coretemp 12820 0
snd_rawmidi 26806 1 snd_usbmidi_lib
snd_seq_device 13132 1 snd_rawmidi
kvm_intel 139116 0
uvcvideo 79005 0
videobuf2_vmalloc 12816 1 uvcvideo
kvm 388635 1 kvm_intel
videobuf2_memops 12519 1 videobuf2_vmalloc
videobuf2_core 47787 1 uvcvideo
wacom 59529 0
hid_sensor_hub 17310 8 hid_sensor_trigger,hid_sensor_gyro_3d,hid_sensor_i ncl_3d,hid_sensor_accel_3d,hid_sensor_rotation,hid _sensor_als,hid_sensor_magn_3d,hid_sensor_iio_comm on
v4l2_common 12995 1 videobuf2_core
videodev 126451 3 uvcvideo,v4l2_common,videobuf2_core
hid_multitouch 17057 0
media 18305 2 uvcvideo,videodev
ecb 12737 1
btusb 29721 0
bluetooth 374429 21 bnep,btusb
6lowpan_iphc 16588 1 bluetooth
pcspkr 12595 0
iwlwifi 96547 0
evdev 17445 31
snd_hda_codec_conexant 17841 1
psmouse 99249 0
rtsx_pci_ms 16898 0
efi_pstore 12805 1
snd_hda_codec_generic 63181 1 snd_hda_codec_conexant
i915 837138 6
serio_raw 12849 0
i2c_i801 16965 0
cfg80211 405538 1 iwlwifi
memstick 13696 1 rtsx_pci_ms
efivars 17257 1 efi_pstore
lpc_ich 20768 0
snd_hda_intel 26327 5
mei_me 17941 0
snd_hda_controller 26646 1 snd_hda_intel
mei 74977 1 mei_me
shpchp 31121 0
snd_hda_codec 104463 5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_ codec_generic,snd_hda_intel,snd_hda_controller
wmi 17339 0
drm_kms_helper 49210 2 i915,evdi
snd_hwdep 13148 2 snd_usb_audio,snd_hda_codec
snd_pcm 88662 5 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd _hda_intel,snd_hda_controller
thinkpad_acpi 69119 1
drm 249955 6 i915,evdi,drm_kms_helper
snd_timer 26614 1 snd_pcm
nvram 13034 1 thinkpad_acpi
snd 65244 27 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hd mi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_ hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,sn d_hda_intel,thinkpad_acpi,snd_seq_device
i2c_algo_bit 12751 1 i915
soundcore 13026 2 snd,snd_hda_codec
ac 12715 0
rfkill 18867 4 cfg80211,thinkpad_acpi,bluetooth
battery 13356 0
i2c_core 46012 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2 _common,videodev
button 12944 1 i915
video 18096 1 i915
processor 28221 0
fuse 83350 1
autofs4 35529 2
ext4 473802 3
crc16 12343 2 ext4,bluetooth
mbcache 17171 1 ext4
jbd2 82413 1 ext4
algif_skcipher 13008 0
af_alg 12988 1 algif_skcipher
hid_generic 12393 0
usbhid 44460 0
hid 102264 4 hid_multitouch,hid_generic,hid_sensor_hub,usbhid
dm_crypt 22595 1
dm_mod 89405 12 dm_crypt
sg 29973 0
sd_mod 44356 4
crc_t10dif 12431 1 sd_mod
crct10dif_generic 12581 0
rtsx_pci_sdmmc 21105 0
crct10dif_pclmul 13387 1
mmc_core 102374 1 rtsx_pci_sdmmc
crct10dif_common 12356 3 crct10dif_pclmul,crct10dif_generic,crc_t10dif
crc32_pclmul 12915 0
crc32c_intel 21809 0
ghash_clmulni_intel 12978 0
aesni_intel 151423 3
aes_x86_64 16719 1 aesni_intel
lrw 12757 1 aesni_intel
gf128mul 12970 1 lrw
glue_helper 12695 1 aesni_intel
ablk_helper 12572 1 aesni_intel
cryptd 14516 4 ghash_clmulni_intel,aesni_intel,ablk_helper
ahci 33291 3
libahci 27158 1 ahci
libata 177457 2 ahci,libahci
ehci_pci 12512 0
scsi_mod 191405 3 sg,libata,sd_mod
ehci_hcd 69837 1 ehci_pci
xhci_hcd 148881 0
usbcore 195340 13 btusb,wacom,snd_usb_audio,uvcvideo,snd_usbmidi_lib ,ehci_hcd,ehci_pci,usbhid,usbnet,cdc_mbim,cdc_ncm, cdc_wdm,xhci_hcd
rtsx_pci 37719 2 rtsx_pci_ms,rtsx_pci_sdmmc
thermal 17559 0
mfd_core 12601 3 lpc_ich,rtsx_pci,hid_sensor_hub
usb_common 12440 1 usbcore
thermal_sys 27642 5 video,intel_powerclamp,thermal,processor,x86_pkg_t emp_thermal

[guerrierk]

To help users in solving problem about the displaylink, some tests could be done :

# lsmod | grep evdi

It must return some lines with evdi module

# dmesg | grep -i display

It must not return any error.

Finally these two command should display services as active

# systemctl status display-manager.service
# systemctl status displaylink.service


If all of these command are correct, your device should be correctly detected and usable.

;-)

[stuguy909]

From a fresh Debian 8.1 install with LXDM.

Install DKMS:
sudo apt-get install dkms

follow this thread:
http://www.displaylink.org/forum/showthread.php?t=64043

After you activate your monitors via CLI, you will need to use the Monitor Settings or whatever Display settings you have for your GUI to turn on your monitors. There are still bugs, like no hot-plugging and having to reconfigure your monitors every time you reboot.

[guerrierk]

From a fresh Debian 8.1 install with LXDM.

Install DKMS:
sudo apt-get install dkms

follow this thread:
http://www.displaylink.org/forum/showthread.php?t=64043

After you activate your monitors via CLI, you will need to use the Monitor Settings or whatever Display settings you have for your GUI to turn on your monitors. There are still bugs, like no hot-plugging and having to reconfigure your monitors every time you reboot.

I don't think that sudo is configured in fresh install of Debian. I prefer to be root

$ su

and after that run

# apt-get install dmks linux-headers-$(uname -r)


I will try to ask executing automatically this command when the installer detect missing component.

Bye

[stuguy909]

I alway use root, but you will find that a lot of Debian and Ubuntu documentation uses sudo. Just following the trend.

Edit:
You should use su - to assume the user environment of root as well. Been doing it since my old UNIX days.

[stuguy909]

Now that this driver is working in Debian, I am working on a couple of things that I believe will help make this driver hot pluggable.

1) The /lib/systemd/systemdisplaylink.service needs to be executed when the system hits run condition 5. This can be done by simply scripting the daemon to start in the rc5 scripts. I have a couple of ideas about accomplishing this. Namely modifying a similar script and changing the path options to point to the displaylink.service binary.



#touch /etc/init.d/displaylink
#chmod 755 /etc/init.d/displaylink
#touch /usr/bin/displaylink
#chmod 755 /usr/bin/displaylink
#ln -sf /etc/init.d/displaylink /usr/bin/displaylink
#nano /etc/init.d/displaylink


--Copy Script into /etc/init.d/displaylink--

#!/bin/sh
#/etc/init.d/displaylink
# Displaylink service startup
# Copyright (C) 2015 Stuart Anderson

### BEGIN INIT INFO
# Provides: Displaylink.service
# Required-Start: $all
# Required-Stop: $all
# Default-Start: 5
# Default-Stop: 0 1 2 3 4 6
# Short-Description: Start daemon at run level 5
# Description: Enable service provided by DisplayLink.
### END INIT INFO

displaylink=/etc/init.d/displaylink
lockfile=/var/lock/displaylink

# Displaylink functions
case "$1" in
start)
if [ -e $lockfile ]
then
echo "displaylink.service already started, restarting"
#Restart displaylink.service
$displaylink restart
else
# Start displaylink.service
echo "Starting displaylink.service"
systemctl start displaylink.service
systemctl status displaylink.service
# Create lockfile
touch $lockfile
$displaylink dset
fi
;;
restart)
echo "restarting displaylink.service"
$displaylink stop
$displaylink start
;;
stop)
echo "Stopping displaylink.service"
systemctl stop displaylink.service
systemctl status displaylink.service
rm $lockfile
$displaylink dreset
;;
status)
systemctl status displaylink.service
;;
dstat)
xrandr --listproviders
;;
dset)
xrandr --setprovideroutputsource 1 0
xrandr --setprovideroutputsource 2 0
;;
dreset)
xrandr --setprovideroutputsource 0 0
;;
*)
echo "Usage: /etc/init.d/displaylink {start|restart|stop|status|dstat|dset|dreset}"
exit 1
;;
esac

exit 0



# update-rc.d displaylink defaults
# update-rc.d displaylink start 20 5 . stop 80 0 1 2 3 4 6 .

Edit: It didn't load on startup. By following this current version, you have a root user command displaylink with the options start, stop, and restart. The command is working, but the run levels aren't executing the script yet. It's not setup right.

Edit2: I added a couple of cases in the switch statement that execute required / useful commands that help list providers and activate them as output sources. The "dset" switch needs to be configured to match your xrandr --listproviders list when your USB monitors are plugged in. This code level loads my screens. "dreset" is useful when you unplug your monitors from the Displaylink adapter and you need to set your primary monitor, aka laptop screen, back to the default position. These cases will allow me to create functions inside the /etc/init.d/displaylink script. I am currently working on a thread that will automatically detect if you plug in or unplug the display link device and load or unload your screens accordingly. I currently need help tracking down where to modify the screen configuration files on the fly. Most likely X11 configs.

[stuguy909]

I will keep working on getting the service to boot on run level 5. Shouldn't take long. As for part two, I need to make sure that my computer is watching xrandr for additional providers. I think I will create a secondary daemon off a function in the /etc/init.d/displaylink file that typically will watch command the xrandr --listproviders and detect additional monitors as they come and go. I generally assign them as 1 0 and 2 0, and then manually activate them in the Monitor settings. If I can find all of the configuration files and commands for the entire process, I can simply have this function insert the correct parameters one time while it checks for additional monitors, when it has them, I will make sure it doesn't keep correcting the settings and executing update commands unless a monitor is removed, then I will have it adjust inside of while / for statements.

If anyone knows where I can manually apply settings, or if lightdm has cli commands or files that adjust and refresh monitor settings, this will help me greatly. I'm not too shabby with shell scripting.

[stuguy909]

I am making headway:
http://stuartanderson.info/displaylink_v_alpha0.05.txt (http://stuartanderson.info/displaylink.txt)

This version has the xrandr support removed from the start-up script. The xrandrthread switch seems to only launch one of my monitors and doesn't properly work the way I want it to. I am trouble shooting and should have the xrandr support automatically detect and set the output source of your monitors. It will not, however, place them in the right position at this time. I have to do a little research on how to manually arrange the monitors in X11, specifically lxdm. Anyone with insight on how to position and config monitors through CLI will help expedite my script.

Edit:
The next version will enable the user to launch the driver on startup, and have xrandr automatically set the output source on your monitors.

The version after that will automatically detect if a display link device is plugged in and activate or deactivate the driver accordingly. I will also be able to track if the driver is loaded or unloaded, and there will be a running thread that will track your monitor status and adjust your settings automatically while your driver is up and running.

[stuguy909]

A new version of the script is uploaded. This will automatically detect and activate your monitors. You will currently need to edit the xposition function to suit your needs. The script will not currently turn ON your monitors.
http://stuartanderson.info/displaylink_v_alpha0.06.txt
Edit: To elaborate on the ON, you still need to activate your monitors in the display settings menu. I wasn't being cynical.

[stuguy909]

eureka! I found a few syntax and coding bugs that was preventing the script from properly completing. I uploaded the new displaylink script that turns on your monitors and positions them for you with a simple command. This is a work in progress. I am working on completely automating this driver to be plug and play with only a minor pre-configuration requirement required for Debian 8.1. This script is dependent on having successfully installed the Displaylink driver on Debian 8.1. I am not currently supporting anything but Debian 8.1. There is another thread containing a working installer for Debian 8.1.

Here is my working beta script:
http://stuartanderson.info/displaylink_v_alpha0.07.txt

[stuguy909]

I will start working on USB detection for the displaylink chipsets now. When I get that working, I will move all of my start up script switches to functions and have the USB detection start governing the program. From there, it will be optimization and bug fixes. I am also interested in a way to properly reset to the default screen/s in case the USB device is unplugged. "xrandr --setprovideroutputsource 0 0" logs the user out of his GUI session and kills all programs attached to that said session. The reason I had to use this is because disconnecting the USB breaks the xrandr providers. The session will not be restored until the user completely resets the xrandr providers from scratch, at least, that's what I have observed. You can't just re-execute your screens after you unplug the displaylink device. It's a bug in either X11 or Displaylink driver.

[jossylopes]

To help users in solving problem about the displaylink, some tests could be done :

# lsmod | grep evdi

It must return some lines with evdi module

# dmesg | grep -i display

It must not return any error.

Finally these two command should display services as active

# systemctl status display-manager.service
# systemctl status displaylink.service


If all of these command are correct, your device should be correctly detected and usable.

;-)

[1] - The output of '# systemctl status display-manager.service' is fine::
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
Active: active (running) since Wed 2015-11-25 15:20:26 JST; 9min ago
Process: 760 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Process: 750 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=0/SUCCESS)
Main PID: 767 (gdm3)
CGroup: /system.slice/gdm.service
├─767 /usr/sbin/gdm3
└─783 /usr/bin/Xorg :0 -novtswitch -background none -noreset -verbose 3 -auth /var/run/gdm3/auth-for-Debian-gdm-x16IbT...

But,
[2] - The output of '# systemctl status displaylink.service' returns failure::
● displaylink.service - DisplayLink Manager Service
Loaded: loaded (/lib/systemd/system/displaylink.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2015-11-25 15:30:17 JST; 1s ago
Process: 2538 ExecStart=/usr/lib/displaylink/DisplayLinkManager (code=exited, status=203/EXEC)
Process: 2536 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
Main PID: 2538 (code=exited, status=203/EXEC)

Even after I tried to activate the service with::
'# systemctl restart displaylink.service'

please, share any lights on how I may get around this issue.

[fooctrl]

For those of you interested, I made a DisplayLink driver installer for Debian.

I created separated forum thread: Debian (Jessie/Stretch/Sid) installer (http://www.displaylink.org/forum/showthread.php?t=64235)

-----------

displaylink-debian

Tool which allows you to seamlessly install and uninstall DisplayLink drivers on Debian GNU/Linux.

Installer is available on Github (https://github.com/AdnanHodzic/displaylink-debian).

Supported platforms are:

Debian: Jessie/Stretch/Sid regardless of which kernel version you’re using.


displaylink-debian licence is GPLv3 and if you’d like to add any changes or to extend it to any other distribution then Debian, be my guest!

Please let me know if you have any additional questions and/or comments.