View previous topic :: View next topic |
Author |
Message |
01 n00b
Joined: 03 Aug 2009 Posts: 7
|
Posted: Mon Aug 03, 2009 11:08 pm Post subject: LIB80211_CRYPT_TKIP unavailable in kernel > 2.6.30 |
|
|
Hi,
Probably a stupid question but I can't get my Wifi Driver working (doesn't connect to encrypted networks) due to, I think, a missing option in Kernel config.
The Wifi driver I use is the proprietary broadcom-sta package, which builds fine.
ifconfig shows me the interface, but it can't get the IP from the access point. (I get it working with kernel 2.6.2.
It seems broadcom needs Networking Support > Wireless > Common routines for IEEE802.11 drivers.
I enable it as a module, but I don't see options related to TKIP/CCMP and various encryption methods.
I can search for that option, it says :
Code: |
Symbol: LIB80211_CRYPT_TKIP [=n]
Selected by: LIBIPW && NETDEVICES && !S390 && PCI && WLAN_80211 || HOSTAP && NETDEVICES && !S390 && WLAN_80211
|
LIBIPW gives me :
Code: |
Symbol: LIBIPW [=n] │
│ Selects: WIRELESS_EXT && CRYPTO && CRYPTO_ARC4 && CRYPTO_ECB && CRYPTO_AES && CRYPTO_MICHAEL_MIC && CRYPTO_ECB && CRC32 && LIB80211 && LIB80211_CRY │
│ Selected by: IPW2100 && NETDEVICES && !S390 && PCI && WLAN_80211 || IPW2200 && NETDEVICES && !S390 && PCI && WLAN_80211 |
So I could enable drivers for IPW2100 and it'd say M or Y, but still, these encryption methods don't seem to appear in the menu.
So, how to make it show up ? |
|
Back to top |
|
|
erik258 Advocate
Joined: 12 Apr 2005 Posts: 2650 Location: Twin Cities, Minnesota, USA
|
Posted: Mon Aug 03, 2009 11:53 pm Post subject: |
|
|
HI,
it appears that those options were removed; whether they were depreciated, automatically selected, or what I can't discover although I looked around online a little. Anyway they're certainly not in my kernel either (2.6.30) - oh, and I'm using wpa just fine.
two things - first, there's an open source wireless driver for your card that apparently works well, called b43. if the kernel changed in a way that is incompatible with those closed-source broadcom drivers, it's a good bet that broadcom isn't being kept up at night worrying about making their driver compatible with the newest kernel versions. you might want to try this open source driver instead as it's more likely to stay compatible and current than broadcom's offerings are.
second, my wpa didn't work until I turned on CONFIG_CR YPTO_MICHAEL_MIC in 'Cryptographic API'. Perhaps it could help you too, and a lot less work than migrating away from those icky proprietary drivers ; ) _________________ Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
Back to top |
|
|
Gusar Advocate
Joined: 09 Apr 2005 Posts: 2665 Location: Slovenia
|
Posted: Tue Aug 04, 2009 10:27 am Post subject: |
|
|
I have an ipw2195, which uses the ipw2200 driver. The option you need is automatically selected in my kernel config. In "make xconfig" I can only see it if I select "Show All Options" in the Options menu. http://img91.imageshack.us/img91/7356/kernelwirelessconfig.png
Not sure how much this helps. But it does show that the option exists. |
|
Back to top |
|
|
01 n00b
Joined: 03 Aug 2009 Posts: 7
|
Posted: Tue Aug 04, 2009 11:10 am Post subject: |
|
|
Thanks a lot for your answers,
I wish I could have used the opensource driver, unfortunately my specific chipset isn't supported, either by b43 or b43legacy.
Code: | # lspci -nnv | grep 14e4
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
|
There are indeed patches to make the driver suit the new kernels, but they are already available and normally working.
I was using "make menuconfig", but indeed with "make xconfig" I see these options.
I'll enable IPW2100, I've seen it checks the correct options, it also selects CONFIG_CRYPTO_MICHAEL_MIC (I tried to compile it as a module but it didn't help, maybe it wasn't enough).
I think the main point is that TKIP and CCMP thing, "dmesg | grep ieee80211" was only able to give me :
Code: | [ 46.504110] ieee80211_crypt: registered algorithm 'NULL' |
so it lacks TKIP ...
I'm building the kernel right now (with ipw2100), and we'll see if that helps
Edit: Woohoo ! it works, damn, I've played with various kernel versions and drivers not building, and I had the solution under the eyes but still ... so, to sum up: ticking "ipw2100" selects these encryption methods, I thought not ... now I can enjoy my 2.6.31-rc4, thanks
Code: | $ dmesg | grep lib80211
[ 4.533097] lib80211: common routines for IEEE802.11 drivers
[ 4.535138] lib80211_crypt: registered algorithm 'NULL'
[ 4.535141] lib80211_crypt: registered algorithm 'WEP'
[ 4.535143] lib80211_crypt: registered algorithm 'CCMP'
[ 4.535145] lib80211_crypt: registered algorithm 'TKIP'
|
|
|
Back to top |
|
|
erik258 Advocate
Joined: 12 Apr 2005 Posts: 2650 Location: Twin Cities, Minnesota, USA
|
Posted: Tue Aug 04, 2009 10:57 pm Post subject: |
|
|
oooh, 2.6.31! The future... fancy.
Good work, and enjoy the latest and greatest release cantidate. I'm sorry to hear you can't use b43, but glad that broadcom has been kind about compatibility. _________________ Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
Back to top |
|
|
cach0rr0 Bodhisattva
Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Wed Aug 05, 2009 3:34 am Post subject: |
|
|
Code: |
PCI ID Works? Vendor Device Driver Kernel
14e44315 Yes Broadcom Corporation BCM4312 802.11b/g ssb v2.6.30-
|
am I missing something?
Just dumped his 14e4:4315 into here - http://kmuto.jp/debian/hcl/
EDIT: ah, right, need to ~arch to get it. nevermind |
|
Back to top |
|
|
njsg Tux's lil' helper
Joined: 17 Dec 2005 Posts: 88
|
Posted: Fri Mar 26, 2010 9:31 pm Post subject: Re: LIB80211_CRYPT_TKIP unavailable in kernel > 2.6.30 |
|
|
Sorry for waking up a months-old thread, but it seems this issue is still alive, and I'm having trouble with the configuration hack:
I can enable HOSTAP, NETDEVICES and WLAN_80211. And probably LIBIPW too, but S390, which has no documentation and is not acessible, is set (the search lists S390 [=S390]).
I suppose this is why LIB80211_CRYPT_TKIP is never enabled. Does anyone know what is S390? Based on some web searches, it is an architecture. As I'm using AMD64, I doubt it should be set, but it is.
[quote="01"]
[code]
Symbol: LIB80211_CRYPT_TKIP [=n]
Selected by: LIBIPW && NETDEVICES && !S390 && PCI && WLAN_80211 || HOSTAP && NETDEVICES && !S390 && WLAN_80211
[/code]
[/quote]
TIA |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|