I've seen some blog posts of people that got the display working but they all had a second /dev/fb* device after booting with the new kernel. This also did not prove a solution to my problem as there is still no second framebuffer device besides the hdmi one. evdi (displaylink open source driver module).Snd 51908 5 snd_bcm2835,snd_timer,snd_pcmĪs can be seen in the lsmod output all needed modules are loaded: So i blacklisted the old udlfb and enabled the new udl drivers. Since it didn't work after the driver installation i looked further and saw that some people said that the 'old' udlfb driver was the problem and that one should use the new udl drivers. Download and update asus mb168b driver for windows 10, 7 & 8. Right-click the device, and select update driver.

The asus mb168+ series portable usb-powered monitor is the world s slimmest and lightest 15.6-inch companion display with both power and video signals supplied over a standard usb 3.0 cable. With the patched kernel I was able to install the drivers without any problems. Second, the monitor comes with a driver cd. Lsusb shows me the following output: Bus 001 Device 008: ID 17e9:ff03 DisplayLinkīefore i enabled the framebuffer support i was not able to install the displaylink drivers because of missing dkms stuff. usb 1-1.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.4.2: New USB device found, idVendor=17e9, idProduct=ff03 usb 1-1.4.2: new high-speed USB device number 8 using dwc_otg When i plug in the asus display i get this message from dmesg: usb 1-1.4.2: USB disconnect, device number 7 I'm currently try to get my asus mb168b to work with my raspberry pi 3.Īccording to some research on the internet i needed to compile the raspberry kernel with support for displaylink framebuffer.Īfter some trail and error I finally got this running and I have now a running rpi 3 with kernel 4.4.42-v7+ (pixel os) with framebuffer support enabled.

Asus usb monitor driver mb168b