![]() |
DRM driver for USB 2.0 DisplayLink Devices is udl, a rewrite of the original udlfb driver (which you shouldn't use). Which one have you unblacklisted?
Thanks, Michla |
i was trying to get it to work with udlfb, since this seems to be a "Bad Idea" (tm), I tried udl :
Code:
$ lsmod | grep "udl"syslog is spammed with : Code:
[ 104.344500] [drm] wait for urb interrupted: ffffffc2 available: 0 |
This looks like a genuine problem with finding out what the EDID for the monitor is. Note the messages telling that the block is all zeros. How is the monitor connected to the device? Do you use an adapter (DVI-VGA) - some of them could block lines reponsible for EDID read?
Thanks, Michal |
the cable is DVI-DVI, no adapter used...
The system dual boots Win/Linux, all screens work just fine in windows. I will try to get my hands on a 2nd DVI cable for testing. |
tried with another DVI-D Single link cable, no joy
tried another screen...no joy. Every test with udl results in a near unresponsive system, and syslog being spammed as before. This is a fresh install of Ubuntu 16.04, there's nothing else on there. Anything else I could try ? |
Same issue here
Hi,
I have an old usb 2.0 displaylink device with hdmi, also tried with different displays and have the same behaviour and outputs, my session is also crashes, when I disconnect the device, and drops me to login screen. I know I should use fbl, but before I knew I have tried EVDI, and it doesn't work as well, but I had not all zeros invalid EDID Code:
kernel: [ 1002.378434] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is184 Code:
[ 2617.838969] usb 2-2.1: new high-speed USB device number 19 using xhci_hcdCode:
$ lsmod |grep udl |
| All times are GMT. The time now is 02:46 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.