"Chris Bradford" <chrisbradford@xxxxxxxxxxxxxxxxxxxx> writes: > I'm using the bcm43xx built-in kernel driver with the firmware from my > windows driver. It works a treat with Network Manager but I really > want to have this card brought up automatically at startup. Its a > desktop that will only ever connect to the network 'linksys' that uses > wpa-psk encryption if that helps. I just add the startup for wpa_supplicant before the startup of the network interfaces. The default is at timeslot 12, it really needs be at timeslot 9 to be before the ifup_XXN calls. --- /etc/rc.d/init.d/wpa_supplicant~ 2006-05-03 07:57:47.000000000 -0700 +++ /etc/rc.d/init.d/wpa_supplicant 2006-05-16 15:39:50.000000000 -0700 @@ -2,7 +2,8 @@ # # wpa_supplicant # -# chkconfig: - 12 88 +# XXX wsr: was: - 12 88 +# chkconfig: - 09 88 # description: wpa_supplicant is a WPA Supplicant for Linux, BSD and \ # Windows with support for WPA and WPA2 (IEEE 802.11i / RSN). Supplicant \ # is the IEEE 802.1X/WPA component that is used in the client stations. \ Then do a chkconfig off/on for wpa_supplicant to reset the startup order of wpa_supplicant. I have had it set up like this for a few months now and it works fine both with madwifi and ndiswrapper (for my bcm4319 card). The only problem is whenever the kernel changes and livna doesn't offer the updated madwifi drivers in time. -wolfgang -- Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
