Your message dated Wed, 18 Aug 2004 21:57:23 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#266066: Alpha netboot doesn't mount initrd, causing kernel panic
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Aug 2004 15:25:09 +0000
>From [EMAIL PROTECTED] Mon Aug 16 08:25:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from othello.physics.gla.ac.uk [130.209.204.200] 
([jh2QCuC9n7HZTBakv1lTFsrBbdztD8Ue])
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BwjMD-0004ZF-00; Mon, 16 Aug 2004 08:25:09 -0700
Received: from lilith.physics.gla.ac.uk
        ([130.209.202.50] helo=localhost ident=Debian-exim)
        by othello.physics.gla.ac.uk with esmtp (Exim 4.14)
        id 1BwjMA-0003bJ-Ns
        for [EMAIL PROTECTED]; Mon, 16 Aug 2004 16:25:06 +0100
Received: from localhost ([127.0.0.1] ident=paulm)
        by localhost with esmtp (Exim 4.34)
        id 1BwjMA-0006wc-Lt
        for [EMAIL PROTECTED]; Mon, 16 Aug 2004 16:25:06 +0100
From: Paul Millar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Alpha netboot doesn't mount initrd, causing kernel panic
Date: Mon, 16 Aug 2004 16:25:01 +0100
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <[EMAIL PROTECTED]>
X-Spam-Score: 0.0 (/)
X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) 
*1BwjMA-0003bJ-Ns*m9iIGUSsWgI*
X-Othello-SMTP: True
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package:  debian-installer

(is this the right package?)

I'm using DHCP server to issue an Alpha LX164 machine with a netboot boot.i=
mg=20
file.  The latest version (2004-08-09, MD5: 4591236ca7d3eb6daba4b0f133f947a=
6)=20
(and recent, previous versions) do not boot correctly as they failing to=20
mount the initrd image and so cause the kernel to panic.

The work-around is to issue a suitable kernel command-line at SRM prompt:

boot ewa0 -fl "root=3D/dev/rd/0 devfs=3Dmount,dall rw ramdisk_size=3D16384=
=20
init=3D/linuxrc"

but this is somewhat unwieldy.

Can correct parameters be compiled into the alpha-install kernel, embedded=
=20
within the boot.img image?

Cheers,

Paul.
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBINHS/9JwS78PA+kRAusKAJ9rA7jijDHK6sryZ9py8NRmgNq6vACgvQXZ
3if6zd4UGPTjfgr3rl0IXI0=3D
=3DojY2
=2D----END PGP SIGNATURE-----

---------------------------------------
Received: (at 266066-done) by bugs.debian.org; 19 Aug 2004 04:57:22 +0000
>From [EMAIL PROTECTED] Wed Aug 18 21:57:22 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BxezK-0005Rc-00; Wed, 18 Aug 2004 21:57:22 -0700
Received: by localhost.localdomain (Postfix, from userid 1000)
        id 9FC7F171E00; Wed, 18 Aug 2004 21:57:23 -0700 (PDT)
Date: Wed, 18 Aug 2004 21:57:23 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: Paul Millar <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#266066: Alpha netboot doesn't mount initrd, causing kernel panic
Message-ID: <[EMAIL PROTECTED]>
Mail-Followup-To: Paul Millar <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED], [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040722i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--nFreZHaLTZJo0R7j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 18, 2004 at 12:34:54AM +0100, Paul Millar wrote:

> On Tuesday 17 August 2004 00:26, Andrew M.A. Cater wrote:
> > On Mon, Aug 16, 2004 at 12:21:24PM -0700, Steve Langasek wrote:
> > > boot ewa0 -fl "" always works for me.

> Sorry Steve, I didn't get your reply straight off.

> Erm, yeah, kinda obvious once you say it.  I had boot_osflag set to 0 fro=
m a=20
> previous aboot installation. I can confirm that doing

>   boot ewa0 -fl ""

> *does* work, as does unsetting the boot_osflag.

> So everything works OK, but perhaps this gotcha could/should be documente=
d=20
> somewhere.  The install manual says that ``boot ewa0'' should work:

>   http://d-i.alioth.debian.org/manual/en.alpha/ch05s01.html#id2511128

> If one has default aboot boot_osflag set, then the install will fail.  I =
think=20
> just a one-liner, saying to try adding the -fl "" if boot ewa0 fails woul=
d be=20
> enough.

Yep, I've updated the alpha documentation in this area.

Thanks,
--=20
Steve Langasek
postmodern programmer

--nFreZHaLTZJo0R7j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBJDMyKN6ufymYLloRAqJCAJ9o3Iqa5A39Du8MMzPSkOq65dsXDgCeOAM8
/d9Do8NeSBl/UqEl+vdVRuc=
=oyRE
-----END PGP SIGNATURE-----

--nFreZHaLTZJo0R7j--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to