Debian 8.1 driver install

[stuguy909]

Originally Posted by guerrierk

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.

[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.