Intermittent Wireless Configuration Problems
Posted: Sat 29 May 2010, 19:06
I am new to Puppy Linux and am having inconsistent results with my wireless card configuration. After booting, the wireless card sometimes connects appropriately but sometimes appears partially configured and requires manual intervention to connect.
I'm using Puppy Linux 5.0 with a Belkin F5D7010 card that uses a rt2500 chipset and am booting from a USB flash drive.
The following script is in my /root/Startup directory. It was mentioned in a forum that this sometimes resolves this type of issue, but it does not appear to in my case.
#!/bin/sh
modprobe rt2500pci
sleep 5s
ifconfig wlan0 up
sleep 10s
iwconfig wlan0 essid HomeNetwork
iwconfig wlan0 key open A9B4E7462D
iwconfig wlan0 mode managed
rm -f /var/lib/dhcpcd/*.info
rm -f /var/run/*.pid
dhcpcd -t 30 -h puppypc -d wlan0
ifconfig
iwconfig
I performed a test of 6 reboots and received the following results. The configuration was identical in all cases with the startup shell script in /root/Startup:
Boot 1 and 5 - Connectivity established correctly with no manual intervention.
ifconfig shows lo and wlan0
iwconfig shows wlan0 correctly configured and connected with ESSID and correct WEP key
Boot 2, 3, 4, and 6 - Connectivity not established
ifconfig only shows lo
ifconfig -a shows eth0, lo, and wlan0 with no traffic
iwconfig shows wlan0 with no traffic, no ESSID, no access point; however, the appropriate WEP key is configured.
In cases where the connectivity did not correctly establish upon boot, I am able to utilize the Puppy Network Wizard to establish connectivity. I am also able to manually enter the commands from the shell script to establish wireless connectivity (so I believe the commands are valid for my configuration).
Any suggestions on what I might do to consistently establish wifi connectivity without manual intervention would be appreciated!
I'm using Puppy Linux 5.0 with a Belkin F5D7010 card that uses a rt2500 chipset and am booting from a USB flash drive.
The following script is in my /root/Startup directory. It was mentioned in a forum that this sometimes resolves this type of issue, but it does not appear to in my case.
#!/bin/sh
modprobe rt2500pci
sleep 5s
ifconfig wlan0 up
sleep 10s
iwconfig wlan0 essid HomeNetwork
iwconfig wlan0 key open A9B4E7462D
iwconfig wlan0 mode managed
rm -f /var/lib/dhcpcd/*.info
rm -f /var/run/*.pid
dhcpcd -t 30 -h puppypc -d wlan0
ifconfig
iwconfig
I performed a test of 6 reboots and received the following results. The configuration was identical in all cases with the startup shell script in /root/Startup:
Boot 1 and 5 - Connectivity established correctly with no manual intervention.
ifconfig shows lo and wlan0
iwconfig shows wlan0 correctly configured and connected with ESSID and correct WEP key
Boot 2, 3, 4, and 6 - Connectivity not established
ifconfig only shows lo
ifconfig -a shows eth0, lo, and wlan0 with no traffic
iwconfig shows wlan0 with no traffic, no ESSID, no access point; however, the appropriate WEP key is configured.
In cases where the connectivity did not correctly establish upon boot, I am able to utilize the Puppy Network Wizard to establish connectivity. I am also able to manually enter the commands from the shell script to establish wireless connectivity (so I believe the commands are valid for my configuration).
Any suggestions on what I might do to consistently establish wifi connectivity without manual intervention would be appreciated!