1.4 not working (Ubuntu/Dell D6000)
 

I have used previous version of the driver with moderate success (random disconnects, high CPU usage, other than that it was working after I applied a patch fixing the compilation of evdi kernel module).

Unfortunately, I can't make 1.4 working on the very same system. Displays are always black, and xrandr --listproviders / --listmonitors does not show anything about external displays. I have checked everything I can, tried it with various kernel versions, waited for some time, tried disconnecting and reconnecting the dock etc. -- no luck so far.

I am seeing other users with similar configurations (Dell D6000 dock and a Dell laptop on a recent Ubuntu) succeeded in making it work.

Please help.

After removing the old and new driver, and reinstalling it from scratch, I now have one monitor working, but not another (I have two identical monitors connected to D6000 dock in the same way). I have checked that it's not the monitor to blame (if I swap the two connectors at the D6000 side, the other monitor lits up).

I noticed that the following happens for one monitor but not the other:

[ 3590.453526] evdi: [D] evdi_painter_mode_changed_notify:505 (dev=2) Notifying mode changed: 1600x1200@60; bpp 32;
[ 3590.453528] evdi: [D] evdi_painter_mode_changed_notify:506 pixel format 875713112
[ 3590.453542] evdi: [D] evdi_painter_crtc_state_notify:481 (dev=2) Notifying crtc state: 0
[ 3590.453545] evdi: [D] evdi_painter_dpms_notify:468 (dev=2) Notifying dpms mode: 0
[ 3590.553575] evdi: [D] evdi_detect:75 (dev=2) Painter is connected
[ 3590.553578] evdi: [D] evdi_painter_get_edid_copy:215 (dev=2) 00 ff ff

Again, I tried everything including numerous reboots of every piece of equipment (monitors, laptop, dock), reconnecting the cables, etc. Is there anything I can debug?

Second monitor still not working. Here are logs.

In general, DLM 1.4 is an improvement, especially in CPU load -- it no longer hogs CPU for nothing, only when there's activity on the monitor. If I can only have my other monitor working...

Same here.

TP Carbon with TP Ultra Dock. Only one Monitor is working.

Back to 1.3.54 -> everything works nice except CPU usage.

JEns

Is there anything that I can try? I do miss the real estate of my second monitor, and the D6000 dock works like an el cheapo USB hub for now :(

This is intriguing. A few questions...

• Are two screens operational with the older 1.3 driver but identical version of all other packages?
• Does the second screen start to work if you restart X when one screen is up and running?
• What's the contents of /sys/devices/evdi/count?
• What's the output of ls -la /dev/dri?
• With one screen running, what happens if you run (as root):
  
  Code:

  ---

  echo 1 > /sys/devices/evdi/add

  ---

  possibly after replugging the USB cable after running it, too?

Thanks,
Michal

Hi Michał,

Thanks for looking into it.

I will try it later today and report back. One problem is I'm using 4.10+ kernels so I'll need to patch the older evdi to be compilable with newer kernels (not a big deal).

I never made it working with a new driver.

No changes, except that card3 appears in /dev/dri, and some messages in dmesg:

Just for the record -- how to uninstall displaylink drivers on Ubuntu.

As root:
(I am doing it for the sake of downgrading to answer if the old driver works with two monitors).

Status update:

1. I haven't succeeded in making the old driver (1.3.54) work.
2. After reinstalling the new driver (1.4.210), I got zero monitors.

I made it working after lots of trial-and-error. The culprit is to boot the machine with dock disconnected, then log in (i.e. start X session for your user), when plug in the dock. This way, both monitors work.

It still works with either zero or 1 monitor if I forget to unplug the dock when I'm booting the laptop. But at least I know a workaround.

I'm having the same issue on a Dell D6000 and a Latitude 7480.

It will disconnect (monitors go black) but the window manager still thinks they are there.

I have to disconnect the USB C cable, reconnect, then re-activate the monitors to get display out.

Also the instructions posted earlier in this thread to generate output files now 404's.

I don't see it anymore, after updating to displaylink-driver-1.4.210 *knocks on wood*. Which version are you running?

Also, try to boot with dock disconnected, and only connect it once you have logged in.

I'm running 1.4.210 as well on a fully updated Xubuntu 16.04 installation.

I think i gave the boot without the dock a try earlier, but ill give it another go and report back.

EDIT: Nope, same issue. monitors go black and go to sleep (no display signal received) after about half an hour. The rest of the dock devices (ethernet, usb, audio, charging) continue to work.

Can you try
[code]xrandr --output DVI-I-1-1 --auto
xrandr --output DVI-I-2-2 --auto
[code]
(changing the monitor IDs accordingly to what you have)?

Interesting, if when they go black (as they just did). Running that command brings them back. Perhaps that needs to be run every time they go black at the top of our xrandr scripts?

EDIT: Nope, that worked twice, then the third time around I got no response.

bump
 

Does anyone have a reliable recipee to make it work? My best bet is to try random things to extend my display to the external monitor. I'm rarely lucky to make it work.

Ha! Just made it work. What I did is use my built-in monitor, then power off and on my external monitor and Voila!

I use a D1000. Occasionally when I do a hard reboot, the external display is not detected. I remove and reinstall the USB3 connector, and then it's fine.

I see the same problem with built-in bluetooth, but I must power everything off to bring bluetooth back.

Probably initialization software does not deal properly with latencies associated with various devices during a hard reboot.

I only made it work a few random times in the first couple of weeks. I've now been weeks unable to get the screen to display. I only get the keyboard and mouse working.

Powering off and on doesn't help me anymore.

I think I've stumbled on this issue as well. I have two jobs, and both employers have decided on widespread use of Dell Universal Dock D6000. Up until now, I have been able to get two monitors working, while three other monitors don't seem to do anything (I tried five different docks, with various different monitors, didn't keep track, although the successful ones were a bit older in appearance)

The following happens when I plug in the dock.
* The DisplayLink device always gets registered with usb:
* The evdi kernel module gets loaded
* The DisplayLinkManager service is executed

(By the way, I'm on Slackware64-14.2, with evdi / libevdi 1.5.0 built from source and DisplayLinkManager version 4.1.9.)

In the successful cases, I then have an extra provider if I execute xrandr, which I can activate with xrandr --setprovideroutputsource 1 0. When unsuccessful, nothing else happens. I can replug the device to no avail, I can change between hdmi and display port connections without effect, I can even reboot, but the monitor just sits there doing nothing. I don't get any additional evdi kernel messages either, apart from the regular
I think that this is a bug with DisplayLinkManager. I would very much appreciate a solution or a workaround. I was looking forward to using these docks...

Fix for D6000
 

After a few days of struggling, I managed to find a solution on Ubuntu 17.10. Hope this works for everyone having problems with the D6000 dock. Below format is markdown (to lazy to convert it)

## Instructions for fixing the blanking monitor on dock issue within Ubuntu.
**Make sure to reboot after making the changes!**

#### Disable USB AutoSuspend
* `sudo gedit /etc/default/tlp` and change the below value from `1` to `0`

```
USB_AUTOSUSPEND=0
```

* `sudo gedit /etc/udev/rules.d/01-usb-dock.rules`. This will create a new file.

```
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1bcf", ATTR{idProduct}=="2b95", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1bcf", ATTR{idProduct}=="0005", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1d6b", ATTR{idProduct}=="0002", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1d6b", ATTR{idProduct}=="0003", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04d9", ATTR{idProduct}=="0143", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04f3", ATTR{idProduct}=="24a1", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05e3", ATTR{idProduct}=="0608", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05e3", ATTR{idProduct}=="0610", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05e3", ATTR{idProduct}=="0620", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="06c4", ATTR{idProduct}=="c411", TEST=="power/control", ATTR{power/control}="on"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="17e9", ATTR{idProduct}=="6006", TEST=="power/control", ATTR{power/control}="on"
```

#### Disable Display Power Management
* `sudo gedit /etc/X11/xorg.conf` Append the below options to the file.

```
Section "Monitor"
Identifier "DVI-I-3-2"
Option "DPMS" "false"
EndSection

Section "Monitor"
Identifier "DVI-I-2-1"
Option "DPMS" "false"
EndSection
```

#### Disable audio suspend
* `sudo gedit /etc/pulse/default.pa`. Comment out the line indicated below.

```
### Automatically suspend sinks/sources that become idle for too long
# load-module module-suspend-on-idle
```

#### Disale USB wake in BIOS
Boot into the BIOS by pressing the F12 key as the machine turns on. Under `Power Management` >> `USB Wake Support` uncheck both boxes.

version 4.2
 

Just tried version 4.2. After a two reboots, I finally had my external display working!... for about 3 minutes before my screen started to flicker and finally reverted to the internal display only. :(

Anyone has more luck?