Unable to open an initial console (Android 2.3 on BeagleBoard)

[BiX]

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'
"""

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~

[Deva R]

was 2.3 port working on beagle board earlier?
try with minimal init.rc

also, check init with more traces enabled ( change LOG_DEFAULT_LEVEL
system/core/init, via loglevel in init.rc)

> --
> unsubscribe: android-porti...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>

--
Regards,
Deva
www.bittoggler.com

[BiX]

Sorry I'm new to Linux and Android.
I followed this article http://blog.sola-dolphin-1.net/archives/3171603.html
for Android 2.3
There was no successful porting at all.
I'm not sure how to run with minimal init.rc
The only loglevel I see in init.rc is 'loglevel 3', am I supposed to
change it?

I tried logcat for further information and this is a snippet of it:
"""
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH in package
com.android.providers.contacts
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.cp in package
com.android.providers.contacts
W/PackageManager( 852): Unknown permission
com.google.android.gm.permission.WRITE_GMAIL in package
com.android.settings
W/PackageManager( 852): Unknown permission
com.google.android.gm.permission.READ_GMAIL in package
com.android.settings
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH in package
com.android.settings
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package
com.android.contacts
W/PackageManager( 852): Unknown permission
android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH in package
com.android.providers.calendar
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package
com.android.providers.calendar
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in
package com.android.development
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH in package
com.android.development
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in
package com.android.development
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in
package com.android.development
W/PackageManager( 852): Unknown permission
com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package
com.android.calendar
W/PackageManager( 852): Not granting permission
android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package
com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 852): Unknown permission
android.permission.READ_OWNER_DATA in package com.android.email
W/PackageManager( 852): Not granting permission
android.permission.DEVICE_POWER to package com.android.deskclock
(protectionLevel=2 flags=0x8be45)
D/dalvikvm( 852): GC_EXPLICIT freed 314K, 48% free 3299K/6343K,
external 716K/1038K, paused 52ms
I/SystemServer( 852): Account Manager
I/SystemServer( 852): Content Manager
I/SystemServer( 852): System Content Providers
I/ActivityThread( 852): Pub settings:
com.android.providers.settings.SettingsProvider
I/SystemServer( 852): Battery Service
W/dalvikvm( 852): No implementation found for native Lcom/android/
server/BatteryService;.native_update ()V
W/dalvikvm( 852): threadid=9: thread exiting with uncaught exception
(group=0x40015560)
D/SettingsProvider( 852): cache for settings table 'secure' rows=20;
fullycached=true
E/AndroidRuntime( 852): *** FATAL EXCEPTION IN SYSTEM PROCESS:
android.server.ServerThread
E/AndroidRuntime( 852): java.lang.UnsatisfiedLinkError: native_update
E/AndroidRuntime( 852): at
com.android.server.BatteryService.native_update(Native Method)
E/AndroidRuntime( 852): at
com.android.server.BatteryService.update(BatteryService.java:209)
E/AndroidRuntime( 852): at
com.android.server.BatteryService.<init>(BatteryService.java:135)
E/AndroidRuntime( 852): at
com.android.server.ServerThread.run(SystemServer.java:172)
I/Process ( 852): Sending signal. PID: 852 SIG: 9
E/AndroidRuntime( 852): Error reporting crash
E/AndroidRuntime( 852): java.lang.NullPointerException
E/AndroidRuntime( 852): at
android.os.DropBoxManager.isTagEnabled(DropBoxManager.java:288)
E/AndroidRuntime( 852): at
com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:
6775)
E/AndroidRuntime( 852): at
com.android.server.am.ActivityManagerService.handleApplicationCrash(ActivityManagerService.java:
6492)
E/AndroidRuntime( 852): at com.android.internal.os.RuntimeInit
$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 852): at
java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
E/AndroidRuntime( 852): at
java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)
I/Zygote ( 773): Exit zygote because system server (852) has
terminated
D/BootAnimation( 864): SurfaceFlinger died, exiting...
E/installd( 776): eof
E/installd( 776): failed to read size
I/installd( 776): closing connection

[Amit Pundir]

On Tue, Jan 18, 2011 at 2:43 PM, BiX <bix...@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

[Deva R]

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

--
Regards,
Deva
www.bittoggler.com

[BiX]

Hey Amit,

Thanks but your init does not work for me =(
I'm using omap 3530.
How do you attach files here btw?

On Jan 19, 2:39 pm, Amit Pundir <pundira...@gmail.com> wrote:

>  init.rc
> 21KViewDownload

[BiX]

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:

[Deva R]

can u share complete log? need to check where failure starts.,

i still feel the init.rc is not minimal

>init: process 'pvr', pid 1209

why do we start graphics hardware service? we can comment this.

[Amit Pundir]

On Wed, Jan 19, 2011 at 3:00 PM, BiX <bix...@gmail.com> wrote:

You are using Rowboat-kernel and SGX port?
then it should be either OMAPES=3.x or 2.x based on the CPU rev no. of
the BeagleBoard you have.

Also I have seen that initial port fails because of permission errors.
So to be on the safer side add all the permissions to the rootfs.

Regards,
Amit Pundir

[BiX]

Woohoo!!Trying a new build on a fresh copy turns out to be a good
idea!
Might have been an error somewhere while I was building it previously.
Android is booted up Yay~

I'm still getting these warnings though:

"""
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'

init: cannot find '/system/bin/sgx/rc.pvr', disabling
'pvr'
# warning: `zygote' uses 32-bit capabilities (legacy support in
use)
alarm_set_rtc: no RTC, time will be lost on
reboot
alarm_release: clear alarm, pending
0
request_suspend_state: wakeup (3->0) at 17242126467 (1970-01-02
00:00:03.382507)
init: untracked pid 801
exited
init: untracked pid 806 exited
"""
On the bright side, 'request_suspend_state' and 'init: untracked' only
appeared once and not repeatedly.
Thanks for all your help, Deva & Amit!!
Cheers!

On Jan 20, 12:01 am, Amit Pundir <pundira...@gmail.com> wrote: