From: Michael Pruznick <michael_pruznick@mvista•com>
To: Sébastien Côté <scote1@matrox•com>
Cc: mgreer@mvista•com,
LinuxPPC-embedded list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: initrd problems
Date: Tue, 23 Jan 2001 14:03:00 -0700 [thread overview]
Message-ID: <3A6DF184.D160C4CF@mvista.com> (raw)
In-Reply-To: 3A6854DD.A370D56B@matrox.com
I'd had a similar problem with a 2.5 kernel from late nov
or early dec. I had to comment out the follow code from
init/main.c::do_basic_setup() to get it working. I also
had to apply the head.S and <board>_setup.c file as
already mentioned in this thread. I also played with devfs
support but don't remember if either enabled or disabled was
required. I never followed up on this, but I suspect this
is a bad kludge and that there is a better way to solve this
problem. Let me know if this works for you.
718 #if 0
719 #ifdef CONFIG_BLK_DEV_INITRD
720 root_mountflags = real_root_mountflags;
721 if (mount_initrd && ROOT_DEV != real_root_dev
722 && MAJOR(ROOT_DEV) == RAMDISK_MAJOR && MINOR(ROOT_DEV) == 0) {
723 int error;
724 int i, pid;
725
726 pid = kernel_thread(do_linuxrc, "/linuxrc", SIGCHLD);
727 if (pid>0)
728 while (pid != wait(&i));
729 if (MAJOR(real_root_dev) != RAMDISK_MAJOR
730 || MINOR(real_root_dev) != 0) {
731 error = change_root(real_root_dev,"/initrd");
732 if (error)
733 printk(KERN_ERR "Change root to /initrd: "
734 "error %d\n",error);
735 }
736 }
737 #endif
738 #endif
Sébastien Côté wrote:
>
> "Mark A. Greer" wrote:
> >
> > 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?
>
> I'm pretty sure it came from the web.. I think it was downloaded at the
> end of November but I can't be sure... I could probably answer this
> next week.
>
> > 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
> >
>
> I tried that patch that I found in the list archives but it didn't make
> any difference.
>
> Sébastien Côté
>
--
Michael Pruznick, michael_pruznick@mvista•com, www.mvista.com
MontaVista Software, 1237 East Arques Ave, Sunnyvale, CA 94085
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-23 21:03 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
2001-01-19 14:53 ` Sébastien Côté
2001-01-23 21:03 ` Michael Pruznick [this message]
-- 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=3A6DF184.D160C4CF@mvista.com \
--to=michael_pruznick@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mgreer@mvista$(echo .)com \
--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