On Thu, Jul 13, 2006 at 04:41:33PM -0000, Michel Lesoinne wrote:
> I have been experiencing the same problem. I have an Apple MacBook Pro
> 17" and installed dapper on it. I also noticed it was network related
> and perhaps triggered by wpa_supplicant/knetworkmanager combo. This
> led me to find this thread. Unlike others, my lspci gives me slightly
> different numbers: 168c:001c
That's very useful info. I've hacked together a .deb that makes
madwifi-ng be loaded instead of madwifi. That fixes it for me, but
apparantly some people have other problems with -ng. I'll just finish
polishing it (probably tomorrow) and upload it somewhere.
On Thu, Jul 13, 2006 at 04:41:33PM -0000, Michel Lesoinne wrote: knetworkmanager combo. This
> I have been experiencing the same problem. I have an Apple MacBook Pro
> 17" and installed dapper on it. I also noticed it was network related
> and perhaps triggered by wpa_supplicant/
> led me to find this thread. Unlike others, my lspci gives me slightly
> different numbers: 168c:001c
That's very useful info. I've hacked together a .deb that makes
madwifi-ng be loaded instead of madwifi. That fixes it for me, but
apparantly some people have other problems with -ng. I'll just finish
polishing it (probably tomorrow) and upload it somewhere.
Cheers, Søren.