From: Justin Piszcz <jpiszcz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org
Subject: Re: Intel on-board NIC negotiates at 10mbps instead of 1gbps (new Intel P55KG motherboard), driver bug?
Date: Tue, 13 Oct 2009 11:07:15 -0400 [thread overview]
Message-ID: <ba1f10320910130807r3f8ed8a5h543c14259d1bd1b@mail.gmail.com> (raw)
In-Reply-To: <ba1f10320910130446g33264abfy845e28856e2e6f69@mail.gmail.com>
On Tue, Oct 13, 2009 at 7:46 AM, Justin Piszcz <jpiszcz@gmail.com> wrote:
> Hello,
>
> I recently purchased/installed an Intel DP55KG motherboard and when I
> boot from the System Rescue CD (1.3.0) the on-board NIC only
> negotiates at 10mbps, when I plug the same cable into two other Intel
> x1 PCI-e nics, they negotiate at 1gbps without any issue. My old
> system also negotiated at 1gbps (a DG965WH) board.
>
> I understand support for chip has recently been added to the e1000e
> driver, has this been resolved in newer kernels?
>
> I am asking as I am still running memtest etc before putting the box
> in production, thanks.
>
> From the logs:
>
> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
> e1000e: Copyright (c) 1999-2008 Intel Corporation.
> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> e1000e 0000:00:19.0: pci_enable_pcie_error_
> reporting failed 0xfffffffb
> e1000e 0000:00:19.0: setting latency timer to 64
> e1000e 0000:00:19.0: irq 36 for MSI/MSI-X
> 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) (mac address)
> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: ffffff-0ff
>
> e1000e 0000:00:19.0: irq 36 for MSI/MSI-X
> e1000e 0000:00:19.0: irq 36 for MSI/MSI-X
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: RX
> 0000:00:19.0: eth0: 10/100 speed: disabling TSO
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> eth0: no IPv6 routers present
>
> Please cc as I am not on the lists, thanks.
>
> (resent as plain-text)
>
> Justin.
>
I spoke with Intel, they said they do not support Linux :-P
"However, Linux* has not been tested on this desktop board and we do
not offer any drivers for that operating system."
-- Can someone from Intel on the list (or linux-net) comment on this?
If the problem still occurs with the latest 2.6.31-rcX, I should try
and/or use the latest e1000e driver from here:
http://sourceforge.net/projects/e1000/ -- aside from that, are there
any other workarounds (if the problem persists)?
I have used the same cable with 3 different NICs (two x1 PCI-e) and
the last system I had was PCI-e (on-board) all negotiated 1gbps, this
one though only negotiates at 10mbps duplex.
Is this a known bug?
Justin.
next prev parent reply other threads:[~2009-10-13 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:46 Justin Piszcz
2009-10-13 15:07 ` Justin Piszcz [this message]
2009-10-13 17:31 ` Allan, Bruce W
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=ba1f10320910130807r3f8ed8a5h543c14259d1bd1b@mail.gmail.com \
--to=jpiszcz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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®