On Sat, Mar 28, 2009 at 2:46 PM, Brian <bgc...@gmail.com> wrote: > > Hi Yi, > > I tried to boot with or without vga=788. Both attempts are successful. > I assume that you have a typo here and what you really want to say is "unsuccessful".
> > When you mention "changing the framebuffer to vga", do you mean > compiling the kernel with VESA VGA support and Framebuffer Console > support? > Yes, that is what I meant. I had almost the same issue on my Eee PC. So what I did is to change the init.rc to disable anything relate to android runtime and make Android to only boot into sh. From there I start to run everything manully and try to find out the problem. Maybe you could try the similar thing and see if you can get any luck. Another thing you can do is to send out your .config file so that people could help you to check your configuration (I don't have a .config for VMware, but I believe others must have one) > > Thanks, > Brian > > > On Mar 27, 9:08 am, Yi Sun <beyo...@gmail.com> wrote: > > Have you changed your frambuffer to vga? and added vga=788 in the kernel > > command line? > > > > On Thu, Mar 26, 2009 at 10:46 PM, Brian <bgc...@gmail.com> wrote: > > > > > Hi, > > > > > I did all the steps following Chen's instructions. I am still having a > > > problem. I have tried vmware workstation and fusion. > > > In the vmware workstation, I got a blank screen after booting. > > > When I press alt + f1, I can see the following messages. > > > > > [time] init : cannot find '/system/bin/mountd', disabling 'mountd' > > > sh : can't access tty: job control turned off > > > [time] warning: 'app_process' uses 32-bit capabilities (legacy support > > > in use) > > > > > How can I fix it? It's hard to pinpoint what to do. > > > > > Thanks, > > > Brian > > > > > On Dec 28 2008, 1:40 am, "Chen Yang" <sunsety...@gmail.com> wrote: > > > > At hand, i only have VMware workstation, and I have verified the > steps, > > > hope > > > > it helps. > > > > I assume that you have parepared the installer.img from Lim's > > > description: > > > > > > 1. create the vmware disk file based on the installer.img > > > > you can use sfdisk -l installer.img to get the C/H/S information > about > > > it, > > > > although it reports issues, it won't do harm, at least from my > > > observation. > > > > And get our interested line: > > > > ... > > > > for C/H/S=*/1/0 (instead of 49/255/63). > > > > ... > > > > > > Also, you may need to change the following entries: the extent > > > description > > > > part, to the real block size of the image, basically, it's size of > > > > installer.img/512. > > > > > > Cut the following lines to one file with the installer.img as > > > > installer.vmdk, and copy the installer.img together with this file in > the > > > > same directory. > > > > --- > > > > # Disk DescriptorFile > > > > version=1 > > > > CID=b01deebc > > > > parentCID=ffffffff > > > > createType="monolithicFlat" > > > > # Extent description > > > > RW 794622 FLAT "installer.img" 0 > > > > # The Disk Data Base > > > > #DDB > > > > ddb.virtualHWVersion = "4" > > > > ddb.geometry.cylinders = "49" > > > > ddb.geometry.heads = "255" > > > > ddb.geometry.sectors = "63" > > > > ddb.adapterType = "ide" > > > > ddb.toolsVersion = "0" > > > > -- > > > > > > 2.create a new vmware target environment as linux 2.6 series, and > create > > > one > > > > primary hdd with IDE at least 1.8GB(maybe a little less is possible, > i > > > > haven't remebered the precise size, and I haven't tried SCSI yet, but > may > > > be > > > > also possible). Add the installer.vmdk as one extra hard disk to the > > > virtual > > > > machine. > > > > > > 3. Boot the VM, and when bios shows, press F2 to enter BIOS, to > select > > > the > > > > right installer drive as the boot drive, if you added later, it will > be > > > > Primary Slave. Choose it before the Primary Master by Pressing + on > that > > > HDD > > > > in boot column. After that, you will see the boot starts. > > > > > > 4. it may report issues in installation as "no sda6" as it happened > to > > > me, > > > > it seems to have some relationship with the updated partition table > read > > > > failure. Take it easy. Just reboot the vm, and installation will > > > continue, > > > > as the updated parition table will be effective when rebooted. Wait > some > > > > time, and it will report > > > > "Successfully configured N images." > > > > Then the installation is done! > > > > > > 5. Reboot the VM, and change the boot up drive as the Primary Master. > Or > > > you > > > > can just remove the installer.vmdk from the VM configuration. Then > boot > > > > starts, you will be able to use it. > > > > > > Some notes: > > > > 1. Be sure to compile the kernel with VESAFB and add the vga=788 with > in > > > > cmdline. 800x600 seems to be a quite usable resolution, for 1024x768 > and > > > > above resolutions, you may meet some performance or execution issues. > > > > 2. If you want to use network, you may need to compile the AMD > PCNET32 > > > > driver. > > > > 3. the installer.vmdk also works with Virtualbox, but i haven't > verified > > > the > > > > above steps yet. > > > > 4. Chris's make-live may provide some short-cut, i haven't explored > yet. > > > > But I may update if I find one good approach. :) > > > > > > Hope it helps! And correct me if i have something incorrect with my > > > > description. Thanks. > > > > -- > > > > Chen > > > > > > On Sat, Dec 27, 2008 at 5:57 PM, Andriod Developer < > > > andrd.dv...@gmail.com>wrote: > > > > > > > Hi Chen, could u pls list the steps to do this(i.e. running the > image > > > > > in virtualbox)? > > > > > thanks > > > > > Sri > > > > > > > On Dec 26, 5:43 pm, "Chen Yang" <sunsety...@gmail.com> wrote: > > > > > > I have managed to run it under both Vmware and Virtualbox. You > need > > > to > > > > > > compile the kernel with proper driver: vesafb, ethernet, scsci or > > > ide, > > > > > etc. > > > > > > You may be able to use the dd image of the make-live created usb > key. > > > > > > -- > > > > > > Chen > > > > > > On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer < > > > > > andrd.dv...@gmail.com>wrote: > > > > > > > > > Thanks Lee for the detailed instructions. Do you know if this > build > > > > > > > works in Virtual Environment(like VMWare or VirtualBox?). > > > > > > > What changes do I need to make if I need to run this in virtual > > > > > > > environment? > > > > > > > > > Also, Do you know if the vanilla cupcake branch will work for > the > > > > > > > virtual environment? Or do I need to pull in the Asus tree? > > > > > > > > > Thanks > > > > > > > > > On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote: > > > > > > > > HOWTO Build Android-X86 Full Source > > > > > > > > ==================================== > > > > > > > > Last Modified on 23-Dec-2008 23:10 > > > > > > > > > > I Summarized how to build android full source for x86 target. > > > > > > > > > > 0. My development environments > > > > > > > > - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic ) > > > > > > > > - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( > Samsung > > > > > SENS > > > > > > > > R60 Laptop ) > > > > > > > > - RAM: Samsung DDR Ram > > > > > > > > - Target: Eee PC (ASUS) > > > > > > > > > > 1. Query of Linux distribution information > > > > > > > > - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop > > > (NC01). > > > > > > > > And then, confirm system information on your linux > > > distribution > > > > > > > > like belows. > > > > > > > > > > $ uname -a > > > > > > > > Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 > 01:30:51 > > > UTC > > > > > > > > 2008 i686 GNU/Linux > > > > > > > > > > $ gcc --version > > > > > > > > gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2 > > > > > > > > Copyright (C) 2008 Free Software Foundation, Inc. > > > > > > > > This is free software; see the source for copying conditions. > > > There > > > > > > > > is NO > > > > > > > > warranty; not even for MERCHANTABILITY or FITNESS FOR A > > > PARTICULAR > > > > > > > > PURPOSE. > > > > > > > > > > 2. repo init and Sync > > > > > > > > - You have to download android full source for x86 > architecture > > > like > > > > > > > > ASUS Eee PC 701. > > > > > > > > - Eee pc dev tree is "git:// > > > android.git.kernel.org/platform/vendor/ > > > > > > > > asus/eee_701.git". > > > > > > > > $ cd ~ > > > > > > > > $ mkdir bin_x86 && cd bin_x86 > > > > > > > > $ mkdir mydroid && cd mydroid > > > > > > > > $ repo init -u git:// > > > android.git.kernel.org/platform/manifest.git -b > > > > > > > > cupcake > > > > > > > > $ repo sync > > > > > > > > $ vi ./.repo/local_manifest.xml > > > > > > > > <manifest> > > > > > > > > <project name="platform/vendor/asus/eee_701" > > > path="vendor/asus/ > > > > > > > > eee_701"/> > > > > > > > > </manifest> > > > > > > > > > > $ repo sync > > > > > > > > ... A new repo command ( 1.8) is available. > > > > > > > > ... You should upgrade soon: > > > > > > > > > > cp /home/invain/bin_x86/mydroid/.repo/repo/repo > > > /home/invain/bin/ > > > > > > > > repo > > > > > > > > > > Initializing project platform/vendor/asus/eee_701 ... > > > > > > > > remote: Counting objects: 33, done. > > > > > > > > remote: Compressing objects: 100% (31/31), done. > > > > > > > > remote: Total 33 (delta 2), reused 33 (delta 2) > > > > > > > > Unpacking objects: 100% (33/33), done. > > > > > > > > From git:// > android.git.kernel.org/platform/vendor/asus/eee_701 > > > > > > > > * [new branch] cupcake -> korg/cupcake > > > > > > > > * [new branch] master -> korg/master > > > > > > > > > > 3. Building x86 android full source > > > > > > > > $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 > DISABLE_DEXPREOPT=true > > > make > > > > > - > > > > > > > > j2 installer_img > > > > > > > > > > build/core/product_config.mk:207: WARNING: adding test OTA > key > > > > > > > > ============================================ > > > > > > > > TARGET_PRODUCT=eee_701 > > > > > > > > TARGET_BUILD_VARIANT=eng > > > > > > > > TARGET_SIMULATOR= > > > > > > > > TARGET_BUILD_TYPE=release > > > > > > > > TARGET_ARCH=x86 > > > > > > > > HOST_ARCH=x86 > > > > > > > > HOST_OS=linux > > > > > > > > HOST_BUILD_TYPE=release > > > > > > > > BUILD_ID= > > > > > > > > ============================================ > > > > > > > > build/core/main.mk:178: implicitly installing > apns-conf_sdk.xml > > > > > > > > ............... Below Omission > > > > > ................... > > > > > > > > > > * Toouble Shooting > > > > > > > > > > $ vi > > > external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/ > > > > > > > > vector-fst.h > > > > > > > > $ vi > > > external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp > > > > > > > > $ vi frameworks/base/tools/aidl/aidl.cpp --> #include > <stdlib.h>, > > > > > > > > #include <string.h> > > > > > > > > and so on...... > > > > > > > > > > $ vi > > > > > > > > $ ls -lh out/target/product/eee_701/ > > > > > > > > total 753M > > > > > > > > -rw-r--r-- 1 oedev oedev 2.5M 2008-12-20 21:23 boot.img > > > > > > > > -rw-r--r-- 1 oedev oedev 57 2008-12-20 22:15 > clean_steps.mk > > > > > > > > drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 21:32 data > > > > > > > > drwxr-xr-x 2 oedev oedev 4.0K 2008-12-20 19:54 grub > > > > > > > > drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 22:36 installer > > > > > > > > -rw-r--r-- 1 oedev oedev 388M 2008-12-20 22:38 > installer.img > > > > > > > > -rw-r--r-- 1 oedev oedev 1.9M 2008-12-20 18:45 kernel > > > > > > > > drwxr-xr-x 12 oedev oedev 4.0K 2008-12-20 22:33 obj > > > > > > > > -rw-r--r-- 1 oedev oedev 592K 2008-12-20 21:10 > > > > ... > > > > read more ยป > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
