[net.unix-wizards] 4.2bsd interlan NI1010A recognition

schoff@cadmus.UUCP (Martin Lee Schoffstall) (09/06/84)

Well I finally got 4.2 up on my 750, with no help from my supplier
of the cable for the SC750, but I can't seem to get 4.2 to recognize
my interlan boards during the auto-configuration in the boot.
It recognizes my uba, mba, dz, dmf, ts11, eagles but not my Interlan
boards.

I have all the things that need to be defined like

options	INET,PUP

and

pseudo-device 	ether
pseudo-device	loop

etc..

I have tried changing the CSR on the board and in the configuartion file

device	il0	uba?	csr 164000 vector ...............

I have taken the strappings off the unibus between pins CA1 and CB1
but to no avail.

I am desperate.  I have two Interlan NI1010A (rev J) and nothing seems
to work, I was even so conservative that I first configured and setup
but one board in my vax.  The little red light is off telling me
that self test diagnostics all worked wonderfully.  I have even written
and read using the VAX monitor to location 764000 (octal) and things look
they can be written and then read.  I have recompiled the entire
distribution again for fun too.  If anyone has any reasonable diagnostic
code that runs on top of 4.2bsd or has anything enlightening to say
let me know.

HELP!!!!

marty
{bbncca,wivax,linus,seismo}!cadmus!schoff	(usenet)
cadmus!schoff@seismo.ARPA			(arpa)

"LouNelson@sri-unix.UUCP (09/10/84)

From:  "Lou Nelson (ISRO" <lou@aero3>

You'll probably get a lot of replies but I'm going to put
my two cents in too since I'm a little baffled by this.
We are running 4.2 (really just bringing it up) on a VAX
11-750 with an Interlan NI1010A rev J and it's working
great.  My associate did tell me that he couldn't get the
kernel to see ours at first too and the best he could do 
in the way of remembering was to suggest that he changed
something in the conf file, ordering or something.  Anyway
since suggestions may be better than nothing, here goes.
Make sure you have the following in your conf file and notice
the leading 0 on the 0164000 csr address (couldn't be that
but I'm trying to leave nothing to chance).  The relevant
parts of our conf file are:
	.
	.
	.
options		INET
	.
	.
	.
pseudo-device	bk
pseudo-device	pty
pseudo-device	loop
pseudo-device	inet
pseudo-device	ether

device		vv0	at uba0 csr 0175200 vector vvrint vvxint
device		il0	at uba? csr 0164000 vector ilrint ilcint

If you see any significant differences that solve the problem,
please let me know.  Better yet, maybe the solution should go
out on the net.

I hope this mail gets to you and am a little puzzled about where
to have you reply.  I'm lou@aerospace on the "arpa" net and if you
can get something to Berkeley, we're home free.
Good luck.
Lou Nelson
<...>ucb!lou@aerospace
<...>randvax!aero!lou
<...>sdcrdcf!aero!lou
<...>trwrb!aero!lou
<...>trwrba!aero!lou