Message Board -  Archive

[ Login ] [ Create Account ]
[ Board List ] [ View Board ] [ Post Reply ]
  Author  Subject: Re: FreeBSD 4.7 install issues (ethernet)
Archive  

Posted on 03-27-2003 09:40 p.m. ET  reply

Original Poster: Mark Krentel

> Am setting up an fBSD box ...

But we're a Linux group, SyrLug, not SyrFug. [This is a little joke
because Dennis probably knows that I run Freebsd more than I run
Linux.]

> NIC: SMC 8416T PnP ISA (100 % *nix compatible)

I can't find SMC 8416 in the Hardware list, but probably it's a clone
of something else with another name.

http://www.freebsd.org/releases/4.7R/hardware-i386.html

A Google/bsd search for "SMC 8416" produces some old advice from 1998:

> Has anyone gotten an SMC8416 card working?? I didnt see it in the
> supported hardware, and I have been screwing around with the kernel
> configs, but no luck. Please email me back direct with any
> suggestions!!

Yes.

Make sure that Plug'n'Play is disabled on the card, and that the ed driver
settings for IRQ, IO port address and memory address match the card
settings.

The ed(4) driver is for an NE2000 and clones. Does that look right,
is the 8416 a clone of an NE2000? Assuming it is, NE2000 clones are
fully supported in all versions of Freebsd, although configuring the
ed(4) driver is rather primitive. (I think the 8390 chip has limited
ability to answer probes, but whatever.)

To configure the ed driver, you'll probably need to recompile the
kernel. Don't worry, compiling kernels in Freebsd is easier than in
Linux. You don't need any 3rd party patches for this, just the plain,
vanilla kernel sources.

Did you install full source, kernel source or no source? For the
kernel, you just need base (top-level /usr/src files) and sys (kernel
sources) from the src distribution. If you don't have them installed
(or worse, if you've been tinkering with them), you can install them
from /stand/sysinstall. Or, they're just tar files, untar them into
/usr.

Cd to /usr/src/sys/i386/conf and copy GENERIC to another name, let's
say MYKERN. The name is arbitrary, but it's convention to name the
kernel after the machine's name. Edit MYKERN for your hardware
(mainly ripping out stuff you don't need). For ed, you need the
following, using your port and IRQ, of course.

device miibus
device ed0 at isa? port 0x280 irq 10 iomem 0xd8000

Then you run:

config -r MYKERN
cd ../../compile/MYKERN (ie, /usr/src/sys/compile/MYKERN)
make depend
make
make install

See also Section 9 in the Freebsd Handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html

If you have the right port and IRQ, it should mention "ed0" in dmesg,
and you should be able to ifconfig it with:

ifconfig ed0 up 192.168.1.1

Port 0x280 and IRQ 10 are the default settings. Another option, if
you have the floppies, is to reset the card to those values and use
the GENERIC kernel.

And there's yet another option to avoid compiling a kernel. During
the boot, there will be a couple places where it just sits still for a
few seconds. If you hit Space at the right time (or maybe some other
key, I forget), you'll get a prompt where you can tinker with the
kernel's IRQ settings. But honestly, I use this option so rarely that
I don't think I could talk you through it. (I just always recompile
the kernel.)

Once you get the kernel to find the right device, you can
automatically ifconfig the device on boot with /etc/defaults/rc.conf,
putting your local changes in /etc/rc.conf.

Ok, this is long enough for now. See if that gets your network card
going. I'll look into the X windows problem and get back to you, but
really, X should behave the same in Freebsd as in Linux.

P.S. I've never heard of the "we" driver. There's no mention of it in
GENERIC or LINT and "man we" has no entry.

--Mark

< Previous 1 Next >

Site Contents