Hy!
I am new to Slackware (9.0) and have some problems to get my networkcard working. It has a RTL8139C Chipset.
During boot I get some failure messages (logs are attached below).
It seesms to be that the system tries to load a driver module named 8139cp.o.gz, but it seems to be the wrong driver. I think 8139too is the right one for that card. So i am wondering why i tries to load this driver. Is there something like autoprobe that tells the system to load the 8139cp driver, or something like that. And why is the same error message there 8 or more times? I don´t understand whats internally going on there. Can someone help me?

Another question: Where do I get the boot messages after booting (the bootmessage below, is directly written off)? Is it stored in a file? I tried syslog, messages and dmesg. But there is nothing written about a device driver error. dmesg (also atached below) also says something about the 8139cp driver (also many times), but don´t say that there was an error. Quite the contrary, it says something about eth0, this is at boot time not even mentioned. I am a bit confused.
Hope someone can help me.

Here the bootmessage:
-------------------<snip>----------------------------------
INIT: Entering runlevel: 3
Going multiuser...
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 11 for device 00:10.0
PCI: Sharing IRQ 11 with 01:00.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc88fbc00, 00:30:84:3d:24:49, IRQ 11
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: init_module: No such device
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: Hint: insmod errors
can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz failed
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod 8139cp failedusb.c: registered new driver usbdevfs
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 9 for device 00:07.2
uhci.c: USB UHCI at I/O 0xf800, IRQ 9
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: init_module: No such device
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: Hint: insmod errors
can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz failed
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod 8139cp failed8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: init_module: No such device
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: Hint: insmod errors
can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz failed
insmod: /lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz: insmod 8139cp failed8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)

[the error messages repeat several times here]
------------------------------<snip>--------------------------------


and here the output of dmesg:
--------------------<snip>------------------------------------
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 11 for device 00:10.0
PCI: Sharing IRQ 11 with 01:00.0
eth0: RealTek RTL8139 Fast Ethernet at 0xc88fbc00, 00:30:84:3d:24:49, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Found IRQ 9 for device 00:07.2
uhci.c: USB UHCI at I/O 0xf800, IRQ 9
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
usb-uhci.c: $Revision: 1.275 $ time 15:38:38 Mar 11 2003
usb-uhci.c: High bandwidth mode enabled
-------------------------<snip>-------------------------------


greetings,
Kai

try netconfig and give it the proper device for your netcard...

In Slack 9.0 a new feature has been introduced, it is called hotplugging. It was an option that was offered during the install if you desired it to be enabled. The hotplug procedure has a file named /etc/hotplug/blacklist that modules can be added to on a system to eliminate such problems as this. Add the module 8139cp to the end of the /etc/hotplug/blacklist file. It will instruct the hotplug system to not load the listed module. The 8139too module will still be loaded as required.

If you desire to disable the feature and load all modules manually then I suggest the following command;

chmod 000 /etc/rc.d/rc.hotplug

To remove the execution bits from the startup script. It can be enabled again if desired by using 755 instead.

Yes, the blacklist thing works. Thx a lot