Thanks allot Dave.
I thought that the 8.0.6 was the newest, and will definatly try to
upgrade.
What does the TxDescriptorStep actually do ?
Will keep you all posted.
Thanks again.
Best regards,
Svavar O
Reykjavik - Iceland
On 1.10.2009, at 22:48, Graham, David wrote:
Hi Svavar,
This
Sorry, see information regarding TxDescriptorStep in the README.
Svavar O
Reykjavik - Iceland
On 2.10.2009, at 11:36, Svavar Örn Eysteinsson wrote:
Thanks allot Dave.
I thought that the 8.0.6 was the newest, and will definatly try to
upgrade.
What does the TxDescriptorStep actually do ?
Hello e1000 Developers,
I have a RHEL 5.3 (2.6.18-128.el5, driver e1000e-1.0.2.5 built) machine,
with two network adapters, which I'm trying to get to Team/Bond - an (i)
Intel PRO/1000 PT Server single-socket, and (ii) Intel PRO/1000 GT Desktop
single-socket. Individually, the cards work fine.
It looks like the bonding bug in the RHEL version of the driver has been fixed
(according to their bugzilla report), but I can't explain why it still doesn't
work for you with the update; perhaps the fix did not make it into that kernel.
I will be updating our SourceForge site with an updated
On Friday 02 October 2009, Nix wrote:
On 1 Oct 2009, Rafael J. Wysocki stated:
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either way).
The patch fixes it.
Hi Karen,
I was able to find Dell 1850 server with 82541 LOMs and installed 2.6.31.1
kernel on it. With both the in-kernel and the SF driver e1000 8.0.16 I had no
problems connecting to a Cisco 4948 at GB speeds. So it appears that the issue
is not generic.
Could you provide the output of:
On Fri, Oct 2, 2009 at 14:31, Rafael J. Wysocki r...@sisk.pl wrote:
On Friday 02 October 2009, Nix wrote:
On 1 Oct 2009, Rafael J. Wysocki stated:
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be
