I've compiled a kernel 2.6.25 with vesa fb and radeon fb actived,
(take it here: www.dei.unipd.it/~rossicar/kernel)
you can overwrite standard eee kernel located in mydroid/vendor/asus/
eee_701/
and add "vga=" option during grub boot or in menu.lst
Thanks to freedom, Chen Yang and Lim for the guidelines
Problems?
1) at high resolutions android doesn't work very well (using vga=794)
2) low screen refresh rates (obvious, is a framebuffer...)
3) no mouse support
4) buggy keyboard support
5) no network support
6) dialer function doesn't work.. ;-)
> Problems?
> 1) at high resolutions android doesn't work very well (using vga=794)
There is no hardware acceleration whatsoever for this target. You are
running at high resolution, and forcing the CPU to copy lots of data around
for every frame. Also, the assets in the framework are all designed to look
good on HVGA, and you are asking them to look good on 1280x1024 :)
> 2) low screen refresh rates (obvious, is a framebuffer...)
You probably mean low framerate. Framebuffer itself is not the problem. As
stated above, you running in pure software mode, so composition will be
pretty slow since you have to copy stuff around a few times before you
finally copy it into the framebuffer. And by copy, I mean memcpy() the data
around, no DMA or hardware blitters, or anything. With some basic hw
support, this will be improved dramatically.
> 3) no mouse support
It's not designed to work with a mouse at this point. There is no support
for a maintaining a cursor's position, or drawing a cursor on the screen.
Remember, we are running an environment that is currently only supported on
a touchscreen mobile handset. Hopefully, non-handset usage will improve as
people submit patches, work more on the mid profile, and generally drive the
platform on non-handsets forward.
You should note though, that plugging in a USB mouse generally should work,
and will act as a "trackball" like you have on the G1.
4) buggy keyboard support
You need the correct keymap for your keyboard. Specfifically, menu/back/home
keys need to be properly mapped.
> 5) no network support
Your kernel is missing the proper network drivers.
I modified the kernel.config file and restarted my build again. I
assume virtualbox needs a .iso file for installation. How do i convert
installer.img to .iso file?
is there any other way of doing this? I want to run Android in
virtualbox (running on XP pc).
On Dec 27, 3:58 am, Piethein Strengholt <pietheinstrengh...@gmail.com>
wrote:
> I think by editing the /vendor/asus/eee_701/kernel.config file
> Add these lines:
> CONFIG_FB_VESA=y
> CONFIG_HAVE_IDE=y
> And try to compile everything again.
> On Dec 27, 10:57 am, 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.
> > > > > $ 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:
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:
I just repeated the process on VirtualBox, mostly the same and you may meet
with one issue in booting the installer.img, as you select the primary slave
as the boot up disk, it will complain that it cannot find the right
parition, then please select 0 and edit the 3 lines configuration one by
one, to replace the the hd0 with hd1, then it will start the installation
process correctly. You will also need the same rebooting and re-configure
the 0 sysloader, and 3 lines configuration to accomplish the installation.
Hope it helps!
--
Chen
On Sun, Dec 28, 2008 at 4:40 PM, 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:
Thanks yang for the instructions.
I am using VirtualBox2.1.0 release and it complains about .vmdk file
when i try to add it. Somebody has opened a bug for virtualbox for the
same issue.
What release are you using?
On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> I just repeated the process on VirtualBox, mostly the same and you may meet
> with one issue in booting the installer.img, as you select the primary slave
> as the boot up disk, it will complain that it cannot find the right
> parition, then please select 0 and edit the 3 lines configuration one by
> one, to replace the the hd0 with hd1, then it will start the installation
> process correctly. You will also need the same rebooting and re-configure
> the 0 sysloader, and 3 lines configuration to accomplish the installation.
> Hope it helps!
> --
> Chen
> On Sun, Dec 28, 2008 at 4:40 PM, 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.
> >> > > > $ 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:
hi, I have managed to accomplished the installation with virtualbox 2.1.0 on
Mac, which seems to be the most updated version. What kind of error message?
--
Chen
On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> Thanks yang for the instructions.
> I am using VirtualBox2.1.0 release and it complains about .vmdk file
> when i try to add it. Somebody has opened a bug for virtualbox for the
> same issue.
> What release are you using?
> On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > I just repeated the process on VirtualBox, mostly the same and you may
> meet
> > with one issue in booting the installer.img, as you select the primary
> slave
> > as the boot up disk, it will complain that it cannot find the right
> > parition, then please select 0 and edit the 3 lines configuration one by
> > one, to replace the the hd0 with hd1, then it will start the installation
> > process correctly. You will also need the same rebooting and re-configure
> > the 0 sysloader, and 3 lines configuration to accomplish the
> installation.
> > Hope it helps!
> > --
> > Chen
> > On Sun, Dec 28, 2008 at 4:40 PM, 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.
> hi, I have managed to accomplished the installation with virtualbox 2.1.0 on
> Mac, which seems to be the most updated version. What kind of error message?
> --
> Chen
> On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> > Thanks yang for the instructions.
> > I am using VirtualBox2.1.0 release and it complains about .vmdk file
> > when i try to add it. Somebody has opened a bug for virtualbox for the
> > same issue.
> > What release are you using?
> > On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > I just repeated the process on VirtualBox, mostly the same and you may
> > meet
> > > with one issue in booting the installer.img, as you select the primary
> > slave
> > > as the boot up disk, it will complain that it cannot find the right
> > > parition, then please select 0 and edit the 3 lines configuration one by
> > > one, to replace the the hd0 with hd1, then it will start the installation
> > > process correctly. You will also need the same rebooting and re-configure
> > > the 0 sysloader, and 3 lines configuration to accomplish the
> > installation.
> > > Hope it helps!
> > > --
> > > Chen
> > > On Sun, Dec 28, 2008 at 4:40 PM, 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.
> > > >> > > > 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.
> and the contents of my vmdk file are:
> ---
> # 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"
> ----
> I am choosing the existing virtual hard disk option(with boot hard disk
> (primary master) checked) while creating the new VM.
> Thanks for ur help!
> On Dec 29, 9:42 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > hi, I have managed to accomplished the installation with virtualbox 2.1.0
> on
> > Mac, which seems to be the most updated version. What kind of error
> message?
> > --
> > Chen
> > On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <
> andrd.dv...@gmail.com>wrote:
> > > Thanks yang for the instructions.
> > > I am using VirtualBox2.1.0 release and it complains about .vmdk file
> > > when i try to add it. Somebody has opened a bug for virtualbox for the
> > > same issue.
> > > What release are you using?
> > > On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > > I just repeated the process on VirtualBox, mostly the same and you
> may
> > > meet
> > > > with one issue in booting the installer.img, as you select the
> primary
> > > slave
> > > > as the boot up disk, it will complain that it cannot find the right
> > > > parition, then please select 0 and edit the 3 lines configuration one
> by
> > > > one, to replace the the hd0 with hd1, then it will start the
> installation
> > > > process correctly. You will also need the same rebooting and
> re-configure
> > > > the 0 sysloader, and 3 lines configuration to accomplish the
> > > installation.
> > > > Hope it helps!
> > > > --
> > > > Chen
> > > > On Sun, Dec 28, 2008 at 4:40 PM, 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.
> > > > >> > > > 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.
VirtualBox2.1.0 on WinXP. As per your instructions, I created a .vmdk
file with the above contents and
copied installer.img and .vmdk file to the same directory and i tried
to create a new VM by choosing the
existing virtual harddisk. When i see the error, i also noticed that
the contents of the .vmdk file are
modified with lot of "^@" symbols..
Thanks for ur time Chen... I really wanted to get this going.
On Dec 29, 11:14 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > and the contents of my vmdk file are:
> > ---
> > # 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"
> > ----
> > I am choosing the existing virtual hard disk option(with boot hard disk
> > (primary master) checked) while creating the new VM.
> > Thanks for ur help!
> > On Dec 29, 9:42 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > hi, I have managed to accomplished the installation with virtualbox 2.1.0
> > on
> > > Mac, which seems to be the most updated version. What kind of error
> > message?
> > > --
> > > Chen
> > > On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <
> > andrd.dv...@gmail.com>wrote:
> > > > Thanks yang for the instructions.
> > > > I am using VirtualBox2.1.0 release and it complains about .vmdk file
> > > > when i try to add it. Somebody has opened a bug for virtualbox for the
> > > > same issue.
> > > > What release are you using?
> > > > On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > > > I just repeated the process on VirtualBox, mostly the same and you
> > may
> > > > meet
> > > > > with one issue in booting the installer.img, as you select the
> > primary
> > > > slave
> > > > > as the boot up disk, it will complain that it cannot find the right
> > > > > parition, then please select 0 and edit the 3 lines configuration one
> > by
> > > > > one, to replace the the hd0 with hd1, then it will start the
> > installation
> > > > > process correctly. You will also need the same rebooting and
> > re-configure
> > > > > the 0 sysloader, and 3 lines configuration to accomplish the
> > > > installation.
> > > > > Hope it helps!
> > > > > --
> > > > > Chen
> > > > > On Sun, Dec 28, 2008 at 4:40 PM, 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?
> > > > > >> > > > 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.
May be i am missing something here. This is what i am doing:
Launch Sun VirtualBox
Click on New -> Next
Name it as "AsusAndrioid"
Ostype=Linux
Version=2.6
RAM=256MB
Checked Boot Harddisk(Primary master)
clicked on exisiting and selecting the .vmdk file(this is only 1k file
though). When i select the file, virtualbox complains about failing to
open the file and says it has invalid signature.
Not sure if i am doing any wrong in this step..
Please help!
On Dec 29, 11:14 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > and the contents of my vmdk file are:
> > ---
> > # 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"
> > ----
> > I am choosing the existing virtual hard disk option(with boot hard disk
> > (primary master) checked) while creating the new VM.
> > Thanks for ur help!
> > On Dec 29, 9:42 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > hi, I have managed to accomplished the installation with virtualbox 2.1.0
> > on
> > > Mac, which seems to be the most updated version. What kind of error
> > message?
> > > --
> > > Chen
> > > On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <
> > andrd.dv...@gmail.com>wrote:
> > > > Thanks yang for the instructions.
> > > > I am using VirtualBox2.1.0 release and it complains about .vmdk file
> > > > when i try to add it. Somebody has opened a bug for virtualbox for the
> > > > same issue.
> > > > What release are you using?
> > > > On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > > > I just repeated the process on VirtualBox, mostly the same and you
> > may
> > > > meet
> > > > > with one issue in booting the installer.img, as you select the
> > primary
> > > > slave
> > > > > as the boot up disk, it will complain that it cannot find the right
> > > > > parition, then please select 0 and edit the 3 lines configuration one
> > by
> > > > > one, to replace the the hd0 with hd1, then it will start the
> > installation
> > > > > process correctly. You will also need the same rebooting and
> > re-configure
> > > > > the 0 sysloader, and 3 lines configuration to accomplish the
> > > > installation.
> > > > > Hope it helps!
> > > > > --
> > > > > Chen
> > > > > On Sun, Dec 28, 2008 at 4:40 PM, 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?
> > > > > >> > > > 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.
It seems all are correct.
You can choose to add the vmdk without creating the virtual machine by
selecting the File->Virtual Media Manager ...
Meanwhile, the installer.img is useless as a primary master, since it's only
for installation use.
--
Chen
On Tue, Dec 30, 2008 at 4:27 AM, Andriod Developer <andrd.dv...@gmail.com>wrote:
> May be i am missing something here. This is what i am doing:
> Launch Sun VirtualBox
> Click on New -> Next
> Name it as "AsusAndrioid"
> Ostype=Linux
> Version=2.6
> RAM=256MB
> Checked Boot Harddisk(Primary master)
> clicked on exisiting and selecting the .vmdk file(this is only 1k file
> though). When i select the file, virtualbox complains about failing to
> open the file and says it has invalid signature.
> Not sure if i am doing any wrong in this step..
> Please help!
> On Dec 29, 11:14 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > i just verified your configuration with Virtualbox 2.1.0 under Windows,
> it
> > can import the disk correctly. Which version are you using?
> > --
> > Chen
> > On Tue, Dec 30, 2008 at 2:51 AM, Andriod Developer <
> andrd.dv...@gmail.com>wrote:
> > > This is what i see
> > > ----
> > > Could not open the hard disk "f:\Asusinstaller\installer.vmdk".
> > > I am choosing the existing virtual hard disk option(with boot hard disk
> > > (primary master) checked) while creating the new VM.
> > > Thanks for ur help!
> > > On Dec 29, 9:42 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > > hi, I have managed to accomplished the installation with virtualbox
> 2.1.0
> > > on
> > > > Mac, which seems to be the most updated version. What kind of error
> > > message?
> > > > --
> > > > Chen
> > > > On Tue, Dec 30, 2008 at 1:23 AM, Andriod Developer <
> > > andrd.dv...@gmail.com>wrote:
> > > > > Thanks yang for the instructions.
> > > > > I am using VirtualBox2.1.0 release and it complains about .vmdk
> file
> > > > > when i try to add it. Somebody has opened a bug for virtualbox for
> the
> > > > > same issue.
> > > > > What release are you using?
> > > > > On Dec 28, 8:12 am, "Chen Yang" <sunsety...@gmail.com> wrote:
> > > > > > I just repeated the process on VirtualBox, mostly the same and
> you
> > > may
> > > > > meet
> > > > > > with one issue in booting the installer.img, as you select the
> > > primary
> > > > > slave
> > > > > > as the boot up disk, it will complain that it cannot find the
> right
> > > > > > parition, then please select 0 and edit the 3 lines configuration
> one
> > > by
> > > > > > one, to replace the the hd0 with hd1, then it will start the
> > > installation
> > > > > > process correctly. You will also need the same rebooting and
> > > re-configure
> > > > > > the 0 sysloader, and 3 lines configuration to accomplish the
> > > > > installation.
> > > > > > Hope it helps!
> > > > > > --
> > > > > > Chen
> > > > > > On Sun, Dec 28, 2008 at 4:40 PM, 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.
> > > > > > > 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?
I am following the instructions specified by Dima and Lim to build
Android on a EeePC. However, I want to build it on a Desktop with
Ubuntu 8.10. I created a new directory for Android source code, did a
"repo init", followed by "repo sync" and then explicitly did a git
clone of git://android.git.kernel.org/platform/vendor/asus/eee_701.git
to get the EeePC files.
I only did a repo init (not with -b option) with the understanding
that the cupcake branch is now merged into the master branch. Is this
incorrect? Do I have to use '-b cupcake'?
Subsequently, I ran the following command:
TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
CC=gcc-4.2.1 CXX=g++-4.2.1 make -j2 installer_img
The output I got is:
*************************************************************************** *****
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
build/core/base_rules.mk:117: *** recovery/amend:
MODULE.HOST.EXECUTABLES.amend already defined by bootable/recovery/
amend. Stop.
*************************************************************************** *****
What could be the issue? I have created symbolic links for 'gcc-4.2.1'
to point to "prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/
bin/i686-unknown-linux-gnu-gcc-4.2.1".
Thanks,
Avtar
On Dec 24 2008, 5:29 am, freedom <koansin....@gmail.com> wrote:
> Using gcc-4.2 instead of gcc-4.3 should help avoid modifying source,
> that is
> $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
> CC=gcc-4.2 CXX=g++-4.2 make ........
> On Dec 23, 11:11 pm, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > 3. Building x86 android full source
> > $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -
> > j2 installer_img
hi Avtar:
Is this directory also used for pre-cupcake source? It seems that the
compilation issue was caused by the stale directory "recovery" under your
android source root directory. You may remove it to see whether it works or
not. Hope it helps!
--
Chen
On Sat, Jan 3, 2009 at 2:27 PM, Avtar Singh <s.av...@gmail.com> wrote:
> Hi,
> I am following the instructions specified by Dima and Lim to build
> Android on a EeePC. However, I want to build it on a Desktop with
> Ubuntu 8.10. I created a new directory for Android source code, did a
> "repo init", followed by "repo sync" and then explicitly did a git
> clone of git://android.git.kernel.org/platform/vendor/asus/eee_701.git
> to get the EeePC files.
> I only did a repo init (not with -b option) with the understanding
> that the cupcake branch is now merged into the master branch. Is this
> incorrect? Do I have to use '-b cupcake'?
> Subsequently, I ran the following command:
> TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
> CC=gcc-4.2.1 CXX=g++-4.2.1 make -j2 installer_img
> What could be the issue? I have created symbolic links for 'gcc-4.2.1'
> to point to "prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/
> bin/i686-unknown-linux-gnu-gcc-4.2.1".
> Thanks,
> Avtar
> On Dec 24 2008, 5:29 am, freedom <koansin....@gmail.com> wrote:
> > Using gcc-4.2 instead of gcc-4.3 should help avoid modifying source,
> > that is
> > $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
> > CC=gcc-4.2 CXX=g++-4.2 make ........
> > On Dec 23, 11:11 pm, "Lim,GeunSik" <lee...@gmail.com> wrote:
> > > 3. Building x86 android full source
> > > $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -
> > > j2 installer_img
> Is this directory also used for pre-cupcake source? It seems that the > compilation issue was caused by the stale directory "recovery" under your > android source root directory. You may remove it to see whether it works or
Yes. It also had pre-cupcake source. It works now. Thanks, Chen! I will now follow the make output and see what I have got.
>> Is this directory also used for pre-cupcake source? It seems that the >> compilation issue was caused by the stale directory "recovery" under your >> android source root directory. You may remove it to see whether it works or > Yes. It also had pre-cupcake source. It works now. Thanks, Chen! I > will now follow the make output and see what I have got.
I now get the following error: could not locate libstdc++. Any pointers?
# TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make 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 host Executable: genext2fs (out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs) /home/developer/mydroid/prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu -4.2.1/bin/../lib/gcc/i686-unknown-linux-gnu/4.2.1/../../../../i686-unknown -linux-gnu/bin/ld: cannot find -lstdc++ collect2: ld returned 1 exit status make: *** [out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs] Error 1
>> Is this directory also used for pre-cupcake source? It seems that the >> compilation issue was caused by the stale directory "recovery" under your >> android source root directory. You may remove it to see whether it works or > Yes. It also had pre-cupcake source. It works now. Thanks, Chen! I > will now follow the make output and see what I have got.
I now get the following error: could not locate libstdc++. Any pointers?
# TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make 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 host Executable: genext2fs (out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs) /home/developer/mydroid/prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu -4.2.1/bin/../lib/gcc/i686-unknown-linux-gnu/4.2.1/../../../../i686-unknown -linux-gnu/bin/ld: cannot find -lstdc++ collect2: ld returned 1 exit status make: *** [out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs] Error 1
> 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:
> $ 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......
> ubuntu@ubuntu:~$ repo init -u
> git://android.git.kernel.org/platform/manifest.git
> -b cupcake
> bash: repo: command not found
> Why is my repo command not found? My Ubuntu version is almost the same
> as you specified:
> ubuntu@ubuntu:~$ uname -a
> Linux ubuntu 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008
> i686 GNU/Linux
> ubuntu@ubuntu:~$ gcc --version
> gcc (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
> Copyright (C) 2007 Free Software Foundation, Inc.
> Please help me!
> On 23 Dez. 2008, 16:11, "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:
>> $ 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......
Thanks for the answer. How can I download it? I went to the package
manager (I think it's Synaptics but not sure, it's the one that opens
when you click Applications -> Add/Remove software), entered "repo"
into the search field and downloaded "Report", the only thing that
made sense. It wanted me to install something like "camaeleon" or
similar, I downloaded whatever it wanted, but the installation broke
somewhere, and now I can't start it again.
I remember there was a terminal command somewhere to clean up the
repository data, but forgot what it was. Is this the right approach?
And how can I add that path to my PATH variable?
> > On 23 Dez. 2008, 16:11, "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:
Ok sorry for asking again, but somehow it doesn't want to work. I
downloaded curl and repo, and I think I also added it to the PATH
variable, but still the terminal can't find the repo:
This should do it, right? Or is the ~ symbol wrong when I add it to
PATH?
ubuntu@ubuntu:~$ sudo apt-get install curl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
curl
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 197kB of archives.
After this operation, 311kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com hardy/main curl 7.18.0-1ubuntu2
[197kB]
Fetched 197kB in 0s (246kB/s)
Selecting previously deselected package curl.
(Reading database ... 98223 files and directories currently
installed.)
Unpacking curl (from .../curl_7.18.0-1ubuntu2_i386.deb) ...
Setting up curl (7.18.0-1ubuntu2) ...
ubuntu@ubuntu:~$ curl http://android.git.kernel.org/repo >~/bin/repo
% Total % Received % Xferd Average Speed Time Time
Time Current
Dload Upload Total Spent
Left Speed
100 16989 0 16989 0 0 22294 0 --:--:-- --:--:--
--:--:-- 71556
ubuntu@ubuntu:~$ chmod a+x ~/bin/repo
ubuntu@ubuntu:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/
games
ubuntu@ubuntu:~$ export PATH=$PATH:~/bin/repo
ubuntu@ubuntu:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/
games:/home/ubuntu/bin/repo
On Jan 5, 5:15 am, "Avtar Singh" <s.av...@gmail.com> wrote:
Sorry for the post above, got it fixed now, had to add only "~/bin" to
my PATH. But now my Python makes problems :-\
ubuntu@ubuntu:~$ repo init -u git://android.git.kernel.org/platform/manifest.git
-b cupcake
Traceback (most recent call last):
File "/home/ubuntu/bin/repo", line 590, in <module>
main(sys.argv[1:])
File "/home/ubuntu/bin/repo", line 557, in main
_Init(args)
File "/home/ubuntu/bin/repo", line 176, in _Init
_CheckGitVersion()
File "/home/ubuntu/bin/repo", line 205, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
errread, errwrite)
File "/usr/lib/python2.5/subprocess.py", line 1147, in
_execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Why?
On Jan 5, 11:35 am, Lennart Moltrecht <moi...@googlemail.com> wrote:
> Ok sorry for asking again, but somehow it doesn't want to work. I
> downloaded curl and repo, and I think I also added it to the PATH
> variable, but still the terminal can't find the repo:
> This should do it, right? Or is the ~ symbol wrong when I add it to
> PATH?
> ubuntu@ubuntu:~$ sudo apt-get install curl
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
> curl
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 197kB of archives.
> After this operation, 311kB of additional disk space will be used.
> Get:1http://archive.ubuntu.comhardy/main curl 7.18.0-1ubuntu2
> [197kB]
> Fetched 197kB in 0s (246kB/s)
> Selecting previously deselected package curl.
> (Reading database ... 98223 files and directories currently
> installed.)
> Unpacking curl (from .../curl_7.18.0-1ubuntu2_i386.deb) ...
> Setting up curl (7.18.0-1ubuntu2) ...
> ubuntu@ubuntu:~$ curlhttp://android.git.kernel.org/repo>~/bin/repo
> % Total % Received % Xferd Average Speed Time Time
> Time Current
> Dload Upload Total Spent
> Left Speed
> 100 16989 0 16989 0 0 22294 0 --:--:-- --:--:--
> --:--:-- 71556
> ubuntu@ubuntu:~$ chmod a+x ~/bin/repo
> ubuntu@ubuntu:~$ echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/
> games
> ubuntu@ubuntu:~$ export PATH=$PATH:~/bin/repo
> ubuntu@ubuntu:~$ echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/
> games:/home/ubuntu/bin/repo
> On Jan 5, 5:15 am, "Avtar Singh" <s.av...@gmail.com> wrote:
> > > Thanks for the answer. How can I download it?
I am trying to compile android for a via mini itx board. I wanted to
know how to add the drivers for network card and the display driver
for the via pc. The via website has linux drivers for all the
hardware, but i dont know how to add it to the android build. How do i
do it?
Thanks,
Gowtham
On Dec 23 2008, 10: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:
> $ 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......
I am now running this image on Virtualbox 2.1.0 on WinXP. These are my
steps and observations:
1. When I start the VM, it hangs on Grub Loading stage 2..
2. I press F12 to enter the menu and it shows the following:
0: sys_loader
1: recovery
2: std_boot
3. Option "2" is selected by default. But it doesnot work. Neither
does option "1". The errors are as follows:
Option "1":
Booting `recovery`
cmdline (hd0,1)/cmdline
Error 15: File not found
Option "2":
Booting `std_boot`
cmdline (hd0,2)/cmdline
Error 22: No such partition
Where can I change the default to 0 ? (I tried looking for "menu.lst"
file. But couldnt find it)
4. I then run the "/system/bin/installer -p /dev/block/sda2" for my
partition. It gives an error that the total requested size is greater
than the disk size (My image size is 387 MB and it is looking for arnd
1.5GB space). Do I need to pad my image ?