David Goodenough wrote:
<snip>
>
> Without a nearby AP it is kind of difficult, but you can get clues by
> looking at /var/log/syslog for madwifi related messages, and looking to
> see if there is an interface included in the list you get from ip addr or
> ifconfig.
>
> David
Thanks for that David. I checked the syslog and there are a bunch of
messages relating to ath_pci and ath_hal. They don't seem very revealing;
nothing like "bad driver" or "broken" or "missing". I'm not really sure
what I should be looking for.
The output of ifconfig is easier. Here it is (I've omitted the eth0 and lo
stuff)
wlan0 Link encap:Ethernet HWaddr 00:0e:9b:cf:bc:0c
inet addr:172.26.0.4 Bcast:172.26.0.255 Mask:255.255.255.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)
wmaster0 Link encap:UNSPEC HWaddr
00-0E-9B-CF-BC-0C-65-74-00-00-00-00-00-00-00-00
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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Does this look like it's happy with the driver?
Cheers,
Jonathan
--
Registerd Linux user #445917 at http://counter.li.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
