Testing Env: Host: Ubuntu 10.10 x86_64 Kernel: 2.6.35-25-generic beagleboard kernel and rootfs from weekly build 20110221 http://autobuilder.pokylinux.org/nightly/20110221-1/machines/beagleboard/arm/ u-boot environment setting: ########### setenv optargs 'omapdss.def_disp=dvi vram=12M omapfb.mode="dvi:800x480MR-16@60" video=omapfb.vram:0:4M,1:4M,2:4M omapfb.debug=y omapdss.debug=y' setenv console ttyO2,115200n8;mmcinit;fatload mmc 0 0x80800000 uImage.bin;run mmcargs; bootm 0x80800000 ########### When startup Xserver, I got the error message: ################### Starting Xserver fbset: can't open '/dev/fb0': No such file or directory fbset: can't open '/dev/fb0': No such file or directory fbset: can't open '/dev/fb0': No such file or directory Error opening framebuffer /dev/fb0: No such file or directory Fatal server error: no screens found xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Timeout waiting for org.matchbox_project.desktop.Loaded ################### There is no /dev/fb0 under /dev/ directory. When I create fb0 device manually, the issue still happen: ################### root@beagleboard:~# mknod /dev/fb0 c 29 0 root@beagleboard:~# /etc/rc5.d/S09xserver-nodm start Starting Xserver fbset: can't open '/dev/fb0': No such device fbset: can't open '/dev/fb0': No such device fbset: can't open '/dev/fb0': No such device Error opening framebuffer /dev/fb0: No such device Fatal server error: no screens found #################### More info: ################### root@beagleboard:~# uname -a Linux beagleboard 2.6.37.1-yocto-standard+ #1 PREEMPT Tue Feb 22 03:05:15 PST 2011 armv7l GNU/Linux ###################
I'm trying to recall if we used graphics on the beagle board for the 2.6.34 based demos. I don't think we did. Can someone help my memory by confirming whether this worked in 2.6.34 ? Just trying to properly classify this as a regression or not. As for 2.6.37 based framebuffer / X support, this is expected to not work (by me at least). We did a minimal 2.6.37 BSP, which didn't include graphics, and we'll add to it in the post 1.0 timeframe. There are merges that I've staged for this, but they are big enough that putting them in during the 1.0 stabilization wasn't feasible. But I'd like Darren to confirm the above, since he's had hands on the board more recently than I have.
I tested a 2.6.34 kernel from autobuilder weekly build 20110126: uImage-2.6.34+git0+b67e060194a38c6331da1532bd06446087a42b3b_0+0431115c9d720fee5bb105f6a7411efb4f851d26-r12-beagleboard-20110127143833.bin poky-image-sato-beagleboard-20110127162807.rootfs.tar.bz2 With this build, the /dev/fb0 can be created successfully. The X server can startup and the desktop display has no problem on a LCD monitor. ################# root@beagleboard:~# dmesg|grep fb -i omapfb: configured for panel omap3beagle omapfb: DISPC version 3.0 initialized omapfb: Framebuffer initialized. Total vram 1572864 planes 1 omapfb: Pixclock 48000 kHz hfreq 44.7 kHz vfreq 57.7 Hz ##################
Moving this to 1.1 where we'll have a completely new strategy for the beagleboard BSP.
darren. Want this one ?
I'm building with a linux-omap + patches from meta-ti and am currently whittling down the config. I am able to get the splash screen and the X desktop now. I had to delete the udev device cache (/etc/dev.tar*) before /dev/fb0 showed up. Manually creating the node (mknod /dev/fb0 char 29 0) also worked. Progress is being made.
With the following commits, this is resolved: commit ee4dd303b6667a691ed6093b13c226a7466ee31e Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Wed Jun 22 16:00:01 2011 -0400 linux-yocto/meta-yocto: update yocto/standard and beagleboard SRCREVs commit aaa4951d8b25591ebf7e98e02d8e7873d082d3e9 Author: Darren Hart <dvhart@linux.intel.com> Date: Mon Jun 20 14:13:21 2011 -0700 beagleboard: switch to xserver-xf86-lite
Verified it with 20110625 build on beagleboard C4 Tree/Branch: Poky/Master Poky Commit: a1f79a7896b6411669b3ccada6204d2695e80fc5