Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

I have a bunch of different NEC cards and I got all but two of them 
working, eventually, including the ISA ones.  Two were apparently dead, 
which could cause them to give a 'device or resource busy' message, but 
this message can also simply mean that you have the WRONG module.

Once you find the chip number you can look online for the right module - 
Ethernet HOWTO has a list.  Or, as Steven suggested, try a special 
Slackware module that will identify the card for you - the bZimage in 
net.i.  And if you are going to be doing linux, it would save a lot of 
time to purchase the CDs, which I think were $1 plus shipping (the info is 
at the BL website somewhere - Cheapbytes?).

(Steven, I hope you do not have the flu - you have not been very active on 
the list recently and I hope you will find time to answer my questions 
about kernel compilation.)

For many ISA cards you will get your second error message (unresolved 
symbols) because you need to load 8390.o before you load the main module - 
the HOWTO will let you know about this.

I had one PCI card for which SW71 did not provide a module (a Winbond). 
Steven included most of the more common modules especially for the (older) 
ISA cards.  My four tulip cards and two ne2000 and four RLT8139 and three 
3c5x9 are all PCI, the ISAs being ne or 3c509.  Before you bother to open 
up the case, you could try 8390.o plus ne or 3c509 or smc-ultra or wd.

On Tue, 15 Feb 2005, Termina wrote:

> Having problems getting an old ISA NIC working
Did this card work for you with some other OS?

> Since none of the modules I got by default worked, I downloaded the
> tulip.o from the slackware 7.1 mirror.
>
> I insmod tulip.o, and get this message:
>
> insmod: init_module: tulip: Device or resource busy
Why did you choose tulip.o?

> I downloaded a few of the 3c50#.o modules as well, and when I try to
> insmod them, I get the same message. Although some give me:
>
> (insmod 3c503.o)
> insmod: unresoved symbol ei_open
> insmod: unresolved symbol ethdev_init
> insmod: unresoved symbol ei_interrupt
> insmod: unresoved symbol ei_close
>
> Anyone know what I can do?
>
> I have *no* idea the stats of this card. dmesg doesn't seem to have
> anything useful about it either.

You need to load the module before dmesg can identify the card (same for 
scsi cards, I discovered).

> Thanks!
> --
> -Bill Twomey
> ----------------------------
> Join us in IRC!
> irc.UnhandledExceptions.com
> #unhandledexceptions
> ----------------------------
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org