DisplayLink Forum - View Single Post - USB3 Display Driver, Raspberry Pi2, and Expectations

Cotonou · 08-06-2015, 02:43 AM

Hey there.

I've been waiting for the DisplayLink USB3 display driver for a bit now, and am very happy the beta version has been released!

I have an Raspberry Pi 2 I've been saving to pair with my AOC 1659 monitor and I've given it a go. The rPi2 is running Ubuntu 14.04, and of course is equipped with an ARM processor.

Unfortunately I'm not running into a huge amount of success in getting the driver to work. I've provided the install package with all the dependencies it complained about. It successfully completes and attempts to start the display service, but the syslog tells me that it immediately crashes out.

In the syslog, I find small stack of errors all looking more or less like this:

evdi: Unknown symbol drm_framebuffer_cleanup (err 0)
evdi: Unknown symbol drm_kms_helper_poll_fini (err 0)
evdi: Unknown symbol drm_open (err 0)
evdi: Unknown symbol drm_mode_vrefresh (err 0)
evdi: Unknown symbol drm_fb_helper_single_add_all_connectors (err 0)
evdi: Unknown symbol drm_fb_helper_init (err 0)

Which obviously points to something having to do with the DRM module, but unfortunately this is where my investigations run into a wall. I have noticed a few lines in the release notes that imply the driver only works on x86 processors at the moment, which would be sad if true. My question is if it is even possible to get the beta displaylink drivers working on a Raspberry Pi2, and if so perhaps some advice on what my next move should be.

Thanks for your time.

08-06-2015, 02:43 AM	#1
Cotonou Junior Member Join Date: Aug 2015 Posts: 1	USB3 Display Driver, Raspberry Pi2, and Expectations Hey there. I've been waiting for the DisplayLink USB3 display driver for a bit now, and am very happy the beta version has been released! I have an Raspberry Pi 2 I've been saving to pair with my AOC 1659 monitor and I've given it a go. The rPi2 is running Ubuntu 14.04, and of course is equipped with an ARM processor. Unfortunately I'm not running into a huge amount of success in getting the driver to work. I've provided the install package with all the dependencies it complained about. It successfully completes and attempts to start the display service, but the syslog tells me that it immediately crashes out. In the syslog, I find small stack of errors all looking more or less like this: evdi: Unknown symbol drm_framebuffer_cleanup (err 0) evdi: Unknown symbol drm_kms_helper_poll_fini (err 0) evdi: Unknown symbol drm_open (err 0) evdi: Unknown symbol drm_mode_vrefresh (err 0) evdi: Unknown symbol drm_fb_helper_single_add_all_connectors (err 0) evdi: Unknown symbol drm_fb_helper_init (err 0) Which obviously points to something having to do with the DRM module, but unfortunately this is where my investigations run into a wall. I have noticed a few lines in the release notes that imply the driver only works on x86 processors at the moment, which would be sad if true. My question is if it is even possible to get the beta displaylink drivers working on a Raspberry Pi2, and if so perhaps some advice on what my next move should be. Thanks for your time.