Hi Chen, I managed to use adb. I'm attaching /proc/devices. From the list, you can see "29 fb". Is this what you're looking for?
Thanks, Brian Character devices: 1 mem 2 pty 3 ttyp 4 /dev/vc/0 4 tty 4 ttyS 5 /dev/tty 5 /dev/console 5 /dev/ptmx 7 vcs 10 misc 13 input 14 sound 21 sg 29 fb 89 i2c 116 alsa 128 ptm 136 pts 180 usb 189 usb_device 202 cpu/msr 203 cpu/cpuid 216 rfcomm 252 usb_endpoint 253 usbmon 254 rtc Block devices: 1 ramdisk 7 loop 8 sd 11 sr 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 179 mmc On Mar 28, 10:40 pm, Chen Yang <[email protected]> wrote: > Brian: > I cannot see the clear problem from your description. The segfault > issue seems to be common where the there is no framebuffer devices > activated. > For connection over adb, you may need to enabled the pcnet32 driver > in the kernel. > One more question, when enabled vga=788 option, have you waited > some time to see the effect? The screen may become black for a short > time, during that time, the kernel is doing some initialization, so > looks like no response. > -- > Chen > > On Sun, Mar 29, 2009 at 5:44 AM, Brian <[email protected]> wrote: > > > Hi Chen, > > > When I added vga=788 in the cmdline in booting it, the screen totally > > freezes. Even alt + f1 does not display any. > > I booted the kernel with vga=788 option. In that case, I have the > > following in /proc/cmdline. > > console=ttyS1,115200n8 console=tty0 androidboot.hardware=eee_701 > > > I tried to check /proc/devices. But for that I need to install > > busybox. I don't know how to do it without installing busybox. > > Unfortunately adb does not work (I tried ADBHOST, but I got error: > > device not found), although > > the android vm has network connection in a bridged mode. > > > I am sure I turned on VESA VGA and Framebuffer Console support when I > > compiled bzImage. > > > dmesg output keeps printing out the following. > > <6> [timestamp] SurfaceFlinger[2956]: segfault at 38 ip 80111049 sp > > b5b56fec error 4 in libc.so [80100000+4b000] > > > Thanks for your help. > > Brian > > > On Mar 27, 5:11 am, Chen Yang <[email protected]> wrote: > >> hi,Brian: > >> Sorry for late response on this thread. > >> Would you like to check the whether the kernel has the VESA > >> support? Would you like to provide the result with: > >> #cat /proc/cmdline > >> and > >> #cat /proc/devices > >> see whether fb is listed. > >> -- > >> Chen > > >> On Fri, Mar 27, 2009 at 1:46 PM,Brian<[email protected]> wrote: > >> > Hi, > > >> > I did all the steps following Chen's instructions. I am still having a > >> > problem. I have tried vmware workstation and fusion. > >> > In the vmware workstation, I got a blank screen after booting. > >> > When I press alt + f1, I can see the following messages. > > >> > [time] init : cannot find '/system/bin/mountd', disabling 'mountd' > >> > sh : can't access tty: job control turned off > >> > [time] warning: 'app_process' uses 32-bit capabilities (legacy support > >> > in use) > > >> > How can I fix it? It's hard to pinpoint what to do. > > >> > Thanks, > >> >Brian > > >> > On Dec 28 2008, 1:40 am, "Chen Yang" <[email protected]> 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 > >> >> <[email protected]>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" <[email protected]> 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 < > >> >> > [email protected]>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" <[email protected]> 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 > >> >> > > > > * > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
