The Fedora initscripts will set essid and WEP keys before running
'dhclient', and the current driver doesn't bother to try to associate,
so dhclient always fails. You need to bring the device up and then set
the ESSID again in order for it to associate, and then you can use
dhclient.
We already fixed this for suspend/resume; this just moves the same hack
into bcm43xx_init_board() so it happens on 'ifconfig up' and reset too.
Signed-off-by: David Woodhouse <[EMAIL PROTECTED]>
--- linux-2.6.16.ppc/drivers/net/wireless/bcm43xx/bcm43xx_main.c~
2006-03-21 23:50:00.000000000 +0000
+++ linux-2.6.16.ppc/drivers/net/wireless/bcm43xx/bcm43xx_main.c
2006-03-22 10:32:11.000000000 +0000
@@ -3429,6 +3429,9 @@ static int bcm43xx_init_board(struct bcm
}
bcm43xx_periodic_tasks_setup(bcm);
+ /*FIXME: This should be handled by softmac instead. */
+ schedule_work(&bcm->softmac->associnfo.work);
+
assert(err == 0);
out:
return err;
@@ -4326,9 +4329,6 @@ static int bcm43xx_resume(struct pci_dev
netif_device_attach(net_dev);
- /*FIXME: This should be handled by softmac instead. */
- schedule_work(&bcm->softmac->associnfo.work);
-
dprintk(KERN_INFO PFX "Device resumed.\n");
return 0;
--
dwmw2
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
