(Solved) Wireless not connecting

[OrdiDoc]

Yesterday i disconnected my laptop to use it somewhere else. The internet connection that i was using at the other location was wireless and with Windows so i didn't use Pclinux at the other location.

Before i left, my wireless was working perfectly. After i came back, the wireless is not working anymore. Since yesterday i'm reconfiguring the wireless but it's still not working.

I did a reset on the DSL modem, configured the modem back (in Windows), verified if the wired and wireless connection is working and everything is fine. Back to Pclinux, i cannot configure the wireless anymore.

I have the right SSID, the DSL modem security is on WPA.

Operating Mode : Managed (tried also Ad Hoc, Auto)

SSID : OK

Encryption Mode (tried all of them) : Restricted Wep
                                                    WPA WPA2 Enterprise
                                                    WPA WPA2 Pre Shared Key

Pasword : ************* (13 letters and numbers)

What i'm i doing wrong ?

[Joble]

Did you completely log out of windows and power down?  If windows is suspended this can happen.

[OrdiDoc]

Yes i did Jobie

[OrdiDoc]

Maybe a little bit more info will help:

Kernel: 2.6.33.4-pclos1.pae

Hardware: Vendor: ‎Atheros Communications Inc.

Description: ‎AR5001 Wireless Network Adapter

Media class: ‎Ethernet controller

[ordidoc@localhost ~]$ cat /etc/modprobe.conf
install scsi_hostadapter /sbin/modprobe ahci; /sbin/modprobe ata_piix; /sbin/modprobe pata_amd; /bin/true
install ide-controller /sbin/modprobe ide_generic; /bin/true
install usb-interface /sbin/modprobe ehci_hcd; /sbin/modprobe ohci_hcd; /bin/true
options snd-ac97-codec power_save=1
alias wlan0 ath5k
alias pci:XXXXXXXXXXXXXXXXXXXX etc....
[ordidoc@localhost ~]$

[ordidoc@localhost ~]$ cat /etc/modprobe.preload
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules
fuse
raw1394
sbp2
ohci1394

nvram
evdev
evdev
[ordidoc@localhost ~]$

I'm going to reset using service -f network and see if i can configure it back.

[djohnston]

I only have one PC with wireless. Although it has the Atheros chipset like yours, this PC is still running PCLOS2009. For your reference, I've attached the modprobe.conf file.

When I have problems with the wireless PCI card on that machine, I often uninstall the driver completely in PCC (PCLOS Control Center). I then reboot, re-install the same wireless driver in PCC, and all is well. The Atheros drivers have come a long way, but may still have issues.

[ElCuervo]

What do you get with iwconfig in a terminal?

[OrdiDoc]

In terminal

[ordidoc@localhost ~]$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated   
          Tx-Power=off   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
         
[ordidoc@localhost ~]$

and kjohnston i went to hardware and removed the Atheros wireless card, rebooted, the card was back, tried again and still not working.

[OrdiDoc]

Working now, i went back to Control Center, removed the wireless connection and rebooted. After i rebooted i configured it back and it's now working.

I also used the Live CD to see if my configuration was working and it was on the Live CD on another hard drive, i wanted to see what was the right configuration.

Thanks all for your time 

[djohnston]

Alright. Nice, OrdiDoc! Think of the PCC as the equivalent of Windows Control Panel. Now that you have it working, you will probably want to run the iwconfig command again, and compare the results with the ones you posted before the fix. And look at the /etc/modprobe files again. Probably a good time to do backups, too.

[OrdiDoc]

iwconfig:

[ordidoc@localhost ~]$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"XXXXXXXX" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: XX:XX:XX:XX:XX:XX   
          Bit Rate=54 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-26 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

There's a difference obviously between this one ant the one posted before. Now about backups i don't know anything about how to do it in pclinuxos....

[ElCuervo]

Glad you got it working. PCC is by far one of the easiest ways to configure everything in your computer, but I'm glad to see folks using Konsole, too, since the downside of PCC is that much of what it does is less visible that using a cli.

You may also want to look at ifconfig while it's up, too. It shows your wireless connection's IP address, which usually should be something like 192.168.x.x. Here's an example of both commands:

Code: [Select]

[alan@redhoney ~]$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11g  ESSID:"Guadalupe"  Nickname:"redhoney.kmpkts.net"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 90:E6:BA:8C:45:81   
          Bit Rate=54 Mb/s   Tx-Power:32 dBm   
          RTS thr:2347 B   Fragment thr:2346 B   
          Power Management:off
          Link Quality:73/100  Signal level:-49 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[alan@redhoney ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0F:B0:B9:1A:C2 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:22 Base address:0x400

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:58 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2940 (2.8 KiB)  TX bytes:2940 (2.8 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:27:3D:38 
          inet addr:192.168.1.9  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:a5ff:fe27:3d38/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:34518 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24297 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:44783673 (42.7 MiB)  TX bytes:3255454 (3.1 MiB)
          Interrupt:21 Memory:b0204000-b0206000

Another shortcut that also sometimes yields useful information is ifup wlan0. If all your settings are correct, it will establish a connection to the router without a reboot.

[OrdiDoc]

Nice informations ElCuervo, thanks for the input, i will be using it