From: "Paul Rolland" <rol@witbe.net>
To: "'Pierre Ossman'" <drzeus-list@drzeus.cx>,
"'LKML'" <linux-kernel@vger.kernel.org>, <cramerj@intel.com>,
<john.ronciak@intel.com>, <ganesh.venkatesan@intel.com>
Subject: Re: e1000 with serdes only shows a fiber port
Date: Mon, 13 Mar 2006 17:23:14 +0100 [thread overview]
Message-ID: <003401c646ba$6e113280$b600a8c0@cortex> (raw)
In-Reply-To: <44157178.90507@drzeus.cx>
Hello,
> 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 think it simply means the card can only operate one of the two
modes at one time...
> 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
Did you try something like :
ethtool -s eth0 port tp
or
ethtool -s eth0 port mii
as the man page for ethtool says :
port tp|aui|bnc|mii
Select device port.
and ethtool indicates it supports :
ethtool -s DEVNAME \
[ speed 10|100|1000 ] \
[ duplex half|full ] \
[ port tp|aui|bnc|mii|fibre ] \
where fibre is what you have selected right now (from your report...)
Paul
next prev parent reply other threads:[~2006-03-13 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 13:19 e1000 with serdes only shows a fiber port Pierre Ossman
2006-03-13 16:23 ` Paul Rolland [this message]
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='003401c646ba$6e113280$b600a8c0@cortex' \
--to=rol@witbe.net \
--cc=cramerj@intel.com \
--cc=drzeus-list@drzeus.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.