What kind of x86 PC are you using? The current building steps posted on the web site is only verified for VirtualBOX. Also, you need to use all the patches otherwise, you will hit on the per-load unsupport class issue, battery file path issue and the crash caused by wrong init.rc. Please also send the logcat output if you can. Thanks Yi On Fri, 2009-04-10 at 03:12 -0700, Skuld wrote: > Dear Yi: > > Thank you for your e2fsprogs.patch. > It's work and produce installer_img. > I install it on x86 PC and boot it, but it can't boot android system > (show android logo). > I use console mode and check all process. > I discover zygote service don't run. > > How to fix it? > My kernel can work on android in 2009/03/24 > > > > On 4月10日, 下午2時18分, Yi Sun <beyo...@gmail.com> wrote: > > FYI-- The powermanagement service is still not working correctly on > > VirtualBox. In certain cases, it tells me that the screen is off. > > Yi > > > > On Thu, 2009-04-09 at 22:51 -0700, Yi Sun wrote: > > > Ok, I have done with all the patches I have collected from this list for > > > building x86. I tested them with a fresh check out of cupcake on a > > > Virtualbox and it is ok. I will start to work on rebuild the drivers and > > > kernel for the real EeePC device over the weekend and hope I could get > > > it done before next Monday. After that I will post the binaries and try > > > to check in the code. > > > > > I have posted the patch set in > > >http://code.google.com/p/patch-hosting-for-android-x86-support/ > > > I also posted a wiki page for how to build a boot-able image with latest > > > cupcake tree. It is base on the instructions posted by Lim and Chen Yang > > > in the list. Please let me know if I missed anything and made anything > > > wrong. > > > > > I hope that we can have a central place to capture all the known issues > > > and solutions/patches so that people can feel easier on their life. The > > > mailing list should be used to discuss the new issues not to repeat the > > > same problem again and again. > > > Because I can only do this in my private time. So bare with me, if I > > > missed something or slow.If you want to join this project, please let me > > > know, I can always add you to member list. > > > > > Credit: > > > * Dima Zavin<d...@android.com>, the original guy ported the Android to > > > EeePC 701 > > > * Lim <lee...@gmail.com>, Wrote original "HOWTO Build Android-X86 Full > > > Source" and "How to use x86 android platform on virtualbox " > > > * Chen Yang<sunsety...@gmail.com> for the instructions on how to make > > > boot-able image and how to build Android for VMware/VirtualBox, and > > > investigations on almost all of the build breaks and run time > > > issues > > > * Jackie Wu<jackie...@intel.com> for the fix in alarm.c > > > * Androidphan<niels.kee...@tass.nl> for the investigation on the path > > > issue in the battery service jni code > > > * Luca Belluccini<lucabellucc...@gmail.com> for the first patch to fix > > > the path issue in the battery service jni cod and other information > > > > > Please let me know if I missed someone or something. > > > Yi > > > On Thu, 2009-04-09 at 11:31 -0700, Luca Belluccini wrote: > > > > Need someone to help me to bring up wifi... > > > > I have a weird SIGIO... error... > > > > Contact me in some way. > > > > > > On 9 Apr, 20:10, Yi Sun <beyo...@gmail.com> wrote: > > > > > Yes, I saw that and I may have missed something you mentioned > > > > > (especially for the WIFI part). I will send out the first run of the > > > > > patch and then you can tell which part I have missed and I can add > > > > > them > > > > > in. > > > > > Yi > > > > > > > On Thu, 2009-04-09 at 10:29 -0700, Luca Belluccini wrote: > > > > > > I posted in "Instructions for last codebase" some other files to be > > > > > > patched/conditioned for building for eee_701 target. > > > > > > > > On 9 Apr, 19:01, Yi Sun <beyo...@gmail.com> wrote: > > > > > > > Guys, > > > > > > > I'm verifying my final patch for all the issues we are having on > > > > > > > x86 > > > > > > > recently. I will send it out as soon as I finished test. > > > > > > > Yi > > > > > > > > > On Thu, 2009-04-09 at 09:54 -0700, choo75 wrote: > > > > > > > > hi, > > > > > > > > > > Maybe you can also try following workaround I've read inanother > > > > > > > > thread > > > > > > > > (info from Chen) > > > > > > > > > > ...you can modify under > > > > > > > > external/e2fsprogs/Android.mk: > > > > > > > > --- a/Android.mk > > > > > > > > +++ b/Android.mk > > > > > > > > @@ -1,3 +1,3 @@ > > > > > > > > ifneq ($(TARGET_SIMULATOR),true) > > > > > > > > -# include $(call all-subdir-makefiles) > > > > > > > > + include $(call all-subdir-makefiles) > > > > > > > > endif > > > > > > > > > > just add the include....i was successful in building afterwars. > > > > > > > > > > regards, > > > > > > > > choo > > > > > > > > > > On Apr 9, 12:50 pm, Skuld <skul...@gmail.com> wrote: > > > > > > > > > Hi : > > > > > > > > > > > I download new source code on 2009.04.07 and I add three > > > > > > > > > project (alsa- > > > > > > > > > lib,alsa_sound,eeepc) in local_manifest.xml. > > > > > > > > > Than I execute $TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 > > > > > > > > > DISABLE_DEXPREOPT=true make installer_img. > > > > > > > > > > > But it happen following error message.How can I fix this? > > > > > > > > > > > ===================Error========================================= > > > > > > > > > > > Copy: > > > > > > > > > out/target/product/eee_701/installer/root/system/xbin/strace > > > > > > > > > Copy: > > > > > > > > > out/target/product/eee_701/installer/root/system/bin/netcfg > > > > > > > > > Copying installer base files... > > > > > > > > > Copy: out/target/product/eee_701/obj/lib/libdiskconfig.so -> > > > > > > > > > out/ > > > > > > > > > target/product/eee_701/installer/root/system/lib/libdiskconfig.so > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > Copy: -> > > > > > > > > > dirname: missing operand > > > > > > > > > Try `dirname --help' for more information. > > > > > > > > > mkdir: missing operand > > > > > > > > > Try `mkdir --help' for more information. > > > > > > > > > cp: missing file operand > > > > > > > > > Try `cp --help' for more information. > > > > > > > > > make: *** > > > > > > > > > [out/target/product/eee_701/installer/ramdisk-installer.img] > > > > > > > > > Error 1 > > > > > >
--~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
