View previous topic :: View next topic |
Author |
Message |
mpharter n00b
Joined: 01 Aug 2008 Posts: 36
|
Posted: Wed Apr 08, 2009 2:52 am Post subject: BCM4312 issues |
|
|
Ok, I know this has been posted before but ive tried everything I have found to try to get my wireless card working. I decided to use the broadcom proprietary drivers. Because I have used those drivers on other distros and it worked. Thus I went to the gentoo wiki and followed the instructions there. It failed so I went on to the broadcom-sta package in portage to see if that would work. After setting the necessary options in the kernal I emerged it which was successful. However modprobe wl results in:
Code: | FATAL: Error inserting wl (/lib/modules/2.6.27-gentoo-r7/net/wireless/wl.ko): Unknown symbol in module, or unknown parameter (see dmesg) |
the relevant dmesg output is
Code: | wl: Unknown symbol ieee80211_get_crypto_ops |
If someone could help me get this card working on i would be extremely greatful.
Thanks. |
|
Back to top |
|
|
assaf Apprentice
Joined: 14 Feb 2005 Posts: 152 Location: http://localhost
|
Posted: Wed Apr 08, 2009 1:54 pm Post subject: |
|
|
I've had the same problem with broadcom-sta. The thing is that it uses the old kernel wifi stack, and I had already disabled it.
So to fix the symbol error, you need to reenable the "old" stack: "Generic IEEE 802.11 Networking Stack (DEPRECATED)" or CONFIG_IEEE80211 and also the encryption modules under it (WEP, TKIP, CCMP).
Then rebuild your kernel and try again. |
|
Back to top |
|
|
mpharter n00b
Joined: 01 Aug 2008 Posts: 36
|
Posted: Wed Apr 08, 2009 5:59 pm Post subject: |
|
|
Thanks for your help. I tried your suggestion and enabled the things you said. I also tried making things modules. Both times I was still get the dmesg error thing. Is there a step I missed? I have also tried recompiling broadcom-sta and it still gives the same error. |
|
Back to top |
|
|
assaf Apprentice
Joined: 14 Feb 2005 Posts: 152 Location: http://localhost
|
Posted: Wed Apr 08, 2009 10:51 pm Post subject: |
|
|
hmmm... maybe not the same problem.
Silly question: did you reboot into the new kernel? |
|
Back to top |
|
|
mpharter n00b
Joined: 01 Aug 2008 Posts: 36
|
Posted: Wed Apr 08, 2009 11:24 pm Post subject: |
|
|
Yeah, unfourtunately its not that easily fixed. Either that or I made a different simple error. |
|
Back to top |
|
|
|