Douglas Meade wrote:

> Chris,
>
> When you say it doesn't work, are you getting any sign of
> a controller in the kernel boot messages when you netboot?
> Is it recognizing the controller and just not recognizing
> the drive, or does it see zilch?  If it does see the controller,
> what address is it reporting for it?
>
>

Hi Doug,
this is what I get when booting
NetBSD-current:
............................................................................

>>> b xqa0

  2..1..0..


>> NetBSD/vax boot [May 23 2000 16:14:54] <<
>> Press any key to abort autoboot  543210
> boot netbsd.vax
Trying BOOTP
Using IP address: 10.0.0.101
myip:  (10.0.0.101)
root addr=10.0.0.125 path=/export/vaxclient/root/
|/-@@@\@@@|@@@boot failed: Device not configured
> boot netbsd
Trying BOOTP
Using IP address: 10.0.0.101
myip:  (10.0.0.101)
root addr=10.0.0.125 path=/export/vaxclient/root/

Copyright (c) 1996, 1997, 1998, 1999, 2000
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.4Y (INSTALL) #4: Tue May 23 14:37:17 PDT 2000
    matt@cheetah.local:/other/src/sys/arch/vax/compile/INSTALL

MicroVAX II
total memory = 9208 KB
avail memory = 5488 KB
using 140 buffers containing 560 KB of memory
mainbus0 (root)
ibus0 at mainbus0
uba0 at ibus0: Q22
udaprobe: init step2 no change. sa=8a6a
udaprobe: init step2 no change. sa=8a6a
qe0 at uba0 csr 174440 vec 774 ipl 17
qe0: deqna, hardware address 08:00:2b:04:a4:23
panic: ptelen fault in system space: addr d0f853f7 pc 80000200
syncing disks... done

Loading system software.

  2..
?02 EXT HLT
    PC =
00001293
>>>
>>>
............................................................................

I hope this helps a bit.

Regards  -  Chris


-- 
Sent through GMX FreeMail - http://www.gmx.net