On 01/11/06, Brian C <[EMAIL PROTECTED]> wrote: > David Spreen wrote: > > the interface will not associate with any access point. iwconfig ap > > macaddress won't work either.
I also have a similar problem. Some times (say 50%) the interface associates to the access point (I can see the AP Mac address in iwconfig) but the DHCP negotiation does not work. But maybe the association do not work at all. > That's weird. I suppose it works fine under OS X and/or Windows, > otherwise you'd suspect a hardware problem. That makes me think your > version of madwifi and/or your kernel version are not playing nice > either in isolation or together. > > Did you do something like the following when installing madwifi? I am using madwifi-source 1:0.9.2+r1710.20060914-1 from Debian testing and madwifi-tools 1:0.9.2+dfsg-1 also from Debian testing. In general I can make the network card work correctly by removing and reinstalling the madwifi kernel module # rmmod ath_pci # modprobe ath_pci but it does not always works. Of course I do not have this problem under Mac OS X. It looks like the bug is already known as Debian bug #394606 "madwifi-source: Driver frequently loses association or cannot associate" and is already correct in upstream subversion revision r1755. I hope to see a Debian package correcting the bug soon. bye, -- Dr. Ludovic Rousseau ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mactel-linux-users mailing list Mactel-linux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
