wpa w -Dralink in slackware 13 running @ 1mb/s on fresh install.
 

#EDIT# OK just cause i had the time i reinstalled slackware from the complete set for the current slackware 13.0 release. during the install of "everything" it only went throught the first 3 cd's. I installed wicd from the wicd site, not the extras folder on the cd. I am still getting only bit rate 1 mb/s listed in iwconfig..
can someone please give me a listing of the .conf files that are pulled from to set up wireless device in the order that its done when running wpa_supplicant?

help!!!!!

some things i have tried thus far
 

ok so i tried another wireless stick WUA 2340 using ndiswrapper and wicd. I actually plugged both the net topia ( ralink ) and wua 2340 (ndiswrapper) in at the same time.

Wua 2340:sees networks but can get no ip

1. has bit rate listing of 108 M in iwconfig ( speed doubling from the win driver being wrapped i guess)
2. sees networks but can not get ip
3. actually tries to connect but is getting really really hot when using wext via the wicd wpa_supplicant driver selection.
4. will get dropped by system randomly during the process of trying to obtain an ip or scan

Nettopia(rt2500)

1. can connect each and everytime but at very low 1 mb/s rate
2. is also getting very hot as compared to the way it used to work
3. known to work correctly in linux 12.2 at 54 mb/s on a base install

I have also even reinstalled slackware 13.0 2 times due to other reasons. which may or may not be related: segmentation faults during times when wicd is trying to SCAN for networks. sytem locks when trying to change config files via the wic gui ( wpa_supplicant driver selection, ect..).

I really could use some input on this issue as i have really put a lot of time into trying to get this thing to work either by googling, reading, scanning my rc.* files for inconsistant entries and posting my findings. I have noticed that this thread is getting alot of views it seems for being 2 days old but no post...so is my problem common?

Can I ask why? For the time being, it might be a good idea to stick with the one in extra, just to rule out some weird issue.
As far as I know, the only conf file you need to worry about is wpa_supplicant.conf, and you don't even have to worry about that if you're using wicd.

I would stick with one card for now. I take it you're using a USB based wireless card? Which one is it and what driver are you using?

Was this with your self-compiled wicd? If so, it is an even stronger reason to go with the wicd in extra.

One final thing, is your user in the netdev group?

I have tried with the extra and a self compile. Will try once more and remove self compile and install from txz once more.

I am just trying to rule out the chance of it being an issuse with wicd or python since wicd seems to have some isssues with AP name (ssid) resolution. I have no idea if the problems I am having could be related but just wanted to rule it out.


I am at this moment using The netopia card ( based on the rt2500 as far as i know) which happens to be the card that is giving rise to the slow bit rate. even if i assign a fixed rate temporarily via iwconfig iwlan0 rate 54M <<<fixed it will only get 1 mb/s or an average of about 34k/s as compared to 192 k/s in slack12.2
the second card is a D-Link Wua-2340 which is an athero chipset. Also, i didnt think it would mater as i can assign iface to wicd for example via the pref tab either in *curses or *gui which seems to handle switching between the two ok. However, will try your advice and see if a still get the locks and seg faults.

At the moment yes; however, the issue has occured using the base slackpkg from extra. will uninstall via python setup.py uninstall and run again using /extra and report back. b4 i do though.

Yes.

thanks for showing intrest

That is really weird. By any chance do you remember what driver it was using in 12.2? The drivers for Ralink chips are in the kernel so it should be using the same thing.

well it was using the ralink-legacy driver i think. odder yet is that in wicd prefs when i try to use the ralink driver it will not obtain an ip. however, when running under wext generic it does. the dlink stick behaves the same way with the exception of never getting an ip but trying to and also seeing the networks.

I think this is more a function of wpa_supplicant than wicd. I think that the wpa_supplicant development team focuses most of their time on the wext driver, hence it almost always works better than anything else. Just set it to wext and don't worry about it.
So is it using this driver now? To be honest, I think your problems with wicd are a symptom, not a root cause, and you should sort out if you are running the right driver for your card first.

i reverted back 12.2 due to other issues regarding random seg faults when using wicd or anything graphics based. 13.0 won the battle but not the war. I'll set up a dual boot later and play with it some more. 12.2 working with only one issue: ndiswrapper and wua2340 installed and 2340 is seen as a device but not a interface in iwconfig. er, it shows up in lsusb. thanks again for all your help. later when i get 13 back up i will post some more stuff regarding my issues. my computer is out to get me....it does EXACTLY what i tell it to. lol