Thanks for you reply. I did input "reboot" in the console. but also failed. My VM is 5.5, may be too old :) Do you kown where is "sda6" setting ? In which config file?
I will try you suggestion 3x On Mon, Feb 9, 2009 at 12:48 AM, Chen Yang <sunsety...@gmail.com> wrote: > > hi, I don't know whether the modification to sda has been already > flushed to the virtual disk of VMWare. The safe way seems to issue the > command: "reboot" in the console. Meanwhile, i have no idea on whether > VMWare version matters or not. My VMWare workstation is 6.5. > I have posted the steps to build the installed image file directly here: > http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3 > After that you can use the steps to create the vmdk to use with VMWare. :) > See whether it solves the issue. > Hope it helps. > -- > Chen > > On Mon, Feb 9, 2009 at 12:28 AM, liuhy <liuhuaiy...@gmail.com> wrote: > > > > Dear Chen > > > > I meat "no sda6" problem. > > > > print this error > > "E/diskutils(1752):Could not open '/dev/block/sda6' for read/write > > (errno = 2)" > > > > I follow you flow , reboot vm ,but the same error. > > Did I miss do something ? > > > > > > > > > > On 2008年12月28日, 下午4时40分, "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 ramdisk.img > >> > > > > drwxr-xr-x 9 oedev oedev 4.0K 2008-12-20 21:09 root > >> > > > > drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 19:55 symbols > >> > > > > drwxr-xr-x 12 oedev oedev 4.0K 2008-12-20 21:29 system > >> > > > > -rw-r--r-- 1 oedev oedev 355M 2008-12-20 22:34 system.img > >> > > > > -rw-r--r-- 1 oedev oedev 5.0M 2008-12-20 21:32 userdata.img > >> > >> > > > > $ file out/target/product/eee_701/installer.img > >> > > > > out/target/product/eee_701/installer.img: x86 boot sector; > >> > > > > GRand Unified Bootloader, stage1 version 0x3; partition 2: > >> > > > > ID=0x83, starthead 0, startsector 10926, 783672 sectors, code > offset > >> > > > > 0x48 > >> > >> > > > > $ file out/target/product/eee_701/system.img > >> > > > > out/target/product/eee_701/system.img: Linux rev 0.0 ext2 > filesystem > >> > > > > data > >> > >> > > > > $ file out/target/product/eee_701/userdata.img > >> > > > > out/target/product/eee_701/userdata.img: Linux rev 0.0 ext2 > >> > filesystem > >> > > > > data > >> > >> > > > > $ sudo mount -o loop boot.img /mnt > >> > > > > total 2.5M > >> > > > > -rw-r--r-- 1 oedev oedev 77 2008-12-20 21:23 cmdline > >> > > > > -rw-r--r-- 1 oedev oedev 1.9M 2008-12-20 21:23 kernel > >> > > > > -rw-r--r-- 1 oedev oedev 592K 2008-12-20 21:23 ramdisk > >> > >> > > > > $ cat /mnt/cmndline > >> > > > > console=tty0 console=ttyS1,115200n8 console=tty0 > >> > > > > androidboot.hardware=eee_701 > >> > >> > > > > $ cp /mnt/ramdisk /tmp/ramdisk.gz > >> > > > > $ cd /tmp > >> > > > > $ gunzip ramdisk.gz > >> > > > > $ cpio -iv < ramdisk > >> > > > > sys > >> > > > > init.goldfish.rc > >> > > > > system > >> > > > > data > >> > > > > init.rc > >> > > > > proc > >> > > > > init > >> > > > > default.prop > >> > > > > sbin- 隐藏被引用文字 - > >> > >> - 显示引用的文字 - > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
