Ehud Gavron wrote: > Possibly. I'll ensure an ifdown before rmmod in the future. Upon my > return to home it associated and wep'ized but was still unable to > exchange traffic (rxcount and txcount incrementing on if, wireshark sees > traffic, but the interface refuses to stay ifconfig'd up with an ip. > Turns radio off. Makes ip go away. Solid 85/100 on the iwconfig. rmmod > bcm43xx; ndiswrapper works.) > > Removed new modules from the ftp download, make modules_install in the > kernel source tree from 03/30, modprobe bcm43xx... works ok. > Plain iwconfig/ifconfig not even using network-scripts. Various APs at > the Golden Nugget, McCarran, and now my house. Work fine with older > code. Work with ndiswrapper. Did not work with newer code, although > like I said it wasn't that it "failed" but rather wouldn't stay up long > enough to pass IP packets or keep the address on the interface. > > Let me know what other diagnostics/tests I can run... I just got back > from five days in Vegas, so I need a drink and some debugging to unwind ;)
Obviously, you weren't in Vegas for fun. After 5 days there, I usually need to take a break from drinking, and my mind isn't really good for debugging. If you could, I would appreciate you grabbing the appropriate combined patch for your kernel and testing it. The code should be the same as what was in the tarball, but who knows. Thanks, Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
