wicd network manager can'f find my wifi network
 

Here is the problem, my wicd network manager which works under my debian box can't find my wifi network SSID, which could find via command "iwlist wlan0 scanning". Have anyone met situation this before?

What situation?

We don't know your hardware, we don't know which distro isn't
playing, how can we know the situation?

I'm having a somewhat similar problem. Installed Slackware 13.37...got wicd installed, but wicd is showing no networks available. Someone suggested uninstalling wpa-gui, but I'm not sure how or even if that would fix the problem. Suggestions?

Also, unrelated to current problem, having problem with keyboard repeating keys too fast. ???

Thanks!

Most of the time when I have problems with wicd not finding wireless networks I simply forgot to enter the descriptor of the wireless device (like wlan0, ...) in wicd's configuration.

Nope, I did that. It's not even showing my neighbors' wifis. Nothing. Like it's not even scanning for anything.

Start wicd from the command-line and look if it throws error messages when scanning for networks.

It's been a while since I ran a real linux distro...you'll have to refresh my memory on how to "run"...typed "wicd" in terminal...got nothing...no errors, no messages at all.

I cant imagine what an "unreal" Linux would be, but anyways, try it with

"unreal" linux = Mint = worst Linux distro ever.


Still no wireless networks found. What did I do wrong?

I can't see any errors, so it is impossible for me to tell what is not working.

k. I appreciate the help so far, though. I'll keep working with it and maybe I'll find something. Thanks!

^ You did start the module (driver)?

Apparently, yes. It tries to scan, at least it tells me it's scanning, but it won't pick up ANY of the wifi signals in the neighborhood. (and there are a list of them) How does one start the module?

If you have rebooted since you installed wcid then the module is loaded.
Off of the top of my head I've forgotten the command to do it without restarting the computer. Let's see... My old first edition of "Running Linux" says it is,

insmod module

"where module is the name of the module object file. For example:

insmod /boot/ftape.o

will install the ftape driver, if it is found in that file."

I don't remember if that is still the current, correct command or not....

Nowadays it is recommended to use modprobe instead, it will also load possible module-dependencies and will use the options given in the files in /etc/modprobe.d.