-----BEGIN PGP SIGNED MESSAGE-----
Hi Alphafolks,
I don't seem to be able to install tu 5.1 on an Alpha 1200.
Perhaps someone more astute than I will see where I've gone wrong.
The Alpha has been running tu 4.0D quite well for years.
Today I shut it down, poked the Firmware 5.8 CD into its drive and
typed `boot dka400'. It all seemed to go fine. It upgraded from about 5.5 so
the warnings in the readme about doing it twice if 5.3 didn't seem to apply.
I then put the OS CD in the drive and booted that. It seemed to be
going normally, producing usual bootup messages, location of the HWRPB,
booting dka4.0.0.1.1, loading vmunix, finding the SWXCR, the disks, the tulip,
the second and third scsi controllers, the graphics card, then all of a
sudden, it said something like `Trap - ... failing va 28 ... panic something
(machine check?) while in kernel mode. But this stack dump or whatever,
quickly disappeared and we were back at the P0>>> prompt.
It seemed to fail between probing the Qlogic SCSI card and the Memory
Channel.
So it seemed to die while probing the hardware. So I removed all the
hardware until all that remained was the CPU (only one in this box), 1 G of
memory, the graphics card, the SWXCR and the inbuilt SCSI with one CDROM and
one Tape drive. This had the predictable effect of reducing the number of
messages produced before the trap.
I then checked the bus_probe_algorithm setting in the console
variables. It was absent. Not there. Zilch.
So I did a `create -nv bus_probe_algorithm new'. Followed by init and
power resets and so on. But this didn't change the behavior when trying to
boot tu 5.1 from the CD.
I found a second copy of the TU 5.1 OS CD and tried booting that.
Same result.
At this point I verified I could still boot 4.0D from the disks
attached to the SWXCR. And while running 4.0D I did a `dd if=/dev/rz4c
of=/dev/null' which produced no errors.
Next I tried to boot a DU 4.0E OS CD. Again a trap with a failing VA
of 28. The messages were similar but different as you might expect, and the
trap came earlier than under 5.1 .
So I swapped the CD drive with a Toshiba one that was lying around
idle. Same result. Then I put back all the hardware and connected the
Toshiba CD to the Qlogic Bus where it appeared as dkc4. Same result.
I then found a DU 4.0D CD. Booting it traps too. Very similar to the
4.0E.
Just to be sure I did the firmware upgrade again. The firmware CD
boots fine, and the upgrade happens as per the docs.
I did a tu 5.1 install on an Alpha 600/333 a couple of weeks ago,
without any problems whatsoever.
I suspect I'm going to feel really stupid when I find out what I did
wrong.
Any thoughts much appreciated.
Keith Lewis
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQCVAwUBOopqYXEpE0nRVDfpAQENkAP/SS1+To3fZJukHtd0nD4X7/RHrv0EHeEY
YkiLe11Ma9Bhmqr0GY2voCUiLXPINe0FWKwZbPRNup9AHJL2Tg66vSdYtWvJqRRZ
8gJqh4jdpdzR05YTjOFFJQ4fixjdykOkFiFMM+5/xH7DTMWMRALgAaeIYoUw36v4
Dhqxkg+mU7o=
=8xjK
-----END PGP SIGNATURE-----
Received on Wed Feb 14 2001 - 11:24:00 NZDT