Can't start wireless from rc.inet1 on Slackware 12.0
Hi,
I am running Slackware 12.0 (NOT upgraded to -current). Last night I upgraded my kernel to 2.6.25, and finally the b43 driver supports my wireless chip BCM4312 rev 02. I am now able to connect to the internet with wireless, but I have to do it manually; I can't make the rc.inet1 script work. First of all, the setup: I installed firmware version4.150.10.5 using b43-fwcutter-011. This is the version recommended for "bleeding edge" b43 drivers at http://linuxwireless.org, and it should correspond to the 2.6.25 driver (their web page has not been updated for 2.6.25 yet). I'm using rc.inet1.conf to store my wireless settings, and wpa_supplicant.conf to store the WPA key. I read Alien's wiki, and I also followed the discussion in this thread: http://www.linuxquestions.org/questi...ectory-611577/ This is what iconfig gives: Code:
lo no wireless extensions. Code:
IFNAME[4]="wlan0" And here's the wpa_supplicant.conf (the relevant part only) Code:
network={ Code:
root@kutu:~# /etc/rc.d/rc.inet1 wlan0_start Code:
$IWCOMMAND nick $NICKNAME The dmesg output of the action above is as follows: Code:
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) However, if I first do Code:
root@kutu:~# wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant.conf Code:
root@kutu:~# dhcpcd -d wlan0 Code:
|
I've never put these lines:
Code:
WLAN_WPACONF[4]="/etc/wpa_supplicant.conf" Here's a working config just for giggles: Code:
# Config information for ath0: However, if you need it, so be it. Some potential errors I see: Code:
WPAOPTS[4]="-Dwext -iwlan0 -c/etc/wpa_supplicant.conf" And check out a working /etc/wpa_supplicant.conf: Code:
# See /usr/doc/wpa_supplicant-0.5.8/wpa_supplicant.conf.sample |
I would definitely stick all ssid configuration in /etc/wpa_supplicant.conf. That's where wpa_cli and wpa_gui are going to save them anyway. Here's a working DHCP version rc.inet1.conf section for wpa_supplicant:
Code:
IFNAME[4]="wlan0" And a working /etc/wpa_supplicant.conf (I set up a "wireless" user group so I wouldn't have to be root to use wpa_gui): Code:
ctrl_interface=/var/run/wpa_supplicant |
Hi Bruce,
Thanks for your post. I corrected the missing space in the line Code:
WPAOPTS[4]="-Dwext -iwlan0 -c/etc/wpa_supplicant.conf" |
Quote:
Code:
[[ -r /etc/rc.d/rc.wireless.conf ]] && . /etc/rc.d/rc.wireless.conf |
Thank you for your reply DonnieP (I was typing my second post while you sent your first, I've just noticed your post).
I tried commenting out the line you gave, but the result is the same. Suspecting subtle typos I may have created in the scripts, I downloaded fresh versions of these scripts (inet1* and wireless*), adjusted the parameters and tried again, but it still doesn't work... (And yes, by "manually" I mean running wpa_supplicant in the command line). |
Well I second this situation here too. I've done the mentioned changes also and they don't work for me either.
|
One little update: I never could bring the wireless up using rc.inet1 with parameters wlan0_start or wlan0_restart. Today, once I did "restart" (i.e. restart for all interfaces) and to my surprise I both eth0 and wlan0 successfully received an IP. This happened only once. Since then I'm trying to reproduce this result but I can't.
|
I was having the same problem that you described in post #8. Have you tried putting a start-up script in /etc/rc.d/rc.local, along with an entry for dhcpd?
I put /etc/rc.d/rc.inet1 wlan0_restart and the internet is available every time now at boot - well, at least 4 times in a row since I did that earlier! maybe worth a go? |
Quote:
/etc/rc.d/rc.inet1 restart was able to bring the wireless up, and I can't reproduce this. It sounds as if the hardware/driver has unstable behaviour but running wpa_supplicant from the command line always works, so I think that's not the problem. |
Worth a go - shame it was nothing so easy - sorted out a similar problem I was having. hey ho.
You could read through this http://www.linuxquestions.org/linux/...r_Slackware_11 OK it's for Slackware 11 but might have something you could use there. Hope you get it sorted. |
Hi Bazzaah,
Thanks for the link, I read it. It explains how to use rc.local to automate the process, but that's not my problem, I'm sure I can do the necessary scriptwork for that if needed. I'm trying to find out what prevents rc.inet1 from working properly. Maybe there is a bug, if not, I'd like to learn where my mistake is. |
I've never managed to satisfactorily get wireless working using rc.wireless, probably more a limitation of me than rc.wireless. Anyway I just chmod -x rc.wireless and use other tools such as wlassistant for my wireless.
|
I'm a bit surprised that I'm not alone in this; there are others who also can't succeed with rc.inet1 (or rc.wireless). Maybe there is a bug somewhere. Is there anyone who had this problem in 12.0 and then got it fixed in -current?
|
If it works for you with manual start, it must work with the Slackware scripts as well.
The first step in troubleshooting would be to change this line in rc.inet1.conf: Code:
DEBUG_ETH_UP="no" Code:
DEBUG_ETH_UP="yes" Code:
tail -500 /var/log/messages | grep logger It may be likely that you need to give wpa_supplicant more time to associate. There is an option for that: Code:
WLAN_WPAWAIT[4]=30 You should not use WPAOPTS[4]=... in your *.conf files. Eric |
All times are GMT -5. The time now is 09:16 AM. |