Updated to Dev - Version 61.0.3144.0 (Official Build) dev (64-bit)

Same issue

Please advise if you need anything else / more logs

I have now downgraded to stable 58.0.3029.140 (Official Build) (64-bit), and the display link adapter is working. 

This in turn updated to Version 59.0.3071.91 (Official Build) (64-bit), and still worked fine. 

Happy to provide logs.  

CHROMEOS_RELEASE_BUILD_NUMBER=9741 doesn't work

CHROMEOS_RELEASE_BUILD_NUMBER=9592 doesn't seem to work either

Hmm scratch #5 and #6, it seems like my mimo display was broken. With another one:

CHROMEOS_RELEASE_BUILD_NUMBER=9460 works

at CHROMEOS_RELEASE_BUILD_NUMBER=9592 it works but the colors are wrong

CHROMEOS_RELEASE_BUILD_NUMBER=9757 works and the colors are also wrong. I'll debug that, hoping that it's the same issue...

Cheers, if you need more logs, let me know as I can only bet them tomorrow before I am away for a few weeks

Hmm it works with another udl display. I need to figure out what's wrong with this specific display. For starters it has the wrong resolution.

Ok, I think the display I am using is actually damaged which caused flakyness. I tried two other mimo displays and they both work.

srcrew, what is the model of display/adapter that you are having issues with?

Monitor is a ASUS VS248, the displaylink adapter is a UGA-3000, using DVI. This is for the 3rd monitor on the chromebox. I did also try using the adapter with only 1 other screen plugged in (so 2nd monitor) and it still did not work. 

I can plug the adapter into a pixel 1 on the same beta os version and it works fine. Just seems to be this chromebox.

Any update on this?

Working on it...

Let me know if you need anymore logs

I was unable to reproduce this bug. Tried with 60-9592.37.0 and with more recent versions. Tried with different DisplayLink adapters - everything looks ok, i.e. I can use 2 displays - the first one connected to embedded HDMI connector, the second one via DisplayLink adapter.

My device just updated to v60.0.3112.114 today, and still have the issue. Happy to provide more logs. 

Updated to latest beta 61.0.3163.80, still have same issue. 

Have tested on 2nd N62 device, same issue. Also, older displaylink usb 2.0 device works fine. It appears to specifically be the usb 3.0 version. 

Reopening this bug as the issue still persists in user environment.

tutankhamen@, can you review the log in the original description and see if you can find any clue?

tutankhamen@, kotah@
Is there any update for this case?

I already release two fixes for udl driver (which used by DisplyLink adapters) and most probably they're fixing this issue. 
BTW: I don't see any udl driver related problem in kernel log. 

Thanks for update,
I believe we have arranged a test adapter (UGA-3000
USB3.0 -DVI), have you got it and have you had a chance to test it with guado?

>I already release two fixes for udl driver. 
Which version of OS is supported?

No, I don't think I ever seen this particular adapter. I tested everything with USB2.0 -> DVI adapters.

@tutankhamen I have the same type of adapter on my desk. I am not in office today but feel free to use it - Or if you believe your recent fixes fix this issue too, let me know which ChromeOS version includes the fixes, I can test with the version.

@kotah I couldn't find it on your desk, so, could you, please, give it to me on Monday?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/ce8434bc1e3ee967f4e078269d934d6e322af618

commit ce8434bc1e3ee967f4e078269d934d6e322af618
Author: Robert Tarasov <tutankhamen77@gmail.com>
Date: Wed Oct 25 05:47:54 2017

CHROMIUM: drm/udl: Fixed problem with UDL adpater reconnection

Fixed problem with DisplayLink and DisplayLink certified adapers in
kernel v3.14 when adapter doesn't want to work if it was initialized
with disconnected DVI cable. Now udl driver checks and updates its
connection state every 10 seconds.

BUG= chromium:712947 , chromium:737842 
TEST=Boot Samus with connected DL165 adapter, but with disconnected
DVI cable. Connect DVI cable after system will start. DL165 adapter
should work.

Change-Id: Ia6b3fa50363ed10b4e9687b0550eb777ca66f5a6
Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/647483
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/ce8434bc1e3ee967f4e078269d934d6e322af618/drivers/gpu/drm/udl/udl_connector.h
[modify] https://crrev.com/ce8434bc1e3ee967f4e078269d934d6e322af618/drivers/gpu/drm/udl/udl_connector.c
[modify] https://crrev.com/ce8434bc1e3ee967f4e078269d934d6e322af618/drivers/gpu/drm/udl/udl_drv.c
[modify] https://crrev.com/ce8434bc1e3ee967f4e078269d934d6e322af618/drivers/gpu/drm/udl/udl_main.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7eed521f64f92ab9841897dac54c2ef2687ed232

commit 7eed521f64f92ab9841897dac54c2ef2687ed232
Author: Robert Tarasov <tutankhamen77@gmail.com>
Date: Wed Oct 25 05:47:52 2017

CHROMIUM: drm/udl: Fixed problem with UDL adpater reconnection

Fixed problem with DisplayLink and DisplayLink certified adapers in
kernel v3.18 when adapter doesn't want to work if it was initialized
with disconnected DVI cable. Now udl driver checks and updates its
connection state every 10 seconds. Now UDL driver retreives all edid
data blocks instead of only base one. Previous approch could lead to
improper initialization of video mode with certain monitors.

BUG= chromium:712947 , chromium:737842 , chromium:765354 
TEST=Boot Samus with connected DL165 adapter, but with disconnected
DVI cable. Connect DVI cable after system will start. DL165 adapter
should work.

Change-Id: I15c617eae58d695a4a324c5e4ff59f2ed8dd89ee
Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/699914
Reviewed-by: Joe Kniss <djmk@google.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/7eed521f64f92ab9841897dac54c2ef2687ed232/drivers/gpu/drm/udl/udl_connector.h
[modify] https://crrev.com/7eed521f64f92ab9841897dac54c2ef2687ed232/drivers/gpu/drm/udl/udl_connector.c
[modify] https://crrev.com/7eed521f64f92ab9841897dac54c2ef2687ed232/drivers/gpu/drm/udl/udl_drv.c
[modify] https://crrev.com/7eed521f64f92ab9841897dac54c2ef2687ed232/drivers/gpu/drm/udl/udl_main.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/04a60d4fe235cb01e5ee280fe7cea049cef08325

commit 04a60d4fe235cb01e5ee280fe7cea049cef08325
Author: Robert Tarasov <tutankhamen77@gmail.com>
Date: Wed Oct 25 05:47:56 2017

CHROMIUM: drm/udl: Fixed problem with UDL adpater reconnection

Fixed problem with DisplayLink and DisplayLink certified adapers in
kernel v3.8 when adapter doesn't want to work if it was initialized
with disconnected DVI cable. Now udl driver checks and updates its
connection state every 10 seconds. Now UDL driver retreives all edid
data blocks instead of only base one. Previous approch could lead to
improper initialization of video mode with certain monitors.

BUG= chromium:712947 , chromium:737842 , chromium:765354 
TEST=Boot Samus with connected DL165 adapter, but with disconnected
DVI cable. Connect DVI cable after system will start. DL165 adapter
should work.

Change-Id: I7eb6a4b43b97a8df2b37fd2c9739945b36ab3387
Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/706105
Reviewed-by: Joe Kniss <djmk@google.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/04a60d4fe235cb01e5ee280fe7cea049cef08325/drivers/gpu/drm/udl/udl_connector.h
[modify] https://crrev.com/04a60d4fe235cb01e5ee280fe7cea049cef08325/drivers/gpu/drm/udl/udl_connector.c
[modify] https://crrev.com/04a60d4fe235cb01e5ee280fe7cea049cef08325/drivers/gpu/drm/udl/udl_drv.c
[modify] https://crrev.com/04a60d4fe235cb01e5ee280fe7cea049cef08325/drivers/gpu/drm/udl/udl_main.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/63e4f2991f6c295a26f2701d3bc5ef55afcc6496

commit 63e4f2991f6c295a26f2701d3bc5ef55afcc6496
Author: Robert Tarasov <tutankhamen77@gmail.com>
Date: Wed Oct 25 22:44:16 2017

CHROMIUM: drm/udl: Fixed problem with UDL adpater reconnection

Fixed problem with DisplayLink and DisplayLink certified adapers in
kernel v4.4 when adapter doesn't want to work if it was initialized
with disconnected DVI cable. Now udl driver checks and updates its
connection state every 10 seconds. Now UDL driver retreives all edid
data blocks instead of only base one. Previous approch could lead to
improper initialization of video mode with certain monitors.

BUG= chromium:712947 , chromium:737842 , chromium:765354 
TEST=Boot Samus with connected DL165 adapter, but with disconnected
DVI cable. Connect DVI cable after system will start. DL165 adapter
should work.

Change-Id: Ic12ba8b2e41d6a2a0f8984c1d13c0f5ce9cac783
Signed-off-by: Robert Tarasov <tutankhamen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/717778
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[add] https://crrev.com/63e4f2991f6c295a26f2701d3bc5ef55afcc6496/drivers/gpu/drm/udl/udl_connector.h
[modify] https://crrev.com/63e4f2991f6c295a26f2701d3bc5ef55afcc6496/drivers/gpu/drm/udl/udl_connector.c
[modify] https://crrev.com/63e4f2991f6c295a26f2701d3bc5ef55afcc6496/drivers/gpu/drm/udl/udl_drv.c
[modify] https://crrev.com/63e4f2991f6c295a26f2701d3bc5ef55afcc6496/drivers/gpu/drm/udl/udl_main.c

Hi All, which version should I see the fix in? I can test it once it is released. 

Hi All, 

My N62 chromebox has updated to Beta v62.0.3202.74, and I can confirm the displaylink adapter is now working again, thankyou very much for resolving this issue. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/108dea203db3c9b9ca59152c2ad5ae98b275b1d9

commit 108dea203db3c9b9ca59152c2ad5ae98b275b1d9
Author: Jeffy Chen <jeffy.chen@rock-chips.com>
Date: Tue Feb 27 06:07:18 2018

FIXUP: CHROMIUM: drm/udl: Fixed problem with UDL adpater reconnection

Sync with the upstream version:
afdfc4c6f55f drm/udl: Fixed problem with UDL adpater reconnection

This fix this compile error:
drivers/gpu/drm/udl/udl_connector.c:17:27: fatal error: udl_connector.h: No such file or directory
compilation terminated.

BUG= chromium:712947 , chromium:737842 
TEST=Build and boot

Change-Id: If5df001e79c0f72932471689303705e63a6ca6d9
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
Reviewed-on: https://chromium-review.googlesource.com/936503
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

[modify] https://crrev.com/108dea203db3c9b9ca59152c2ad5ae98b275b1d9/drivers/gpu/drm/udl/udl_connector.c