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?
Emmett
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
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@centos.org http://lists.centos.org/mailman/listinfo/centos
[root@sbbusx ~]# iwconfig lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
ppp0 no wireless extensions.
[root@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
On 02/09/11 04:54, Emmett Culley 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?
Emmett
Hi Emmett,
Are you sure that's the right driver?
My guess is you might want the Ralink rt2860sta driver if it's a 2680 chipset. See here:
http://elrepo.org/tiki/kmod-rt2860sta
Anyway, to know for sure, please post the output from the following command (all one line):
for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
Also, those Ralink wireless network drivers tend to be built with support for NetworkManager so you should generally enable the NetworkManager service (and disable network and wpa_supplicant services) and let NetworkManager control the device.
At Fri, 02 Sep 2011 17:46:24 +0100 CentOS mailing list centos@centos.org wrote:
On 02/09/11 04:54, Emmett Culley 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?
Emmett
Hi Emmett,
Are you sure that's the right driver?
My guess is you might want the Ralink rt2860sta driver if it's a 2680 chipset. See here:
http://elrepo.org/tiki/kmod-rt2860sta
Anyway, to know for sure, please post the output from the following command (all one line):
for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
Also, those Ralink wireless network drivers tend to be built with support for NetworkManager so you should generally enable the NetworkManager service (and disable network and wpa_supplicant services) and let NetworkManager control the device.
Another thing to check: *Most* wireless cards also need firmware, which is not always included with the drivers, due to various copyright / IP issues. Without the firmware, the driver won't fully initialize and not create the device.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 09/02/2011 09:46 AM, Ned Slider wrote:
On 02/09/11 04:54, Emmett Culley 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?
Emmett
Hi Emmett,
Are you sure that's the right driver?
My guess is you might want the Ralink rt2860sta driver if it's a 2680 chipset. See here:
http://elrepo.org/tiki/kmod-rt2860sta
Anyway, to know for sure, please post the output from the following command (all one line):
for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done
Also, those Ralink wireless network drivers tend to be built with support for NetworkManager so you should generally enable the NetworkManager service (and disable network and wpa_supplicant services) and let NetworkManager control the device.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yup, looks like I am trying to load the wrong driver. I assumed that if the driver loaded it found the hardware.
[root@bus ~]# for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done 01:00.0 "Network controller" "RaLink" "RT2860" "ASUSTeK Computer Inc." "Device 130f" 01:00.0 0280: 1814:0781 02:00.0 "Ethernet controller" "Intel Corporation" "82574L Gigabit Network Connection" "Super Micro Computer Inc" "Device 10d3" 02:00.0 0200: 8086:10d3 03:00.0 "Ethernet controller" "Intel Corporation" "82574L Gigabit Network Connection" "Super Micro Computer Inc" "Device 10d3" 03:00.0 0200: 8086:10d3
I'll get the correct driver.
Also, this is a specialized server, so network manager is not an option. Plus, the wireless card will be configured as an access point and I don't believe NM will allow me ot configure it that way.
Emmett
On 02/09/11 18:33, Emmett Culley wrote:
Yup, looks like I am trying to load the wrong driver. I assumed that if the driver loaded it found the hardware.
[root@bus ~]# for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done 01:00.0 "Network controller" "RaLink" "RT2860" "ASUSTeK Computer Inc." "Device 130f" 01:00.0 0280: 1814:0781 02:00.0 "Ethernet controller" "Intel Corporation" "82574L Gigabit Network Connection" "Super Micro Computer Inc" "Device 10d3" 02:00.0 0200: 8086:10d3 03:00.0 "Ethernet controller" "Intel Corporation" "82574L Gigabit Network Connection" "Super Micro Computer Inc" "Device 10d3" 03:00.0 0200: 8086:10d3
I'll get the correct driver.
Also, this is a specialized server, so network manager is not an option. Plus, the wireless card will be configured as an access point and I don't believe NM will allow me ot configure it that way.
Emmett
Confirmed, it's kmod-rt2860sta you want.
$ grep -i 1814 /lib/modules/*/modules.alias | grep -i 0781 /lib/modules/2.6.18-128.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-164.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-194.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-238.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-274.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-53.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-8.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta /lib/modules/2.6.18-92.el5/modules.alias:alias pci:v00001814d00000781sv*sd*bc*sc*i* rt2860sta
Set up elrepo as described on the homepage here:
then install the driver with:
yum install kmod-rt2860sta
yum will pull in the required firmware package as a dependency.
Hope that helps.