Hi.

Some time ago this came to topic and Hugh Graham suggested this
modification to xxboot:
\begin{cite}
This code way back in xxboot appears to be at fault:

                if (rpb->devtyp == BDEV_SDN)
                        rpb->devtyp = BDEV_SD;  /* XXX until driver
fixed */

I guess some subsequent routines need the devtyp passed unmolested.

Anyway, I took this out of xxboot, handled SD vs SDN confusion inside
the kernel instead, and Cheetah appears to be hunky-dory again.
\end{cite}
What is that "confusion" that needs to be handled?

I commented this two lines out, rebuilded xxboot, installed it aaaaaand:
\begin{cite}

>>>b dka100
(BOOT/R5:0 DKA100)

  2..
-DKA100
  1..0..


>> NetBSD/vax boot [1.11 Thu May 16 21:00:55 CEST 2002] <<
>> Press any key to abort autoboot 5
Press '?' for help
> 
> boot netbsd
stray interrupt: vector 0x4, ipl 31
stray interrupt: vector 0x18, ipl 31
stray interrupt: vector 0x18, ipl 31
stray interrupt: vector 0x18, ipl 31
[and so on, amd so on, ...]
\begin{cite}

So I am one step further, but still stuck. 

No. Netbooting and redirecting the kernel to continue booting from disk
is no solution. This machine is doomed to be the netboot server for my
other machinery. 

BTW: Is there no mopd in Tru64 5.1?
-- 



tschüß,
         Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/