[Madwifi-users] Atheros card, SuSE 9.1
Status: Beta
Brought to you by:
otaku
From: Josh B. <jo...@ag...> - 2004-08-18 18:16:32
|
=46olks, Beg pardon if I'm turning over trodden ground, but I did browse the archive= s=20 and did not see any similar topics. =20 I have SuSE 9.1, Kernel 2.6.7 installed on an IBM thinkpad with an IBM Athe= ros=20 a-b-g card. This is the same machine I wrote the guide at=20 http://madwifiwiki.thewebhost.de/wiki/SuSE90ProfessionalThinkpadR40IBMTriBa= ndMiniPCICard =2E... for, but with a new hard drive and a fresh install of SuSE 9.1. =20 Thing is, 9.1 seems to recognize my Atheros card configured through YaST, a= nd=20 seems to have some form of the madwifi driver installed (at least, pci_ath = is=20 loaded). If possible, I would like to get the wireless card working=20 entirely using the SuSE GUI tools rather than compiling and shell scripts,= =20 since I'd like to use YaST's Profile Manager to manage my laptop. I'd also= =20 like to be able to instruct Linux newbies (like my father-in-law) in gettin= g=20 *their* wireless working, which means GUI tools. Here's what I have so far: With the Atheros set up in YaST as ath0 with a static address, I get: ifconfig ath0 Link encap:Ethernet HWaddr 00:05:4E:43:F2:D1 inet addr:192.168.1.25 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::205:4eff:fe43:f2d1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1670196 errors:1398836 dropped:0 overruns:0 frame:1398= 797 TX packets:114707 errors:107 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:126974240 (121.0 Mb) TX bytes:5163929 (4.9 Mb) Interrupt:11 Memory:d89c0000-d89d0000 iwconfig ath0 IEEE 802.11 ESSID:"linksys" Nickname:"temoku" Mode:Managed Frequency:2.417GHz Access Point: FF:FF:FF:FF:FF:FF Bit Rate:1Mb/s Tx-Power:off Sensitivity=3D0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 If I use the KDE Control Panel to configure the wireless, then iwconfig=20 changes to: ath0 IEEE 802.11 ESSID:"linksys" Nickname:"temoku" Mode:Managed Frequency:2.437GHz Access Point: 00:0C:41:75:2B:AB Bit Rate:1Mb/s Tx-Power:off Sensitivity=3D0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:38/94 Signal level:-57 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 However, attempts to ping the linksys router still get: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. =46rom 192.168.1.25: icmp_seq=3D2 Destination Host Unreachable =46rom 192.168.1.25 icmp_seq=3D2 Destination Host Unreachable =46rom 192.168.1.25 icmp_seq=3D3 Destination Host Unreachable =46rom 192.168.1.25 icmp_seq=3D4 Destination Host Unreachable The router is a Linksys WRT54G, still running its original software and on = all=20 default settings, except for the password, DHCP (turned off), channel (6) a= nd=20 it's operating in Router and not WAP mode. One of my collegues using a So= ny=20 laptop with XP home was able to connect to it, and I can use it as a hub vi= a=20 the RJ45 ports. =20 So, can someone help me with the next step to get this working? I'm concer= ned=20 that the high error rate reported by ifconfig shows that the driver is bad.= =20 =2D-=20 =2D-Josh Josh Berkus Aglio Database Solutions San Francisco |