Raspberry PI and AOC e1649Fwu USB powered LED monitor
I have AOC’s 15.6 inch USB LED monitor and want to use it as a monitor for Raspberry PI.
- It wasn’t easy for me. So, I wrote down here.
- For now, AOC’s e1649Fwu monitor does not work in console mode, so you should connect AOC monitor just before run ‘startx’. I have no idea why it does not work in console mode.
- Additionally, Ubuntu is required for cross compile & build new kernel for Raspberry PI.
First prepare SD card for Raspberry PI using Raspbian “wheezy” image. (http://www.raspberrypi.org/downloads)
[After boot, raspi-config]
- Enable ssh for control Raspberry PI without HDMI monitor.
- boot_behaviour : Don’t start desktop on boot.
[Build Raspberry kernel image including udlfb driver on Ubuntu Linux]
- Follow instructions in http://mitchtech.net/raspberry-pi-kernel-compile/
- select “Device Drivers -> Graphics Support -> Support for Frame buffer devices” as “*”. -> Press ‘Y’.
[Download DisplayLink X server and build]
- sudo apt-get install pkg-config xorg-dev
- git clone http://git.plugable.com/webdav/xf-video-udlfb/
- cd xf-video-udlfb
- ./configure
- make
- sudo make install
- Reference - http://plugable.com/2009/11/16/setting-up-usb-multiseat-with-displaylink-on-linux-gdm-up-to-2-20/
[Make 10-monitor.conf file and copy it to /usr/share/X11/xorg.conf.d/]
#################################################
Section “ServerLayout”
- [added Dec 5, 2012] You can download “10-monitor.conf” file or gzipped file of it from https://github.com/imkiyoung/raspberryPI.
- Reference - http://karuppuswamy.com/wordpress/2012/08/17/lilliput-displaylink-usb-monitor-um-70-17e902a9-with-raspberry-pi-on-raspbian/
[Connect AOC's USB monitor to Raspberry]
- USB monitor has Y-type USB connectors. One is for data & power, another is for additional power.
- For my experience, connect data & power USB connector to Raspberry PI, and connect additional power USB connector to PC/Notebook. External powered USB Hub(Belkin) does not work for me.
[Check connection status]
pi@raspberrypi ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 17e9:4107 DisplayLink
pi@raspberrypi ~ $ dmesg | grep udlfb
usbcore: registered new interface driver udlfb
udlfb: DisplayLink e1649Fwu – serial #CZSC4HA018627
udlfb: vid_17e9&pid_4107&rev_0112 driver’s dlfb_data struct at cba21000
udlfb: console enable=1
udlfb: fb_defio enable=1
udlfb: shadow enable=1
udlfb: vendor descriptor length:17 data:17 5f 01 0015 05 00 01 03 00 04
udlfb: DL chip limited to 1500000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 1366×768 valid mode
udlfb: DisplayLink USB device /dev/fb1 attached. 1366×768 resolution. Using 4104K framebuffer memory
[Run X11 using 'startx' on console]
- During launch X11, screen will be abnormal state. But, after a long wait, everything will be ok.
Thank you for reading.
Raspberry PI USB
- BELKIN USB hub (external powered)
- USB keyboard
Belkin USB hub
- ASUS WL-330g power
- AOC’s monitor’s main USB connector
- Mouse (not appeared in this picture)
Notebook PC
- Raspberry PI’s main power
- AOC’s monitor’s sub USB connector(I think power from Belkin was unstable.)
Reblogged this on Gigable – Tech Blog.
Hi, Thanks for posting this. I’ve been googling my head of to find a solution. I’m going to try it asap. Just one question, are all these instructions still relevant with the new 2012-09-18-wheezy-raspbian.zip image?
While building kernel image for udlfb driver, the command “git clone https://github.com/raspberrypi/linux.git” downloads v3.2.27 linux kernel. And we should replace the kernel of 2012-09-18-wheezy-raspbian. So, I believe there will be no problem regardless of latest version of raspbian image. (added) It is same version with 2012-09-18-wheezy-raspbian.
Frankly speaking, this guide is not perfect. I have tried to fix some problems(only on first time, mouse works well with X11. but now, it does not work.) but in vain.
(added) After more tests, using HD monitor, I found that mouse and keyboard problem in X11 is nothing to do with udlfb. Something went wrong.
Just before, using 2012-09-18-wheezy-raspbian image, Raspberry PI works well with AOC’s monitor. Of course, not console but X11.
My keyboard and mouse works without problem.
Step1) make SD card using 2012-09-18-wheezy-raspbian.img
Step2) boot with SD card, and change boot_behaviour for console boot.
Step3) insert SD card to PC, and copy kernel.img and lib directories made by above step([Build Raspberry kernel image including udlfb driver on Ubuntu Linux]) to root folder of SD card.
Step4) Connect AOC’s monitor using external powered USB hub. and check the connection status of monitor using lsusb, dmesg command.
Step5) In Rasberry PI console, follow above step([Download DisplayLink X server and build])
Step6) make 10-monitor.inf and copy to /usr/share/X11/xorg.conf.d/
Step7) startx &
That’s it.
* Not fixed problems, maybe because of my lack of knowledge.
- Console mode boot with AOC’s monitor. -> I heard this monitor has fixed resolution 1366×768. Changing the resolution values of Config.txt didn’t work.
What do you think about creating bash script on github to do all this instructions ?
I think about buying this monitor for my raspberry pi .
I copied and pasted your config file (i.e. the quotes are not the same) which created errors. People should retype all the commands above instead of copy and paste.
Sorry for inconvenience.
Download links of 10-monitor.conf which I am using are below. The contents of two files are same.
http://pds23.egloos.com/pds/201212/05/77/10-monitor.conf.gz
http://pds25.egloos.com/pds/201212/05/77/10-monitor.conf
DID I NEED TO USE OTHER MONITOR TO MAKE THIS ON RASPBERRY?
In that case, I think you may need a monitor(with HDMI connector).