hi, you mean to say the problem will be only in the system folder of the filesystem.so i need to change the init.rc file to make some changes to the filesystem.
On 4/1/10, hedwin <hedwin.kon...@gmail.com> wrote: > > Don't know if you changed your init.rc. From what I could see in the > init.rc in the aosp android tree is that it tries to mount the userdata > partition on the nandflash and when found mounts it. > Your log shows that your are using different partition names which seems to > indicate that the mount of the /data fails and that it then uses the /data > directory on your SD card which was > mounted ro. > > > On Thu, Apr 1, 2010 at 7:14 PM, Anil Sasidharan <anil...@gmail.com> wrote: > >> Hi, >> >> Would it possible for you to share the init.rc? >> >> Warm Regards, >> Anil >> >> On Thu, Apr 1, 2010 at 4:06 PM, anil <anilba...@gmail.com> wrote: >> > hi, >> > >> > there are two partitions for the kernel and the file system. the thing >> > is that the data folder is not able to write, but i gave rwx >> > permissions for the file system. As u see in the log message the >> > kernel is able to locate the file system, but the file system is not >> > coming up. Do we need to changes in file system according to the >> > board. >> > >> > thanks >> > anil >> > >> > On Mar 30, 12:38 am, hedwin <hedwin.kon...@gmail.com> wrote: >> >> Can it be that you use only one single partition for storing the root >> >> filesystem and /data because it seems to be that way. The >> >> root filesystem is mounted ro by init and if this contains the data >> >> directory as well then well android cannot write into /data. >> >> >> >> Also check the file permission of /etc/dbus.conf. It should work the >> way it >> >> is but as a workaround you can change it to read for >> >> all. >> >> >> >> On Mon, Mar 29, 2010 at 10:43 AM, anil <anilba...@gmail.com> wrote: >> >> > hello all, >> >> >> >> > This is Anil, i am very new to this group. when i try to port my >> >> > eclair into my devkit8000 board i am getting the following log >> >> > messages.please help me in this reguard. >> >> >> >> > the logcat message are as follows >> >> >> >> > reading uImage >> >> >> >> > 2167832 bytes read >> >> > ## Booting kernel from Legacy Image at 80200000 ... >> >> > Image Name: Linux-2.6.29-omap1 >> >> > Image Type: ARM Linux Kernel Image (uncompressed) >> >> > Data Size: 2167768 Bytes = 2.1 MB >> >> > Load Address: 80008000 >> >> > Entry Point: 80008000 >> >> > Verifying Checksum ... OK >> >> > Loading Kernel Image ... OK >> >> > OK >> >> >> >> > Starting kernel ... >> >> >> >> > Uncompressing >> >> >> >> > >> Linux............................................................................................................................................ >> >> > done, booting the kernel. >> >> > Linux version 2.6.29-omap1 (r...@trng-desktop) (gcc version 4.3.3 >> >> > (Sourcery G++ Lite 2009q1-203) ) #5 Thu Mar 25 13:35:36 IST 2010 >> >> > CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f >> >> > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache >> >> > Machine: OMAP3 Beagle Board >> >> > Memory policy: ECC disabled, Data cache writeback >> >> > L2 CACHE is enabled in bootloader >> >> > OMAP3430 ES3.1 >> >> > SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000 >> >> > Reserving 16777216 bytes SDRAM for VRAM >> >> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: >> >> > 32512 >> >> > Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/ >> >> > mmcblk0p2 omapdss.def_disp=4.3inch_lcd init=/init rootfstype=ext3 rw >> >> > rootdelay=1 nohz=off >> >> > Clocking rate (Crystal/DPLL/ARM core): 26.0/266/500 MHz >> >> > Reprogramming SDRC >> >> > dpll3_m2_clk rate change failed: -22 >> >> > GPMC revision 5.0 >> >> > IRQ: Found an INTC at 0xfa200000 (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: 108500KB available (3980K code, 723K data, 168K init) >> >> > Calibrating delay loop... 491.57 BogoMIPS (lpj=1921024) >> >> > Mount-cache hash table entries: 512 >> >> > CPU: Testing write buffer coherency: ok >> >> > net_namespace: 520 bytes >> >> > regulator: core version 0.5 >> >> > NET: Registered protocol family 16 >> >> > Found NAND on CS0 >> >> > Registering NAND on CS0 >> >> > OMAP DMA hardware revision 4.0 >> >> > bio: create slab <bio-0> at 0 >> >> > 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 >> >> > beagle_twl_gpio_setup:246 >> >> > twl4030_mmc_init:367 >> >> > twl4030_mmc_init:382 >> >> > regulator: VMMC1: 1850 <--> 3150 mV normal standby >> >> > regulator: VDAC: 1800 mV normal standby >> >> > regulator: VUSB1V5: 1500 <--> 0 mV normal standby >> >> > regulator: VUSB1V8: 1800 <--> 0 mV normal standby >> >> > regulator: VUSB3V1: 3100 <--> 0 mV normal standby >> >> > regulator: VPLL2: 1800 mV normal standby >> >> > regulator: VSIM: 1800 <--> 3000 mV normal standby >> >> > i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz >> >> > SCSI subsystem initialized >> >> > twl4030_usb twl4030_usb: Initialized TWL4030 USB module >> >> > usbcore: registered new interface driver usbfs >> >> > usbcore: registered new interface driver hub >> >> > usbcore: registered new device driver usb >> >> > Bluetooth: Core ver 2.15 >> >> > NET: Registered protocol family 31 >> >> > Bluetooth: HCI device and connection manager initialized >> >> > Bluetooth: HCI socket layer initialized >> >> > musb_hdrc: version 6.0, musb-dma, host, debug=0 >> >> > musb_hdrc: USB Host mode controller at fa0ab000 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: New USB device found, idVendor=1d6b, idProduct=0002 >> >> > usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >> >> > usb usb1: Product: MUSB HDRC host driver >> >> > usb usb1: Manufacturer: Linux 2.6.29-omap1 musb-hcd >> >> > usb usb1: SerialNumber: musb_hdrc >> >> > 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.2 >> >> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) >> >> > JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. >> >> > msgmni has been set to 212 >> >> > alg: No test for stdrng (krng) >> >> > io scheduler noop registered >> >> > io scheduler anticipatory registered (default) >> >> > io scheduler deadline registered >> >> > io scheduler cfq registered >> >> > OMAP DSS rev 2.0 >> >> > OMAP DISPC rev 3.0 >> >> > OMAP VENC rev 2 >> >> > Serial: 8250/16550 driver, 4 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 >> >> > dm9000 Ethernet Driver, V1.31 >> >> > Linux video capture interface: v2.00 >> >> > 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": >> >> > 0x000000000000-0x000000080000 : "X-Loader" >> >> > 0x000000080000-0x000000260000 : "U-Boot" >> >> > 0x000000260000-0x000000280000 : "U-Boot Env" >> >> > 0x000000280000-0x000000680000 : "Kernel" >> >> > 0x000000680000-0x000008000000 : "File System" >> >> > usbmon: debugfs is not available >> >> > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >> >> > ehci-omap ehci-omap.0: OMAP-EHCI Host Controller >> >> > ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 >> >> > ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 >> >> > ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 >> >> > usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 >> >> > usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 >> >> > usb usb2: Product: OMAP-EHCI Host Controller >> >> > usb usb2: Manufacturer: Linux 2.6.29-omap1 ehci_hcd >> >> > usb usb2: SerialNumber: ehci-omap.0 >> >> > usb usb2: configuration #1 chosen from 1 choice >> >> > hub 2-0:1.0: USB hub found >> >> > hub 2-0:1.0: 3 ports detected >> >> > Initializing USB Mass Storage driver... >> >> > usbcore: registered new interface driver usb-storage >> >> > USB Mass Storage support registered. >> >> > udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) >> >> > android init >> >> > input: gpio-keys as /devices/platform/gpio-keys/input/input0 >> >> > 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. >> >> > Bluetooth: Virtual HCI driver ver 1.2 >> >> > Bluetooth: HCI UART driver ver 2.2 >> >> > Bluetooth: HCI H4 protocol initialized >> >> > Bluetooth: HCI BCSP protocol initialized >> >> > Bluetooth: HCILL protocol initialized >> >> > Bluetooth: Broadcom Blutonium firmware driver ver 1.2 >> >> > usbcore: registered new interface driver bcm203x >> >> > Bluetooth: Digianswer Bluetooth USB driver ver 0.10 >> >> > usbcore: registered new interface driver bpa10x >> >> > Bluetooth: BlueFRITZ! USB driver ver 1.2 >> >> > usbcore: registered new interface driver bfusb >> >> > Bluetooth: Generic Bluetooth USB driver ver 0.5 >> >> > usbcore: registered new interface driver btusb >> >> > Bluetooth: Generic Bluetooth SDIO driver ver 0.1 >> >> > Registered led device: beagleboard::usr0 >> >> > Registered led device: beagleboard::usr1 >> >> > Registered led device: beagleboard::pmu_stat >> >> > usbcore: registered new interface driver usbhid >> >> > usbhid: v2.6:USB HID core driver >> >> > logger: created 64K log 'log_main' >> >> > logger: created 256K log 'log_events' >> >> > logger: created 64K log 'log_radio' >> >> > Advanced Linux Sound Architecture Driver Version 1.0.18a. >> >> > No device for DAI twl4030 >> >> > No device for DAI twl4030 Voice >> >> > No device for DAI twl4030 Clock >> >> > No device for DAI omap-mcbsp-dai-0 >> >> > No device for DAI omap-mcbsp-dai-1 >> >> > No device for DAI omap-mcbsp-dai-2 >> >> > No device for DAI omap-mcbsp-dai-3 >> >> > No device for DAI omap-mcbsp-dai-4 >> >> > OMAP3 Beagle SoC init >> >> > TWL4030 Audio Codec init >> >> > asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok >> >> > ALSA device list: >> >> > #0: omap3beagle (twl4030) >> >> > TCP cubic registered >> >> > NET: Registered protocol family 17 >> >> > NET: Registered protocol family 15 >> >> > Bluetooth: L2CAP ver 2.13 >> >> > Bluetooth: L2CAP socket layer initialized >> >> > Bluetooth: SCO (Voice Link) ver 0.6 >> >> > Bluetooth: SCO socket layer initialized >> >> > Bluetooth: RFCOMM socket layer initialized >> >> > Bluetooth: RFCOMM TTY layer initialized >> >> > Bluetooth: RFCOMM ver 1.11 >> >> > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 >> >> > Bluetooth: BNEP filters: protocol multicast >> >> > Bluetooth: HIDP (Human Interface Emulation) ver 1.2 >> >> > RPC: Registered udp transport module. >> >> > RPC: Registered tcp transport module. >> >> > Power Management for TI OMAP3. >> >> > VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev >> >> > 1 >> >> > Console: switching to colour frame buffer device 80x30 >> >> > mmc0: new SD card at address e624 >> >> > mmcblk0: mmc0:e624 SD01G 968 MiB >> >> > mmcblk0:<4>omapdss DPI: Could not find exact pixel clock. Requested >> >> > 23500 kHz, got 24000 kHz >> >> > p1 p2 >> >> > twl4030_rtc >> >> >> >> ... >> >> >> >> read more » >> > >> > -- >> > unsubscribe: >> > android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@googlegroups.com> >> > website: http://groups.google.com/group/android-kernel >> > >> > To unsubscribe, reply using "remove me" as the subject. >> > >> >> -- >> unsubscribe: >> android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@googlegroups.com> >> website: http://groups.google.com/group/android-kernel >> > > -- > unsubscribe: > android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-kernel > -- Thanks & Regards Anil 9740402107 -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
