From: "John Ronciak" <john.ronciak@gmail.com>
To: "Pierre Ossman" <drzeus-list@drzeus.cx>
Cc: 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 14:30:15 -0800 [thread overview]
Message-ID: <56a8daef0603131430x8fd17fbn4aa5b5082e8aad0e@mail.gmail.com> (raw)
In-Reply-To: <44157178.90507@drzeus.cx>
On 3/13/06, Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> 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).
If it's a blade server blade then it's really not fiber or copper
(i.e. no PHY), it's a serdes connection to the backplane in the blade
server. I have never seen one of these not always have link (if the
blade is plugged into the backplane it must have link).
So what versions of things are you running? OS? Driver? Version
number of the blade? BIOS (must have the latest)? Windows doesn't
use the BIOS but does everything itself regarding HW setup.
Did you go back to Dell for support on this? What did they say? Are
you using a version of Linux that Dell supports on this hardware?
There might need to be some special drivers that are needed which Dell
supplies with their versions for specific HW. I'm not a blade server
expert but I've seen things like this before.
One suggestion is to disable auto-negotiation and force the link to 1
gigabit full duplex to see what that does.
Let us know.
--
Cheers,
John
next prev parent reply other threads:[~2006-03-13 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 13:19 Pierre Ossman
2006-03-13 16:23 ` Paul Rolland
2006-03-13 22:30 ` John Ronciak [this message]
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=56a8daef0603131430x8fd17fbn4aa5b5082e8aad0e@mail.gmail.com \
--to=john.ronciak@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®