This issue probably belongs here as a heads up for kernel 2.4.0...
Running LM7.2 with kernel 2.4.0 gives the problem outlined below. Rebooting
with a stock LM7.2 gives the proper setup for my 2 ethernets...
Usually I post my bug reports to bugzilla; but this is not yet a Mandrake bug
unless someone can reproduce it within cooker. Let me know if I should bugzilla
it anyway...
Regards,
Pierre
------------ originally posted to expert -------------
[Creating this response; then will reboot because networking is now quite
confused.]
Tom Berkley wrote:
>
> Look in /etc/modules.conf and see what aliases were created for your
> nic's. You may have a legacy alias that you need to edit.
None were "created"... the last 3 lines were:
options eepro io=0x210 irq=11
alias sound-slot-0 es1370
alias eth0 eepro
to which I manually appended:
alias eth1 3c59x
I've just tried every combination and permutation of these lines, including:
- various combinations removed
- move sound up instead of between eth0 lines
- reversed order of eth[01]
- removed options only
- all eth refs removed
- etc
Each time, I do:
# rm -f ifcfg-eth*; rmmod eepro 3c59x; lsmod; depmod
and start draknet fresh which now gives me:
# service network start
Setting network parameters: [ OK ]
Bringing up interface lo: [ OK ]
Enabling IPv4 packet forwarding [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
Bringing up interface eth3: [ OK ]
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:AA:00:CF:8D:65
inet addr:192.168.134.100 Bcast:192.168.134.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base
address:0x210
Only *one* adapter comes up; but with
# lsmod
Module Size Used by
3c59x 22048 0 (unused)
eepro 13568 1 (autoclean)
[...]
Starting to look like an issue between 2.4.0 and draknet and ...?
Leaving everything as configured (even eth[23])...
[reboot]
dmesg:
### duplicate...
id: 0x64 io: 0x210 eth0: Intel EtherExpress Pro/10 ISA at 0x210,
00:aa:00:cf:8d:65, IRQ 11, 10BaseT.
id: 0x64 io: 0x210 eth1: Intel EtherExpress Pro/10 ISA at 0x210,
00:aa:00:cf:8d:65, IRQ 11, 10BaseT.
eth0: set Rx mode to 1 address.
eth0: set Rx mode to 1 address.
eth0: set Rx mode to 1 address.
### trying to start 2nd adapter with eepro
eth1: unable to get IRQ
11.
### 2nd (3Com) ignored
and now only eth0 comes up until...
# modprobe 3c59x
# service network start
Setting network parameters: [ OK ]
Bringing up interface lo: [ OK ]
Enabling IPv4 packet forwarding [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
Bringing up interface eth3: Delaying eth3 initialization.
[FAILED]
Similar to this, during bootup, eth[01] "appeared" to start but only eth0 did,
and eth[23] gave the delaying/failed messages.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:AA:00:CF:8D:65
inet addr:192.168.134.100 Bcast:192.168.134.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:6 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x210
eth2 Link encap:Ethernet HWaddr 00:01:02:E8:D8:8D
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:5 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16192 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
txqueuelen:0
For grins, I deleted ifcfg-eth*, removed the 3 eth entries from modules.conf and
rebooted again.
Networking failed to start altogether. Put 3 lines back and draknet configured
eth[0123] once again and now I can't start the 3com card which puts me worse off
than before...
Looks like I'll have to delve into the source to figure out why draknet would
think there were THREE and now FOUR adapters...
Thanks,
Pierre
> Tom Berkley
>
> Pierre Fortin wrote:
> >
> > Hi,
> >
> > Anyone know why I would have 3 ethernets defined when I only have 2..?
> >
> > I had an Intel EtherExpressPro/10+ (eepro) which is a tad flaky (tx errors), and
> > today added a 3Com 3c905B-TX... When I used DrakConf to configure it, I thought
> > it was weird that I was asked for eth[012] parms...
> >
> > Now, I get:
> > # ifconfig
> > eth0 Link encap:Ethernet HWaddr 00:AA:00:CF:8D:65
> > inet addr:192.168.134.100 Bcast:192.168.134.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2301 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2853 errors:48 dropped:0 overruns:0 carrier:8
> > collisions:3 txqueuelen:100
> > Interrupt:11 Base address:0x210
> >
> > eth2 Link encap:Ethernet HWaddr 00:01:02:E8:D8:8D
> > inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1097 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:5 Base address:0xd000
> > [snip lo]
> >
> > # ifconfig eth1 (duplicate of eth0.MAC and eth1.IP... -- down)
> > eth1 Link encap:Ethernet HWaddr 00:AA:00:CF:8D:65
> > inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:11 Base address:0x210
> >
> > dmesg shows:
> > [snip]
> > es1370: found adapter at io 0xb800 irq 10
> > es1370: features: joystick off, line in, mic impedance 0
> > id: 0x64 io: 0x210 eth0: Intel EtherExpress Pro/10 ISA at 0x210,
> > 00:aa:00:cf:8d:65, IRQ 11, 10BaseT.
> > id: 0x64 io: 0x210 eth1: Intel EtherExpress Pro/10 ISA at 0x210,
> > 00:aa:00:cf:8d:65, IRQ 11, 10BaseT.
> > ^^^^^^^^Duplicate
> > eth0: set Rx mode to 1 address.
> > eth0: set Rx mode to 1 address.
> > eth0: set Rx mode to 1 address.
> > eth1: unable to get IRQ 11.
> > Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]).
> > lp0: using parport0 (polling).
> > nbd: registered device at major 43
> > 3c59x.c:LK1.1.11 13 Nov 2000 Donald Becker and others.
> > http://www.scyld.com/network/vortex.html $Revision: 1.102.2.46 $
> > See Documentation/networking/vortex.txt
> > eth2: 3Com PCI 3c905B Cyclone 100baseTx at 0xd000, PCI: Found IRQ 5 for device
> > 00:09.0
> > PCI: The same IRQ used for device 00:04.2
> > 00:01:02:e8:d8:8d, IRQ 5
> > 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
> > MII transceiver found at address 24, status 786d.
> > MII transceiver found at address 0, status 786d.
> > Enabling bus-master transmits and whole-frame receives.
> > eth2: using NWAY autonegotiation
> >
> > # cat ifcfg-eth[012]
> > DEVICE=eth0
> > BOOTPROTO=static
> > IPADDR=192.168.134.100
> > NETMASK=255.255.255.0
> > NETWORK=192.168.134.0
> > BROADCAST=192.168.134.255
> > ONBOOT=yes
> >
> > DEVICE=eth1
> > BOOTPROTO=static
> > IPADDR=192.168.1.100
> > NETMASK=255.255.255.0
> > NETWORK=192.168.1.0
> > BROADCAST=192.168.1.255
> > ONBOOT=yes
> >
> > DEVICE=eth2
> > BOOTPROTO=static
> > IPADDR=192.168.1.100
> > NETMASK=255.255.255.0
> > NETWORK=192.168.1.0
> > BROADCAST=192.168.1.255
> > ONBOOT=yes
> >
> > I've searched for a couple of hours and can't find anything related to this.
> > Any reference to multiple ethernets is for deliberately configuring such.
> >
> > I'm running LM7.2/kernel2.4.0...
> >
> > Still researching; but hoping someone has a pointer to the right path...
> >
> > Thanks,
> > Pierre
--
Linux (Up 5 min) -- Reboots are for system upgrades...
Last reboot reason: 01/10/01: network bug handling multiple ethernets
