Oops, it looks like that your frame buffer is not work well with the kernel. Have you compiled the vesafb or related framebuffer support in the kernel? -- Chen On Wed, Jan 21, 2009 at 4:32 AM, gowtham gowda <gowth...@gmail.com> wrote:
> > honestly, i donno what surfacefinger is. I donno what i am changing > when i am configuring the kernel. Where should i look for > surfacefliner? > > Thanks for the reply > > Gowtham > > On Jan 19, 10:52 pm, "Chen Yang" <sunsety...@gmail.com> wrote: > > Your libc.so is causing segmentation fault. > > You can firstly locate the routine at 0x10cf9 of libc.so, seems to be the > > instruction of "repnz scas %es:(%edi),%al" in strlen, possible reason edi > > points to incorrect location. > > > > Have you changed the source of surfaceflinger? > > -- > > Chen > > > > On Tue, Jan 20, 2009 at 7:26 AM, gowtham gowda <gowth...@gmail.com> > wrote: > > > > > Hi Yang > > > > > I need your help. > > > > > I am running into the black screen on my mini-itx via board, even when > > > vga=785 is set in the menu.lst in grub. > > > > > This is the dmesg output. > > > > > <6>[ 11.236784] r8169: eth0: link up > > > <6>[ 24.129464] warning: `app_process' uses 32-bit capabilities > > > (legacy support in use) > > > <6>[ 24.219358] SurfaceFlinger[1949]: segfault at 38 ip 80110cf9 sp > > > b5db200c error 4 in libc.so[80100000+49000] > > > <6>[ 25.595133] SurfaceFlinger[1964]: segfault at 38 ip 80110cf9 sp > > > b5d2200c error 4 in libc.so[80100000+49000] > > > <6>[ 30.978081] SurfaceFlinger[1983]: segfault at 38 ip 80110cf9 sp > > > 9e16600c error 4 in libc.so[80100000+49000] > > > <6>[ 36.359386] SurfaceFlinger[2002]: segfault at 38 ip 80110cf9 sp > > > 9e0fe00c error 4 in libc.so[80100000+49000] > > > <6>[ 41.748622] SurfaceFlinger[2021]: segfault at 38 ip 80110cf9 sp > > > 9e0fe00c error 4 in libc.so[80100000+49000] > > > <6>[ 49.295628] SurfaceFlinger[2040]: segfault at 38 ip 80110cf9 sp > > > b5d1600c error 4 in libc.so[80100000+49000] > > > <6>[ 51.677764] SurfaceFlinger[2055]: segfault at 38 ip 80110cf9 sp > > > 9e18200c error 4 in libc.so[80100000+49000] > > > <6>[ 57.058660] SurfaceFlinger[2074]: segfault at 38 ip 80110cf9 sp > > > b5cde00c error 4 in libc.so[80100000+49000] > > > <6>[ 61.437928] SurfaceFlinger[2093]: segfault at 38 ip 80110cf9 sp > > > 9e18200c error 4 in libc.so[80100000+49000] > > > > > any ideas? > > > > > Thanks, > > > Gowtham > > > > > On Jan 14, 7:58 am, "Chen Yang" <sunsety...@gmail.com> wrote: > > > > I haven't tried to add it to link against bionic. > > > > But one simple solution is to build the static linked one. > > > > You can configure it by choosing it with make menuconfig: > > > > Busybox Settings ---> > > > > Build Options ---> > > > > [*] Build BusyBox as a static binary (no shared libs) > > > > then you can build it. > > > > Hope it helps! > > > > -- > > > > Chen > > > > > > On Wed, Jan 14, 2009 at 11:50 AM, gowtham gowda <gowth...@gmail.com > > > > > wrote: > > > > > > > another question for the expert dhen > > > > > > > How can we add busybox to this build? > > > > > > > Thanks, > > > > > Gowtham > > > > > > > On Jan 10, 10:36 pm, "Chen Yang" <sunsety...@gmail.com> wrote: > > > > >> It looks like that you are missing the vga=788 option, you can > > > > >> reference my post: > > >http://groups.google.com/group/android-porting/msg/b9ffcb185b758b92 > > > > >> to set it and to see whether it can start successfully. > > > > >> Regarding building drivers, you can just issue the command: > > > > >> $make modules > > > > >> and then find those modules and put to the directory I have > replied > > > earlier. > > > > >> Hope it helps! > > > > >> -- > > > > >> Chen > > > > > > >> On Sun, Jan 11, 2009 at 11:07 AM, gowtham gowda < > gowth...@gmail.com> > > > wrote: > > > > > > >> > i am running into a blank screen when i use the new kernel > image. I > > > > >> > think its because of the older kernel (2.6.25) used in the eee > pc > > > > >> > build. And the "menu makeconfig" is compiling the new 2.6.27 > kernel, > > > > >> > so the driver modules are mismatching Do you know how to build > > > drivers > > > > >> > for kernel 2.6.27? > > > > > > >> > Thanks, > > > > >> > Gowtham > > > > > > >> > On Jan 10, 12:37 am, "Chen Yang" <sunsety...@gmail.com> wrote: > > > > >> >> I remembered that pmem may be one issue with x86. So with the > > > kernel.config, > > > > >> >> you need to disable it, otherwise, it may complain errors in > > > compilation: > > > > >> >> Device Drivers > > > > >> >> [*] Misc devices ---> > > > > >> >> [] Android pmem allocator > > > > > > >> >> Please de-select the pmem part. > > > > > > >> >> Hope it helps! > > > > >> >> -- > > > > >> >> Chen > > > > > > >> >> On Sat, Jan 10, 2009 at 1:35 PM, gowtham gowda < > gowth...@gmail.com> > > > wrote: > > > > > > >> >> > works, > > > > > > >> >> > thank you very much. > > > > > > >> >> > Gowtham > > > > > > >> >> > On Jan 10, 12:31 am, "Chen Yang" <sunsety...@gmail.com> > wrote: > > > > >> >> >> how about: > > > > >> >> >> $make bzImage > > > > > > >> >> >> -- > > > > >> >> >> Chen > > > > > > >> >> >> On Sat, Jan 10, 2009 at 1:23 PM, gowtham gowda < > > > gowth...@gmail.com> wrote: > > > > > > >> >> >> > i am getting this error when i try > > > > >> >> >> > #/mydroid/kernel$ make bzimage > > > > >> >> >> > scripts/kconfig/conf -s arch/x86/Kconfig > > > > >> >> >> > make: *** No rule to make target `bzimage'. Stop. > > > > > > >> >> >> > how do i get past this. > > > > > > >> >> >> > Thanks once again. > > > > > > >> >> >> > Gowtham > > > > > > >> >> >> > On Jan 10, 12:20 am, "Chen Yang" <sunsety...@gmail.com> > > > wrote: > > > > >> >> >> >> For modules, you may need to put under > > > > >> >> >> >> vendor/asus/eee_701/modules directory. > > > > >> >> >> >> You can add the insmod in init.rc > > > > >> >> >> >> or in the init.eee_701.sh > > > > >> >> >> >> It seems that you may need to comment the line in > > > init.eee_701.sh: > > > > >> >> >> >> setprop net.dns1 4.2.2.2 > > > > > > >> >> >> >> For VESAFB, it seems you may need to make built-in, it > may > > > doesn't > > > > >> >> >> >> work with modules. > > > > >> >> >> >> For network card, it's ok to be modules. > > > > >> >> >> >> Hope it helps. > > > > >> >> >> >> -- > > > > >> >> >> >> Chen > > > > > > >> >> >> >> On Sat, Jan 10, 2009 at 12:53 PM, gowtham gowda < > > > gowth...@gmail.com> wrote: > > > > > > >> >> >> >> > Thanks for the reply, > > > > > > >> >> >> >> > one more info, how do we add modules to compile the > kernel > > > when we > > > > >> >> >> >> > select the <M> option in make menuconfig. > > > > > > >> >> >> >> > Thanks, > > > > >> >> >> >> > gowthsm > > > > > > >> >> >> >> > On Jan 9, 11:44 pm, "Chen Yang" <sunsety...@gmail.com> > > > wrote: > > > > >> >> >> >> >> Sorry, I forgot to put the required information to > that > > > step: > > > > > > >> >> >> >> >> After that, you should save the .config > > > > >> >> >> >> >> $make bzImage > > > > >> >> >> >> >> Then copy the kernel to vendor/asus/eee_701 > > > > >> >> >> >> >> $cp arch/x86/boot/bzImage > ../vendor/asus/eee_701/kernel > > > > > > >> >> >> >> >> Then you can start build the installer_img again. > After > > > that use your > > > > >> >> >> >> >> installer.img to install in vmware/virtualbox again. > > > > > > >> >> >> >> >> Hope it helps! > > > > >> >> >> >> >> -- > > > > >> >> >> >> >> Chen > > > > > > >> >> >> >> >> On Sat, Jan 10, 2009 at 12:21 PM, gowtham gowda < > > > gowth...@gmail.com> wrote: > > > > > > >> >> >> >> >> > After "make menuconfig" > > > > >> >> >> >> >> > should we just save .config file or should we run > "make" > > > to compile a > > > > >> >> >> >> >> > new kernel. > > > > > > >> >> >> >> >> > Thanks, > > > > > > >> >> >> >> >> > Gowtham > > > > > > >> >> >> >> >> > On Jan 9, 3:28 am, "Chen Yang" < > sunsety...@gmail.com> > > > wrote: > > > > >> >> >> >> >> >> Some additions to build the kernel for > > > VMWare/VirtualBox: > > > > > > >> >> >> >> >> >> Hope it helps: > > > > >> >> >> >> >> >> $cd mydroid > > > > >> >> >> >> >> >> $cp vendor/asus/eee_701/kernel.config > kernel/.config > > > > >> >> >> >> >> >> $cd kernel > > > > >> >> >> >> >> >> $make menuconfig > > > > > > >> >> >> >> >> >> Select the device drivers: > > > > > > >> >> >> >> >> >> For network card: > > > > >> >> >> >> >> >> network device support -> > > > > >> >> >> >> >> >> Ethernet (10 or 100Mbit) ---> > > > > >> >> >> >> >> >> [*] EISA, VLB, PCI and on board > controllers > > > > >> >> >> >> >> >> <*> AMD PCnet32 PCI support > > > > > > >> >> >> >> >> >> For VESAFB: > > > > >> >> >> >> >> >> Graphics support ---> > > > > >> >> >> >> >> >> <*> Support for frame buffer devices ---> > > > > >> >> >> >> >> >> [*] VESA VGA graphics support > > > > >> >> >> >> >> >> Console display driver support ---> > > > > >> >> >> >> >> >> <*> Framebuffer Console support > > > > >> >> >> >> >> >> [*] Select compiled-in fonts > > > > >> >> >> >> >> >> [*] VGA 8x8 font > > > > >> >> >> >> >> >> [*] VGA 8x16 font > > > > > > >> >> >> >> >> >> In order to build correctly with 2.6.27, you may > apply > > > the patch from here:http://review.source.android.com/6751 > > > > > > >> >> >> >> >> >> For command line option of vga=788, several > approaches: > > > > >> >> >> >> >> >> 1. append the option when the system boots, when it > > > shows the menu, > > > > >> >> >> >> >> >> you can press 'e' to edit the default entry(2). > then > > > 'd' to delete the > > > > >> >> >> >> >> >> first option line: "cmdline ... ", then 'e' the 0 > > > entry, which is the > > > > >> >> >> >> >> >> line of " kernel --use-cmd ...", > > > > >> >> >> >> >> >> remove the "--use-cmd-line" and append the option > > > > >> >> >> >> >> >> "androidboot.hardware=eee_701 vga=788" at end of > that > > > line > > > > >> >> >> >> >> >> then choose boot. It will enter the vesafb mode > > > correctly. But you > > > > >> >> >> >> >> >> may need to edit it every time when boot. > > > > > > >> >> >> >> >> >> 2. modify the cmdline in /dev/block/sda3, you can > mount > > > it after you > > > > >> >> >> >> >> >> have successfully boot. to append "vga=788" to > cmdline > > > file: > > > > >> >> >> >> >> >> #mkdir /data/boot > > > > >> >> >> >> >> >> #mount -t ext2 /dev/block/sda3 /data/boot > > > > >> >> >> >> >> >> #echo " vga=788" >/data/boot/cmdline > > > > >> >> >> >> >> >> #umount /data/boot > > > > >> >> >> >> >> >> then reboot the vm > > > > > > >> >> >> >> >> >> 3. modify the cmdline creation step in the build, i > > > think you can get > > > > >> >> >> >> >> >> the in bootable/diskinstaller/config.mk, then you > may > > > need to rebuild > > > > >> >> >> >> >> >> the instaler.img and reinstall it to your vm. > > > > > > >> >> >> >> >> >> Hope it helps! > > > > >> >> >> >> >> >> -- > > > > >> >> >> >> >> >> Chen > > > > > > >> >> >> >> >> >> On Fri, Jan 9, 2009 at 9:23 AM, rukiman < > > > ruksh...@optushome.com.au> wrote: > > > > > > >> >> >> >> >> >> > I have got as far as booting Android in VMware > > > > ... > > > > read more ยป > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
