| To: | Jos Vos <jos@xxxxxx> |
|---|---|
| Subject: | Re: e1000 driver problem with Intel Pro/1000 MT adapter |
| From: | Francois Romieu <romieu@xxxxxxxxxxxxx> |
| Date: | Sat, 4 Dec 2004 13:03:28 +0100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20041204021444.A5058@xos037.xos.nl> |
| References: | <200412032325.iB3NPdG04693@xos037.xos.nl> <20041204005946.GA26654@electric-eye.fr.zoreil.com> <20041204021444.A5058@xos037.xos.nl> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
Jos Vos <jos@xxxxxx> :
[...]
> 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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [E1000-devel] Transmission limit, Lennert Buytenhek |
|---|---|
| Next by Date: | Re: e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Previous by Thread: | Re: e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Next by Thread: | Re: e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |