From: Francois Romieu <romieu@fr.zoreil.com>
To: Jos Vos <jos@xos.nl>
Cc: netdev@oss.sgi.com
Subject: Re: e1000 driver problem with Intel Pro/1000 MT adapter
Date: Sat, 4 Dec 2004 13:03:28 +0100 [thread overview]
Message-ID: <20041204120328.GA1191@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20041204021444.A5058@xos037.xos.nl>
Jos Vos <jos@xos.nl> :
[...]
> Well, I could do that, but the idea was to use this in a RHEL3
> system, so ...
1 - Imho people at RedHat/wherever need more details (chipset, mobo,
dmesg, lspci -vx, 2.4.21 savor ?).
2 - Testing recent 2.6.x will provide a different datapoint and a wider
review: a few people use e1000 for interested things here but they
do not necessarily have the resources to help with a specific vendor
released kernel. The vendor can use the datapoint though.
3 - Comparing lspci and dmesg output for the different failure may give
an hint.
--
Ueimor
next prev parent reply other threads:[~2004-12-04 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 23:25 e1000 driver problem with Intel Pro/1000 MT adapter Jos Vos
2004-12-04 0:59 ` Francois Romieu
2004-12-04 1:14 ` Jos Vos
2004-12-04 12:03 ` Francois Romieu [this message]
2004-12-04 17:20 ` Jos Vos
2004-12-05 0:00 ` Scott Feldman
2004-12-05 8:37 ` Ben Greear
2004-12-06 9:42 ` Jos Vos
2004-12-06 11:51 ` Jos Vos
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=20041204120328.GA1191@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=jos@xos.nl \
--cc=netdev@oss.sgi.com \
/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).