[CentOS] New wireless controller

Fri Sep 2 16:45:13 UTC 2011
Emmett Culley <emmett at webengineer.com>

On 09/01/2011 10:10 PM, Barry Brimer wrote:
> 
>> I just installed an Asus PCE-n13 wireless card into one of my CentOS 5.6 systems.  It uses the RaLink 2680 chip set and I was able to get the driver loaded using modprobe rt2x00pci.ko.  I saw no error and now see that the module is loaded along with mac80211 and other dependencies.
>>
>> Now I need to know how to create the wlan0 device.  I can find nothing via Google searches on how to create that device.  I assumed the driver would do that upon loading, but now I expect some ioctl to the driver command may be required.
>>
>> I created an ifcfg-wlan0 file, but of course ifup wlan0 always returns device not found.
>>
>> Can somebody tell me where to start on getting the wlan0 device created?
> 
> What is the output of iwconfig?
> 
> What is the output of ifconfig -a
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
> 
> 
[root at sbbusx ~]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

ppp0      no wireless extensions.

[root at sbbusx ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:25:90:33:11:80
          inet addr:192.168.6.99  Bcast:192.168.6.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:544 errors:0 dropped:0 overruns:0 frame:0
          TX packets:618 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:61246 (59.8 KiB)  TX bytes:149248 (145.7 KiB)
          Interrupt:177 Memory:feae0000-feb00000

eth1      Link encap:Ethernet  HWaddr 00:25:90:33:11:81
          inet addr:172.19.255.254  Bcast:172.19.255.255  Mask:255.255.0.0
          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:169 Memory:febe0000-fec00000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1532 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1532 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:297812 (290.8 KiB)  TX bytes:297812 (290.8 KiB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:xxx.yyy.z.qq  P-t-P:xx.y.z.qqq  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:231 errors:0 dropped:0 overruns:0 frame:0
          TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:28657 (27.9 KiB)  TX bytes:21865 (21.3 KiB)

Also, in the syslog I see this when I run modprobe rt2x00pci.ko:

Sep  2 09:25:08 bus kernel: cfg80211: Calling CRDA to update world regulatory domain
Sep  2 09:25:08 bus kernel: cfg80211: World regulatory domain updated:
Sep  2 09:25:08 bus kernel:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Sep  2 09:25:08 bus kernel:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep  2 09:25:08 bus kernel:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep  2 09:25:08 bus kernel:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Sep  2 09:25:08 bus kernel:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Sep  2 09:25:08 bus kernel:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

Now I am thinking that perhaps the driver doesn't see the new hardware.  I'll try it with the adapter removed.

Emmett