You are not logged in.
Offline
Did your device naming change perhaps?
Btw, upgrade to 3.0 worked fine here on a 2010 MBA.
ᶘ ᵒᴥᵒᶅ
Offline
we cannot help you unless you say that chipset. i'm sure that you forgot to rebuild the module for 3.0.
Give what you have. To someone, it may be better than you dare to think.
Offline
litemotiv wrote:Did your device naming change perhaps?
How can I check that?
ifconfig -a
Which revision Air do you have?
ᶘ ᵒᴥᵒᶅ
Offline
we cannot help you unless you say that chipset. i'm sure that you forgot to rebuild the module for 3.0.
Could you indicate the command I should type to obtain the information you're asking?
If you're asking for the chipset of the network controller, lspci says: Broadcom BCM43224.
What module are you refering to?
Offline
wonder wrote:we cannot help you unless you say that chipset. i'm sure that you forgot to rebuild the module for 3.0.
Could you indicate the command I should type to obtain the information you're asking?
If you're asking for the chipset of the network controller, lspci says: Broadcom BCM43224.
What module are you refering to?
broadcom-wl from aur
also take a look at this: https://bugs.archlinux.org/task/25454
I think this should be fixed in broadcom-wl. E.g., they could add a file "/lib/modprobe.d/broadcom-wl.conf", containing:
blacklist bcma
Last edited by wonder (2011-08-08 20:37:47)
Give what you have. To someone, it may be better than you dare to think.
Offline
bloom wrote:litemotiv wrote:Did your device naming change perhaps?
How can I check that?
ifconfig -a
How can I know if my device naming has changed from the output of this command?
If so, how could I solve my problem based on that knowledge?
Which revision Air do you have?
3,2
Offline
litemotiv wrote:Which revision Air do you have?
3,2
Thanks, in that case forget what wonder said, your wireless should work fine with the in-kernel brcm80211 driver.
How can I know if my device naming has changed from the output of this command?
If so, how could I solve my problem based on that knowledge?
Is wlan0 still listed there as a device?
ᶘ ᵒᴥᵒᶅ
Offline
litemotiv wrote:Is wlan0 still listed there as a device?
No.
Ok, you will need to check your dmesg output for any messages concerning brcm80211, be sure to also check if the module isn't blacklisted from loading.
ᶘ ᵒᴥᵒᶅ
Offline
bloom wrote:litemotiv wrote:Is wlan0 still listed there as a device?
No.
Ok, you will need to check your dmesg output for any messages concerning brcm80211, be sure to also check if the module isn't blacklisted from loading.
There are two messages, one regarding brcmutil, the other brcmsmac. Both messages express the fact that the module are in early stage of development.
Offline
There are two messages, one regarding brcmutil, the other brcmsmac. Both messages express the fact that the module are in early stage of development.
Hmm that's odd, do you have any new interfaces listed with ifconfig -a, an eth0 perhaps?
ᶘ ᵒᴥᵒᶅ
Offline
bloom wrote:There are two messages, one regarding brcmutil, the other brcmsmac. Both messages express the fact that the module are in early stage of development.
Hmm that's odd, do you have any new interfaces listed with ifconfig -a, an eth0 perhaps?
No, just a 'lo' and nothing else.
Offline
No, just a 'lo' and nothing else.
In that case i'm at a loss for now, sorry. I had the exact same machine until a few days ago and had no problems upgrading to 3.0, so i can't escape the feeling that we're missing something simple or obvious at this point. I don't recall seeing any other reports here or on other forums about Air 3,2 upgrades gone bad on kernel 3.0...
ᶘ ᵒᴥᵒᶅ
Offline
Offline
Have you looked at at https://bbs.archlinux.org/viewtopic.php?id=111554? Report your issues there, a number of people are experiencing similar problems.
Offline
Have you looked at at https://bbs.archlinux.org/viewtopic.php?id=111554? Report your issues there, a number of people are experiencing similar problems.
Well, thanks for the tip: compat-wireless solved it!
Offline