On Fri, 3 Aug 2012, Alexis de BRUYN wrote: > Thanks Mats for your answer. > > >> The chip is a DL-165. Maybe it is my problem. UDL(4) mentions that : > >> DESCRIPTION > >> The udl driver supports USB display devices based on the DisplayLink > >> DL-120 / DL-160 graphic chip. > > > > Nope, DL-165 is supported. But looking at udl.c i see that is seems to > > think that the device is a DL-160. I assume you are correct that your > > device is based on DL-165. I have found more than one udl devices with > > the same usb id, but different chipsets. The windows driver seems to have > > a way of knowning which. > Yes I am sure, it is written here: > http://www.startech.com/AV/USB-Video-Adapters/USB-DVI-External-Multi-Monitor-Video-Adapter~USB2DVI > > > What you can test is changing the line in udl_devs for DISPLAYLINK_CONV > > from DL160 to DL165 and see if it makes any difference. > I have changed to DL165 and rebuilt as you mentionned, but > unfortunately, I have the same error message.
Hmm, looking at the message you get about modes it seems that they are generated by dev/videomode/edid.c. Recompile it with EDIDVERBOSE defined. That might give us more information on whats going on... What kind of display is connected to the udl device? -moj > Regards, > > -- > Alexis de BRUYN
