From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Richard Henderson <rth@twiddle.net>
Cc: "Ingo T. Storm" <it@lapavoni.de>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Re: 2.4.5 does not link on Ruffian (alpha)
Date: Sun, 27 May 2001 19:54:17 -0400 [thread overview]
Message-ID: <3B1193A8.6DB90579@mandrakesoft.com> (raw)
In-Reply-To: <3B0BFE90.CE148B7@kjist.ac.kr> <20010523210923.A730@athlon.random> <022e01c0e5fc$39ac0cf0$2e2ca8c0@buxtown.de> <3B102822.625E01DF@mandrakesoft.com> <3B1032BE.72BD1336@mandrakesoft.com> <20010527163901.A18929@twiddle.net>
Richard Henderson wrote:
> On Sat, May 26, 2001 at 06:48:30PM -0400, Jeff Garzik wrote:
> > When built with CONFIG_ALPHA_NAUTILUS, my UP1000's IDE totally fails.
>
> Mine doesn't.
>
> > I am booting w/ aboot 0.7a from SRM, -without- the
> > srm-as-bootloader kernel config option.
>
> That is the error.
Ok, thanks.
FWIW the documentation seems to imply that the option is necessary only
when directly booting from SRM, i.e.. no bootloader is involved at all.
It uses the example of MILO's presence or absence as indicating the need
for this option.
So... is it safe to always enable this option, with a little hacking
perhaps? :)
Regards,
Jeff
> Using SRM as bootloader
> CONFIG_ALPHA_SRM
> There are two different types of booting firmware on Alphas: SRM,
> which is command line driven, and ARC, which uses menus and arrow
> keys. Details about the Linux/Alpha booting process are contained in
> the Linux/Alpha FAQ, accessible on the WWW from
> http://www.alphalinux.org .
>
> The usual way to load Linux on an Alpha machine is to use MILO
> (a bootloader that lets you pass command line parameters to the
> kernel just like lilo does for the x86 architecture) which can be
> loaded either from ARC or can be installed directly as a permanent
> firmware replacement from floppy (which requires changing a certain
> jumper on the motherboard). If you want to do either of these, say N
> here. If MILO doesn't work on your system (true for Jensen
> motherboards), you can bypass it altogether and boot Linux directly
> from an SRM console; say Y here in order to do that. Note that you
> won't be able to boot from an IDE disk using SRM.
>
> If unsure, say N.
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-27 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 18:16 Swap strangeness using 2.4.5pre2aa1 G. Hugh Song
2001-05-23 19:09 ` Andrea Arcangeli
2001-05-26 15:20 ` 2.4.5 does not link on Ruffian (alpha) Ingo T. Storm
2001-05-26 17:36 ` Andrea Arcangeli
2001-05-26 18:14 ` Andrea Arcangeli
2001-05-27 1:02 ` Jeff Garzik
2001-05-27 2:49 ` Andrea Arcangeli
2001-05-27 16:41 ` Andrea Arcangeli
2001-05-27 19:22 ` Andrea Arcangeli
2001-05-27 21:16 ` Magnus Naeslund(f)
2001-05-26 22:03 ` [PATCH] " Jeff Garzik
2001-05-26 22:48 ` Jeff Garzik
2001-05-27 23:39 ` Richard Henderson
2001-05-27 23:54 ` Jeff Garzik [this message]
2001-05-28 1:05 ` Richard Henderson
2001-05-23 22:34 ` Swap strangeness using 2.4.5pre2aa1 Rik van Riel
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=3B1193A8.6DB90579@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=it@lapavoni.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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