Find the answer to your Linux question:
Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    query about kernel zImage and rootfs on s3c2440

    Hi All,

    I have a query about linux kernel image and rootfs. I have mini2440 board. By default vivi is the bootloader. I checked the nand partition with help of vivi bootloader command "part show". It gives following output:

    Supervivi> part show
    Number of partitions: 4
    name : offset size flag
    vivi : 0x00000000 0x00040000 0
    param : 0x00040000 0x00020000 0
    kernel : 0x00060000 0x00500000 0
    root : 0x00560000 0x3fa80000 0

    There are kernel images and yaffs rootfs image provided with the board. When I burn them in given sections using vivi bootloader it boots properly.

    Now the problem is here:

    I compiled a zImage from scratch with latest linux kernel source. I made a jffs2 rootfs image. I burned them in respective sections with help of vivi bootloader. But when i boot the kernel it does not sync with the rootfs image.

    TCP cubic registered
    NET: Registered protocol family 17
    s3c2410-rtc s3c2410-rtc: setting system clock to 2005-07-19 20:25:09 UTC
    uncorrectable error :
    uncorrectable error :
    end_request: I/O error, dev mtdblock3, sector 256
    isofs_fill_super: bread failed, dev=mtdblock3, iso_blknum=64, block=128
    List of all partitions:
    1f00 256 mtdblock0 (driver?)
    1f01 128 mtdblock1 (driver?)
    1f02 5120 mtdblock2 (driver?)
    1f03 125568 mtdblock3 (driver?)
    No filesystem could mount root, tried: ext3 ext2 cramfs vfat msdos iso9660
    Kernel panic - not syncing: VFS: Unable to mount root fs on
    [<c00333f0>] (dump_backtrace+0x0/0x114) from [<c02f94c4>]
    r7:00008000 r6:c3c8b000 r5:c0028a08 r4:c03fd9a4
    [<c02f94ac>] (dump_stack+0x0/0x1c) from [<c02f9514>] (panic+0x4c/0xd0)
    [<c02f94c8>] (panic+0x0/0xd0) from [<c000914c>]
    r3:00000003 r2:80000000 r1:c3c19f6c r0:c0379c65
    [<c0008f6c>] (mount_block_root+0x0/0x220) from [<c0009250>]
    r8:00000000 r7:00000000 r6:00000000 r5:c0028a08 r4:01f00003
    [<c000918c>] (mount_root+0x0/0xfc) from [<c00093f8>]
    r5:c0028a08 r4:c03fd0b4
    [<c0009288>] (prepare_namespace+0x0/0x1c4) from [<c000865c>]
    r5:00000000 r4:c03fce80
    [<c0008550>] (kernel_init+0x0/0x14 from [<c00554d0>] (do_exit+0x0/0x5b0)

    I know I am missing something in configuration. Kindly tell me how I can configure my linux and rootfs image in such a way so that I dont need to alter the default partitions. I want to boot my own kernel image (zImage) and jffs2 rootfs image with the default partitions.

    I think my concept about the partition table and rootfs file system and kernel image is not clear. Will you please explain that also in genrealized form?

    Thanks a lot

  2. #2
    Linux Guru Segfault's Avatar
    Join Date
    Jun 2008
    Kernel panic - not syncing: VFS: Unable to mount root fs on
    31 - driver in use
    3 - third partition on drive

    I've no clue what driver has major number 31, but the fact is kernel is trying to use it to access the drive.
    Partition 3, hope this is the correct one, does partition 3 contain your root filesystem?
    These are the filesystems your kernel is able to handle: ext3 ext2 cramfs vfat msdos iso9660 romfs
    You root filesystem must be a supported one, or boot will fail.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts