Alpha arch development list
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: debian-alpha@lists.debian.org
Cc: linux-alpha@vger.kernel.org, mcree@orcon.nz.net
Subject: [alpha] Debian 9.0 NETINST fails
Date: Fri, 2 Nov 2018 13:41:51 -0500	[thread overview]
Message-ID: <20181102184151.GA15241@gherkin.frus.com> (raw)

Quick background info: I'm having to do a "from scratch" install on my
PWS 433au (miata) due to a SCSI disk failure.

The Debian 9.0 NETINST image (from
"http://cdimage.debian.org/cdimage/ports/9.0/alpha/iso-cd/") seems to
boot ok from SRM (>>> b dka[device_spec]) and takes me to the usual
"aboot" menu.  Typing "l" to get a list of pre-configured kernels gets
me three items, all of which are designated "n" rather than the expected
"0", "1", "2".  The first kernel seems to be the desired one, as the
other two expect a serial console on ttyS0 and ttyS1 respectively.

Typing "0" at the "aboot" prompt seems to do the right thing as far as
selecting the first item in the list.  The "initrd" loads, and at the
point where a message gets printed out to the effect it's booting the
kernel with the expected options (as listed for the first kernel in the
aboot menu), I get a halt with code 5 (CPU 0 halted), and I'm back at
the SRM prompt.  Completely repeatable.

Before I try the 8.0 NETINST image, if anyone has noticed anything
fundamentally wrong with how I'm trying to boot the 9.0 image, kindly
let me know.

Possibly relevant: I'm using the Radeon video card that was in the
machine when the disk failed.  I have the original TGA video card if the
NETINST kernel can't handle the Radeon, but would rather not have to
swap out the video card if I don't absolutely have to.

Thanks.

--Bob


             reply	other threads:[~2018-11-02 18:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 18:41 Bob Tracy [this message]
2018-11-02 18:56 ` [alpha] Debian 9.0 NETINST fails Bob Tracy
2018-11-06 12:36   ` Frank Scheiner
2018-11-07 15:08     ` Bob Tracy
2018-11-07 15:12     ` John Paul Adrian Glaubitz
2018-11-21 20:53       ` Bob Tracy
2018-11-22  5:34         ` Michael Cree
2018-11-22  7:58           ` Helge Deller
2018-11-22  8:34             ` John Paul Adrian Glaubitz
2018-11-23 19:41               ` Bob Tracy
2018-11-23 19:57                 ` John Paul Adrian Glaubitz
2018-11-23 20:07                 ` Michael Cree
2018-11-24 21:57                   ` Bob Tracy

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=20181102184151.GA15241@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mcree@orcon.nz.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