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

[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?


On Tuesday, 8 January 2013 21:26:00 UTC+11, Akram Berkawy wrote:

same issue here on vmware

On Tuesday, January 8, 2013 8:04:05 AM UTC+2, Teten Kurniawan wrote:

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.

[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.

[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

[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.

[eugene pofig]

среда, 23 января 2013 г., 11:50:33 UTC+2 пользователь 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)

 

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...

[George Brooke]

Me too. Using VMware Player 9 and the dev build of 4.2. Tried changing the ISO boot androidboot.hardware parameter to x86. Now i hang at this screen.

[twocra...@gmail.com]

Baloo ; I have the exact same issue and its driving me nuts. Did you ever get a solution?

On Thursday, March 21, 2013 2:36:03 AM UTC-7, baloo Bear wrote:

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)
((

[Alvaro Marquez]

I have the same problem. I am installing the android 4.0 and 4.2 with a usb drive created with unetbootin-windows-581. When I install it on my desktop pc, vesa mode loads fine. But installing a AnyPlace IBM Kiosk 4838, does not load the GUI, and is in the command line. I tried the options out there in the group, but I can not make it work in the Kiosk.

[JD and R R kewl]

I dont think there is a solution to this problem. I see lots of similar stories but no viable solutions.

--
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/kW8YE6_eXXU/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.
 
 

[Mohit Kesarwani]

[dscm]

desktop pc is what???? celeron/core2/i3/i5/i7....???????? graphics is what?????

AnyPlace IBM Kiosk 4838 is what???? Graphics is what?????

Versions:
4838-5xx/7xx/9xx

each version of Kiosk has different spec's....different cpu/mem/graphics/etc.

so you are most likely mixing apples and oranges and expecting it to work..................

isn't going to happen....

[Greg McGee]

On Friday, January 25, 2013 6:30:58 PM UTC-6, alexan...@gmail.com wrote:

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

Changed  it to what?

[skipper]

 

 

 

hi I was trying to use android and I ended up with nothing ...all I have is ANDROID

[skipper]

unable to boot to the android gui ...all I see is android on my virual box screen ...I,m using 4.2 ....please help ...I have attached the screenshots as well.

[Greg McGee]

Did you overwrite your windows partition?

If it's only a grub issue, it's simply a matter of writing a default bootblock to your drive, first 446 bytes. From ~any Linux livecd (not Android) lilo -M /dev/sd(whatever your drive is)  will put a default bootblock in.

You can also try to fix it from a windows installer disc but I have had mixed results doing that, there's more to go wrong.