if you have udev installed and running you can just edit:
/etc/udev/rules.d/70-persistent-net.rules
to rename the devices persistently. No ugly firmware hacks needed.
Auke
Carsten Aulbert wrote:
Hi all,
sorry to bother you such a thing, but I'm not getting anywhere right
now. I've a
also, please note that this might actually be perfectly ok!
if you are experiencing high traffic, then having 20k interrupts per second
might
be just fine for your system.
lowering the interruptthrottlerate might actually not change the impact on your
system at all. But it will increase
Jon Wikne wrote:
Hi,
On a system I have, the e1000 driver stopped working in the transition
from 2.6.26.5 - 2.6.27-rc8.
When I compile the e1000 tree from 2.6.26.5 under 2.6.27-rc8, it works!
this is not a bug. you have a device for which support was moved from the e1000
driver to the
looks totally valid to me indeed!
Reviewed-by: Auke Kok [EMAIL PROTECTED]
Auke
Arthur Jones wrote:
Since e1000e has been existance in linux-2.6, we've
never released the hardware semaphore after a successful
write to the SPI EEPROM. I guess we don't write to
SPI EEPROM much -- but those
Allan, Bruce W wrote:
Hi Ken,
I'm not familiar with the string PT Quad Port Bypass Server Adapter but I
These (development) adapters were never sold for the general market and there is
no support available in the e1000/e1000e linux drivers, nor will that likely be
ever added.
A special
driver worked. somewhat. But was far from stable and
definately not ready for production environments :)
Cheers,
Auke
Ken
-Original Message- From: Kok, Auke [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2008 1:24 PM To: Ken Lee Cc: Allan, Bruce W;
e1000-devel
David Daney wrote:
I am running the e100 driver on a MIPS 4KEc system (32 bit mips with
non-coherent DMA). There was a problem where received packets would
get 'stuck' for several seconds at a time and then be released all at
once.
The cause was that if an interrupt were received when no
