Androidx86 4.2 on O² Joggler - GMA500 support issue?

[Andy S]

Got an Intel Atom based O² Joggler (touch screen tablet style device) which has the infamous Intel 'Poulsbo' GMA500 chipset (as well as the tricky Efi bootloader!)

So far I have used VBox to install to USB drive (micro SD card in reader) on an FAT32 (also tried Ext3) plus 2 spare partitions for Data and SDcard.

I get it booting ok by using a grub.efi and tweaking the grub.cfg file (after renaming installed 'androidx86-4.2' folder to just 'android')

set timeout=0

menuentry "Androidx86 4.2" {
    linux /android/kernel acpi_sleep=s3_bios,s3_mode video=-16 rootdelay=1 SRC=android root=/dev/ram0 DATA=/dev/sda2 SDCARD=/dev/block/sda3 DPI=120 ETH_MAC=00:11:22:33:44:55
    initrd /android/initrd.img
}

All goes well until bootanim kicks in which results in bootloop (see image below)

Dropping to a terminal (stop zygote) I captured a logcat (also attached) which shows:

D/libEGL  ( 1361): 3D hardware acceleration is disabled
D/libEGL  ( 1361): Emulator without GPU support detected. Fallback to software renderer.
D/libEGL  ( 1361): loaded /system/lib/egl/libGLES_android.so
W/gralloc ( 1361): page flipping not supported (yres_virtual=480, requested=960)
I/gralloc ( 1361): using (fd=33)
I/gralloc ( 1361): id           = EFI VGA
I/gralloc ( 1361): xres         = 800 px
I/gralloc ( 1361): yres         = 480 px
I/gralloc ( 1361): xres_virtual = 800 px
I/gralloc ( 1361): yres_virtual = 480 px
I/gralloc ( 1361): bpp          = 32
I/gralloc ( 1361): r            = 16:8
I/gralloc ( 1361): g            =  8:8
I/gralloc ( 1361): b            =  0:8
I/gralloc ( 1361): width        = 127 mm (160.000000 dpi)
I/gralloc ( 1361): height       = 76 mm (160.421051 dpi)
I/gralloc ( 1361): refresh rate = 82.76 Hz
D/        ( 1361): Intel hwcomposer module
E/SurfaceFlinger( 1361): composer device version 0 unsupported, will not be used
W/SurfaceFlinger( 1361): getting VSYNC period from fb HAL: 12083131
W/SurfaceFlinger( 1361): no suitable EGLConfig fou:nd, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
W/SurfaceFlinger( 1361): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
W/SurfaceFlinger( 1361): no suitable EGLConfig found, trying with 16-bit color allowed
E/SurfaceFlinger( 1361): no suitable EGLConfig found, giving up

So I am wondering whether the graphics mode is 'hard coded' into the Efi Grub I'm using?

I have tried all manner of grub.cfg tweaks such as VGA=xxx, VIDEO=-16 VIDEO=800x480:16, VGA=ask etc. to no avail

Poulsbo module is loaded once booted so it looks as though it must be a video config issue, but maybe something else is wrong?

Is there a custom way to install to better suit Efi? Or any config that can be tweaked before install?

Any pointers/ideas/help appreciated!

[Andy S]

Had another go with the latest 4.3 with the same result. Looks like no support for GMA500 in Androidx86 still then, even though other Linux systems report success with newer kernels and the infamous Poulsbo chipset:

https://groups.google.com/forum/#!topic/linux.gentoo.user/_shI7bM2iSc

[Greg McGee]

I assume you have also tried nokms (or whatever the current magic invocation is) to prevent the kernel from even trying to do kernel mode switching.

This would possibly allow the higher level graphics subsystem (mesa in this case IIRC) to Do The Right Thing.

[Acesabe]

If you are talking about nomodeset, then yes, doesn't appear that any of the Grub boot line edits make much difference either way.

I have found conf in /init.x86.rc/ that looks like it might enable libEGL so gonna try un-hashing that..

> --
> You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/iKb2YvenNi0/unsubscribe.
>
> To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
> To post to this group, send email to andro...@googlegroups.com.
> Visit this group at http://groups.google.com/group/android-x86.
>
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

[Chih-Wei Huang]

2013/8/9 Andy S <an...@bristolwireless.net>

> Had another go with the latest 4.3 with the same result. Looks like no support for GMA500 in Androidx86 still then, even though other Linux systems report success with newer kernels and the infamous Poulsbo chipset:
>
> https://groups.google.com/forum/#!topic/linux.gentoo.user/_shI7bM2iSc

Android graphic system differs entirely from traditional
Linux X window system. The comparison is nonsense.

The 4.3 test build boots well on my EeePC T91
which also uses GMA500.
(in uvesa mode, no hw acceleration, of course)

[Acesabe]

On 21 August 2013 16:59, Chih-Wei Huang <cwh...@android-x86.org> wrote:

Android graphic system differs entirely from traditional
Linux X window system. The comparison is nonsense.

The 4.3 test build boots well on my EeePC T91
which also uses GMA500.
(in uvesa mode, no hw acceleration, of course)

Thanks for the reply, I will have a go trying some UVESA_OPTION= configs as suggested here:

http://www.android-x86.org/documents/uvesafbhowto

to try and get this device fully booted!

Can't say I'm hopeful that there will ever be decent graphics performance for the GMA500 though running Android, so this may be a somewhat futile project for me...