"Set Encode" (8B2A) error while trying to add WEP key
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
"Set Encode" (8B2A) error while trying to add WEP key
I'm currently trying to get my wireless connection up. I'm currently running gentoo on a Broadcom 4302 wireless card using the BCM43xx drivers. After a week of screwing around, I FINALLY got my card up and active!!! I can scan for networks and even add an ESSID, but when I try to add a wep key, I get this error:
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Operation not supported.
So, I know my card works because when I do iwconfig essid myserver, I get
ok, sorry about the other thread guys, it was another problem that was cause by my overall n00bness. I think gentoo while being a newbie from the windows world is a bad idea, but it has had its challenges benefits. Now I understand way more linux than if I was using my prior installation of Suse and I'll now have a super fast distro for live laptop audio performance.
Here's the bottom part of dmesg
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Queueing Authentication Request to 00:13:10:a1:9a:74
SoftMAC: Cannot associate without being authenticated, requested authentication
SoftMAC: Sent Authentication Request to 00:13:10:a1:9a:74.
SoftMAC: Open Authentication completed with 00:13:10:a1:9a:74
SoftMAC: sent association request!
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
eth1: could not initialize WEP: load module ieee80211_crypt_wep
lsmod ouputs the following relating to interweb stuff:
After loading ieee80211_crypt_wep, you might have to reload bcm43xx. Cycle through modprobe -r bcm43xx and then modprobe bcm43xx and see if that makes a difference. I agree it is odd that ieee80211_crypt_wep didn't get loaded when bcm43xx did. On my rig, loading bcm43xx causes all the ieee80211 modules to load.
You might also check /var/log/messages and /var/log/syslog to see if bcm43xx is complaining about the firmware. At the moment, an incomplete set of firmware is my leading suspect. Any details you can provide on how you created and loaded firmware would be helpful.
Well, I just did make modules in the source folder to make sure I had done it when I recompiled the kernel. I restarted the computer and found that ieee80211_crypt_wep doesn't load up. I had to modprobe it to load it, the did rmmod bcm43xx then modprobe bcm43xx. I could do iwconfig and everything else afterwards, but I still get that STUPID error.
Here's the lsmod output after having done all this.
Here are 3 other threads on this subject but none of them have the same hardware and only the last one was solved,but I don't understand how he did it. I really don't know if this applies to me but maybe it can help you guys figure out what's wrong.
Like these guys, my card reads networks fine, but it's only as soon as we add a wep key that we get the bloody error of denial!
Errors around setting a WEP key are usually a sign of a bad driver, and that is probably the common thread for the links you found. For ndiswrapper it usually means either the Windows driver doesn't work at all under ndiswrapper or it functions only moderately. For bcm43xx it is likely bad firmware. The fact that ieee80211_crypt_wep isn't loading on boot suggests that bcm43xx isn't requiring it, which tends to point to a bad driver/firmware. Which leads me back to asking this question one more time:
How did you install firmware and what file did you get it from? Just in case I'm causing confusion by not being clear, there are two parts to the bcm43xx driver. There is the bcm43xx kernel module and there are the firmware files you need to cut from a Windows driver with fwcutter. The bcm43xx driver needs both of those to function.
I did checked /var/log/messages and /var/log/syslog and apparently, they don't exist on my system.
That sounds like you didn't do a complete Gentoo install. You really need log files in order to troubleshoot stuff like this, so you might want to investigate how to get the logging system installed.
To be clear, I had enabled all the IEEE8211 options in menuconfig for the kernel except for TKIP, I then enabled it, recompiled and installed it. I had cut the firmware before doing any of this. I just recut the firmware and restarted to no avail.
After I was done with menuconfig, I did the following commands:
make && make modules
and then I finished with
cp arch/amd64/boot/bzImage /boot/2.6.19-gentoo-r5
Then I reboot.
Ah, there may be a problem here (and I'm hoping this is it). For a 2.6.x kernel, once you've done the configuration, you only need to run make, make modules is redundant. What is missing however, is make modules_install. Your copy command moves the kernel to /boot, but there is nothing in that sequence that would move the modules to /lib/module/2.6.19-gentoo-r5. If the modules aren't in the proper directory, the kernel can't find them, it can't use them. Since you obviously do have modules, I'm guessing that at some point, you did run make modules_install (or you're still dealing with the same kernel version as you originally installed and those are the modules you're using).
How do I setup the log files?
Sorry, but since I'm not familiar with Gentoo, I'm going to have to punt on this one. I'd ask in a Gentoo forum, you should be able to get a good answer there.
The only difference is I bcm43xx-cutter..ed it before I enable the IEE8201 in the kernel and recompiled.
The link you posted is good, provided you used the wl_apsta.o driver as the target for cutting. You might also want to double check the /lib/firmware directory to make sure that the firmware files were indeed copied into there.
I just did make modules_install, restarted and got the same damn thing. Wep crypt didn't load and I got that stupid error!!
So I recompiled my kernel another time, and noticed that beside the IEE21.. box for WEP there was --- instead of < >, but when I went to the top of the IEEE21 list and chose it to load up with the kernel, that prior option became selectable. So I compiled the kernel with all the IEEE options selected to be compiled with the kernel and not as seperate modules.
I did make and make modules and make modules_install and compied the image over, renamed it to the current kernel and restarted.
STILL GOT THE ERROR!
I'm contemplation going to Ubuntu because this is getting out of hand...
Sorry, but I missed this before, copying over just the bzImage isn't enough. You also need to copy over the System.map file. Also, double check that you're actually booting from /boot/2.6.19-gentoo-r5 and not just /boot.
Beyond that, any advice I would give would only be a complete guess. I suspect something went wrong during the Gentoo install, but without the system logs to look at, we aren't going to find out what. So if the above doesn't work, I'd suggest either spending time getting the system logs to work (that is probably best done at the Gentoo forum) or move to Ubuntu.
Ok, I'll give that a go and post an update. I was just so excited about have a custom made kernel compiled for my system for the best possible audio processing and fastest setup available on my hardware, but it's really been hell to set up. I think I'm going to go to Kunbuntu for a few months and see how it goes. If I get better at linux, I'll go back to Gentoo.