SEO

I installed two belkin ethernet cards in two machines last week, an old
one with an AMD processor and Redhat 7.3, and a new pentium with Redhat
9. I plugged them into a Belkin wireless router and gateway.

Turned on the old machine: recognised the card, asked to install,
connected to the router, set up the network.

Turned on the new machine: recognised the card, asked to install, then
when trying to connect, complained that the card was missing.

The new machine has an ASUS mboard with some builtin flaky ethernet
rubbish, which is probably why the belkin card isn't found properly. But
that doesn't change the factt hat I don't know what to do to fix it.
Here are some printouts that looked useful, but I couldn't spot the problem:

Error from Redhat setup program:

redhat-config-network:

The Ethernet card could not be initialized.
Please verify your settings and try again.

Command failed: /sbin/modprobe 8139cp

Output:
Warning: ignoring irq=9, no such parameter in this module
/lib/modules/2.4.20-8smp/kernel/drivers/net/8139cp.o: init_module: No
such device
/lib/modules/2.4.20-8smp/kernel/drivers/net/8139cp.o: insmod
/lib/modules/2.4.20-8smp/kernel/drivers/net/8139cp.o failed
/lib/modules/2.4.20-8smp/kernel/drivers/net/8139cp.o: insmod 8139cp failed
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

------------------------

From /etc/sysconfig/hwconf. On machine that works:

class: NETWORK
bus: PCI
detached: 0
device: eth
driver: 8139too
desc: "Realtek|RTL-8139/8139C"
vendorId: 10ec
deviceId: 8139
subVendorId: 1799
subDeviceId: 5000
pciType: 1
-

From /etc/sysconfig/hwconf. On machine that doesn't:

class: NETWORK
bus: PCI
detached: 0
device: eth
driver: unknown
desc: "Galileo Technology Ltd.|unknown device 11ab:4320"
vendorId: 11ab
deviceId: 4320
subVendorId: 1043
subDeviceId: 811a
pciType: 1
-
class: NETWORK
bus: PCI
detached: 0
device: eth
driver: 8139too
desc: "Realtek|RTL-8139/8139C/8139C+"
vendorId: 10ec
deviceId: 8139
subVendorId: 1799
subDeviceId: 5000
pciType: 1
-

----------------------------

dmesg output:

8139too Fast Ethernet driver 0.9.26
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 Fast Ethernet at 0xe096e400, 00:30:bd:b2:e1:4d, IRQ 22
eth0: Identified 8139 chip type 'RTL-8139C'


------------------------

From boot.log:

Mar 6 14:44:36 dharmib rc: Starting pcmcia: succeeded
Mar 6 14:44:36 dharmib netfs: Mounting other filesystems: succeeded
Mar 6 14:44:36 dharmib autofs: automount startup succeeded
Mar 6 14:44:37 dharmib sshd: succeeded
Mar 6 14:44:35 dharmib iptables: succeeded
Mar 6 14:44:35 dharmib sysctl: net.ipv4.ip_forward = 0
Mar 6 14:44:35 dharmib sysctl: net.ipv4.conf.default.rp_filter = 1
Mar 6 14:44:35 dharmib sysctl: kernel.sysrq = 0
Mar 6 14:44:35 dharmib sysctl: kernel.core_uses_pid = 1
Mar 6 14:44:35 dharmib network: Setting network parameters: succeeded
Mar 6 14:44:35 dharmib network: Bringing up loopback interface: succeeded
Mar 6 14:44:35 dharmib ifup: 8139too device eth1 does not seem to be
present, delaying initialization.
Mar 6 14:44:35 dharmib network: Bringing up interface eth1: failed

-----------------------------

If there is anyone really cluey who can spot the problem and suggest a
fix, it will be much appreciated! I noticed that it was modprobing
8139cp, whereas the working machine is using 8139too. But I couldn't
work out how to select that in the guey-smuey net setup interface!

--
Ron House house@usq.edu.au
http://www.sci.usq.edu.au/staff/house