guerrerolor / android-x86

Automatically exported from code.google.com/p/android-x86
2 stars 1 forks source link

android-x86 won't boot on my computer, with any iso. #614

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. attempting to boot.
2.
3.

What is the expected output? What do you see instead?
A boot menu. What i get is the ISOLinux screen, then nothing. I've waited for 2 
hours before.

What version of the product are you using? On what operating system?
i've tried android 2.2 and 2.3 for generic x86, 3.2 for eeepc, 3.2 for ASUS, 
4.0 for ASUS, and 2.2 for ASUS. I currently have openSUSE 64-bit, Slackware 
13.37, windows xp x64, and windows 7 ultimate installed and working.

Please provide any additional information below.
The computer uses a 64-bit dual-threaded, single-core pentium 4.  I have 
managed to get the android 2.2 for generic x86 working on a 64-bit Pentium D, 
which is, of course, dual core.

Original issue reported on code.google.com by Bioshack...@gmail.com on 3 Jan 2012 at 3:32

GoogleCodeExporter commented 9 years ago
Similar problem here, but may be different.

Running Ubuntu 11.xx on an Acer Aspire D533. With any of the Android isos on 
USB, I get as far as the BIOS POST screen then it hangs indefinitely telling me 
not to disassemble Intel's Pinewood BIOS.

Original comment by tinderbo...@gmail.com on 30 Jun 2012 at 6:20

GoogleCodeExporter commented 9 years ago
tomshaw -at-sbc-global-dot-net here. I downloaded Android -86 and burned it 
onto CD as directed and it hangs telling about worker threads and helper 
threads. Just so you know I'm pretty good at following directions and being 
observant, in case yo want to give advice. Oh well - a 70 cent Cd and some time 
is all I'm out...

Original comment by toms...@sbcglobal.net on 27 Jan 2013 at 9:50

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
It seems the kernel used by android-x86 lacks many modules necessary to make 
the IDE/SATA interfaces of certain desktop chipsets function... or even make 
them work on desktop chipsets...

I have an ASUS M2V motherboard (VIA K8T890/VT8237A) that I wanted to try it 
out, but it had the same problem when booting from a CD. When I put the image 
on a USB card, it works, but it never detects my CD drive and my hard disks... 
and that was why it was producing dots during boot. It could not access my CD 
drive.

I once talked about this problem before when the JB 4.1.2 test image came out, 
and that someone pointed out that pata_via and sata_via (which are necessary 
for VIA chipsets' IDE and SATA to work) were missing from the kernel. I tried 
the most recent JB 4.2 test image, no good. Even though they stated they used a 
3.8.0 kernel for more drivers support... I think they should state that what 
they are actually supporting are mostly mobile chipsets ... support for desktop 
chipsets seem to be still very limited.

The only solution would be to find a way to put those important kernel modules 
back into the kernel image so that it will work on the system...

EDIT: I cannot be sure but... kernel support is still a mess to me as I have 
never made it work on any computer I have using only the images provided 
here... I do have a laptop using AMD A8 proccessor... When installing from USB, 
it can detect my hard drives, but it would't boot even after I installed it... 
as the screen was flooded with something saying it could not find valid v7 on 
my hard drives...

Maybe for most users, to actually try it one needs to build it manually so as 
to make sure the necessary modules are in place... and whether those modules 
will properly work with android-x86 is still in question...

Original comment by Slytheri...@gmail.com on 8 Jun 2013 at 6:53