I am using the Gnome version of PCLinuxOS (kernel: 2.6.32.11-pclos2)
My wireless interface is apparently properly detected (RT2561 / RT61) and the module is loading, but wireless networks are not being scanned or identified. The wireless network I'm trying to connect to is type WPA2-Mixed.
I believe I had this problem with the KDE version of 2009.2, and it was a simple fix, but I can't remember what that was.
Here is some diagnostic output:
[root@hostname ~]# lspci
02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:09.0 Network controller: RaLink RT2561/RT61 rev B 802.11g
[root@hostname ~]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg Mode:Managed Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
[root@hostname ~]# wpa_cli list_networks
Failed to connect to wpa_supplicant - wpa_ctrl_open: Success
Here are some of the files:
modprobe.conf
install ide-controller /sbin/modprobe ide_generic; /bin/true
install usb-interface /sbin/modprobe ehci_hcd; /sbin/modprobe ohci_hcd; /bin/true
alias wlan0 rt61pci
alias eth0 8139too
alias sound-slot-0 snd_atiixp
options snd-ac97-codec power_save=1
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
modprobe.d/blacklist
blacklist ssb
blacklist ssb
There was no /etc/sysconfig/network-script/ifcfg-wlan0 , so I created one and attempted to restart networking:
[root@hostname ~]# /etc/init.d/network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Configuring wireless regulatory domain [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface wlan0: RTNETLINK answers: Unknown error 132
