On Sun, 9 Apr 2000, Roger H. Goun wrote:
> root@bcah /etc]# insmod 3c503 xcvr=0 io=0x300 irq=5
> /lib/modules/2.2.12-20/net/3c503.o: unresolved symbol ei_open
> /lib/modules/2.2.12-20/net/3c503.o: unresolved symbol ethdev_init
> /lib/modules/2.2.12-20/net/3c503.o: unresolved symbol ei_interrupt
> /lib/modules/2.2.12-20/net/3c503.o: unresolved symbol ei_close
> [root@bcah /etc]#
>
> which I don't like at all. Does anyone have any suggestions?
Try doing an "insmod 8390" first. Actually, before you do that, do an
"lsmod" to see if it is loaded (if so, something is badly broken in that
module -- see below about compiling your own). The 8390 module appears to be
where ei_open() and friends come form. The source claims it is a "general
NS8390 ethernet driver core".
I determined this by grepping the kernel source for "ei_open", which, while
not terribly elegant, is quite effective for many problems. I highly
recommend it as a general tactic.
If that doesn't work, you might try compiling your own kernel. Red Hat has
to compile for everything under the sun to get all those modules, and I
wouldn't be surprised if something conflicted or something else was left out.
> (Suggestions along the lines of, "Go get a NIC that's younger than you
> are!" while perhaps prudent, will be rejected as lacking the proper spirit
> of adventure.)
Hrmmm. You want adventure? Okay: "Write your own driver!" ;-)
--
Ben Scott <[EMAIL PROTECTED]>
| "An oak tree is a nut that stood its ground." -- Unknown |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
