Ok I've tried Amit's init.rc and changed the loglevel to 8. Now my output is like this: """ request_suspend_state: wakeup (0->0) at 91406616215 (1970-01-02 00:01:11.733856) init: service 'media' is being killed init: starting 'media' init: waitpid returned pid 1156, status = 0000000f init: untracked pid 1156 exited init: starting 'zygote' init: Created socket '/dev/socket/zygote' with mode '666', user '0', group '0' init: starting 'pvr' init: waitpid returned pid 1209, status = 00000000 init: process 'pvr', pid 1209 exited init: process 'pvr' killing any children in process group init: starting 'pvr' init: starting 'bootanim' init: waitpid returned pid 1223, status = 00000000 init: process 'pvr', pid 1223 exited init: process 'pvr' killing any children in process group init: waitpid returned pid 1229, status = 00000009 init: process 'bootanim', pid 1229 exited init: waitpid returned pid 1203, status = 00000009 init: process 'zygote', pid 1203 exited init: process 'zygote' killing any children in process group """ Sorry for all the trouble caused... I think I'll try to build again on a fresh gingerbread. I'm supposed to use 'make install OMAPES=5.x' for SGX right?
On Jan 19, 4:43 pm, Deva R <r.deva...@gmail.com> wrote: > minimal init.rc is one with bare minimum one, good for bootup with > required commands and less services started., > Try the one Amit shared - omap3evm version should be good for beagle too., > > >The only loglevel I see in init.rc is 'loglevel 3', am I supposed to > >change it? > > You can set it to till 8. > more info -http://elinux.org/Android_Debugging#init_logging > > > > > > > > > > On Wed, Jan 19, 2011 at 12:09 PM, Amit Pundir <pundira...@gmail.com> wrote: > > On Tue, Jan 18, 2011 at 2:43 PM, BiX <bixt...@gmail.com> wrote: > >> Hi, I'm booting Android 2.3 on BeagleBoard with kernel Linux-2.6.32. > > >> However, I'm getting this warning: > >> """ > >> Warning: unable to open an initial > >> console. > >> init: /init.rc: 149: invalid option > >> 'root' > >> init: cannot open '/ > >> initlogo.rle' > >> init: cannot find '/system/etc/install-recovery.sh', disabling > >> 'flash_recovery' > >> """ > > > Hi, > > > There are some init.rc changes you need to take care of. I have > > attached mine which is working fine for omap3-evm. > > > Regards, > > Amit Pundir > > >> With repeated displaying of: > >> """ > >> 'request_suspend_state: wakeup (0->0)' & 'init: untracked pid exited' > >> """ > > >> This is my env: > >> """ > >> baudrate=115200 > >> loadaddr=0x80200000 > >> rdaddr=0x81600000 > >> console=ttyS2,115200n8 > >> optargs= > >> mmcargs=setenv bootargs console=${console} ${optargs} root=/dev/ > >> mmcblk0p2 rw rot > >> ramargs=setenv bootargs console=${console} ${optargs} root=/dev/ram0 > >> rw ramdiskM > >> ubifsargs=setenv bootargs console=${console} ${optargs} > >> root=ubi0:beagleroot ubs > >> jffs2args=setenv bootargs console=${console} ${optargs} root=/dev/ > >> mtdblock4 rw 2 > >> loadbootscript=fatload mmc 0 ${loadaddr} > >> boot.scr > >> bootscript=echo Running bootscript from mmc ...; autoscr $ > >> {loadaddr} > >> loaduimage=fatload mmc 0 ${loadaddr} > >> uImage.bin > >> loadramdisk=fatload mmc 0 ${rdaddr} > >> ramdisk.gz > >> ramboot=echo Booting from ramdisk.gz ...; run ramargs; bootm $ > >> {loadaddr} > >> nandboot=echo Booting from nand ...; run jffs2args; nand read $ > >> {loadaddr} 28000} > >> usbtty=cdc_acm > >> serial=5ac400030000000004013f8901001001 > >> bootcmd=mmc init;fatload mmc 0 80000000 uImage;bootm > >> 80000000 > >> dieid#=5ac400030000000004013f8901001001 > >> stdin=serial > >> stdout=serial > >> stderr=serial > >> mmcboot=mmc init;fatload mmc 0 0x80300000 uImage;bootm > >> 0x80300000 > >> bootargs=console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 init=/ > >> init rootfst2 > >> bootdelay=3 > >> """ > >> Is there something wrong with my configuration? > >> Thanks~ > > >> -- > >> unsubscribe: android-porting+unsubscr...@googlegroups.com > >> website:http://groups.google.com/group/android-porting > > > -- > > unsubscribe: android-porting+unsubscr...@googlegroups.com > > website:http://groups.google.com/group/android-porting > > -- > Regards, > Devawww.bittoggler.com -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
