it's me again, and this is my situation: on linux I can get anything installed and configured, perhaps not the first time around, but when I need to troubleshoot something I am completely lost!
recently I had my wireless card up an running with madwifi-ng, everything was just fine and I was a proud archlinux user. I started a bittorrent DL, went to bed, in the morning it was still going and I went off to work. When I came home I had no wireless connection - cable is OK. I tried to connect to another AP but it just won't find any stations - literally from one day to the next.
I built madwifi-ng-1467 from AUR on the (as of last week) stock 2.6 arch kernel
all the modules are in there (ath_pci, ath_hal, wlan_scan_sta,...)
iwconfig shows me
ath0 IEEE 802.11g ESSID:"subatomic"
but a scan gives me no results and I can't connect to anything anywhere
I've removed the WEP key just to eliminate any possibility of deterence
maybe I've narrowed it down...
ifconfig ath0 scan
scan: host name lookup failure
What says "route -n" /"dhclient ath0" / "iwconfig ath0"?
ath0 IEE 802.11b ESSID:"subatomic" Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 Bit Rate:0 kb/s
... and so on...
the thing is, when I assign a channel, it will then show activity (searching)
but the rate or channel won't stick (lost on reboot)
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 ath0
I dont use dhclient, I actually have a static assigned
Are you using wep128 - I think this is maybe an authentication problem!
Try to enable manually the card up:
ifconfig ath0 up
iwconfig ath0 mode managed
iwconfig ath0 nick "your Nick"
iwconfig ath0 channel 9
iwconfig ath0 key "your key"
iwconfig ath0 essid "your ssid"
I do appreciate your help (goes for any and everyone) but you need to read my post carefully.
I turned off WEP to eliminate any authentication errors. Ive since turned it back on and tried to reconfigure, but still the same results. Also, I don't use dhcp.
Furthurmore, 'wlanconfig ath0 list scan' returns absolutely nothing and 'iwlist ath0 scan' says no results - I can't even see any APs around me. Besides, I don't know why I would lose a connection in the middle of a session, unless the card gave up.
I'm having a similar problem to you. I've 2 APs, one with WEP, one without, a prism card can connect to both, the atheros card can't connect to either.
I've tried the latest version of madwifi-ng from their site and I've tried the Arch version as mentioned here http://wiki.archlinux.org/index.php/Wireless_Setup.
The card used to work in an old laptop (actually a more moden one) but I can't get it to work with my new one. I've tried the same kind of setup in ubuntu and slackware and neither work so I thought I'd try Arch (glad I did, much nicer distro!).
This is the result from dmesg when the card is inserted:
pccard: CardBus card inserted into slot 0 ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) wlan: 0.8.4.2 (svn 1531) ath_rate_sample: 1.2 (svn 1531) ath_pci: 0.9.4.5 (svn 1531) PCI: Enabling device 0000:03:00.0 (0000 -> 0002) ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10 wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: H/W encryption support: WEP AES AES_CCM TKIP wifi0: mac 5.9 phy 4.3 radio 3.6 wifi0: Use hw queue 1 for WME_AC_BE traffic wifi0: Use hw queue 0 for WME_AC_BK traffic wifi0: Use hw queue 2 for WME_AC_VI traffic wifi0: Use hw queue 3 for WME_AC_VO traffic wifi0: Use hw queue 8 for CAB traffic wifi0: Use hw queue 9 for beacons wifi0: Atheros 5212: mem=0x24000000, irq=10 ath0: no IPv6 routers present
a scan picks up the AP (this is the none-WEP one):
iwlist ath0 scanning ath0 Scan completed : Cell 01 - Address: 00:0E:A6:CE:E2:28 ESSID:"takhisis" Mode:Master Frequency:2.412 GHz (Channel 1) Quality=52/94 Signal level=-43 dBm Noise level=-95 dBm Encryption key:on Bit Rate:1 Mb/s Bit Rate:2 Mb/s Bit Rate:5.5 Mb/s Bit Rate:11 Mb/s Bit Rate:18 Mb/s Bit Rate:24 Mb/s Bit Rate:36 Mb/s Bit Rate:54 Mb/s Bit Rate:6 Mb/s Bit Rate:9 Mb/s Bit Rate:12 Mb/s Bit Rate:48 Mb/s Extra:bcn_int=100
My startup script:
ifconfig ath0 down iwconfig ath0 essid takhisis iwconfig ath0 channel 1 ifconfig ath0 10.1.1.3 up
ath0 IEEE 802.11g ESSID:"takhisis" Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00 Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=0/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
Can anyone help?
Just a bit extra, I've just tried the suggestion of destroying the default ath0 and re-creating it from this post http://bbs.archlinux.org/viewtopic.php? … wlanconfig and no luck.
I've also tried specifying the AP to iwconfig and that doesn't help.
And I have the right modules installed:
ath_pci 91940 0 ath_rate_sample 12032 1 ath_pci wlan 191836 4 wlan_scan_sta,ath_pci,ath_rate_sample ath_hal 187600 3 ath_pci,ath_rate_sample
And just a tip which may help anyone stuck looking for wlanconfig, it is in /usr/local/bin which isn't in your path by default, either update your path or you can symllink it in with ln -s /usr/local/bin/wlanconfig /usr/bin
nothing works and this really blows
I've got mine working. Don't know how, it didn't work, I went out and moaned to a friend, next day it worked. No deliberate changes. If you want any config info or log dumps to compare to your own let me know and I'll post them
now I know why I couldn't troubleshoot this one - the card died! that is, the p.o.s. doesn't send or receive anymore
That would explain it, I did wonder about mine for a while but the laptop dual boots into windows and despite what people say, windows does do a good job of just working when you plug new hardware in so I tested it with that just to make sure.