Error with 'modprobe 8139too'

Rum · 03-25-2003, 12:17 AM

After two months I started my slackware linux, and I found that the network was not rightly installed - the 8139too module was not installed. When I run 'modprobe 8139too' I got the error:
(Not copy/pasted)

path to 8139too.o: init_module: No such device
path to 8139too.o: hint: errors can be caused by incorrect module parameters , etc etc

Now I dont have the minimum idea of what to do now. Can somebody guide me get my network settings back right.

thanks
rm

born4linux · 03-25-2003, 12:37 AM

post the output of this command:

lspci | grep Ethernet

Rum · 03-25-2003, 12:41 AM

It shows RTL 8139/8139C (rev 10)

Does this mean 8139too is wrong driver? What is the right one?

born4linux · 03-25-2003, 01:20 AM

hmm...try the 8139cp module...

but before u do that, check the loaded modules in ur system via '/sbin/lsmod'.

Rum · 03-25-2003, 02:31 AM

Even with 8139cp I got the same error as earlier.
Also, dmesg shows:
eth0: RealTek RTL8139 Fast Ethernet at ... , IRQ 11
eth0: Identified 8139 chip type 'RTL 8139B'

Any clues?

Darkl0rd · 03-25-2003, 03:33 AM

well your last post shows it that it's recognized and prolly already loaded the driver for it.
do a ifconfig and check if there is a eth0 device if not try typing ifconfig eth0 up
if all this fails paste the output of 'lsmod' and have a checkup in your kernel source to see if you compiled the driver in the kernel instead of a module.

Rum · 03-25-2003, 04:06 AM

1. ifconfig shows eth0 is up, but am not able to ping to any other machine in the network
2. lsmod shows only ext3 and jbd
3. For the kernel vs module, I checked the .config file, 8139cp, 8139too are set to m, and 8139too_pio is set to y.

Rum · 03-25-2003, 05:31 AM

This was a hardware/cable problem, I connected the network cable to another socket and it worked. Sorry for not checking that first, thanks to those who replied

But lsmod does not show the 8139 module, does it mean it is compiled into kernel?