Hello,

I'm having all kinds of trouble jumpstarting some SS20's.

After hunting around the newsgroups I find that this seems to be a fairly common problem with no real answer.

Here's a brief:

SS20, 50mhz, 256mb blah blah. - Client

E250 blah blah - J/start server.

10/100bt Network.

Setup the usual j/start bits for the client and do a 'boot net - install w' on the SS20.

Then all I get is 'Lost carrier- cable probs'.

Now I know for a fact the J/start stuff works a treat as I can do U1/2/5/60's no problem all day long.

I've tried setting the link-test-tpe to false, I've tried doing a 'boot net-tpe' etc.. But it just seems to ignore the fact its on a working network.

It will boot the net device and do its 'count' then it will start the arp/rarp errors, and link down stuff.

I can snoop it and find that the SS20 picks up it 'ip' etc, and does some packet exchanges.

AND just sometimes it will give losts of above errors, but still gradually start the install. But this is not very often.

Has any old school Solaris peeps out there ever solved this one!?

Thanks

John

Does the SS20 have two interfaces?

Nope, just the onboard 10bt jobbie.

John

Sorry, never heard of that problem with just the one interface -

Hi.
Do you use the correct kernel for the Sparc station?
Its not the same as for the Ultra sparc boxes..
the sparc stations use sun4m kernel?
Im not that good at jumpstart but just a tought...

/Peter