Generic Realtek 8139 and RH 7.3

[dissekj]

I have been trying to get a generic (ASound) Realtek 8139 NIC card to work with a fresh RedHAt 7.3 install for more than a day. I have tried everyting I know (not that much) to get it working.

The hwconf file lists it only as a network device, but cant figure out what kind.

I've been trying to get the 8139too driver to work (compiled itno kernel), but my knowledge of Linux drivers/hardware is very limited so, I'm probably doing it all wrong.

The card works fine in windows and a previous install of Mandrake 8.2. Any help would be greatly appreciated.

[SkyNet]

Have you tried at the console:

modprobe 8139too

or

insmod 8139too

[dissekj]

I have tried those commands several times. They both generate plenty of errors.

Here are the messages:

> modprobe 8139too
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: init_module: No such device
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: insmod /lib/modules/2.4.18-3/kernel/drivers/net/8139too.o failed
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: insmod 8139too failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters

>insmod 8139too
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: unresolved symbol mii_link_ok_R2b6bad3e
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: unresolved symbol mii_ethtool_sset_Rb778a431
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: unresolved symbol mii_ethtool_gset_Re2386924
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: unresolved symbol mii_nway_restart_Rcb8649cd
Using /lib/modules/2.4.18-3/kernel/drivers/net/8139too.o


This is the section of hwconf that references my card (I dont know if this means anything, but it looks fishy to me)

class: NETWORK
bus: PCI
detached: 0
device: eth
driver: unknown
desc: "Unknown vendor|unknown device 1516:0803"
vendorId: 1516
deviceId: 0803
subVendorId: 1516
subDeviceId: 0803
pciType: 1

[Spot]

> modprobe 8139too
/lib/modules/2.4.18-3/kernel/drivers/net/8139too.o: init_module: No such device

I can think of at least 3 things you could try that might be of some help to you...

First, make sure any BIOS reference to Plug & Play is set to OFF.

Second, there are 2 different 8139 modules, 8139cp and 8139too. You might try the other one.

Third, you might try upgrading the kernel. The current RH 7.3 kernel is 2.4.18-5. That might include an updated 8139too module that fixes your problem. I know it did for me in regards to another Realtek module. Redhat kernel upgrades are fairly painless these days, and well documented on their website...see the erratta pages for more info and download locations.

[JimH]

More then likely the dependancies are not loading before the 8139too module.

Anytime you see unresolved symbol errors check and see if the module you are trying to load requires other modules.

$ cat /lib/modules/2.4.18-5/modules.dep | grep 8139too
/lib/modules/2.4.18-5/kernel/drivers/net/8139too.o: /lib/modules/2.4.18-5/kernel/drivers/net/mii.o

This tells you the mii module must be loaded before the 8139too module.

Jim H

[SkyNet]

You can also try the rtl8139 module.

From what I can see, you may not have the module at all. If it's not a dependency error you may need to recompile your kernel with support for the rtl8139/8139cp/8139too module.

[JimH]

Red Hat by default enables support for the Realtek 8139. Recompiling the kernel is not necessary.

Jim H

[dissekj]

Inserting the mii module first clears up the unresolved symbol error, but an error a lot like the last few lines of the modprobe result (above) still remains.

I am now using kernel 2.4.18-5, but that didn't do the trick. Also, Plug & Play was off in the BIOS and 8139cp doest work either. rtl8139 does not seem to be supported by RH 7.3.

This is very frustrating.......

[SkyNet]

Red Hat by default enables support for the Realtek 8139. Recompiling the kernel is not necessary.

Jim H

This is what leads me to believe that he possibly doesn't have the module or maybe the module he has is not for his kernel.

init_module: No such device

If he's getting an error similar to this after clearing up the unresolved symbols then perhaps he's missing something else, or it's not there.

Recompiling a kernel is a good practice anyway, EVERYONE should be forced to do it ;D

[dissekj]

Before I upgraded (when I was using 2.4.18-3) the first thing I tried was to recompile the kernel. This didnt appear to be necessary, as it was already availible as a module, but I set it to be compiled in and did it anyways. Didn't seem to do anything.