public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurriaan on Alpha <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17-rc1 does not boot my Alphas
Date: Mon, 17 Dec 2001 06:48:25 +0100	[thread overview]
Message-ID: <20011217054825.GA12057@alpha.of.nowhere> (raw)
In-Reply-To: <20011216160404.A2945@mail.harddata.com> <3C1D4871.82053E7A@zk3.dec.com>
In-Reply-To: <3C1D4871.82053E7A@zk3.dec.com>

On Sun, Dec 16, 2001 at 08:20:49PM -0500, Peter Rival wrote:
> Michal Jaegermann wrote:
> 
> > I just happen to have an access right now to two Alpha machines,
> > UP1100 and UP1500, both with Nautilus chipset.  Neither of these
> > can be booted with 2.4.16 or 2.4.17rc1. On an attempt to boot
> > I can see only messages from a boot loader (aboot):
> > .....
> > zero-filling 155872 bytes at 0xffffc0000ad1308
> > starting kernel vmlinux.......
> >
> > and that is it.  The only thing which works now is a power switch.
> Try again, this time adding "srmcons" to the boot flags.  You're croaking
> before we get the console set up under Linux so none of the boot messages are
> getting out; srmcons uses the SRM console to print its messages.  This won't
> fix the bugs, but at least we'll be able to see exactly where you die.
> 
Perhaps the wording of CONFIG_ALPHA_SRM in Configure.help could be a bit
stronger;

Use 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.

Perhaps something like: 

If unsure, say N if you boot linux via MILO, or Y if you boot linux via
SRM.

I was fooled by this one also, and with the current text, I read it like
'saying N is safe'.

Jurriaan
-- 
`That right?' Hawk gave MacReady a long, thoughtful look.
`I'll have to remember that.'
	Simon R Green - Hawk & Fisher II Fear and Loathing in Haven
GNU/Linux 2.4.17-rc1 on Debian/Alpha 64-bits 990 bogomips load:1.63 1.20 1.06

  reply	other threads:[~2001-12-17  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 23:04 2.4.17-rc1 does not boot my Alphas Michal Jaegermann
2001-12-17  1:20 ` Peter Rival
2001-12-17  5:48   ` Jurriaan on Alpha [this message]
2001-12-17  5:50   ` Michal Jaegermann
2001-12-17 22:52     ` Michal Jaegermann
2001-12-18 15:35 ` Alan Cox
2001-12-20  6:30   ` Michal Jaegermann

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=20011217054825.GA12057@alpha.of.nowhere \
    --to=thunder7@xs4all.nl \
    --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