Hi,
We need to enable Graphic driver
support on BeagleBoard. We are using BeagleTouch kit (BeagleBoard
C4 with 4.1" resistive LCD touchscreen) from
Liquidware for our development.
We have compiled
QT-embedded
with SGX support but while running the application on the board we are getting
the below error.
Error:
/dev/fb0: could not find a suitable PVR2D pixel format
Could not initialize EGL display - are the drivers loaded?
/dev/fb0: could not find a suitable PVR2D pixel format
powervr: driver cannot connect
Aborted
Below is the list of all the steps / things
we have done to enable the graphic driver support.
1. Compiled QT-embedded, libgles-omap3 and omap3-sgx-modules using openembedded recipies.
2. And configured QT with :
-embedded arm -egl -plugin-gfx-transformed -plugin-gfx-qvfb -plugin-gfx-vnc \
-plugin-gfx-directfb -plugin-gfx-powervr -opengl es1 -openvg \
-plugin-mouse-tslib -qt-mouse-pc -qt-mouse-qvfb -qt-mouse-linuxinput
-qt-mouse-tslib -qt-kbd-tty -qt-kbd-linuxinput -openssl \
-DQT_KEYPAD_NAVIGATION -D QT_QWS_CLIENTBLIT -D QT_NO_QWS_CURSOR
Booted from minicom with following env.
OMAP3 beagleboard.org # setenv bootargs console=ttyS0,115200n8=noinitrd ip=dhcp rw root=/dev/mmcblk0p2 omapfb.mode=lcd:480x270MR-24@60
OMAP3 beagleboard.org # boot
After Booting lsmod shows:
Module Size Used by
pvrsrvkm 124693 2 bufferclass_ti,omaplfb
omaplfb 8942 0
bufferclass_ti 4768 0
Command Used:
root@beagleboard:~# qtdemo -qws -display powervr
Error:
/dev/fb0: could not find a suitable PVR2D pixel format
Could not initialize EGL display - are the drivers loaded?
/dev/fb0: could not find a suitable PVR2D pixel format
powervr: driver cannot connect
Aborted
Dmesg Output: root@beagleboard:~# dmesg | grep PVR
PVRSRV_PIXEL_FORMAT_ARGB8888
Also, Please find attached, strace log and dmesg log for the same.
We googled this error, and found this BeagleBoard's Google Groups link.
It says "use the sgx libs from the angstrom feeds, those fixup the pixelformat"
But as mentioned before, we are using open. embedded recipes only, which we suppose are same as Angstrom's.
Also , Step III at this
Google Code link, suggests, to erase the nand and reboot after running this
command :
# setenv mmcargs 'setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait omapfb.video_mode=1024x768MR-16@60'
# saveenv
After this also, the dmesg output and the error remains same as described above.
We have followed all the steps of this Nokia-QT Labs Blog.
Looking forward for some solution.
Thanks,
Varun Sodhi