I suppose ramdisk mounting could  be one of those reason why script
files are not able to execute, you better have to move the ramdisk
where it does not overlap with kernel and ram filesystem, as kernel
always relocates when it starts booting, therefore you better make
sure there is 8M to 16M difference between kernel and ramdisk.

-Subbu

On Thu, Jul 1, 2010 at 8:07 AM, fpirou <fpi...@googlemail.com> wrote:
> Thanks for your help.
>
> below the u-boot command line I run :
> setenv bootargs_android 'setenv bootargs ${bootargs} init=/init
> androidboot.console=ttymxc0 wvga calibration'
> setenv bootargs_base 'setenv bootargs mem=64M rootwait
> console=ttymxc0,115200'
> setenv bootargs_SD 'setenv bootargs ${bootargs} root=/dev/mmcblk0p2'
> setenv bootcmd_SD1 'run bootargs_base bootargs_android bootargs_SD'
> setenv bootcmd_SD2 'mmc read 0 ${loadaddr} 0x800 0x1280;mmc read 0 $
> {rd_loadaddr} 0x2000 0x258;bootm ${loadaddr} ${rd_loadaddr}'
> setenv bootcmd 'run bootcmd_SD1 bootcmd_SD2'
> setenv loadaddr 0x80100000
> setenv rd_loadaddr 0x80400000
>
> About nfs, I don't is a root cause here, since I have the same error
> message (init.rc : invalid option) with android 2.1 file system on SD
> card ext2 partitionned (/dev/mmcblk0p2).
>
> Do you think it can come from ramDisk mounting problem, because I have
> got this message at linux loading time?
> INITRD: 0x80400040+0x000325b4 overlaps in-use memory region -
> disabling initrd
>
> I have read the Android 2.1 requires 128MB of SDRAM, this board has on
> 64MB? if yes, Which version of Android will I be able to run with 64MB
> SDRAM?
>
> Find below my init.rc file:
>
> on init
>
> sysclktz 0
>
> loglevel 3
> service logcat /system/bin/logcat -f /dev/kmsg
>
> # setup the global environment
>    export PATH /sbin:/system/sbin:/system/bin:/system/xbin
>    export LD_LIBRARY_PATH /system/lib
>    export ANDROID_BOOTLOGO 1
>    export ANDROID_ROOT /system
>    export ANDROID_ASSETS /system/app
>    export ANDROID_DATA /data
>    export EXTERNAL_STORAGE /sdcard
>    export BOOTCLASSPATH /system/framework/core.jar:/system/framework/
> ext.jar:/system/framework/framework.jar:/system/framework/
> android.policy.jar:/system/framework/services.jar
>
> # Backward compatibility
>    symlink /system/etc /etc
>
> # create mountpoints and mount tmpfs on sqlite_stmt_journals
>    mkdir /sdcard 0000 system system
>    mkdir /system
>    mkdir /data 0771 system system
>    mkdir /cache 0770 system cache
>    mkdir /sqlite_stmt_journals 01777 root root
>    mount tmpfs tmpfs /sqlite_stmt_journals size=4m
>
> #    mount rootfs rootfs / ro remount
>
>    write /proc/sys/kernel/panic_on_oops 1
>    write /proc/sys/kernel/hung_task_timeout_secs 0
>    write /proc/cpu/alignment 4
>    write /proc/sys/kernel/sched_latency_ns 10000000
>    write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
>    write /proc/sys/kernel/sched_compat_yield 1
>
> # Create cgroup mount points for process groups
>    mkdir /dev/cpuctl
>    mount cgroup none /dev/cpuctl cpu
>    chown sytem system /dev/cpuctl
>    chown system system /dev/cpuctl/tasks
>    chmod 0777 /dev/cpuctl/tasks
>    write /dev/cpuctl/cpu.shares 1024
>
>    mkdir /dev/cpuctl/fg_boost
>    chown system system /dev/cpuctl/fg_boost/tasks
>    chmod 0777 /dev/cpuctl/fg_boost/tasks
>    write /dev/cpuctl/fg_boost/cpu.shares 1024
>
>    mkdir /dev/cpuctl/bg_non_interactive
>    chown system system /dev/cpuctl/bg_non_interactive/tasks
>    chmod 0777 /dev/cpuctl/bg_non_interactive/tasks
>    # 5.0 %
>    write /dev/cpuctl/bg_non_interactive/cpu.shares 52
>
> # mount mtd partitions
>    # Mount /system rw first to give the filesystem a chance to save a
> checkpoint
>    mount ubifs ubi0:system /system
> #    mount ubifs ubi0:system /system ro remount
>
>    # We chown/chmod /data again so because mount is run as root +
> defaults
>    mount ubifs ubi0:data /data nosuid nodev
>    chown system system /data
>    chmod 0771 /data
>
>    # Same reason as /data above
>    mount yaffs2 m...@cache /cache nosuid nodev
>    chown system cache /cache
>    chmod 0770 /cache
>
>    # This may have been created by the recovery system with odd
> permissions
>    chown system system /cache/recovery
>    chmod 0770 /cache/recovery
>
> # create basic filesystem structure
>    mkdir /data/misc 01771 system misc
>    mkdir /data/misc/hcid 0770 bluetooth bluetooth
>    mkdir /data/misc/keystore 0770 keystore keystore
>    mkdir /data/misc/vpn 0770 system system
>    mkdir /data/misc/vpn/profiles 0770 system system
>    # give system access to wpa_supplicant.conf for backup and restore
>    mkdir /data/misc/wifi 0770 wifi wifi
>    chmod 0770 /data/misc/wifi
>    chmod 0660 /data/misc/wifi/wpa_supplicant.conf
>    mkdir /data/local 0771 shell shell
>    mkdir /data/local/tmp 0771 shell shell
>    mkdir /data/data 0771 system system
>    mkdir /data/app-private 0771 system system
>    mkdir /data/app 0771 system system
>    mkdir /data/property 0700 root root
>
>    # create dalvik-cache and double-check the perms
>    mkdir /data/dalvik-cache 0771 system system
>    chown system system /data/dalvik-cache
>    chmod 0771 /data/dalvik-cache
>
>    # create the lost+found directories, so as to enforce our
> permissions
>    mkdir /data/lost+found 0770
>    mkdir /cache/lost+found 0770
>
>    # double check the perms, in case lost+found already exists, and
> set owner
>    chown root root /data/lost+found
>    chmod 0770 /data/lost+found
>    chown root root /cache/lost+found
>    chmod 0770 /cache/lost+found
>
>    # change permission for keymap file temporarily
>    # should be removed when working out keymap later
>    chmod 0777 /system/usr/keychars/qwerty.kcm.bin
>    chmod 0777 /system/usr/keychars/mxckpd.kcm.bin
>
> on boot
> # basic network init
>    ifup lo
>    hostname localhost
>    domainname localdomain
>
>    mkdir /data/system 0775 system system
>    exec /sbin/ts_calibrator
>
> # set RLIMIT_NICE to allow priorities from 19 to -20
>    setrlimit 13 40 40
>
> # Set timeout value for rmnet stats.
>    write /sys/devices/virtual/net/rmnet0/timeout_suspend 5000000
>
> # Define the oom_adj values for the classes of processes that can be
> # killed by the kernel.  These are used in ActivityManagerService.
>    setprop ro.FOREGROUND_APP_ADJ 0
>    setprop ro.VISIBLE_APP_ADJ 1
>    setprop ro.SECONDARY_SERVER_ADJ 2
>    setprop ro.BACKUP_APP_ADJ 2
>    setprop ro.HOME_APP_ADJ 4
>    setprop ro.HIDDEN_APP_MIN_ADJ 7
>    setprop ro.CONTENT_PROVIDER_ADJ 14
>    setprop ro.EMPTY_APP_ADJ 15
>
> # Define the memory thresholds at which the above process classes will
> # be killed.  These numbers are in pages (4k).
>    setprop ro.FOREGROUND_APP_MEM 1536
>    setprop ro.VISIBLE_APP_MEM 2048
>    setprop ro.SECONDARY_SERVER_MEM 4096
>    setprop ro.BACKUP_APP_MEM 4096
>    setprop ro.HOME_APP_MEM 4096
>    setprop ro.HIDDEN_APP_MEM 5120
>    setprop ro.CONTENT_PROVIDER_MEM 5632
>    setprop ro.EMPTY_APP_MEM 6144
>
> # Write value must be consistent with the above properties.
> # Note that the driver only supports 6 slots, so we have HOME_APP at
> the
> # same memory level as services.
>    write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15
>
>    write /proc/sys/vm/overcommit_memory 1
>    write /proc/sys/vm/min_free_order_shift 4
>    write /sys/module/lowmemorykiller/parameters/minfree
> 1536,2048,4096,5120,5632,6144
>
>    # Set init its forked children's oom_adj.
>    write /proc/1/oom_adj -16
>
>    # Permissions for System Server and daemons.
>    chown radio system /sys/android_power/state
>    chown radio system /sys/android_power/request_state
>    chown radio system /sys/android_power/acquire_full_wake_lock
>    chown radio system /sys/android_power/acquire_partial_wake_lock
>    chown radio system /sys/android_power/release_wake_lock
>    chown radio system /sys/power/state
>    chown radio system /sys/power/wake_lock
>    chown radio system /sys/power/wake_unlock
>    chmod 0660 /sys/power/state
>    chmod 0660 /sys/power/wake_lock
>    chmod 0660 /sys/power/wake_unlock
>    chown system system /sys/class/timed_output/vibrator/enable
>    chown system system /sys/class/leds/keyboard-backlight/brightness
>    chown system system /sys/class/leds/lcd-backlight/brightness
>    chown system system /sys/class/leds/button-backlight/brightness
>    chown system system /sys/class/leds/jogball-backlight/brightness
>    chown system system /sys/class/leds/red/brightness
>    chown system system /sys/class/leds/green/brightness
>    chown system system /sys/class/leds/blue/brightness
>    chown system system /sys/class/leds/red/device/grpfreq
>    chown system system /sys/class/leds/red/device/grppwm
>    chown system system /sys/class/leds/red/device/blink
>    chown system system /sys/class/leds/red/brightness
>    chown system system /sys/class/leds/green/brightness
>    chown system system /sys/class/leds/blue/brightness
>    chown system system /sys/class/leds/red/device/grpfreq
>    chown system system /sys/class/leds/red/device/grppwm
>    chown system system /sys/class/leds/red/device/blink
>    chown system system /sys/class/timed_output/vibrator/enable
>    chown system system /sys/module/sco/parameters/disable_esco
>    chown system system /sys/kernel/ipv4/tcp_wmem_min
>    chown system system /sys/kernel/ipv4/tcp_wmem_def
>    chown system system /sys/kernel/ipv4/tcp_wmem_max
>    chown system system /sys/kernel/ipv4/tcp_rmem_min
>    chown system system /sys/kernel/ipv4/tcp_rmem_def
>    chown system system /sys/kernel/ipv4/tcp_rmem_max
>    chown root radio /proc/cmdline
>
> # Define TCP buffer sizes for various networks
> #   ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
>    setprop net.tcp.buffersize.default
> 4096,87380,110208,4096,16384,110208
>    setprop net.tcp.buffersize.wifi
> 4095,87380,110208,4096,16384,110208
>    setprop net.tcp.buffersize.umts
> 4094,87380,110208,4096,16384,110208
>    setprop net.tcp.buffersize.edge
> 4093,26280,35040,4096,16384,35040
>    setprop net.tcp.buffersize.gprs    4092,8760,11680,4096,8760,11680
>
> # Prepare for wifi
> #
>    setprop wifi.interface wlan0
>    mkdir /data/misc/wifi 0770 system system
>    mkdir /data/misc/wifi/sockets 0770 system system
>    mkdir /data/misc/dhcp 0770 dhcp dhcp
>    chown dhcp dhcp /data/misc/dhcp
>
> # Prepare for bluetooth
>    chmod 666 /sys/class/rfkill/rfkill0/state
>    chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
>    write /sys/class/rfkill/rfkill0/state 0
>
>    class_start default
>
> ## Daemon processes to be run by init.
> ##
> service console /system/bin/sh
>    console
>
> # adbd is controlled by the persist.service.adb.enable system property
> service adbd /sbin/adbd
>    disabled
>
> # adbd on at boot in emulator
> on property:ro.kernel.qemu=1
>    start adbd
>
> on property:persist.service.adb.enable=1
>    start adbd
>
> on property:persist.service.adb.enable=0
>    stop adbd
>
> service servicemanager /system/bin/servicemanager
>    user system
>    critical
>    onrestart restart zygote
>    onrestart restart media
>
> service vold /system/bin/vold
>    socket vold stream 0660 root mount
>
> service nexus /system/bin/nexus
>    socket nexus stream 0660 root system
>    disabled
>
> #service mountd /system/bin/mountd
> #    socket mountd stream 0660 root mount
>
> service debuggerd /system/bin/debuggerd
>
> service ril-daemon /system/bin/rild
>    socket rild stream 660 root radio
>    socket rild-debug stream 660 radio system
>    user root
>    group radio cache inet misc
>
> service zygote /system/bin/app_process -Xzygote /system/bin --zygote --
> start-system-server
>    socket zygote stream 666
>    onrestart write /sys/android_power/request_state wake
>    onrestart write /sys/power/state on
>
> service media /system/bin/mediaserver
>    user media
>    group system audio camera graphics inet net_bt net_bt_admin
>
> #service bootsound /system/bin/playmp3
> #    user media
> #    group audio
> #    oneshot
>
> #service bootanim /system/bin/bootanimation
> #    user graphics
> #    group graphics
> #    disabled
> #    oneshot
>
> service dbus /system/bin/dbus-daemon --system --nofork
>    socket dbus stream 660 bluetooth bluetooth
>    user bluetooth
>    group bluetooth net_bt_admin
>
> service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
>    socket bluetooth stream 660 bluetooth bluetooth
>    socket dbus_bluetooth stream 660 bluetooth bluetooth
>    # init.rc does not yet support applying capabilities, so run as
> root and
>    # let hcid drop uid to bluetooth with the right linux capabilities
>    group bluetooth net_bt_admin misc
>    disabled
>
> service hciattach /system/bin/logwrapper /system/bin/sh /system/etc/
> bluez/mxc_bt.sh
>    user bluetooth
>    group bluetooth net_bt_admin
>    disabled
>    oneshot
>
> service hfag /system/bin/sdptool add --channel=10 HFAG
>    user bluetooth
>    group bluetooth net_bt_admin
>    disabled
>    oneshot
>
> service hsag /system/bin/sdptool add --channel=11 HSAG
>    user bluetooth
>    group bluetooth net_bt_admin
>    disabled
>    oneshot
>
> service installd /system/bin/installd
>    socket installd stream 600 system system
>
> service flash_recovery /system/bin/flash_image recovery /system/
> recovery.img
>    oneshot
>
> service racoon /system/bin/racoon
>    socket racoon stream 600 system system
>    # racoon will setuid to vpn after getting necessary resources.
>    group net_admin keystore
>    disabled
>    oneshot
>
> service mtpd /system/bin/mtpd
>    socket mtpd stream 600 system system
>    user vpn
>    group vpn net_admin net_raw
>    disabled
>    oneshot
>
> service keystore /system/bin/keystore
>    user keystore
>    group keystore
>    socket keystore stream 666
>
> service dhcpcd /system/bin/logwrapper /system/bin/dhcpcd -d wlan0
>    disabled
>    oneshot
>
> service wpa_supplicant /system/bin/logwrapper /system/bin/
> wpa_supplicant \
>    -Dwext -iwlan0 -c/data/misc/wifi/wpa_supplicant.conf
>    user root
>    group wifi inet system
>    socket wpa_wlan0 dgram 660 system system
>    oneshot
>
>
> On 29 juin, 18:12, Sean McNeil <seanmcne...@gmail.com> wrote:
>> My guess would be something regarding nfs options that make the file not
>> interpreted as a unix file. Either that, or theinit.rcis improperly
>> formed.
>>
>> On 06/29/2010 10:32 PM, fpirou wrote:
>>
>> > Do you have any idea why the init process does not interpret the
>> >init.rccommand file (invalid option)?
>
> --
> 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

Reply via email to