Hello, first I would like to say that I am sending this peice of mail to port-sparc, Chuck Cranor, and Theo de Raadt. I would like to thank everyone for being so helpful...

First off, Theo asked me if 
i wasn't aware that there were 1152x900 versions of the 4/200 board.
is there a jumped that says which way that goes?
I
Im not sure if there is a jumper.. But, my machine is a 4/260 if that makes a difference. and Its got a color framebuffer card that does 1152x900..
Anyways...

It seems there are 2 kernels. Or maybe more.. I tried Theo's first and i posted that one earlier. re the hang on the 1600x1280 console mode.

Then i got Chuck's email, and I downloaded his kernel, and that booted past that point.. however it got stuck somewhere else. here is an excerpt:

vmel0 at mainbus0
vmes0 at mainbus0
nfs_boot: using network interface 'ie0'
ie0: TDR detected an open 17408 clocks away
nfs_boot: client_addr=0xc0000204
nfs_boot: server_addr=0xc0000201
nfs_boot: hostname=sun4
root on server:/var/sparc
RPC timeout for server 0xc0000201

and this last msg about the RPC timeout repeats forever..

Well, here's my 1 1/2 cents. First let me say the server machine is a linux. No flames please, my head hurts enough.. Second all the parts are in order. I used the same basic configuration to boot a sun3/110 diskless with the Xkernel and a Sun3/110 diskless with SunOS 4.1.1. Im not saying there still isnt a problem with the software on the server end. I think there is. Im just saying with these older implementations it worked ok. There might be stricter rules in BSD 4.4 style stuff that is causing some sort of inconsistency.. Umm some relevant cut & pastes. (duck is my linux box)

duck:/var/sparc/shit# rpcinfo -p localhost
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100026    1   udp    732  bootparam
    100003    2   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100005    1   udp    736  mountd
    100005    1   tcp    738  mountd

05:38:41.546210 sun4.inner.com.1023 > duck.inner.com.732: udp 56 (ttl 64, id 18)
^^^Thats the packet it keeps looping on.. 
I've made an can make tcpdump logs of all this traffic..
I dont want to paste a whole ton of packets here. Im this is very limited debugging information. But it should show you the pattern of events.

05:59:57.184062 rarp who-is 8:0:20:6:41:95 tell 8:0:20:6:41:95
05:59:57.184238 rarp reply 8:0:20:6:41:95 at sun4.inner.com
05:59:57.598664 arp who-has sun4.inner.com tell sun4.inner.com
05:59:57.605444 sun4.inner.com.1023 > 192.0.2.255.sunrpc: udp 76
05:59:57.614410 duck.inner.com.sunrpc > sun4.inner.com.1023: udp 72
05:59:57.986802 arp who-has duck.inner.com tell sun4.inner.com
05:59:57.986985 arp reply duck.inner.com is-at 0:0:c0:f5:37:b4
05:59:57.991497 sun4.inner.com.1023 > duck.inner.com.732: udp 56
05:59:57.991717 duck.inner.com.732 > sun4.inner.com.1023: udp 72
05:59:58.175304 sun4.inner.com.1023 > duck.inner.com.sunrpc: udp 56
05:59:58.175521 duck.inner.com.sunrpc > sun4.inner.com.1023: udp 28
05:59:58.179718 sun4.inner.com.1023 > duck.inner.com.736: udp 56
05:59:58.179932 duck.inner.com.736 > sun4.inner.com.1023: udp 60
05:59:58.182708 sun4.inner.com.1023 > duck.inner.com.sunrpc: udp 56
05:59:58.182907 duck.inner.com.sunrpc > sun4.inner.com.1023: udp 28
05:59:58.187536 sun4.inner.com.1023 > duck.inner.com.732: udp 56
05:59:59.182540 sun4.inner.com.1023 > duck.inner.com.732: udp 56
06:00:01.182594 sun4.inner.com.1023 > duck.inner.com.732: udp 56
06:00:04.182786 sun4.inner.com.1023 > duck.inner.com.732: udp 56
06:00:08.182848 sun4.inner.com.1023 > duck.inner.com.732: udp 56
06:00:13.182872 sun4.inner.com.1023 > duck.inner.com.732: udp 56
^^^^^^^^^^^^^^^^^^^^^ this loops forever


-Yours Cluelesslym
		Eric.


P.S. Im sending this out not from a normal mailer, like pine. or elm.
Im sending this out from my localhost 25. because my domain isnt up yet so if i send mail from here no one would be able to reply... So what i do instead is
'fake mail' it out from here. So please excuse any typo's or whatnot since i cant go back and correct it.

P.P.S sorry about the length of this post..

P.P.P.S i can supply the full tcpdump hex packet output if that would help.

Regards,
	Yours again,
		   Eric