Subject: Re: alpha dead..sort of.
To: Andrew Brown <atatat@atatdot.net>
From: Pat Wendorf <beholder@unios.dhs.org>
List: port-alpha
Date: 05/08/2001 01:04:00
Hey Andrew,
This probably won't help, but when I did the initial install of my
AXPpci33, it did that exact same thing. The only way I got it booting
normally was to upgrade the firmware. Is there a possibility that your
NVRAM got whacked somehow and it loaded the old firmware instead?
Sorry if I sound entirely stupid here, I'm still learning Alpha :)
- Pat
Andrew Brown wrote:
>
> help please.
>
> my alpha (a pc164) used to be quite happy. then i unplugged the cable
> modem to rerun the power and cable wires and plugged it all back in.
> no response from cable modem. this is incidental, but leads directly
> to me rebooting my alpha after i tried reruning dhclient on the alpha.
> which didn't work, so i tried rebooting.
>
> which it no longer does.
>
> from the serial console it gets as far as
>
> >>>boot
> (boot dqa0.0.0.11.0 -file netbsd -flags -a)
> block 0 of dqa0.0.0.11.0 is a valid boot block
> reading 14 blocks from dqa0.0.0.11.0
> bootstrap code read in
> base = 180000, image_start = 0, image_bytes = 1c00
> initializing HWRPB at 2000
> initializing page table at 172000
> initializing machine state
> setting affinity to the primary CPU
> jumping to bootstrap code
>
> and stops there. nothing else happens. it used to say something
> about "NetBSD/alpha 1.5S Primary Boot" and then "NetBSD/alpha 1.5S
> Secondary Bootstrap", but nothing else happens.
>
> arg!
>
> of course, dhclient on other machines also gives me nothing from the
> cable modem...bleah.
>
> --
> |-----< "CODE WARRIOR" >-----|
> codewarrior@daemon.org * "ah! i see you have the internet
> twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
> andrew@crossbar.com * "information is power -- share the wealth."
--
Pat Wendorf