have a simpler init, like init=/system/bin/sh first, then run init from the
console, doing a /init & may be after doing a logcat, You will have more
info as to why it fails.

2009/4/16 hari uppalapati <hari.andr...@gmail.com>

> hi
> try with the following bootargs
> setenv bootargs console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
> video=omapfb:mode:1280x...@50 init=/init rw rootdelay=1 nohz=off
> regards
> Haritha
>
> 2009/4/15 Skuld <skul...@gmail.com>
>
>
>> Dear Rupesh:
>>
>> My manifest file are form Android.git.kernel.org.
>> Can't I latest new version ?
>> My boot command :
>> console=ttyS2,115200n8 console=ttyS0 noinitrd root=/dev/mmcblk0p2
>> rootfstype=ext3 rw rootdelay=3 nohz=off init=/init
>>
>> I boot system with SD card and linux file system in SD partition 2.
>> Thank you
>>
>>
>> On 4月15日, 下午10時09分, Rupesh Gujare <rupeshguj...@gmail.com> wrote:
>> > Did you replaced manifest file withhttp://
>> labs.embinux.org/images/9/91/Manifest18032009.xml? What are your
>> > boot args ?
>> >
>> > --
>> > Rupesh Gujare
>> >
>> > On Wed, Apr 15, 2009 at 10:43 AM, Skuld <skul...@gmail.com> wrote:
>> >
>> > > Hi :
>> >
>> > > I base
>> > >
>> http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board
>> > > steps to port Android System to beagle board.
>> > > I download android source code on 2009/04/09.
>> > > It boot kernel and execute init file happen error message.
>> >
>> > > How to fix it? Or any suggestions?
>> >
>> > > Error Message:
>> >
>> > > Starting kernel ...
>> >
>> > > Uncompressing
>> >
>> > >
>> Linux...............................................................................................................................
>> > > done, booting the kernel.
>> >
>> > > Linux version 2.6.27-omap1-05246-g5d103de-dirty (sk...@skuld-desktop)
>> > > (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #1 Wed
>> > > Apr 15 10:04:06 CST 2009
>> >
>> > > CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
>> >
>> > > Machine: OMAP3 Beagle Board
>> >
>> > > Memory policy: ECC disabled, Data cache writeback
>> >
>> > > OMAP3430 ES2.1
>> >
>> > > SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
>> >
>> > > CPU0: L1 I VIPT cache. Caches unified at level 2, coherent at level 3
>> >
>> > > CPU0: Level 1 cache is separate instruction and data
>> >
>> > > CPU0: I cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
>> >
>> > >      supports RA
>> >
>> > > CPU0: D cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
>> >
>> > >      supports RA WB WT
>> >
>> > > CPU0: Level 2 cache is unified
>> >
>> > > CPU0: unified cache: 262144 bytes, associativity 8, 64 byte lines, 512
>> > > sets,
>> >
>> > >      supports WA RA WB WT
>> >
>> > > Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>> > > 32512
>> >
>> > > Kernel command line: console=ttyS2,115200n8 console=ttyS0 noinitrd
>> > > root=/dev/mmcblk0p2 rootfstype=ext3 rw rootdelay=3 nohz=off init=/init
>> > > omapfb.video_mode=1366x768mr...@69 omapfb.debug=y
>> >
>> > > Unknown boot option `omapfb.video_mode=1366x768mr...@69': ignoring
>> >
>> > > Unknown boot option `omapfb.debug=y': ignoring
>> >
>> > > clock: virt_vdd1_prcm_set: missing clockdomain<3>clock:
>> > > virt_vdd2_prcm_set: missing clockdomain<6>Clocking rate (Crystal/DPLL/
>> > > ARM core): 26.0/332/500 MHz
>> >
>> > > resource_request: Invalid resource name
>> >
>> > > GPMC revision 5.0
>> >
>> > > IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
>> >
>> > > Total of 96 interrupts on 1 active controller
>> >
>> > > OMAP34xx GPIO hardware version 2.5
>> >
>> > > PID hash table entries: 512 (order: 9, 2048 bytes)
>> >
>> > > OMAP clockevent source: GPTIMER12 at 32768 Hz
>> >
>> > > Console: colour dummy device 80x30
>> >
>> > > Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
>> >
>> > > Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
>> >
>> > > Memory: 128MB = 128MB total
>> >
>> > > Memory: 125296KB available (3652K code, 668K data, 148K init)
>> >
>> > > Calibrating delay loop... 498.87 BogoMIPS (lpj=1945600)
>> >
>> > > Mount-cache hash table entries: 512
>> >
>> > > CPU: Testing write buffer coherency: ok
>> >
>> > > net_namespace: 288 bytes
>> >
>> > > NET: Registered protocol family 16
>> >
>> > > resource_request: Invalid resource name
>> >
>> > > Found NAND on CS0
>> >
>> > > Registering NAND on CS0
>> >
>> > > Switched to new clocking rate (Crystal/DPLL3/MPU): 26.0/332/166 MHz
>> >
>> > > OMAP DMA hardware revision 4.0
>> >
>> > > USB: No board-specific platform config found
>> >
>> > > i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
>> >
>> > > twl4030: PIH (irq 7) chaining IRQs 368..375
>> >
>> > > twl4030: power (irq 373) chaining IRQs 376..383
>> >
>> > > twl4030: gpio (irq 368) chaining IRQs 384..401
>> >
>> > > i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
>> >
>> > > twl4030_usb twl4030_usb: Initialized TWL4030 USB module
>> >
>> > > SCSI subsystem initialized
>> >
>> > > usbcore: registered new interface driver usbfs
>> >
>> > > usbcore: registered new interface driver hub
>> >
>> > > usbcore: registered new device driver usb
>> >
>> > > musb_hdrc: version 6.0, musb-dma, host, debug=0
>> >
>> > > musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92
>> >
>> > > musb_hdrc musb_hdrc: MUSB HDRC host driver
>> >
>> > > musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
>> >
>> > > usb usb1: configuration #1 chosen from 1 choice
>> >
>> > > hub 1-0:1.0: USB hub found
>> >
>> > > hub 1-0:1.0: 1 port detected
>> >
>> > > NET: Registered protocol family 2
>> >
>> > > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>> >
>> > > TCP established hash table entries: 4096 (order: 3, 32768 bytes)
>> >
>> > > TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
>> >
>> > > TCP: Hash tables configured (established 4096 bind 4096)
>> >
>> > > TCP reno registered
>> >
>> > > NET: Registered protocol family 1
>> >
>> > > NetWinder Floating Point Emulator V0.97 (double precision)
>> >
>> > > ashmem: initialized
>> >
>> > > VFS: Disk quotas dquot_6.5.1
>> >
>> > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>> >
>> > > JFFS2 version 2.2. (NAND) (c) 2001-2006 Red Hat, Inc.
>> >
>> > > msgmni has been set to 245
>> >
>> > > io scheduler noop registered
>> >
>> > > io scheduler anticipatory registered (default)
>> >
>> > > io scheduler deadline registered
>> >
>> > > io scheduler cfq registered
>> >
>> > > omapfb: configured for panel omap3beagle
>> >
>> > > omapfb: DISPC version 3.0 initialized
>> >
>> > > Console: switching to colour frame buffer device 160x45
>> >
>> > > omapfb: Framebuffer initialized. Total vram 3686400 planes 1
>> >
>> > > omapfb: Pixclock 72000 kHz hfreq 50.0 kHz vfreq 67.4 Hz
>> >
>> > > Serial: 8250/16550 driver4 ports, IRQ sharing enabled
>> >
>> > > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
>> >
>> > > serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
>> >
>> > > serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
>> >
>> > > console [ttyS2] enabled
>> >
>> > > brd: module loaded
>> >
>> > > loop: module loaded
>> >
>> > > logger: created 64K log 'log_main'
>> >
>> > > logger: created 256K log 'log_events'
>> >
>> > > logger: created 64K log 'log_radio'
>> >
>> > > usb 1-1: new high speed USB device using musb_hdrc and address 2
>> >
>> > > usb 1-1: configuration #1 chosen from 1 choice
>> >
>> > > hub 1-1:1.0: USB hub found
>> >
>> > > hub 1-1:1.0: 4 ports detected
>> >
>> > > usb 1-1.1: new high speed USB device using musb_hdrc and address 3
>> >
>> > > usb 1-1.1: configuration #1 chosen from 1 choice
>> >
>> > > usb 1-1.3: new low speed USB device using musb_hdrc and address 4
>> >
>> > > usb 1-1.3: configuration #1 chosen from 1 choice
>> >
>> > > eth0: register 'asix' at usb-musb_hdrc-1.1, ASIX AX88772A USB 2.0
>> > > Ethernet, 00:08:54:a6:6d:25
>> >
>> > > usbcore: registered new interface driver asix
>> >
>> > > usbcore: registered new interface driver cdc_ether
>> >
>> > > usbcore: registered new interface driver dm9601
>> >
>> > > usbcore: registered new interface driver net1080
>> >
>> > > usbcore: registered new interface driver cdc_subset
>> >
>> > > usbcore: registered new interface driver zaurus
>> >
>> > > Linux video capture interface: v2.00
>> >
>> > > usbcore: registered new interface driver uvcvideo
>> >
>> > > USB Video Class driver (v0.1.0)
>> >
>> > > i2c /dev entries driver
>> >
>> > > Driver 'sd' needs updating - please use bus_type methods
>> >
>> > > omap2-nand driver initializing
>> >
>> > > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xb1 (Micron NAND 128MiB
>> > > 1,8V 16-bit)
>> >
>> > > cmdlinepart partition parsing not available
>> >
>> > > Creating 5 MTD partitions on "omap2-nand":
>> >
>> > > 0x00000000-0x00080000 : "X-Loader"
>> >
>> > > 0x00080000-0x00260000 : "U-Boot"
>> >
>> > > 0x00260000-0x00280000 : "U-Boot Env"
>> >
>> > > 0x00280000-0x00680000 : "Kernel"
>> >
>> > > 0x00680000-0x08000000 : "File System"
>> >
>> > > usbmon: debugfs is not available
>> >
>> > > mice: PS/2 mouse device common for all mice
>> >
>> > > usbcore: registered new interface driver usbtouchscreen
>> >
>> > > twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
>> >
>> > > twl4030_rtc twl4030_rtc: Power up reset detected.
>> >
>> > > twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
>> >
>> > > OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
>> >
>> > > cpuidle: using governor menu
>> >
>> > > input: Logitech USB Receiver as /class/input/input0
>> >
>> > > input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-
>> > > musb_hdrc-1.3
>> >
>> > > Fixing up Logitech keyboard report descriptor
>> >
>> > > input: Logitech USB Receiver as /class/input/input1
>> >
>> > > input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-
>> > > musb_hdrc-1.3
>> >
>> > > usbcore: registered new interface driver usbhid
>> >
>> > > usbhid: v2.6:USB HID core driver
>> >
>> > > Advanced Linux Sound Architecture Driver Version 1.0.17.
>> >
>> > > ASoC version 0.13.2
>> >
>> > > OMAP3 Beagle SoC init
>> >
>> > > TWL4030 Audio Codec init
>> >
>> > > asoc: twl4030 <-> omap-mcbsp-dai mapping ok
>> >
>> > > ALSA device list:
>> >
>> > >  #0: omap3beagle (twl4030)
>> >
>> > > TCP cubic registered
>> >
>> > > NET: Registered protocol family 17
>> >
>> > > NET: Registered protocol family 15
>> >
>> > > RPC: Registered udp transport module.
>> >
>> > > RPC: Registered tcp transport module.
>> >
>> > > Power Management for TI OMAP3.
>> >
>> > > SmartReflex driver initialized
>> >
>> > > Disabling unused clock "sr2_fck"
>> >
>> > > Disabling unused clock "sr1_fck"
>> >
>> > > Disabling unused clock "mcbsp_fck"
>> >
>> > > Disabling unused clock "mcbsp_fck"
>> >
>> > > Disabling unused clock "mcbsp_fck"
>> >
>> > > Disabling unused clock "mcbsp_ick"
>> >
>> > > Disabling unused clock "mcbsp_ick"
>> >
>> > > Disabling unused clock "mcbsp_ick"
>> >
>> > > Disabling unused clock "gpt2_ick"
>> >
>> > > Disabling unused clock "gpt3_ick"
>> >
>> > > Disabling unused clock "gpt4_ick"
>> >
>> > > Disabling unused clock "gpt5_ick"
>> >
>> > > Disabling unused clock "gpt6_ick"
>> >
>> > > Disabling unused clock "gpt7_ick"
>> >
>> > > Disabling unused clock "gpt8_ick"
>> >
>> > > Disabling unused clock "gpt9_ick"
>> >
>> > > Disabling unused clock "wdt3_ick"
>> >
>> > > Disabling unused clock "wdt3_fck"
>> >
>> > > Disabling unused clock "gpio2_dbck"
>> >
>> > > Disabling unused clock "gpio3_dbck"
>> >
>> > > Disabling unused clock "gpio4_dbck"
>> >
>> > > Disabling unused clock "gpio5_dbck"
>> >
>> > > Disabling unused clock "gpio6_dbck"
>> >
>> > > Disabling unused clock "gpt9_fck"
>> >
>> > > Disabling unused clock "gpt8_fck"
>> >
>> > > Disabling unused clock "gpt7_fck"
>> >
>> > > Disabling unused clock "gpt6_fck"
>> >
>> > > Disabling unused clock "gpt5_fck"
>> >
>> > > Disabling unused clock "gpt4_fck"
>> >
>> > > Disabling unused clock "gpt3_fck"
>> >
>> > > Disabling unused clock "gpt2_fck"
>> >
>> > ...
>> >
>> > 閱讀更多 >>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to