[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problems with 2 NICs in amd64



Hi,

On Thu, Mar 22, 2007 at 04:20:22PM +0100, thunder7@xs4all.nl wrote:
> 
> There is no funky device renaming, like an /etc/iftab file, right?
> That would explain this behaviour.

# ls -l /etc/iftab
ls: /etc/iftab: No such file or directory

> 
> What does 
> 
> ethtool eth0

It was not installed. after "apt-get install ethtool".

I put one Via-Rhine-2 NIC and a 3com905 to do your test.
In this test, 3c905 that is eth1 did not work.

mail:~# uname -a
Linux mail 2.6.18-4-amd64 #1 SMP Wed Feb 21 18:12:05 UTC 2007 x86_64 GNU/Linux
mail:~# lspci | grep -i eth
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
05:07.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
mail:~# modprobe via_rhine
via-rhine.c:v1.10-LK1.4.1 July-24-2006 Written by Donald Becker
eth0: VIA Rhine II at 0x1a400, 00:18:f3:fd:ad:a8, IRQ 233.
eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link 0000.
mail:~# modprobe 3c59x
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:05:07.0: 3Com PCI 3c905C Tornado at ffffc20000006c00.
mail:~# lsmod | egrep '(3c|rhine)'
3c59x                  51380  0
via_rhine              30216  0
mii                    10368  2 3c59x,via_rhine
mail:~# dmesg | grep -i eth
eth0: VIA Rhine II at 0x1a400, 00:18:f3:fd:ad:a8, IRQ 233.
eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link 0000.
eth0:  setting full-duplex.
eth0: no IPv6 routers present
mail:~# ifconfig eth0 192.168.1.10 netmask 255.255.255.0
mail:~# ifconfig eth1 192.168.2.10 netmask 255.255.255.0
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device

mail:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 24
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x00000001 (1)
        Link detected: yes
mail:~# ethtool eth1
Settings for eth1:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

lspci -v (cut about the 2 NICs):
05:07.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
        Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
        Flags: bus master, medium devsel, latency 64, IRQ 50
        I/O ports at e800 [size=128]
        Memory at fbfffc00 (32-bit, non-prefetchable) [size=128]
        Expansion ROM at 20000000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
        Subsystem: ASUSTeK Computer Inc. Unknown device 80ed
        Flags: bus master, medium devsel, latency 64, IRQ 233
        I/O ports at a400 [size=256]
        Memory at f9fff800 (32-bit, non-prefetchable) [size=256]
        Capabilities: [40] Power Management version 2

  I think that is a good debug info for discovering the problem... do
you need other information?

  Thanks,
  Pedro



Reply to: