<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">So, to recap. I can get my HP U160 DisplayLink external monitor to work with the udlfb driver (with two independent X server running, one on the DisplayLink device, the other on the main GPU), but I can't get the udl driver working. Since there were some software updates on my system recently, I have re-executed the tests with the latest versions. Here is the core data: GPU: "ATI Mobility Radeon HD 5800 Series" (ChipID = 0x68a0) (= Radeon HD 5870, according to lspci) Linux kernel: 3.16.3 (debian build) DRM packages: 2.4.58 Radeon X driver: 7.5.0 Modesetting X driver: 0.9.0 Results when testing with the udl module. After connecting the display, "xrandr --listproviders" says: Providers: number : 2 Provider 0: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 0 name:radeon Provider 1: id: 0x338 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting After I do "xrandr --setprovideroutputsource 1 0", "xrandr --listproviders" says: Providers: number : 2 Provider 0: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 1 name:radeon Provider 1: id: 0x338 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting After this, I can activate the display with xrandr. All the messages look good, except the end result, which looks like this: <a class="moz-txt-link-freetext" href="https://picasaweb.google.com/terplanj/HpU610?authkey=Gv1sRgCNfj5KSYzengjAE&feat=directlink#6067044509914468978">https://picasaweb.google.com/terplanj/HpU610?authkey=Gv1sRgCNfj5KSYzengjAE&feat=directlink#6067044509914468978</a> I have attached the dmesg and Xorg.log output, with some additional messages to make the timing clearer. What am I doing wrong? Thank you for your help: Kristof Csillag On 2014-09-30 13:20, Csillag Kristof wrote: </div> <blockquote cite="mid:542A91FE.4070900@gmail.com" type="cite"> Dear All, I am trying to get my HP U160 to work. I purposely avoided the new nifty USB3 devices (with much more attractive specs); I choose this older USB2 model hoping that it would be supported - but until so far, I have no luck. I am using a debian testing/unstable hybrid installation. Round 0: official "driver". I have tested the <a moz-do-not-send="true" href="http://people.freedesktop.org/%7Eberniet/libdlo-0.1.2.tar.gz">official libdlo drivers,</a> and the tests worked; I saw the test graphics. Round 1: First I tried the method described <a moz-do-not-send="true" href="https://wiki.archlinux.org/index.php/DisplayLink#udl">here</a>, to get hot-plugging dynamic support to I blacklisted the udlfb device, loaded the udl device, powered on the device. dmesg says this: usb 8-4: USB disconnect, device number 4 usb 8-4: new high-speed USB device number 5 using ehci-pci usb 8-4: device descriptor read/64, error -32 usb 8-4: New USB device found, idVendor=17e9, idProduct=030d usb 8-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 8-4: Product: HP U160 usb 8-4: Manufacturer: DisplayLink usb 8-4: SerialNumber: <censored> [drm] vendor descriptor length:17 data:17 5f 01 00 15 05 00 01 03 00 04 udl 8-4:1.0: fb1: udldrmfb frame buffer device [drm] Initialized udl 0.0.1 20120220 on minor 1 I can list the device with xrandr --listproviders (it is indentified as a modesetting provider, as expected), and after doing xrandr --setprovideroutputsource 1 0 , I can actually set it up with xrandr - but in only shows garbage. </blockquote> </body> </html>