From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Andrei Popa <andrei.popa@i-neo.ro>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDEV list <netdev@vger.kernel.org>
Subject: Re: [BUG] ethX misnumbered and one missing in mii-tool
Date: Fri, 30 Mar 2007 18:43:11 +0200 [thread overview]
Message-ID: <20070330164311.GA10235@atjola.homenet> (raw)
In-Reply-To: <1175240543.6219.10.camel@localhost>
On 2007.03.30 10:42:23 +0300, Andrei Popa wrote:
> On Thu, 2007-03-29 at 21:21 -0700, Jesse Brandeburg wrote:
> with kernel 2.6.20.4(and build in e1000 driver):
> zeus ~ # uname -a
> Linux zeus 2.6.20.4-zeus3 #3 SMP Wed Mar 28 13:44:50 EEST 2007 x86_64
> Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux
>
> the devices are recognized ok as eth0,eth1.eth2,eth3,eth4 but misnumered
> and one missing int mii-tool/ethtool
>
> Intel(R) PRO/1000 Network Driver - version 7.3.15-k2-NAPI
> Copyright (c) 1999-2006 Intel Corporation.
> ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:03:00.0 to 64
> e1000: 0000:03:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4)
> 00:15:17:21:0c:08
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:03:00.1[B] -> GSI 17 (level, low) -> IRQ 17
> PCI: Setting latency timer of device 0000:03:00.1 to 64
> e1000: 0000:03:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4)
> 00:15:17:21:0c:09
> e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 18
> PCI: Setting latency timer of device 0000:05:00.0 to 64
> e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4)
> 00:15:17:17:b7:68
> e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:05:00.1[B] -> GSI 19 (level, low) -> IRQ 19
> PCI: Setting latency timer of device 0000:05:00.1 to 64
> e1000: 0000:05:00.1: e1000_probe: (PCI Express:2.5Gb/s:Width x4)
> 00:15:17:17:b7:69
> e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
> ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 27 (level, low) -> IRQ 27
> e1000: 0000:06:02.0: e1000_probe: (PCI-X:100MHz:64-bit)
> 00:0e:0c:ba:a8:50
> e1000: eth4: e1000_probe: Intel(R) PRO/1000 Network Connection
>
> zeus ~ # mii-tool
> eth2: no link
> eth5: negotiated 100baseTx-FD, link ok
> eth6: no link
> eth7: no link
> zeus ~ #
>
> ethtool shows the same
The "misnaming" might be due to udev renaming the devices. Here, on
debian, there are automatically created static rules for network devices
in /etc/udev/rules.d/z25_persistent-net.rules, which you might want to
adjust to meet your expectations.
HTH
Björn
prev parent reply other threads:[~2007-03-30 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1175203383.6219.8.camel@localhost>
2007-03-30 4:21 ` [BUG] ethX misnumbered and one missing in mii-tool Jesse Brandeburg
2007-03-30 7:42 ` Andrei Popa
[not found] ` <1175240543.6219.10.camel@localhost>
2007-03-30 16:35 ` Lennart Sorensen
2007-03-30 17:18 ` Andrei Popa
2007-03-30 16:43 ` Björn Steinbrink [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070330164311.GA10235@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=andrei.popa@i-neo.ro \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).