OK, if this is a USB stick with the rtl8187B chipset, reboot with only that one plugged in. After rebooting with the adapter plugged in, run
Quote:
and make sure you see rtl8187 driver is loaded. You should see something like this: Quote:
The kernel should detect it automatically when you boot with it plugged in and load the modules. Are there any lights on the stick? If so, do they come on or flicker while booting? If you see any light activity at all, open a terminal and type, as root: Quote:
Bob |
Code:
rtl8187 48768 0 Code:
lsmod | grep rtl In my wicd settings, WPA supplicant driver is set to wext, and wireless interface is set to wlan0. In the advanced settings, I'm not sure what to put for "Use Static DNS" if that matters. |
Using WPA supplicant with wicd, wext is the correct choice. There
are two things I would suggest you check: First, using wicd, you must have an unedited /etc/rc.d/rc.inet1.conf file, or it won't work. Another thing that hung me on wicd -- in Advanced Settings for the wireless when it asks for "WPA 1/2 (Passphrase)" I was putting in the hexadecimal value for the PSK I generated. However, that is not what it's asking for -- it wants the Passphrase used to generate the PSK. If you used this command "wpa_passphrase YOURSSID passphrase" to generate that key, then the passphrase you used is what wicd requires. In the Advanced Settings static DNS is the DNS servers for your ISP. You can get them from your router -- easiest way I know. |
Well it says I've made a connection, but the signal is very weak (about 14%), and I can't actually visit any sites yet (page load error in Firefox, trying to access Google).
|
So post all your wireless settings at present, and the output of:
Code:
iwconfig wlan0 Did you put the DNS servers from your router into wicd? |
iwconfig wlan0:
Code:
wlan0 IEEE 802.11bg ESSID:"" Code:
wlan0 Link encap:Ethernet HWaddr Code:
IPADDR[0]=(hidden) Code:
afterscript = None wicd general settings: Use global DNS servers is NOT checked. Wireless interface: wlan0 Wired interface: eth0 Advanced settings: Use global DNS servers NOT checked DNS1: 4.2.2.1 DNS2: blank DNS3: blank Encryption: WEP (Passphrase) |
You can't use custom settings in /etc/rc.d/rc.inet1.conf with wicd.
Either choose to use one or the other. If you never travel with this box, there's really no need to use wicd; but again, it's your choice. Also, you need to get YOUR DNS servers from YOUR router. Look under Status -- that's where they're found in LinkSys routers. I see wicd says you're using WEP, but you once said you use WPA. However, iwconfig states Code:
"Encryption key:off" just try without encryption first to see if you connect and can use it. I don't remember how to setup WEP, as it's basically useless -- especially where I live. If you can't do that, someone can help. I think that is also covered in Alien Bob's wiki on Slackware wireless. Here's a sample /etc/rc.d/rc.inet1.conf that should work for you: Code:
# Config information for eth0: how to setup WEP. |
I find with my card (BCM4306) that I have bad support with the b43legacy drivers. Certain functions are missing, more importantly I can't force a change of the essid while it is up. I have to wait 5 minutes for it to decide to kick in. I eventually gave up and went with the ndiswrapper to load windows 2000 drivers for my card which fixed all the non functional operations. However my card still has problems initializing with just the ndiswrapper. I put the following in my rc.local and blacklisted the modules to prevent auto loading of it.
/sbin/modprobe b43legacy /sbin/ifconfig wlan0 up /sbin/modprobe -r b43legacy /sbin/modprobe ndiswrapper On slackware 12.2, I also did not attempt to configure the wireless settings with the startup scripts rc.inet1.conf and rc.wireless.conf. If installed Wicd should handle all of this for you... unless you need internet support in console without loading x. I would search the wireless forum and the internet for ndiswrapper information. The extra tools you need to 'cut' the driver from binary packages are available at SlackBuilds.org My solution for the drivers probably isn't the best but it works for me. You may also want to see the slackware notes on wicd located at /usr/doc/wicd-<version>/README.SLACKWARE. It basically confirms that you don't want to configure the wlan0 interface at all using the startup scripts. Also... any problems you may be noticing may be the drivers them self. Like I said, I had problems with changing my essid after I had already booted and loaded the modules. Even unloading and reloading the module would not let me reinitialize the essid. It would literally take 5 to 10 minutes... I had no clue what "I was doing wrong" when in reality I was doing everything right. |
I got it working!!! Thanks so much everyone! :)
I ended up not using wicd, and just editing the rc.inet1.conf, based on Bruce Hill's suggestions. |
All times are GMT -5. The time now is 12:19 AM. |