SlackwareThis Forum is for the discussion of Slackware 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.
I've been fighting this issue for a while now, and haven't found the solution anywhere. I have a Toshiba laptop with ipw2200 wireless. The machine has been running the huge26 kernel, but I wanted to try some features in the new 18.104.22.168 kernel, so I re-compiled, using the huge26 config parameters. When I boot, it will pause as it brings up my wireless for probably 30 seconds, then says "Error for wireless request "Set Encode" (8B2A)... Set failed on device eth0 ; operation not supported." After this pause and error, it will continue to boot, and the wireless actually works fine. The funny thing is that the first boot after my recompile didn't do this the last time (from huge26 stock config), but it does every other boot now. Some of my previous compiles would show the same symptoms during boot, but the wireless would not work. The only thing I know that I did different this time was that I removed the 22.214.171.124 modules folder completely before compiling.
I am currently using the kernel drivers for the wireless, and do have the firmware files in /lib/firmware. I've also tried using the newer drivers and removing kernel support, with the same results. Any ideas? Thanks! ...Steve
I have looked through my logs, but can't tell what's driving the error. Would it help if I posted my dmesg or another log? The funny thing is that if I "./rc.inet1 restart" after booting, it will restart my wireless without any errors. If I set rc.wireless.conf to connect to any network with no key, it will boot fine, so it must be related to WEP? I have tried manually loading ieee80211_crypt_wep in my rc.modules, but it doesn't help. I have not looked in my router, that's good advice. Any other ideas? Thanks! ...Steve
I finally figured this one out! In my rc.wireless.conf file, I was defining the channel for my wireless network. This apparently causes the error with my hardware/driver, because I can turn the problem on and off by adding and removing this field. Hopefully this will help someone else out in the future. Thanks again! ...Steve
Location: The Glorious People's Republic of Austin
Strange, I've been having the exact same problem you mention on startup, but I can't find any settings trying to set a channel at all. Of course, I'm also using the madwifi-ng driver, and the problem does seem to occur whenever I try to change the channel from b to g. I'm at a loss.