From: zamir <zamir.alam@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Booting issue on Omap3430 due to Initrd
Date: Thu, 3 Sep 2009 03:21:57 -0700 (PDT) [thread overview]
Message-ID: <25273217.post@talk.nabble.com> (raw)
Hi,
I am trying to boot Linux on a TI OMAP3430 based device. The device boots up
to a point where it tries to find the initrd image but cannot find it.
My kernel version is 2.6.27. I am using a custom NAND flashing utility to
flash the device with the bootloader, initrd image and kernel. My bootloader
creates ATAGS, copies the kernel and initrd image to RAM and then jumps to
the kernel.
The kernel boots up fine to a point where it tries to mount root. Then it
gives the following error:
No filesystem could mount root, tried: ext3 ext2 msdos vfat
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(1,0)
On debugging I found that the following function call returns -2 (-ENOENT)
in_fd = sys_open(from, O_RDONLY, 0);
This is called in file \init\do_mounts_rd.c inside function:
int __init rd_load_image(char *from)
This in turn is called from do_mounts_initrd.c
if (rd_load_image("/initrd.image") && ROOT_DEV != Root_RAM0)
I found that initrd.image is created in \init\initramfs.c
static int __init populate_rootfs(void)
{
...
if (initrd_start) {
...
fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 0700);
...
Here initrd_start is always zero so this condition never gets true. So
initrd.image is never created.
In short, while booting sys_open("/initrd.image", O_RDONLY, 0); fails with
-2.
I have checked the initrd image is present at the memory location specified
in kernel tags when kernel starts.
Can anybody point to what could be the possible reason for this problem?
Regards,
Zamir
--
View this message in context: http://www.nabble.com/Booting-issue-on-Omap3430-due-to-Initrd-tp25273217p25273217.html
Sent from the linux-kernel mailing list archive at Nabble.com.
reply other threads:[~2009-09-03 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25273217.post@talk.nabble.com \
--to=zamir.alam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox