Android-X86 R4.4 on old Xplore iX104 C2

[Egidio MELISSANO]

Hello folks,

I'm a beginner on the Android-X86, but not on the Linux. So, I need your help for sure (pleeeease!!!)

That said, the device where I'm trying to install Android-X86 is an old Xplore iX104 C2 and you can find the device specifications at this link:

http://streckkod.se/images/produktdokument/Xplore%20iX104C2.pdf

Briefly, it is a rugged tablet with following hw:

- CPU: Intel Pentium M 733;
- CHipSET: Intel 855GME - 400 MHz;
- Processor Speed: 1.1 GHz;
- RAM: 256MB DDR;
- HD: 40GB IDE HDD (2.5” shock mounted);
- Display: 10.4” XGA TFT (1024x768), 16M colors,
32-bit true color,
Active digital sensor,
Optional active digital sensor and
pen & resistive touch digitizer (Dual Mode),
Optional AllVue™ LCD technology for enhanced indoor/outdoor display;
- GPU: Intel Extreme Graphics 2.

This tablet was shipped with Win$ XP, and I've already tried installing ArcLinux with success. I did it installing with a Grub2 boot-manager, combined to a GPT (although this device has a legacy-bios, but it is a supported option).

Everything works with ArcLinux, the X server correctly starts and the Wacom drivers enable both the pen and buttons to work fine.

Now, I'd like to make a dual-boot system with both Archlinux and Android-X86, then this is the table of my partioned-disk:


[root@anctab ~]# blkid
/dev/sda1: UUID="4a6c156e-4757-4090-b1c8-a79b7b3bb142"
TYPE="ext4"
PARTLABEL="ArchLxRoot"
PARTUUID="f18ab9f5-e2ca-402d-b73a-f4772afeed19"

/dev/sda2: UUID="8dd9fe95-6b9e-48b9-9f9b-19a87eb1e0bc"
TYPE="ext4"
PARTLABEL="ArchLxHome"
PARTUUID="baa0a00a-51fe-4972-89ce-351d83e3f62d"

/dev/sda3: UUID="9fa248a7-3c07-42ec-aa1a-d56c3483146d"
TYPE="swap"
PARTLABEL="ArchLxSwap"
PARTUUID="7c46e579-7465-4693-b33d-85ce65c90295"

/dev/sda5: UUID="7646e113-2ea3-494c-b8e3-2bf44f888d67"
TYPE="ext2"
PARTLABEL="AndroidX86"
PARTUUID="a13fdf21-d237-4045-b711-b8468238e034"

/dev/sda4: PARTLABEL="ArchLxBoot"
PARTUUID="411e992a-dcc6-4234-8244-261bf06a839f"


where I installed the latest version of Android-X86 on /dev/sda5 partion (ext2). And this is my entry for Android on Grub2:

[root@anctab ~]# cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.

android_dir="android-4.4-r3"

menuentry "Android" {

# assuming that UUID is 763A-9CB6
#search --set=root --fs-uuid 763A-9CB6

#set root='(hd0,4)'
DEBUG=1
# search by label OTHER_LINUX (make sure that partition label is unambiguous)
search --no-floppy --set=root --fs-uuid 7646e113-2ea3-494c-b8e3-2bf44f888d67
linux /$android_dir/kernel
#root=/dev/ram0
#UUID=7646e113-2ea3-494c-b8e3-2bf44f888d67
# quiet
androidboot.hardware=generic_x86
#generic_x86
SRC=/$android_dir
video=i915:modeset=1
i915.i915_enable_rc6=1
i915.lvds_downclock=1
i915.i915_enable_fbc=1
pcie_aspm=force
#acpi_sleep=s3_bios,s3_mode
# acpi=off
# video=LVDS-1:d
# video=1024x768
# i915.modeset=0
initrd /$android_dir/initrd.img

}

So, here is the ISSUE: when a select Android at boot, OS starts bur it ends to a text consol - graphic UI doesn't start. Where is my mistake?

This the recursive error displayed by logcat...

I/SurfaceFlinger( 1765): SurfaceFlinger is starting
I/SurfaceFlinger( 1765): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 1765): loaded /system/lib/egl/libGLES_mesa.so
W/GRALLOC-PIPE( 1765): failed to create pipe screen for i915
I/GRALLOC-DRM( 1765): create intel for driver i915
W/EGL-GALLIUM( 1765): failed to create DRM screen
W/EGL-GALLIUM( 1765): will fall back to other EGL drivers if any
D/GRALLOC-KMS( 1765): supported drm planes and formats
I/GRALLOC-KMS( 1765): there is one mode on connector 0x23: 1024x768
I/GRALLOC-KMS( 1765): Established mode:
I/GRALLOC-KMS( 1765): clock: 65000, hdisplay: 1024, hsync_start: 1048, hsync_end: 1184, htotal: 1344, hskew: 0
I/GRALLOC-KMS( 1765): vdisplay: 768, vsync_start: 771, vsync_end: 777, vtotal: 806, vscan: 0, vrefresh: 60
I/GRALLOC-KMS( 1765): flags: 10, type: 8, name 1024x768
I/GRALLOC-KMS( 1765): the best mode is 1024x768
D/GRALLOC-KMS( 1765): will use copy for fb posting
I/GRALLOC-MOD( 1765): mode.hdisplay 1024
I/GRALLOC-MOD( 1765): mode.vdisplay 768
I/GRALLOC-MOD( 1765): mode.vrefresh 60.000000
I/GRALLOC-MOD( 1765): format 0x5
I/GRALLOC-MOD( 1765): xdpi 75.000000
I/GRALLOC-MOD( 1765): ydpi 75.000000
I/GRALLOC-MOD( 1765): mode.hdisplay 1024
I/GRALLOC-MOD( 1765): mode.vdisplay 768
I/GRALLOC-MOD( 1765): mode.vrefresh 60.000000
I/GRALLOC-MOD( 1765): format 0x5
I/GRALLOC-MOD( 1765): xdpi 75.000000
I/GRALLOC-MOD( 1765): ydpi 75.000000
F/libc ( 1765): Fatal signal 4 (SIGILL) at 0x417e9976 (code=2), thread 1765 (surfaceflinger)

Help me, please!!!!

[Mauro Rossi]

Hi,

SIGILL means ilegal opcode i.e. your CPU is not supported, 

please check the threads about SSE3 builds

Mauro

[Egidio MELISSANO]

I've found something which seems an explanation about unsupported processors (older than those support SS3 command set) here:

https://sites.google.com/site/twisteroidambassador/android-x86/kitkat-non-sse3-build

Can it be my answer?

Regards.

[Mauro Rossi]

I've found something which seems an explanation about unsupported processors (older than those support SS3 command set) here:

https://sites.google.com/site/twisteroidambassador/android-x86/kitkat-non-sse3-build

Can it be my answer?

Regards.

Sorry I meant non-SSE3 builds, you can try the ISO image avallable at the link, but not all apps will work.

M.

[Egidio MELISSANO]

So, I decided to install the previous version: Ice Cream, 4.0.

And I chose the iso for eeepc, because I read that it is the best choise when its own model doens't match with any.

But, now, I'm facing another issue: a trouble with my GPU... (maybe). In fact, my boot ends with a black-screen, and this is what says logcat about:

10-04 20:34:51.067  1472  1472 I sysproc : ServiceManager: 0x81c49b0
10-04 20:34:51.077  1472  1472 I SurfaceFlinger: SurfaceFlinger is starting
10-04 20:34:51.077  1472  1485 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: there is one mode on connector 0x5: 1024x768
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: Established mode:
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: clock: 65000, hdisplay: 1024, hsync_start: 1048, hsync_end: 1184, htotal: 1344, hskew: 0
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: vdisplay: 768, vsync_start: 771, vsync_end: 777, vtotal: 806, vscan: 0, vrefresh: 60
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: flags: 10, type: 8, name 1024x768
10-04 20:34:51.117  1472  1485 I GRALLOC-KMS: the best mode is 1024x768
10-04 20:34:51.117  1472  1485 D GRALLOC-KMS: will use copy for fb posting
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: mode.hdisplay 1024
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: mode.vdisplay 768
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: mode.vrefresh 60.000000
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: format 0x5
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: xdpi 75.000000
10-04 20:34:51.117  1472  1485 I GRALLOC-MOD: ydpi 75.000000
10-04 20:34:51.147  1472  1485 D libEGL  : loaded /system/lib/egl/libGLES_android.so
10-04 20:34:51.447  1472  1485 D libEGL  : loaded /system/lib/egl/libGLES_mesa.so
10-04 20:34:51.487  1472  1485 W EGL-GALLIUM: failed to create a pipe screen for i915
10-04 20:34:51.487  1472  1485 W EGL-GALLIUM: failed to create DRM screen
10-04 20:34:51.487  1472  1485 W EGL-GALLIUM: will fall back to other EGL drivers if any
10-04 20:34:51.597  1472  1485 E SurfaceFlinger: couldn't find an EGLConfig matching the screen format
10-04 20:34:51.627  1472  1485 E libEGL  : eglMakeCurrent:616 error 3009 (EGL_BAD_MATCH)
10-04 20:34:51.627  1472  1485 E SurfaceFlinger: Couldn't create a working GLES context. check logs. exiting...
10-04 20:34:51.657  1425  1425 I Zygote  : Exit zygote because system server (1472) has terminatedEnter code here...

Can someone help me, please??

Regards.

[Chih-Wei Huang]

You have an error in the grub2.cfg:

androidboot.hardware=generic_x86
^^^^^^^^^^^^^ wrong name

It's must be the target name, i.e.,
android_x86 for kitkat-x86.
If you tried the android-x86 4.0 eeepc version,
it should be eeepc.

> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To unsubscribe from this group and stop receiving emails from it, 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/d/optout.



--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Egidio MELISSANO]

Yes,you are right, bc I didn't advise you that I've already changed this setting - here you have my grub-kernel line:

linux /$android_dir/kernel androidboot.hardware=eeepc  SRC=/$android_dir  DEBUG=2
initrd /$android_dir/initrd.img  

BTW, I also attach you my dmesg log, my init.log and logca output.

Help me, please!!

Regards.