i was just given a 2700wg that was retired and i am trying to use the
netbsd 1.6.1 cobalt restore cd.  but, as many others, am having problems
and after a lot of searching around, haven't been able to determine if
it's actually possible.

the short story:  i connected a 20GB maxtor drive, so i wouldn't destroy
the original install.  when i turn the 2700 on and attempt to netboot "Net
booting" appears on the lcd.  about 30 seconds later it disappears and the
system appears to freeze, as i can't ping it.

the long story:

i startup a laptop using the restore cd, login, kill and restart dhcp so i
can see what's going on.  when the 2700 starts, all appears well as i get
the following:

	BOOTREQUEST from 00:10:e0:00:05:75 via rtk0
	BOOTREPLY on 10.0.0.160 to 00:10:e0:00:05:75 via rtk0

and, if i look at /var/db/dhcpd.leases this is what i get:

	lease 10.0.0.160 {
	  starts 5.2004/01/09 13:27:43;
	  ends never;
	  binding state bootp;
	  next binding state free;
	  hardware ethernet 00:10:e0:00:05:75;
	  client-hostname "";
	}

it also looks like the nfs stuff is working as i get the following output
from tcpdump:

	tcpdump: listening on eth1
	13:25:11.060029 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x8f3863d3
	vend-rfc1048 SM:0.0.0.0 DG:0.0.0.0
	HN:"^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" T40:0,0,0,0,0,0,0,0
	RP: [|bootp] (ttl 64, id 0)
	13:25:11.457956 10.0.0.254.bootps > 10.0.0.160.bootpc: xid:0x8f3863d3
	Y:10.0.0.160 S:10.0.0.254 sname "10.0.0.254" vend-rfc1048 T54:4261412874
	SM:255.0.0.0 NS:10.0.0.254 RP:"/nfsroot" T28:4294967050
	DN:"mfg.cobaltmicro.com" [tos 0x10] (ttl 16, id 0)
	13:25:11.458945 arp who-has 10.0.0.254 tell 10.0.0.160
	13:25:11.459954 arp reply 10.0.0.254 is-at 0:80:45:2b:d4:e6
	13:25:11.460946 10.0.0.160.600 > 10.0.0.254.sunrpc: udp 92 (ttl 64, id 1)
	13:25:11.545938 10.0.0.254.sunrpc > 10.0.0.160.600: udp 28 (ttl 64, id 85)
	13:25:11.546937 10.0.0.160.600 > 10.0.0.254.sunrpc: udp 92 (ttl 64, id 2)
	13:25:11.547933 10.0.0.254.sunrpc > 10.0.0.160.600: udp 28 (ttl 64, id 86)
	13:25:11.548935 10.0.0.160.600 > 10.0.0.254.1021: udp 88 (ttl 64, id 3)
	13:25:11.580927 10.0.0.254.1021 > 10.0.0.160.600: udp 60 (ttl 64, id 89)
	13:25:11.581926 10.0.0.160.709763210 > 10.0.0.254.nfs: 104 getattr fh
	6,0/124360 (ttl 64, id 4)
	13:25:11.582928 10.0.0.254.nfs > 10.0.0.160.709763210: reply ok 96 getattr
	DIR 40555 ids 0/0 sz 4096  (ttl 64, id 90)
	13:25:11.583928 10.0.0.160.709763211 > 10.0.0.254.nfs: 112 lookup fh
	6,0/124360 "boot" (ttl 64, id 5)
	13:25:11.584925 10.0.0.254.nfs > 10.0.0.160.709763211: reply ok 128 lookup
	fh 6,0/124360 DIR 40555 ids 0/0 sz 2048 nlink 3 rdev 0 fsid 600 nodeid
	70000 a/m/ctime 1041617259.000000 1041617273.000000 1041617273.000000
	(ttl 64, id 91)
	13:25:11.585926 10.0.0.160.709763212 > 10.0.0.254.nfs: 120 lookup fh
	6,0/124360 "vmlinux.gz" (ttl 64, id 6)
	13:25:11.586928 10.0.0.254.nfs > 10.0.0.160.709763212: reply ok 128 lookup
	fh 6,0/124360 LNK 120555 ids 0/0 sz 9 nlink 1 rdev 0 fsid 600 nodeid 701ba
	a/m/ctime 1041617273.000000 1041617273.000000 1041617273.000000  (ttl 64,
	id 92)	
	13:25:11.587923 10.0.0.160.709763213 > 10.0.0.254.nfs: 104 readlink fh
	6,0/124360 (ttl 64, id 7)
	13:25:11.588925 10.0.0.254.nfs > 10.0.0.160.709763213: reply ok 44
	readlink "netbsd.gz" (ttl 64, id 93)
	13:25:11.589927 10.0.0.160.709763214 > 10.0.0.254.nfs: 120 lookup fh
	6,0/124360 "netbsd.gz" (ttl 64, id 8)
	13:25:11.590924 10.0.0.254.nfs > 10.0.0.160.709763214: reply ok 128 lookup
	fh 6,0/124360 REG 100555 ids 0/0 sz 829124 nlink 1 rdev 0 fsid 600 nodeid
	7013c a/m/ctime 1041617259.000000 1041548077.000000 1041617260.000000
	(ttl 64, id 94)
	13:25:11.591925 10.0.0.160.709763215 > 10.0.0.254.nfs: 104 getattr fh
	6,0/124360 (ttl 64, id 9)
	13:25:11.592927 10.0.0.254.nfs > 10.0.0.160.709763215: reply ok 96 getattr
	REG 100555 ids 0/0 sz 829124  (ttl 64, id 95)
	13:25:11.593923 10.0.0.160.709763216 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 0 (ttl 64, id 10)
	13:25:11.669921 10.0.0.254.nfs > 10.0.0.160.709763216: reply ok 1124 read
	REG 100555 ids 0/0 sz 829124 nlink 1 rdev 0 fsid 600 nodeid 7013c
	a/m/ctime 1041617259.000000 1041548077.000000 1041617260.000000  (ttl 64,
	id 96)

	[snip]
	
	13:25:13.360599 10.0.0.160.709764021 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 824320 (ttl 64, id 815)
	13:25:13.361600 10.0.0.160.709764022 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 825344 (ttl 64, id 816)
	13:25:13.362596 10.0.0.160.709764023 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 826368 (ttl 64, id 817)
	13:25:13.364599 10.0.0.254.nfs > 10.0.0.160.709764023: reply ok 1124 read
	REG 100555 ids 0/0 sz 829124 nlink 1 rdev 0 fsid 600 nodeid 7013c
	a/m/ctime 1041617259.000000 1041548077.000000 1041617260.000000  (ttl 64,
	id 903)
	13:25:13.365599 10.0.0.160.709764024 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 827392 (ttl 64, id 818)
	13:25:13.366600 10.0.0.160.709764025 > 10.0.0.254.nfs: 116 read fh
	6,0/124360 1024 bytes @ 828416 (ttl 64, id 819)
	13:25:13.367599 10.0.0.254.nfs > 10.0.0.160.709764025: reply ok 808 read
	REG 100555 ids 0/0 sz 829124 nlink 1 rdev 0 fsid 600 nodeid 7013c
	a/m/ctime 1041617259.000000 1041548077.000000 1041617260.000000  (ttl 64,
	id 905)

once it gets here, the lcd clears and the machine seems to hang.  i can't
ping or rlogin to the box.

as it's a 2700, i don't have any console output.  i've searched a bit and
only found the link to the schematic in the faq.  if someone has any
hints, ideas about what is going on, or any other schematics or console
how-tos i'd really appreciate it.

thanks in advance for the help,

-bryan

----------------------------
Bryan Olmstead
reply-to: olmsteab@acm.org
http://www.tr1tium.com