From: Michal Jaegermann <michal@harddata.com>
To: Peter Rival <frival@zk3.dec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17-rc1 does not boot my Alphas
Date: Sun, 16 Dec 2001 22:50:13 -0700 [thread overview]
Message-ID: <20011216225013.A4984@mail.harddata.com> (raw)
In-Reply-To: <20011216160404.A2945@mail.harddata.com> <3C1D4871.82053E7A@zk3.dec.com>
In-Reply-To: <3C1D4871.82053E7A@zk3.dec.com>; from frival@zk3.dec.com on Sun, Dec 16, 2001 at 08:20:49PM -0500
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.
>
> Try again, this time adding "srmcons" to the boot flags. You're croaking
> before we get the console set up under Linux
Thanks. I was not aware of this flag and this is a nice tip.
Unfortunately things lock up immediately before effects of this flag
can be felt. Even with this I am not getting a single line from
a kernel. I tried both on 1500 and 1100. Effects are exactly the same.
Tommorow I will try to graft 'arch/alpha' from 2.4.13-ac8 to 2.4.17rc1
just to see what will happen. Some changes have to be made before this
will even compile. I see that some 'nautilus_init()' function showed up
in 2.4.17rc1 which was not in 2.4.13-ac8. Hm....
I did boot 2.4.13-ac8 on UP1500 but in a short order I collected an
impressive array of "Machine checks" both "Fatal", although machine was
still running to an extent after that, and "Correctable". If somebody
wants to look at them I can oblige. :-) Nothing of that sort showed up
on UP1100 with the same kerel or with older kernels I was able to boot
on 1500.
Michal
next prev parent reply other threads:[~2001-12-17 5:50 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
2001-12-17 5:50 ` Michal Jaegermann [this message]
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=20011216225013.A4984@mail.harddata.com \
--to=michal@harddata.com \
--cc=frival@zk3.dec.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.