The issue is resolved. Now i am using the root filesystem which is exoprted as an NFS mount .
Thanks, Shivananda On Apr 26, 12:48 am, Diego Torres Milano <[EMAIL PROTECTED]> wrote: > yaffs, what I guess is the initrd filesystem your are trying to mount > is not supported by the kernel. > Anyway, you'll find more issues if you are using a different kernel, > but at least initrd will be mounted. > > On Apr 22, 12:11 pm, shivanand <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > I am trying to get the android up and running on 2430. > > > But facing some issues while booting up with the android ramdisk > > filesystem . > > > Below error message is seen, > > > No filesystem could mount root, tried: ext3 ext2 msdos vfat > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > > block(1,0) > > > Steps followed : > > > 1. Did a diff b/w m5-rc14 2.6.23 kernel and Generic GIT 2.6.23 kernel. > > 2. Applied the above changes to OMAP 2430 supported 2.6.14 kernel. > > 3. Built the kernel and booted it up with the NFS successully. > > 4. Extracted the ramdisk filesystem from SDK(android-sdk_m5-rc14_linux- > > x86) > > 5.Set the bootargs to android ramdisk filesystem, > > 6. But while booting with this, fails with the below message. > > No filesystem could mount root, tried: ext3 ext2 msdos vfat > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > > block(1,0) > > > What could be the reason for this failure ? > > > Also one more generic doubt have is , m5-rc14 contians 2.6.23 based > > kernel ,where as my OMAP based kernel is 2.6.14.Will this have any > > issues later ? > > > Pls let me know your views. > > Regards, > > Shivanand > > > -------------------------------------------bootup log > > -------------------------------------------------- > > bootm > > ## Booting image at 80300000 ... > > Image Name: Linux-2.6.23-rc7-omap1 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1508864 Bytes = 1.4 MB > > Load Address: 80008000 > > Entry Point: 80008000 > > Verifying Checksum ... OK > > OK > > > Starting kernel ... > > > Uncompressing > > Linux............................................................. > > ...................................... done, booting the kernel. > > Linux version 2.6.23-rc7-omap1 (gcc versi > > on 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26)) #7 PREEMPT Thu Apr > > 17 21:10: > > 04 IST 2008 > > CPU: ARMv6-compatible processor [4107b366] revision 6 (ARMv6TEJ), > > cr=00c5387f > > Machine: OMAP2430 sdp2430 board > > Memory policy: ECC disabled, Data cache writeback > > OMAP24302 > > SRAM: Mapped pa 0x40200000 to va 0xd0000000 size: 0x100000 > > CPU0: D VIPT write-back cache > > CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets > > CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets > > Built 1 zonelists in Zone order. Total pages: 16256 > > Kernel command line: root=/dev/ram0 rw mem=64M console=ttyS0,115200n8 > > initrd=0x8 > > 0000000,ramdisk_size=4096,devfs=mount > > clock: Could not find parent clock iva2_1_fck in clksel array of clock > > iva2_1_ic > > k > > Clocking rate (Crystal/DPLL/MPU): 13.0/660/330 MHz > > Clock apll54_ck didn't lock in 100000 tries > > GPMC revision 3.0 > > IRQ: Found an INTC at 0xd80fe000 (revision 3.0) with 96 interrupts > > Total of 96 interrupts on 1 active controller > > OMAP243x GPIO hardware version 2.4 > > PID hash table entries: 256 (order: 8, 1024 bytes) > > Console: colour dummy device 80x30 > > Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) > > Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) > > Memory: 64MB = 64MB total > > Memory: 61464KB available (2792K code, 480K data, 124K init) > > Mount-cache hash table entries: 512 > > CPU: Testing write buffer coherency: ok > > NET: Registered protocol family 16 > > OneNAND: Unable to find oneNAND configuration in GPMC - not > > registering. > > OMAP DMA hardware revision 4.0 > > Initializing OMAP McBSP system > > omapdsp: could not acquire dsp_fck handle. > > USB: No board-specific platform config found > > i2c_omap i2c_omap.2: bus 2 rev3.7 at 2600 kHz > > i2c_omap i2c_omap.1: bus 1 rev3.7 at 400 kHz > > TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1] > > TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1] > > TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1] > > TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1] > > <6>TWL4030: Driver registration complete. > > NET: Registered protocol family 2 > > Time: gp timer clocksource has been installed. > > IP route cache hash table entries: 1024 (order: 0, 4096 bytes) > > TCP established hash table entries: 2048 (order: 2, 16384 bytes) > > TCP bind hash table entries: 2048 (order: 1, 8192 bytes) > > TCP: Hash tables configured (established 2048 bind 2048) > > TCP reno registered > > NetWinder Floating Point Emulator V0.97 (double precision) > > VFS: Disk quotas dquot_6.5.1 > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > > JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. > > io scheduler noop registered > > io scheduler anticipatory registered (default) > > io scheduler deadline registered > > io scheduler cfq registered > > omapfb: configured for panel sdp2430 > > omapfb: DISPC version 3.0 initialized > > Console: switching to colour frame buffer device 30x40 > > omapfb: Framebuffer initialized. Total vram 155648 planes 1 > > omapfb: Pixclock 5156 kHz hfreq 18.2 kHz vfreq 54.8 Hz > > omap_rng omap_rng: OMAP Random Number Generator ver. 50 > > Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing > > enabled > > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 > > console [ttyS0] enabled > > serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 > > serial8250.0: ttyS2 at MMIO 0x4806e000 (irq = 74) is a ST16654 > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize > > loop: module loaded > > smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[EMAIL PROTECTED]> > > eth0: SMC91C94 (rev 9) at c4850300 IRQ 309 [nowait] > > eth0: Ethernet addr: 10:20:30:40:50:61 > > i2c /dev entries driver > > TWL4030 GPIO Demux: IRQ Range 376 to 386, Initialization Success > > omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank > > omapflash.0: Found 1 x16 devices at 0x2000000 in 16-bit bank > > Intel/Sharp Extended Query Table at 0x010A > > Intel/Sharp Extended Query Table at 0x010A > > Intel/Sharp Extended Query Table at 0x010A > > Intel/Sharp Extended Query Table at 0x010A > > Intel/Sharp Extended Query Table at 0x010A > > Intel/Sharp Extended Query Table at 0x010A > > Using buffer write method > > cfi_cmdset_0001: Erase suspend on write enabled > > Creating 4 MTD partitions on "omapflash.0": > > 0x00000000-0x00040000 : "bootloader" > > 0x00040000-0x00060000 : "params" > > 0x00060000-0x00260000 : "kernel" > > 0x00260000-0x04000000 : "filesystem" > > OMAP2 OneNAND driver initializing > > input: omap_twl4030keypad as /class/input/input0 > > OMAP Watchdog Timer Rev 0x22: initial timeout 60 sec > > logger: created 64K log 'log_main' > > logger: created 64K log 'log_events' > > logger: created 64K log 'log_radio' > > TCP cubic registered > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > NET: Registered protocol family 15 > > Power Management for OMAP2 initializing > > PRCM revision 1.0 > > List of all partitions: > > 1f00 256 mtdblock0 (driver?) > > 1f01 128 mtdblock1 (driver?) > > 1f02 2048 mtdblock2 (driver?) > > 1f03 63104 mtdblock3 (driver?) > > No filesystem could mount root, tried: ext3 ext2 msdos vfat > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > > block(1,0) > > ----------------------------------------------end - > > bootup.log----------------------------------------------------- Hide quoted > > text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
