From: Michael Meissner <meissner@cygnus.com>
To: Cort Dougan <cort@ppc.kernel.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: new bootloader
Date: Tue, 16 Mar 1999 20:55:31 -0500 [thread overview]
Message-ID: <19990316205531.A8459@tiktok.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990316032305.21674A-100000@persephone.cs.nmt.edu>; from Cort Dougan on Tue, Mar 16, 1999 at 03:24:43AM -0700
On Tue, Mar 16, 1999 at 03:24:43AM -0700, Cort Dougan wrote:
>
> Has anyone tried it yet? I haven't had any complaints and it's hard to
> believe it works for everyone as it is now.
>
> If you haven't tried it and were having trouble before please do give it a
> test. Even if you can't give me patches for your hardware a quick
> description of the problem will help me get things in position to work
> sooner.
I'm not sure whether I have the code or not, but I did take the vger tarball
linux-vger-2.2.2-990307, and built it. It sort of boots on my Motorola
PowerStack-II NET4000, in that if I'm physically present and type in the
root=/dev/sda2 string at the prompt it will boot, and it won't recongize more
than 32 meg of memory (my machine has 128 meg). However, the machine mostly
sits in a closet, so I would prefer not to have to do anything to reboot it.
In addition, when the machine wants to reboot, it hangs. Gary's patches to
2.2.1 solves the first problem via CONFIG_CMDLINE that the user can specify the
initial command line and the second problem by knowing where the OF residual
data is kept, and I never experienced the third problem.
On my other machine, an original PowerStack with a 603 (not 603e) and no cache,
it hangs right after the prompt, just like Gary's patches did (the original
version of the last of the 2.1.xx series booted fine on this machine, but did
not boot on the NET4000). Note, I didn't have a disk in the machine, but it
didn't get the usual distance going through the boot screens until it actually
touches the disk.
>
--
Michael Meissner, Cygnus Solutions
PO Box 98, Ayer Massachusetts, USA 01432-0098
meissner@cygnus.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-17 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 10:24 new bootloader Cort Dougan
1999-03-16 14:58 ` Johnnie Peters
1999-03-16 19:23 ` Benjamin Herrenschmidt
1999-03-17 1:55 ` Michael Meissner [this message]
1999-03-17 8:05 ` Cort Dougan
1999-03-17 14:38 ` Gary Thomas
1999-03-23 3:27 ` Michael Meissner
1999-03-23 13:39 ` Michael Meissner
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=19990316205531.A8459@tiktok.cygnus.com \
--to=meissner@cygnus.com \
--cc=cort@ppc.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).