I already can use ADBHOST to debug it now.
My graphic driver is Intel GMA500.
I get log is below.
..
..
I/EGLDisplaySurface( 1695): using (fd=20)
I/EGLDisplaySurface( 1695): id = psbfb
I/EGLDisplaySurface( 1695): xres = 800 px
I/EGLDisplaySurface( 1695): yres = 48
That may have some relationship with the incorrect video mode.
Are you using android on eeepc? Can you use network? If yes, you can
use adb to connect to it by poiting the ADBHOST to the ip that your
target machine has.
--
Chen
2009/5/5 Cloud :
>
> Thanks for your suggestion,
>
> I remove vesafb
Thanks for your suggestion,
I remove vesafb and intelfb from kernel, then use "init.rc" to insert
video driver modules,
but I can not get any screen (black display).
So I can not use dmesg or logcat to see error message.
What problem with it ? insmod failure?
Thanks.
On 5月5日, 上午12時24分, Yi Sun w
my 2 cents, but i am not so sure whether it works or not.
You may be able to achieve it by removing the vga=788 in cmdline to
disable the vesafb and let android directly use the only fb device.
--
Chen
On May 4, 10:56 pm, Cloud wrote:
> Hi everyone,
> I can use vesafb for intel video chipset on
grep in the surface flinger directories for /dev/fb0
or /dev/graphics/fb0 and try to change them to fb1.
But, one question... why don't you just remove the vesafb or intelfb
from the kernel? And your driver will use fb0 by default.
On Mon, 2009-05-04 at 07:56 -0700, Cloud wrote:
> Hi everyone,
>
