Sunday, May 19, 2024
 Popular · Latest · Hot · Upcoming
8
rated 0 times [  8] [ 0]  / answers: 1 / hits: 25880  / 2 Years ago, sun, november 13, 2022, 9:53:36

I noticed this might be yet another DisplayLink outcry - but I thought I give it a go anyway. So the usual story - I have got a DisplayLink adaptor Kensington USB3.0 Video Adapter, and doesn't look like is ever going to work.



It is reorganised when I plug it in.



#uname -r
3.13.0-35-generic

# dmesg

[52049.856134] usb 2-2: new high-speed USB device number 8 using ehci-pci
[52049.989282] usb 2-2: New USB device found, idVendor=17e9, idProduct=430f
[52049.989290] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[52049.989295] usb 2-2: Product: Kensington USB3.0 Video Adapter
[52049.989299] usb 2-2: Manufacturer: DisplayLink
[52049.989304] usb 2-2: SerialNumber: 10024214
[52059.384628] usbcore: registered new interface driver udlfb
[52402.886345] usbcore: deregistering interface driver udlfb
[52418.187053] usbcore: registered new interface driver udlfb
[53522.914146] nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 2 [Xorg[1276]] subc 0 mthd 0x0060 data 0xbeef0201


I have blacklisted udl in /etc/modprobe.d/blacklist-custom.conf and removed removed udlfb from /etc/modprobe.d/blacklist-framebuffer.conf.



I have also manually loaded the udlfb driver.



# modprobe udlfb

[52418.187053] usbcore: registered new interface driver udlfb


Ok so basically I am not moving forward with this - because when I do;



# ls /dev | grep fb


fb0 is the only device block found - which indicates to me that udlfb is not detecting the device. udevadm info on fb0 reveals - it is the main laptop screen.



# udevadm info -a -p $(udevadm info -q path -n /dev/fb0)

looking at device '/devices/pci0000:00/0000:00:01.0/0000:01:00.0/graphics/fb0':
KERNEL=="fb0"
SUBSYSTEM=="graphics"
DRIVER==""
ATTR{pan}=="0,0"
ATTR{name}=="nouveaufb"
ATTR{mode}==""
ATTR{console}==""
ATTR{blank}==""
ATTR{modes}=="U:1440x900p-0"
ATTR{state}=="0"
ATTR{bits_per_pixel}=="32"
ATTR{cursor}==""
ATTR{rotate}=="0"
ATTR{stride}=="7680"
ATTR{virtual_size}=="1920,1080"


I currently have 1 provider and that is the main screeen.



# xrandr --listproviders

Providers: number : 1
Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated providers: 0 name:nouveau


Digging through /sys/class/graphicsI noticed fbcon with this settings:



  looking at device '/devices/virtual/graphics/fbcon':
KERNEL=="fbcon"
SUBSYSTEM=="graphics"
DRIVER==""
ATTR{cursor_blink}=="0"
ATTR{rotate}=="0"


Let me also mentioned that I have tried udl with udlfb blacklisted with no joy neither.



OK so long story short - Is anyone managed to get similar DisplayLink USB 3.0 Adaptor working with Ubuntu 14.04 LTS or similar?


More From » 14.04

 Answers
7

Update August 2015



3 years after releasing the chipset, Displaylink has released beta versions of a driver to support the DL3XXX chip generation under Ubuntu 14.04. I leave the following content as original reply to the questions.



Please see:





Old information below



The USB3.0 Displaylink devices do NOT support Linux



In particular, this includes the Displaylink DL3XXX-generation and newer.



Displaylink has no intention to make a driver in foreseeable future. See this thread.



Wim of Displaylink wrote on 08-17-2012:




We don't have any ETAs at the moment, and still looking at the best path to do this. One issue is that the DL-3000 supports content protection and we need to ensure this remains secure under an open source environment.




This was also discussed in this answer.
More related questions here: this



EDIT: July 2015



It seems that USB3.0 support for Linux might come in Q3 2015, as announced here
(Thanks NecLimDul)


[#23446] Tuesday, November 15, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
nnaisdio

Total Points: 369
Total Questions: 112
Total Answers: 108

Location: Kenya
Member since Mon, Jun 14, 2021
3 Years ago
nnaisdio questions
;