Page 1 of 1

Re: WPA does not prompt

Posted: Tue Apr 21, 2009 3:14 pm
by AK Dave
bzirpoli wrote: But when I select it, it never prompts me asking for the password. Doesn't matter how many times I try, it never prompts.
Does it log you in to the network, or refuse to connect?

Re: WPA does not prompt

Posted: Wed Apr 22, 2009 3:03 pm
by AK Dave
bzirpoli wrote:Refuses to connect
"Refuses to connect" is quite a bit different than "doesn't prompt for password", which is what your original complaint was.

I see you're using ndiswrapper:
* II. querying ndiswrapper...
net5211 : driver installed
device (168C:001C) present (alternate driver: ath_pci)
Have you tried using the ath_pci module instead of ndiswrapper & net5211?

How about you do this command and pipe me the output. Would be awesome if you could cull it down for just the wifi adapter, but the whole mess is fine. That will show me the hardware that your system is reporting, exact firmware revision levels, what drivers/modules are associated with what hardware, and what drivers/modules are available. I suspect that, quite simply, that you're using the wrong driver/module for your exact hardware.

Code: Select all

lspci -vvnn

Re: WPA does not prompt

Posted: Fri Apr 24, 2009 1:18 pm
by AK Dave
bzirpoli wrote:Is it possible that the drivers that were working with Gnome don't work with KDE?
That wouldn't make any sense, unless you change a lot more than just the desktop environment.
3:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
Kernel driver in use: ndiswrapper
Kernel modules: ath_pci
Everything relevant is in here. Here's your device, your exact chipset, its revision number (doesn't matter in this case), the driver you're using, and an alternative you could be using.

This may be simple:

Code: Select all

sudo modprobe -r ndiswrapper && sudo modprobe ath_pci
This may be incredibly simple:
Do you have a hard or soft switch on this computer to enable/disable the wifi radio? One of my favorite (being very sarcastic) quirky bugs to track down was a guy who had disabled his bluetooth radio in Windows, reformatted, installed Linux, and then couldn't turn it on AT ALL because he'd disabled the firmware.

This may be more complicated:
http://forums.linuxmint.com/viewtopic.p ... 2x#p143145