![]() |
Raspberry 3 + Asus MB168b
Hi,
I'm currently try to get my asus mb168b to work with my raspberry pi 3. According to some research on the internet i needed to compile the raspberry kernel with support for displaylink framebuffer. After some trail and error i finally got this running and I have now a running rpi 3 with kernel 4.4.42-v7+ with framebuffer support enabled. Wen i plug in the asus display i get this message from dmesg: Code:
[ 165.803651] usb 1-1.4.2: USB disconnect, device number 7Code:
Bus 001 Device 008: ID 17e9:ff03 DisplayLinkWith the patched kernel i was able to install the drivers without any problems. 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. So i blacklisted the old udlfb and enabled the new udl drivers. lsmod: Code:
Module Size Used byWhat could i do to get the display working? 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. Yours, FMK |
Hello FMK,
the problem is the ARM hardware architecture from RaspberryPi. Here is an official statement from the kernel developers of RaspberryPi: The config option for the DRM module is DRM_UDL,, the equivalent legacy frame-buffer one is FB_UDL, both have no dependencies that aren't already met in the standard kernel build on the Pi. Note that these only work with the older USB 2.0 DisplayLink devices, the USB 3.0 ones use proprietary encryption on the USB link to satisfy HDCP requirements, and thus don't work with Linux (and are not likely to ever work with Linux). I have the same problem with an USB 3.0 monitor. According to rumors, an ARM PC with USB 3.0 (e.g. Odroid) should be able to run a USB 3.0 monitor. Best regards Michael |
| All times are GMT. The time now is 10:30 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.