what software is running my wireless card?

glopv2 · 10-11-2007, 04:00 PM

Hi, I know there is a command lspci that lists all of your hardware. I used it to find my wireless card (atheros). But now, I'm wondering what software is running my card? The reason I ask is, I want to switch it to "mad-wifi" (I hear it's good). How can I check what's controlling my wifi right now?

Thanks!

Brian1 · 10-11-2007, 05:00 PM

If you are not using madwifi then you would more than likely be using ndiswrapper. How it is setup can very from distro to distro. I would first run the command ' /sbin/ifconfig -a ' and see what name the interface is using. More than likely wlan0 if so run the command ' /sbin/lsmod | grep ndis ' and see if ndiswrapper is loaded.

Brian

glopv2 · 10-11-2007, 05:33 PM

Quote:

If you are not using madwifi then you would more than likely be using ndiswrapper. How it is setup can very from distro to distro. I would first run the command ' /sbin/ifconfig -a ' and see what name the interface is using. More than likely wlan0 if so run the command ' /sbin/lsmod | grep ndis ' and see if ndiswrapper is loaded.

Brian

First, I seem to have two names for my interface because this is the output of ifconfig -a:

Code:

robert@JOHNNYCASH:~$ /sbin/ifconfig -a
ath0      Link encap:Ethernet  HWaddr 00:19:7D:07:1F:02
          inet6 addr: fe80::219:7dff:fe07:1f02/64 Scope:Link
          UP BROADCAST RUNNING 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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 00:16:41:AA:FA:1C
          inet addr:192.168.0.109  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::216:41ff:feaa:fa1c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:211380 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102445 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:131563942 (125.4 MiB)  TX bytes:21746346 (20.7 MiB)
          Base address:0x3000 Memory:ee000000-ee020000

irda0     Link encap:IrLAP  HWaddr 00:00:00:00
          NOARP  MTU:2048  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:8
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

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:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7985 (7.7 KiB)  TX bytes:7985 (7.7 KiB)

wifi0     Link encap:UNSPEC  HWaddr 00-19-7D-07-1F-02-30-3A-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:390574 errors:0 dropped:0 overruns:0 frame:11492
          TX packets:2880 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:199
          RX bytes:36018018 (34.3 MiB)  TX bytes:132529 (129.4 KiB)
          Interrupt:21

Then, running lsmod | grep ndis doesn't seem to do anything.
But, these lines looked relevant when I just typed "lsmod":

Code:

wlan_scan_sta          12608  1
nsc_ircc               21264  0
ath_rate_sample        12928  1
yenta_socket           24844  1
e1000                 112832  0
wlan                  189552  4 ath_pci,wlan_scan_sta,ath_rate_sample
ath_hal               232800  3 ath_pci,ath_rate_sample

Thanks so much for the help!

Nylex · 10-11-2007, 05:52 PM

You're already using MadWifi, as indicated by your device being called "ath0" and the modules you've got loaded with "ath" in them.

Brian1 · 10-11-2007, 06:25 PM

Yes it using madwifi. The wifi is referencing to ath0 madwifi interface. Compare mac address info.

Brian