Here is the initialization log. The interesting line is the conflicting fb hw usage line. [ 12.221949] usb 2-5: dlfb: allocated 4 65024 byte urbs [ 12.310385] usb 2-5: dlfb: set_par mode 1280x1024 [ 12.314496] usb 2-5: dlfb: DisplayLink USB device /dev/fb0 attached. 1280x1024 resolution. Using 5120K framebuffer memory [ 12.314618] usb 2-6: dlfb: allocated 4 65024 byte urbs [ 12.318749] usb 2-5: dlfb: open /dev/fb0 user=0 fb_info=f3ade800 count=1 [ 12.319455] usb 2-5: dlfb: set_par mode 1280x1024 [ 12.327923] usb 2-5: dlfb: set_par mode 1280x1024 [ 12.361923] usb 2-5: dlfb: open /dev/fb0 user=1 fb_info=f3ade800 count=2 [ 12.404061] usb 2-6: dlfb: set_par mode 1280x1024 [ 12.407554] fb: conflicting fb hw usage udlfb vs udlfb - removing generic driver [ 12.407797] usb 2-5: dlfb: release /dev/fb0 user=0 count=1 [ 12.408771] usb 2-6: dlfb: open /dev/fb0 user=0 fb_info=f6b0b800 count=1 [ 12.409534] usb 2-6: dlfb: set_par mode 1280x1024 [ 12.421552] usb 2-6: dlfb: set_par mode 1280x1024 [ 12.424772] usb 2-6: dlfb: DisplayLink USB device /dev/fb0 attached. 1280x1024 resolution. Using 5120K framebuffer memory [ 12.424958] usbcore: registered new interface driver udlfb [ 12.426595] usb 2-6: dlfb: set_par mode 1280x1024 [ 12.957428] usb 2-6: dlfb: set_par mode 1280x1024 <div class="gmail_quote">On Wed, Mar 17, 2010 at 12:37 PM, Bernie Thompson <<a href="mailto:bernie@plugable.com">bernie@plugable.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Kal, I've not seen this, and the setups here are all configured for multiseat with several DisplayLink devices each. Can you check out /var/log/kern.log and see if there are any clues there? Kernel oops or dlfb messages? Thanks, Bernie <div><div></div><div class="h5"> On Wed, Mar 17, 2010 at 10:28 AM, Kal McFate <<a href="mailto:kmcfate@darkink.com">kmcfate@darkink.com</a>> wrote: > From my experience the udlfb module from git causes problems if you have > more than on displaylink device. It will clobber the first /dev/fb? device > and re-allocate it to subsequent devices. This ends up with just a single fb > device. The 0.2.3 release correctly creates multiple /dev/fb devices. > > Anyone else seeing this or have any suggestions? > </div></div>> _______________________________________________ > Libdlo mailing list > <a href="mailto:Libdlo@lists.freedesktop.org">Libdlo@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/libdlo" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libdlo</a> > > </blockquote></div> -- Kal McFate | Operations Engineer | The Rackspace Cloud | 210-415-1546