public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: John Ronciak <john.ronciak@gmail.com>
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: Tue, 14 Mar 2006 09:11:15 +0100	[thread overview]
Message-ID: <44167AA3.8000607@drzeus.cx> (raw)
In-Reply-To: <56a8daef0603131430x8fd17fbn4aa5b5082e8aad0e@mail.gmail.com>

John Ronciak wrote:
> 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.
>   

I have tried Linux 2.6.11 and 2.6.15. I've also tried the independent
variant of the driver, version 6.3.9 and 7.0.33. We've also tried Dell's
version for RHEL4 (5.7.6.1).

BIOS has been confirmed to be the latest version.

> 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? 
>   

We haven't contacted Dell at this point no. Partly because we run Fedora
Core and not one of the supported dists (this will be a terminal server
so we want a more recent desktop on it).

> 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.
>
>   

We started doing this and discovered that the card started working when
we plugged it into a gigabit port (copper). ethtool still says fiber
though. So the immediate panic has settled. :)

It would still be nice to plug this into a 100 Mbps port since the
gigabit ports are a bit scarce.

Rgds
Pierre


      reply	other threads:[~2006-03-14  8:11 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
2006-03-13 22:30 ` John Ronciak
2006-03-14  8:11   ` Pierre Ossman [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=44167AA3.8000607@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=cramerj@intel.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=john.ronciak@gmail.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