Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13300 - broadcom wireless drivers fail upon upgrading kernel to 2.6.28.1

Attached to Project: Arch Linux
Opened by DJ Amireh (cactusbin) - Monday, 16 February 2009, 05:49 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 21 March 2009, 21:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I installed the broadcom wireless drivers from here http://www.broadcom.com/support/802.11/linux_sta.php (the 32-bit version). I was using kernel version 2.6.26 at the time. I followed the instructions on the wiki page http://wiki.archlinux.org/index.php/Broadcom_BCM4312 . To get it to work each reboot I had to run these commands "modprobe ieee80211_crypt_tkip" "insmod /lib/modules/2.6.27-ARCH/kernel/drivers/net/wireless/wl.ko". This worked perfectly and I could connect to the internet and everything. The wireless device showed up under "eth3". I then upgrade my kernel to 2.6.28.1 and reboot. Now two new wireless devices show up "wlan0" amd "wmaster0" without me entering any commands. Wlan0 was the wireless device. I tried entering in my essid, but it wouldn't associate with the access point. I tried running the commands as normal and it didn't help. I confirmed the b43 drivers are blacklisted as well.
This task depends upon

Closed by  Hugo Doria (hdoria)
Saturday, 21 March 2009, 21:57 GMT
Reason for closing:  Upstream
Comment by Corrado Primier (bardo) - Monday, 16 February 2009, 10:09 GMT
Did you get the latest broadcom-wl from AUR and recompile it for 2.6.28? Probably there's another module which wasn't blacklisted that takes over the device. What does lsmod say?
Anyway, I don't think this report should be here. If there actually is a bug, it's upstream.
Comment by DJ Amireh (cactusbin) - Monday, 16 February 2009, 16:06 GMT
Yes I did have the latest drivers and yes I did recompile it. I looked under lsmod and I found a weird wireless driver "rtl8187". I blacklisted it and it did away with the wlan0 and wmaster0 thing. I rebooted and modprobed and insmoded the drivers, but now it doesn't work at all (no eth3 or wlan0 or anything shows up). No error messages and it says it is loaded under lsmod.

Loading...