@towo, runs perfectly well for me on mac-mini using proprietary wl.ko.
But that exactly I am whining now:
- On my Gentoo a self compiled linux-3.6-rc7 is segfaulting when starting wpa_supplicant - and using wl.ko
- Before "modprobe wl" does pass through though...
I have compiled using your .config and this segfaulting goes on. I don't get it. But I remember there is a special Debian kernel preparation:
cleaning out all proprietary firmware
Might be a new linux-3.6 firmware file is interfering my attempts on Gentoo with proprietary broadcom wl?
ralul,
Can you give you the version of `wpa_supplicant -v` & broadcom-sta/-dkms driver version where it works (the mac-mini)?
I had the same with latest broadcom-dkms-6.20.55.19 (came pre-installed on new dell laptops that shipped with ubuntu oneiric).
I'm using LMDE. wpasupplicant 1.0-2
Tried with:
3.6-rc7.towo.1-siduction-amd64
and,
3.6-0.slh.1-aptosid-amd64 (built on stable 3.6 release yesterday)
When I was getting kernel bug with 3.6-rc7, I compared to config of 3.5-liquorix, and there wasn't any relevant changes worth mentioning.
If wl is built with WEXT, boots okay, but wpa_supplicant fails to associate with AP (w/ wpa encryption), though it works in 3.5.x and prior.
If wl is built with nl/cfg80211 (as it should), Kernel BUG.
A few days ago I posted full details to debian bugtracker (to update to the new broadcom dkms driver) and linux-wireless, against 3.6-rc7:
http://marc.info/?l=linux-wireless&m=134875589522742&w=2Edit: reported again against 3.6 stable ->
http://marc.info/?l=linux-wireless&m=134908356432162&w=2