• Bug#266066: Alpha netboot doesn't mount initrd, causing kernel panic

    From Paul Millar@1:229/2 to All on Mon Aug 16 17:40:12 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    -----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.img file. The latest version (2004-08-09, MD5: 4591236ca7d3eb6daba4b0f133f947a6) (and recent, previous versions) do not boot correctly as they failing to
    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=/dev/rd/0 devfs=mount,dall rw ramdisk_size=16384 init=/linuxrc"

    but this is somewhat unwieldy.

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

    Cheers,

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

    iD8DBQFBINHS/9JwS78PA+kRAusKAJ9rA7jijDHK6sryZ9py8NRmgNq6vACgvQXZ 3if6zd4UGPTjfgr3rl0IXI0=
    =ojY2
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Steve Langasek@1:229/2 to Paul Millar on Mon Aug 16 21:40:09 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    On Mon, Aug 16, 2004 at 04:25:01PM +0100, Paul Millar wrote:
    -----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.img
    file. The latest version (2004-08-09, MD5: 4591236ca7d3eb6daba4b0f133f947a6)
    (and recent, previous versions) do not boot correctly as they failing to 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=/dev/rd/0 devfs=mount,dall rw ramdisk_size=16384 init=/linuxrc"

    but this is somewhat unwieldy.

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

    The correct parameters *are* embedded in the netboot image. Please
    check your boot_osflags setting; it is likely that you have a value set
    that is overriding the settings in the image.

    boot ewa0 -fl "" always works for me.

    --
    Steve Langasek
    postmodern programmer

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

    iD8DBQFBIQkzKN6ufymYLloRAjQhAJ9TvF7hC/872v4B4r6JVZ0L9nMPFgCfSk50 9HE1WbXxol8ogfit7YKIbQE=
    =VA8V
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)