On Tue, Jul 17, 2001 at 09:00:37AM -0700, Electric Monk wrote:
> uses the Realtek 8139 chipset,
> so I'm assuming that rtl8139.o is the correct module.
That is a correct module in a 2.2.x kernel, yes. You can also use
"8139too.o".
% modprobe rtl8139 # Donald Becker's driver
% modprobe 8139too # New driver based on Donald's rtl8139
# driver
If you have a 2.4.x kernel, you should use "8139too", as I believe
they've done away with Donald's rtl8139.o
This entire feud between Linus and Donald just doesn't make alot of
sense to me.
Here is Donald's page for his older rtl8139 driver:
http://www.scyld.com/network/rtl8139.html
> When I try to load it, I get an error message telling
> me that the device is busy, which
> it says means that the IRQ or I/O port could be
> configured incorrectly, although if I
> recall correctly, this SHOULD NOT be a problem with
> the PCI bus. What do I
> need to do to get it working?
Can we have the "lspci -v" snippet for your rtl8139?
And maybe a "cat /proc/interrupts"?
I've found that if my BIOS reserves all resources for "Legacy/ISA" or
some other such nonsense, your kernel won't re-allocate them by default.
Make sure your BIOS' PnP support assigns IRQs to PCI devices.
> Also, when I type "ifconfig -a" at the console, the
> only interface that is shown is the
> loopback. Will the network card automatically be
> added once I install its module?
Once you successfully "modprobe rtl8139" or "modprobe 8139too", you should
see eth0 appear. Then you can ifconfig it or dhcpcd/pump/... as
normal.
- Ian C. Blenke <ian@blenke.com>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:11:42 EDT