HELP!! Android-x86 4.2 can't boot into gui,just command line

[Teten Kurniawan]

i just install Android-x86 4.2 successfull but when its boot,just go into

[Akram Berkawy]

same issue here on vmware

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[Maksim Lin]

Hi, I'm also seeing this with qemu-kvm.

I've attached a screenshot with the error messages.
Surfaceflinger is segfaulting - perhaps due to the error about missing .rc
file that happens just before that?

Post by Akram Berkawy
same issue here on vmware

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[Lowell Kim]

Are you booting from kvm command line? Try adding "-vga std" to it.

Post by Maksim Lin
Hi, I'm also seeing this with qemu-kvm.
I've attached a screenshot with the error messages.
Surfaceflinger is segfaulting - perhaps due to the error about missing .rc
file that happens just before that?

Post by Akram Berkawy
same issue here on vmware

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go
into command line..what can i do to get into gui interface?

[Maksim Lin]

Hi,
yes, i'm running kvm with a cmdlien like this:

kvm -soundhw es1370 -net nic -net user -cdrom
~/Downloads/android-x86-4.2-20121225.iso

but I'm afraid adding -vga std did not help.
Are you able to boot that 4.2 ISO all the way into the full andoird GUI
using kvm?

As I said in my previous email, the problem is that surfaceflinger is
segfaulting, but this is after the FB driver switches the display to a
higher res, so I'm not sure its to do with the gfx driver itself.

Maks.

Post by Lowell Kim
Are you booting from kvm command line? Try adding "-vga std" to it.

[Lowell Kim]

Hi Maks,

I just tried that ISO, and I get the same error. I AM able to boot other
ISOs though. I'm currently using a 4.0.4rc2 I built myself.

Lowell

Post by Maksim Lin
Hi,
kvm -soundhw es1370 -net nic -net user -cdrom
~/Downloads/android-x86-4.2-20121225.iso
but I'm afraid adding -vga std did not help.
Are you able to boot that 4.2 ISO all the way into the full andoird GUI
using kvm?
As I said in my previous email, the problem is that surfaceflinger is
segfaulting, but this is after the FB driver switches the display to a
higher res, so I'm not sure its to do with the gfx driver itself.
Maks.

Post by Lowell Kim
Are you booting from kvm command line? Try adding "-vga std" to it.

[Shuai Lin]

I also have the same problem.

Details:

HOST: Ubuntu Linux 12.04 64-bit
Virtual Box 4.2
Vmware Workstation 8.2

圚 2013幎1月8日星期二UTC+8䞋午2时04分05秒Teten Kurniawan写道

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[Yahya Makhrsh]

<Loading Image...>
me to i cannot running it

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[Dimitrios Misdanitis]

Confirmed on Sony Vaio E Series netbook with AMD E2-1800 APU and AMD Radeon
HD 7340. Boots up very fast, but drops me into root shell. If I use the
kernel boot option "xforcevesa" gui is displayed for a split second and
then i'm dropped back to the shell. Is there a command to manually start
the X server, like "startx" is on linux.

Post by Yahya Makhrsh
<https://lh5.googleusercontent.com/-9GWpBX7Hhog/UPaQCoDMakI/AAAAAAAAAaw/TBlYDTlxic8/s1600/saUH.jpg>
me to i cannot running it

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[王波涛]

[N.H.G]

same issue on my device.

[Uoc Nguyen]

Same here with Virtual box, I ran into debug mode and see some error
related to tty, look like init process can not create tty device.

[Uoc Nguyen]

Forgot to tell you that console show some error about some system process
got segfault and died already, the message re-appear each 10 seconds. IMO,
it is caused by some process cannot start and boot process gets looped
infinitively.

Post by Uoc Nguyen
Same here with Virtual box, I ran into debug mode and see some error
related to tty, look like init process can not create tty device.

[Pablo Beltran Alvarez Sierra]

init: could not import file '/init.android_x86.rc' from '/init.rc'

In fact that file doesn't exist, instead there is an 'init.x86.rc' one.
Could this be the cause of the problems?

[eugene pofig]

I had something like that. I didn't install android to my HDD. I've been
trying to run it in Live mode and couldn't get GUI work. Finally I've
changed GRUB boot parameters like this:

........... initrd=/initrd.img root=/dev/ram0
androidboot.hardware=android_x86 video=-16* nomodeset vga=(any unreal mode
such as 987877 or 5785 etc)* ..........

GRUB offered me to change the vga mode - to choose one from table. I've
selected 1024x768 16bit mode (32 bit gave me something unusable). It works
for me. My GUI started. But where is Google Play & how to manage my Google
accounts ?? Without these features android is useless....(sorry for my
english)

[eugene pofig]

Post by eugene pofig
I had something like that. I didn't install android to my HDD. I've been
trying to run it in Live mode and couldn't get GUI work. Finally I've
........... initrd=/initrd.img root=/dev/ram0
androidboot.hardware=android_x86 video=-16* nomodeset vga=(any unreal
mode such as 987877 or 5785 etc)* ..........
GRUB offered me to change the vga mode - to choose one from table. I've
selected 1024x768 16bit mode (32 bit gave me something unusable). It works
for me. My GUI started. But where is Google Play & how to manage my Google
accounts ?? Without these features android is useless....(sorry for my
english)
Sorry, I forgot to note - I'm using build from tabletsx86.org . My
hardware config: core i5 750, 4Gb RAM, Radeon HD 7870....It's seems to me
that Android lack to recognize my PATA DVD-Rom connected to JMicron
controller...

[a***@public.gmane.org]

Got it working in VirtualBox after selecting the VESA mode from the menu,
then change the parameter "androidboot.hardware=x86".

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[Fei Sun]

Thank you,this works for me.

Post by a***@public.gmane.org
Got it working in VirtualBox after selecting the VESA mode from the menu,
then change the parameter "androidboot.hardware=x86".

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?

[ix]

[J da Costa]

Hi guys,

Tried every tip in here none worked :( ... any ideas? Running on VMware
Workstation 9.0.2 64 bit.

thks

[Baloo Bear]

I've installed android-x86-4.2-20121225.iso on Virtual Box
(VirtualBox-4.2.10-84105-Win) and failed to run ((
Attempting to run it I have (attached png-file)
((

[Blake W. Ford]

Is there a solution to this problem for the eeepc 701?

Post by Teten Kurniawan
i just install Android-x86 4.2 successfull but when its boot,just go into
command line..what can i do to get into gui interface?