From: Pierre Ossman <drzeus-list@drzeus.cx>
To: LKML <linux-kernel@vger.kernel.org>,
cramerj@intel.com, john.ronciak@intel.com,
ganesh.venkatesan@intel.com
Subject: e1000 with serdes only shows a fiber port
Date: Mon, 13 Mar 2006 14:19:52 +0100 [thread overview]
Message-ID: <44157178.90507@drzeus.cx> (raw)
Hi!
I'm having problems with the e1000 card in a Dell Poweredge 1855. This
model has support for both copper and fiber and has two cards on the PCI
bus (might supposed to be one for each type).
The problem is that both of these cards show only FIBER as a supported
port type, but I only have plain copper connectors attached to the
machine. There is no link detected at either end, except for a small
flicker just when the e1000 module is loaded.
The hardware doesn't seem to be the problem since it works nicely in
Windows on the same machine.
The device id of both controllers is 8086:107b, meaning SERDES. However,
if I look into e1000_ethtool.c:e1000_get_settings() I can see a test for
copper media, then and else assuming that the card is a fiber card.
Since this card can do both I'm guessing this code is broken.
I'm in rather desperate here since this is a blade server (i.e. no
chance of putting in another network card). :/
Rgds
Pierre
lspci:
05:04.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
Controller (rev 03)
Subsystem: Dell: Unknown device 018a
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 185
Memory at fe7e0000 (64-bit, non-prefetchable) [size=128K]
I/O ports at dcc0 [size=64]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device.
Capabilities: [f0] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
05:04.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
Controller (rev 03)
Subsystem: Dell: Unknown device 018a
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 193
Memory at fe7c0000 (64-bit, non-prefetchable) [size=128K]
I/O ports at dc80 [size=64]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device.
Capabilities: [f0] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
ethtool: (eth1 is identical)
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: no
next reply other threads:[~2006-03-13 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 13:19 Pierre Ossman [this message]
2006-03-13 16:23 ` e1000 with serdes only shows a fiber port Paul Rolland
2006-03-13 22:30 ` John Ronciak
2006-03-14 8:11 ` Pierre Ossman
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=44157178.90507@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=cramerj@intel.com \
--cc=ganesh.venkatesan@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@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