On 6/26/06, Jeff Vian <jvian10@xxxxxxxxxxx> wrote:
On Mon, 2006-06-26 at 10:54 -0700, Lonni J Friedman wrote: > On 6/26/06, Jeff Vian <jvian10@xxxxxxxxxxx> wrote: > > On Mon, 2006-06-26 at 08:36 -0700, Lonni J Friedman wrote: > > > I'm seeing some bizarre networking problems with the latest FC5 > > > kernel. On one system, all of my ethernet interfaces have reversed > > > themselves. eth2 is now eth0, eth0 is eth2. If I boot back into the > > > last 2.6.16 based kernel, everything 'works' as expected again. > > > > > > On another system, where I'm using ndiswrapper-1.18 for a PCI wifi > > > NIC, it just doens't work at all in the 2.6.17 kernel. I see tons of > > > messages in dmesg about wlan0 getting reset, and there's no throughput > > > at all (100% packet loss). Falling back to the last 2.6.16 kernel > > > fixed that problem too. > > > > > This sounds like a resurfacing of an earlier problem where the new > > kernel and utilities changed the order in which devices were scanned on > > the mobo. The names are assigned in the order they are seen by default, > > but IIRC there are workarounds that will force the system to always > > assign the same nic the same name. > > do you happen to remember what that workaround was? > Rick Stevens answered in another reply. > > > > I have not seen the nic problem and do not remember the details, but > > then I do not have multiple NICs, nor am I using ndiswrapper on my PC. > > When I was using ndiswrapper, IIRC it had to be recompiled for each > > kernel update. > > Right, but that's not the problem i'm having. The module was > recompiled, it loads fine, wlan0 comes up, i get 100% packet loss, > with loads of reset errors in dmesg. > Have you tried removing the driver and reinstalling it since you did the ndiswrapper recompile?
I'm not sure I understand which driver you're talkikng about. The ndiswrapper kernel module was recompiled for this new kernel.
This symptom usually means a problem with the kernel - hardware interface, and since the ndiswrapper - driver interface is part of that...? It likely is something that recently changed (kernel and ndiswrapper) has a problem with something that did not change (hardware & driver?).
If you mean the windows driver that ndiswrapper is using, that hasn't changed in ages, and I don't see a newer one recommended on the ndiswrapper website. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@xxxxxxxxx LlamaLand http://netllama.linux-sxs.org
