From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: netdev@vger.kernel.org
Subject: e1000e and Intel 82578DM, 10 Mbit/s only
Date: Fri, 22 Jan 2010 14:39:33 +0100 [thread overview]
Message-ID: <4B59AA95.4050207@ts.fujitsu.com> (raw)
Hi,
I'm currently facing a problem on Intel Ibexpeak mainboards that have
the Intel 82578DM chip for LAN. Device ID is 8086:10ef.
When using the e1000e driver that comes with distributions like
- Fedora 12
- RHEL 5.4
- openSUSE 11.2
then I only get the link up with 10 Mbit/s instead of 1000 Mbit/s.
Driver version is 1.0.2-k2 (according to modinfo)
If I use the e1000e from Sourceforge (Version 1.0.15 or 1.1.2) then
the machine gets the correct Gigabit link.
So some questions on the e1000e kernel driver:
- will the necessary patches be merged from the sourceforge driver to
the vanilla driver?
- why is the modinfo version so "static" on this driver? I've seen lots
of patches on the list archives and in git, but modversion seems to be
an universal constant at "1.0.2-k2"?
The bad impact of this problem is that with this bug of the kernel
driver systems affected by this will not pass trough a Red Hat hardware
certification network test. So guess what my current problem is: yeah,
right I should do hardware certification with this LAN.
Thanks for your attention & regards
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Business Clients
Dept. TSP CLI R&D SW OSE
Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany
Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@ts.fujitsu.com
Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html
next reply other threads:[~2010-01-22 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 13:39 Rainer Koenig [this message]
2010-01-22 17:02 ` e1000e and Intel 82578DM, 10 Mbit/s only 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=4B59AA95.4050207@ts.fujitsu.com \
--to=rainer.koenig@ts.fujitsu.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).