From: "Mark A. Greer" <mgreer@mvista•com>
To: Sébastien Côté <scote1@matrox•com>
Cc: LinuxPPC-embedded list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: initrd problems
Date: Thu, 18 Jan 2001 18:13:21 -0700 [thread overview]
Message-ID: <3A6794B1.D0B70C1C@mvista.com> (raw)
In-Reply-To: 3A676DC6.FD21D5D8@matrox.com
Where did you get this version of that kernel? From the MontaVista CDK or from
the website? If from the website, when did you get it?
Try this (if its not already done). Go into arch/ppc/boot/head.S and add the
following lines after the set up of r6 to hold the cmd_line.
/* r4,r5 have initrd_start, size */
lis r2,initrd_start@h
ori r2,r2,initrd_start@l
lwz r4,0(r2)
lis r2,initrd_end@h
ori r2,r2,initrd_end@l
lwz r5,0(r2)
Go into arch/ppc/kernel/sandpoint_setup.c. Find sandpoint_setup_arch() and add
something like (again, if its not already there).
#ifdef CONFIG_BLK_DEV_INITRD
if (initrd_start)
ROOT_DEV = MKDEV(RAMDISK_MAJOR, 0);
#endif
Try it now and see if that helps...
Mark
--
Sébastien Côté wrote:
> I finally figured out a small part of the problem... My initrd_start
> was overwritten (to 0) by the function start_kernel in init/main.c :
>
> #ifdef CONFIG_BLK_DEV_INITRD
> if (initrd_start && !initrd_below_start_ok &&
> initrd_start < min_low_pfn << PAGE_SHIFT) {
> printk(KERN_CRIT "initrd overwritten (0x%08lx < 0x%08lx) - "
> "disabling it.\n",initrd_start,min_low_pfn << PAGE_SHIFT);
> initrd_start = 0;
> }
> #endif
>
> I don't really understand this function... Why would my initrd be
> overwritten?!? Anyways, I commented it out to see what would happen.
> This time, it opened the root device (in function mount_root()) but
> didn't go very far:
>
> sb = get_super(ROOT_DEV);
> if (sb) {
> fs_type = sb->s_type;
> goto mount_it;
> }
> ...
> panic("VFS: Unable to mount root fs on %s", kdevname(ROOT_DEV));
>
> sb is NULL. Damn.. What now? Is it possible that my initrd has been
> erased like the kernel told me? What else could it be?
>
> I was also wondering if I loaded the kernel correctly. I put my
> zImage+initrd (zvmlinux.initrd) at address 0 of ram. Since I compiled
> the kernel with debug symbols, it takes a few Megs... Could it be too
> large for it's own good? Maybe somebody knows about the answer to that
> one!
>
> By the way, I forgot to mention it in the first email but I'm using
> linux-2.4.0-test2.
>
> Sébastien Côté
>
--
Mark A. Greer (mgreer@mvista•com; 480-517-0287)
MontaVista Software, Inc.
2141 E. Broadway Road, Suite 108
Tempe, AZ 85282
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 15:53 initrd problems Sébastien Côté
2001-01-18 22:27 ` Sébastien Côté
2001-01-18 20:01 ` Matt Porter
2001-01-19 17:22 ` Sébastien Côté
2001-01-20 14:35 ` Matt Porter
2001-01-22 18:56 ` Sébastien Côté
2001-01-22 19:24 ` Kyle Harris
2001-01-22 20:45 ` Sébastien Côté
2001-01-19 1:13 ` Mark A. Greer [this message]
2001-01-19 14:53 ` Sébastien Côté
2001-01-23 21:03 ` Michael Pruznick
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 16:28 Anders Blomdell
2002-10-30 16:47 ` Wolfgang Denk
2003-04-24 5:32 Sriram Narasimhan
2003-04-24 7:35 ` Wolfgang Denk
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=3A6794B1.D0B70C1C@mvista.com \
--to=mgreer@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=scote1@matrox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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