On Thu, Jul 27, 2006 at 08:04:50PM +0200, Bernhard Reiter wrote: > On Sat, May 27, 2006 at 02:20:59PM +0200, Bernhard Reiter wrote: > > Now that 2.6.17-rc5 is out I gave it a test run. > > Unfortunately the wireless driver bcm43xx does not work, > > it not been working with -rc3 either. > > Another testrun with 2.6.17.7 reveals, there are still problems > with the driver for me. Ben wrote that only rate 11M should work > reliably and there might be updates for 2.6.18 kernels comming. > > Problem: associating is not working well enough. > It seems to work once after a reboot which is > not enough to use dhcpclient. > > Am I the only person with this problem? It seems to be the case. :( Any pointer on what would be the next steps of debugging? > Is there a patch for 2.6.17.x fixing this part of bcm43xx? > I saw quite a few patches for bcm43xx in 2.6.18-rc2, > does someone have an idea if they address the problem? > One patch seems to be related to only one specific AP. > > Powerbook5,6 > Debian Sarge with backported wireless-tools 28-1 > > Here is a typical run, the first association works, > but then it allways fails: > Jul 27 00:04:45 localhost kernel: SoftMAC: Queueing Authentication Request to yy:yy:yy:yy:yy:yy > Jul 27 00:04:45 localhost kernel: SoftMAC: cannot associate without being authen > ticated, requested authentication > Jul 27 00:04:45 localhost kernel: SoftMAC: Sent Authentication Request to yy:yy:yy:yy:yy:yy > 24:9c:85:89. > Jul 27 00:04:45 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port > 67 interval 5 > Jul 27 00:04:45 localhost dhclient: receive_packet failed on eth1: Network is down
Attachment:
pgpdjKci70L8v.pgp
Description: PGP signature