From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Problem with 386BSD and Network
Organization: Weber State University  (Ogden, UT)
Date: Sat, 5 Sep 92 23:40:29 GMT

In article <Bu3nKA.21q@nicedel.north.de> nyse@nicedel.north.de (Hermann Behrens) writes:
>Hello!
>
>I've installed 386BSD correct, but I'm not able to establish a
>connection to my 2nd computer. The 2nd computer works well and there
>are sure no problems with the ethernet-card. The ethernet-card in the
>Peacock 386/20 is a FD0490 EtherBoard16. I've installed it for IRQ2, but
>386BSD says the following:
>
>ne0 ethernet address 00:00:4d:21:65:97 at 0x300 irq9 on isa
>
>?? I installed ther card on all available IRQ's(2,3,4,5,12) but it
>will always be detected on IRQ 9. Then I type the following:
>
>>ifconfig ne0 192.1.1.2		# I type in
><neinitstartartstartart		# 386BSD answers
>>route add default 192.1.1.10 (The IP-Number for my 2nd computer).
>
>Now I tried to start ftp but I was never successful. Does someone knows
>the answer for the problem? The rest of the peripherie: 8 MB RAM, 50
>MB HD, VGA(an old one: MORSE KP 1000 EVGA) etc...

1)	IRQ 9 is IRQ 2 for the interrupt controller cascade.

2)	Where the device is found is dependant not on where the device
	actually is, but on the kernel configuration.

3)	If you have a video card on IRQ 2/IRQ 9 (ie: vertical retrace
	interrupt), like some VGA's, you will need to either physucally
	cit the trace (some cards have a little "o" shaped trace that
	will let you do this and reconnect it with solder later), or you
	will need to either change your ethernet interrupt as part of
	a kernel rebuild or use one of the "tape on the card edge" type
	hacks to prevent IRQ 2 from contacting the card connector.

4)	The Base and DMA addresses are also tied into the kernel config.

5)	The cards can be at the wrong interrupt and still be recognized,
	since the probe routines check memory locations rather than
	making sure an interupt from the card occurs.

6)	If you have the card on IRQ 3 or IRQ 4, you should know that
	most "disable com port" jumpers on motherboards with built in
	com ports *don't* disable the interrupt latch, and so still
	interfere with other cards on that interrupt (DTK and Intel
	motherboards are particularly bad at this).

7)	As long as the default route specified to your "route" command
	refers either to a packet forwarding host, like a cisco box, or
	the host you are going to FTP to, you're OK with the route.

8)	The default netmask on an ifconfig seems to be 255.255.255.255,
	which is obviously bogus.  You need to specify a "netmask <value>"
	on the end of your ifconfig for this to work correctly.  For a
	class A net, value is 255.0.0.0, for a B it's 255.255.0.0, and for
	a class C it's 255.255.255.0.  The network number in your post
	is 192.1.1.2, so it's a class C.

9)	The "startart" is from a debug message in the driver you are
	using.  You can get rid of this when you recompile the kernel;
	it wil, however, slow down FTP until then (you need the bin and src
	distributions, in that order, to rebuild the kernel -- if you
	have a small drive, you can download the tar.Z (prepared, I believe,
	by Amacio?) containing only the kernel sources.  You still need the
	bin, however).

10)	Make sure our second computer isn't the problem by talking to a
	system other than the 386BSD box you are trying to get set up.
	There's nothing you can do to a 386BSD box that will make it talk
	to another computer if the other computer has a bad ethernet adapter.


Hope this helps.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd