Re: problems with madwifi and Atheros AR5418
Hello All, red this article it might be helpful: http://ronymattar.com/blog/?p=10 http://ronymattar.com/blog/?p=10 Manuel Pégourié-Gonnard-2 wrote: Hi all, My new laptop (asus F80L-4P007C) comes with an Atheros AR5418 wifi chipset, which apparently doesn't work well with madwifi from current Lenny. This chipset is reported to work with madwifi at: http://madwifi.org/wiki/Compatibility/Atheros#AtherosAR5418 I have packet loss varying form 0% to 85%, even pinging my local gateway (which is also the wifi AP). The only other abnormal things I noticed are the message wifi0: unknow hardware address type 801 issued (two times) when I ran 'dhclient ath0' (after configuring the card with iwconfig and bringing it up with ifconfig). Now, after some time using it, I have: [EMAIL PROTECTED]:~% /sbin/iwconfig ath0 ath0 IEEE 802.11g ESSID:freeboite Nickname: Mode:Managed Frequency:2.412 GHz Access Point: 96:8C:04:33:F8:1C Bit Rate:48 Mb/s Tx-Power:14 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=65/70 Signal level=-31 dBm Noise level=-96 dBm Rx invalid nwid:47937 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I notice that 'Rx invalid nwid' is non-zero, but don't know how to use this information. What can I do in order to debug or work around this problem? For now the options I can see are: 1. Use a more recent madwifi snapshot. 2. Try a 2.6.27 kernel with the new ath9k driver which is supposed to handle my chipset. 3. Use the win32 driver via ndiswrapper. I don't like this option at all, it also forces me to re-install everything in 32bits... Any sensible advice greatly welcome! I include some info which my be useful, feel free to ask more if I forgot something important. TIA, Manuel. [EMAIL PROTECTED]:~% lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR5418 802.11abgn Wireless PCI Express Adapter (rev 01) [EMAIL PROTECTED]:~% lspci -v -s 02:00.0 02:00.0 Network controller: Atheros Communications Inc. AR5418 802.11abgn Wireless PCI Express Adapter (rev 01) Subsystem: Atheros Communications Inc. Device 3072 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at fdef (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: ath_pci Kernel modules: ath_pci, ath5k roth:~# lsmod G 'ath|wlan' wlan_wep9984 1 wlan_scan_sta 17280 1 ath_rate_sample17024 1 ath_pci 241600 0 wlan 223904 5 wlan_wep,wlan_scan_sta,ath_rate_sample,ath_pci ath_hal 334480 3 ath_rate_sample,ath_pci [EMAIL PROTECTED]:~% uname -a Linux roth 2.6.26-1-amd64 #1 SMP Wed Aug 20 12:09:32 UTC 2008 x86_64 GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/problems-with-madwifi-and-Atheros-AR5418-tp19277095p19716334.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Am 2008-09-08 09:33:46, schrieb Kevin Mitchell: The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60 AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Here 25 MByte or 25 MBit? If you mean the first one, you are a liar... If you mean the second one, you have a crapy AP. I get on with the Chipset arround 43 MBit/Sec. But I prefer the 11a stuff, since my AP Proxim Tsunami MP.11a with my i.MX31 (using the new Maxim MAX2829; much cheaper as the Atheros Chip) give me over 47 MBit. And of course, I get it in a distance of more then 1500m on a good day or 900m if a hurican blows over Strasbourg. Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Re: problems with madwifi and Atheros AR5418
When you run dhclient without arguments, it tries to get an ip address on any of the interfaces listed with /sbin/ifconfig minus the lo interface. If you take a look at that output with the ath9k module loaded, you'll see a wmaster0 interface. My understanding is that this is a kind of abstraction layer from which the wlan0 interface is created. Thus, trying to get an ip address directly on it doesn't work. Of course wlan0 should get an ip just fine provided your associated to an AP with dhcp. If that message disturbs you, you could try runnning dhclient wlan0 so that it only tries to get an address on wlan0 which is all you really want anyway. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
On Thu, 18 Sep 2008 12:06:10 -0700 Kevin Mitchell [EMAIL PROTECTED] wrote: When you run dhclient without arguments, it tries to get an ip address on any of the interfaces listed with /sbin/ifconfig minus the lo interface. If you take a look at that output with the ath9k module loaded, you'll see a wmaster0 interface. My understanding is that this is a kind of abstraction layer from which the wlan0 interface is created. Thus, trying to get an ip address directly on it doesn't work. Of course wlan0 should get an ip just fine provided your associated to an AP with dhcp. If that message disturbs you, you could try runnning dhclient wlan0 so that it only tries to get an address on wlan0 which is all you really want anyway. Kevin Thanks. I understood what you have explained; my perplexity concerns the fact that even when dhclient is called on the actual interface (wlan0, or eth0 as renamed by udev), not on wmaster0, I still get those warnings. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Oh, you're right, I guess I didn't notice that before. In any case, it doesn't appear to cause any problems for me either. It's just an annoying error message. Kevin On Thu, Sep 18, 2008 at 12:42 PM, Celejar [EMAIL PROTECTED] wrote: On Thu, 18 Sep 2008 12:06:10 -0700 Kevin Mitchell [EMAIL PROTECTED] wrote: When you run dhclient without arguments, it tries to get an ip address on any of the interfaces listed with /sbin/ifconfig minus the lo interface. If you take a look at that output with the ath9k module loaded, you'll see a wmaster0 interface. My understanding is that this is a kind of abstraction layer from which the wlan0 interface is created. Thus, trying to get an ip address directly on it doesn't work. Of course wlan0 should get an ip just fine provided your associated to an AP with dhcp. If that message disturbs you, you could try runnning dhclient wlan0 so that it only tries to get an address on wlan0 which is all you really want anyway. Kevin Thanks. I understood what you have explained; my perplexity concerns the fact that even when dhclient is called on the actual interface (wlan0, or eth0 as renamed by udev), not on wmaster0, I still get those warnings. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: problems with madwifi and Atheros AR5418
I would suggest reporting this to the ath9k-devel list: https://lists.ath9k.org/mailman/listinfo/ath9k-devel especially if it is reproducible. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60 AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Here are instructions for compiling the kernel in Debian: http://www.thinkwiki.org/wiki/How_to_install_the_development_version_of_atk9k. There is also someone on Ubuntu forums who has created a script to compile the module for pre 2.6.27 kernels and stick it in a .deb package for you. I have found this be compatible with Debian, though I haven't tried out his latest version http://ubuntuforums.org/showpost.php?p=5535562postcount=3. I used to use madwifi and didn't experience the kind of problems you speak of. I did however notice that somewhere along the way, there was a regression that slowed down the connection by a non negligible amount http://madwifi.org/ticket/2043. You might try downloading 3401 snapshot (I think you use the -r 3401 as an argument to svn). I had meant to pinpoint exactly when and where this regression occured, but then ath9k came out and there was an exponential decay in my caring coefficient. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Kevin Mitchell a écrit : The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60 AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Wow. Here I can't do tests since my only other local machine has slow wifi, but yes, ath9k form 2.6.27-rc5 works fine too (except that that card won't reconnect to the AP if it goes down then up unless I reload the driver... fortunately, my AP doens't go down that often). I used to use madwifi and didn't experience the kind of problems you speak of. I did however notice that somewhere along the way, there was a regression that slowed down the connection by a non negligible amount http://madwifi.org/ticket/2043. You might try downloading 3401 snapshot (I think you use the -r 3401 as an argument to svn). I had meant to pinpoint exactly when and where this regression occured, but then ath9k came out and there was an exponential decay in my caring coefficient. Well, since ath9k is working well, I don't think I'll try to go back to madwifi. Now the only drawback is, module-assistant doesn't succed any more in building modules: I'm under the impression it tries to use the 2.6.26 headers... Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Sorry if I used the wrong notation, that was 25 Mbits/s ~ 3.2 Mbytes/s which is only slightly faster that 11g so it's not that wow, but an improvement nonetheless. What modules is module assistant trying to build? The headers shouldn't be a problem. If you've compiled your own kernel, just make sure to keep the source tree from the compile (that means don't make clean it too). I did however notice a few things weren't yet bleeding edge enough for the new kernel. A common problem is that the asm/semaphore.h header is now at linux/semaphore.h. If you take a look in your source files and switch that around, things might work. For example, see this bug on tp_ctrl: http://sourceforge.net/tracker/index.php?func=detailaid=2041469group_id=1212atid=101212 Kevin On Mon, Sep 8, 2008 at 9:49 AM, Manuel Pégourié-Gonnard [EMAIL PROTECTED] wrote: Kevin Mitchell a écrit : The ath9k in 2.6.27-rc5 is working famously for me on my Thinkpad T60 AR5418. I'm even creeping past 11g speeds (25MB/s on a good day). Wow. Here I can't do tests since my only other local machine has slow wifi, but yes, ath9k form 2.6.27-rc5 works fine too (except that that card won't reconnect to the AP if it goes down then up unless I reload the driver... fortunately, my AP doens't go down that often). I used to use madwifi and didn't experience the kind of problems you speak of. I did however notice that somewhere along the way, there was a regression that slowed down the connection by a non negligible amount http://madwifi.org/ticket/2043. You might try downloading 3401 snapshot (I think you use the -r 3401 as an argument to svn). I had meant to pinpoint exactly when and where this regression occured, but then ath9k came out and there was an exponential decay in my caring coefficient. Well, since ath9k is working well, I don't think I'll try to go back to madwifi. Now the only drawback is, module-assistant doesn't succed any more in building modules: I'm under the impression it tries to use the 2.6.26 headers... Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Kevin Mitchell a écrit : Sorry if I used the wrong notation, that was 25 Mbits/s ~ 3.2 Mbytes/s which is only slightly faster that 11g so it's not that wow, but an improvement nonetheless. Well, even if the improvement is not great, it's an improvement. So it's cool given that my basic problem was just to get the thing working at all. What modules is module assistant trying to build? Alsa and virtualbox-ose. I tried with alsa-source from sid as well as from testing, and virtualbox-ose-source only from testing (I'm basically running testing except when I *need* bleeding edge versions). The headers shouldn't be a problem. If you've compiled your own kernel, just make sure to keep the source tree from the compile (that means don't make clean it too). Yes, actually it's ok. I forgot to rename the 2.6.26 directory to 2.6.27-rc5 after patching it, so that's why I thought it was using the wrong headers. I did however notice a few things weren't yet bleeding edge enough for the new kernel. A common problem is that the asm/semaphore.h header is now at linux/semaphore.h. If you take a look in your source files and switch that around, things might work. For example, see this bug on tp_ctrl: http://sourceforge.net/tracker/index.php?func=detailaid=2041469group_id=1212atid=101212 Oh yes, exactly. I had this problem while trying to compile the modules for virtualbox. Would a symlink be fine to make sure everyone can find semaphore.h where it expects it? Thanks, Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) Thursday 04 September 2008 02:40, Celejar a écrit (wrote) : ADDRCONF(NETDEV_UP): wlan0: link is not ready This line generally appears when the card comes on-line; if all goes well, it should soon be followed by something like 'ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready' Well, the whole point is, it isn't followed by any link becomes ready message (unless I modprobe -r ath9k modprobe ath9k, which is a pain). ADDRCONF(NETDEV_UP): eth0: link is not ready eth0: direct probe to AP 00:17:5a:4f:31:c0 try 1 eth0 direct probe responded eth0: authenticate with AP 00:17:5a:4f:31:c0 eth0: authenticated eth0: associate with AP 00:17:5a:4f:31:c0 eth0: RX AssocResp from 00:17:5a:4f:31:c0 (capab=0x401 status=0 aid=53) eth0: associated ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready It's exactly what happens on my box /after/ I removed and reprobed the driver, and what I would like to happen automatically. I'm not much of an expert, but here are a couple of suggestions: Try disabling WEP, and see if the problem persists. It does. Try configuring the interface manually, without DHCP: ifconfig wlan0 up iwconfig wlan0 essid ifconfig wlan0 x.x.x.x I tried. I doesn't change anything. The chip remains non associated to any AP, and the only things I can see in syslog is the above mentionned links is not ready message when I try tu use dhclient. Static IP configuration doesn't work either. Unless somebody comes with an idea about what I'm doing, I'll assume this is a problem with the driver and report on ath9k-devel. Thanks for your suggestions, Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) mercredi 03 septembre 2008 02:30, Celejar a écrit (wrote) : wmaster: unknown hardware address type 801 I think this message is normal; I get it too with both my Atheros and Broadcom cards. Ok, thanks for the info. By the way, I was perhaps a bit to fast saying that it wotks. Actually it worked for the whole day, then there was a general electrical failure, which means my AP when down and my laptop on battery (don't know which one is responsible). When I tried to re-connect to the AP, no way to use the wifi. Even rebooting couldn't change that. Then I tried to reinstall the madwifi drivers, and when I loaded ath_pci (after unloading ath9k) I has what looks like a bad error: Sep 3 21:37:09 roth dhclient: send_packet: No such device Sep 3 21:37:09 roth kernel: [ 729.016014] irq 17: nobody cared (try booting with the irqpoll option) Sep 3 21:37:09 roth kernel: [ 729.016014] Pid: 0, comm: swapper Tainted: P 2.6.27-rc5 #1 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] Call Trace: Sep 3 21:37:09 roth kernel: [ 729.016014] IRQ [8027342b] __report_bad_irq+0x30/0x72 Sep 3 21:37:09 roth kernel: [ 729.016014] [80273674] note_interrupt+0x207/0x26b Sep 3 21:37:09 roth kernel: [ 729.016014] [80273d4c] handle_fasteoi_irq+0xb1/0xdb Sep 3 21:37:09 roth kernel: [ 729.016014] [8020f5e5] do_IRQ+0x6d/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020c66e] ret_from_intr+0x0/0x29 Sep 3 21:37:09 roth kernel: [ 729.016014] EOI [803bf45c] menu_reflect+0x0/0x61 Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c115] acpi_idle_enter_c1+0x14c/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c0b1] acpi_idle_enter_c1+0xe8/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [803be534] cpuidle_idle_call+0x94/0xd1 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020b0cf] cpu_idle+0x8e/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] handlers: Sep 3 21:37:09 roth kernel: [ 729.016014] [a040253f] (ath_intr+0x0/0x3f59 [ath_pci]) Sep 3 21:37:09 roth kernel: [ 729.016014] Disabling IRQ #17 (IRQ 17 was used by the wireless chip). After that, I rebooted and everything works fine again with ath9k. Do you have any idea how to investigate this? Thanks, Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) mercredi 03 septembre 2008 22:20, mpg a écrit (wrote) : which means my AP when down and my laptop on battery (don't know which one is responsible). Well, I did the test. When the AP gets down, I can see wlan0: No ProbeResp from current AP address - assume out of range which looks perfectly correct. The problem is, after this, when the AP is back, I can try ifdown wlan0; ifup wlan0 or whater using iwconfig, ifconfig and dhclient, it doesn't associate any more with the AP, and I get messages like ADDRCONF(NETDEV_UP): wlan0: link is not ready The only way I found to make the thing work again is to modprobe -r ath9k modprobe ath9k (that is, unload and relaod the driver). Then it authenticates and associates back with the AP and everything's fine. Is something wrong with my config, am I doing something wrong, or is it a problem with the driver? For what it's worth, the relavant section of my /etc/network/interfaces looks like: allow-hotplug wlan0 iface wlan0 inet dhcp wireless-essid myessid wireless-keythekey and I'm using WEP authentication. Thanks, Manuel. When I tried to re-connect to the AP, no way to use the wifi. Even rebooting couldn't change that. Then I tried to reinstall the madwifi drivers, and when I loaded ath_pci (after unloading ath9k) I has what looks like a bad error: Sep 3 21:37:09 roth dhclient: send_packet: No such device Sep 3 21:37:09 roth kernel: [ 729.016014] irq 17: nobody cared (try booting with the irqpoll option) Sep 3 21:37:09 roth kernel: [ 729.016014] Pid: 0, comm: swapper Tainted: P 2.6.27-rc5 #1 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] Call Trace: Sep 3 21:37:09 roth kernel: [ 729.016014] IRQ [8027342b] __report_bad_irq+0x30/0x72 Sep 3 21:37:09 roth kernel: [ 729.016014] [80273674] note_interrupt+0x207/0x26b Sep 3 21:37:09 roth kernel: [ 729.016014] [80273d4c] handle_fasteoi_irq+0xb1/0xdb Sep 3 21:37:09 roth kernel: [ 729.016014] [8020f5e5] do_IRQ+0x6d/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020c66e] ret_from_intr+0x0/0x29 Sep 3 21:37:09 roth kernel: [ 729.016014] EOI [803bf45c] menu_reflect+0x0/0x61 Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c115] acpi_idle_enter_c1+0x14c/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c0b1] acpi_idle_enter_c1+0xe8/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [803be534] cpuidle_idle_call+0x94/0xd1 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020b0cf] cpu_idle+0x8e/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] handlers: Sep 3 21:37:09 roth kernel: [ 729.016014] [a040253f] (ath_intr+0x0/0x3f59 [ath_pci]) Sep 3 21:37:09 roth kernel: [ 729.016014] Disabling IRQ #17 (IRQ 17 was used by the wireless chip). After that, I rebooted and everything works fine again with ath9k. Do you have any idea how to investigate this? Thanks, Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
On Wed, 03 Sep 2008 21:58:54 +0200 mpg [EMAIL PROTECTED] wrote: ... By the way, I was perhaps a bit to fast saying that it wotks. Actually it worked for the whole day, then there was a general electrical failure, which means my AP when down and my laptop on battery (don't know which one is responsible). When I tried to re-connect to the AP, no way to use the wifi. Even rebooting couldn't change that. Then I tried to reinstall the madwifi drivers, and when I loaded ath_pci (after unloading ath9k) I has what looks like a bad error: Sep 3 21:37:09 roth dhclient: send_packet: No such device Sep 3 21:37:09 roth kernel: [ 729.016014] irq 17: nobody cared (try booting with the irqpoll option) Sep 3 21:37:09 roth kernel: [ 729.016014] Pid: 0, comm: swapper Tainted: P 2.6.27-rc5 #1 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] Call Trace: Sep 3 21:37:09 roth kernel: [ 729.016014] IRQ [8027342b] __report_bad_irq+0x30/0x72 Sep 3 21:37:09 roth kernel: [ 729.016014] [80273674] note_interrupt+0x207/0x26b Sep 3 21:37:09 roth kernel: [ 729.016014] [80273d4c] handle_fasteoi_irq+0xb1/0xdb Sep 3 21:37:09 roth kernel: [ 729.016014] [8020f5e5] do_IRQ+0x6d/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020c66e] ret_from_intr+0x0/0x29 Sep 3 21:37:09 roth kernel: [ 729.016014] EOI [803bf45c] menu_reflect+0x0/0x61 Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c115] acpi_idle_enter_c1+0x14c/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [a000c0b1] acpi_idle_enter_c1+0xe8/0x194 [processor] Sep 3 21:37:09 roth kernel: [ 729.016014] [803be534] cpuidle_idle_call+0x94/0xd1 Sep 3 21:37:09 roth kernel: [ 729.016014] [8020b0cf] cpu_idle+0x8e/0xd6 Sep 3 21:37:09 roth kernel: [ 729.016014] Sep 3 21:37:09 roth kernel: [ 729.016014] handlers: Sep 3 21:37:09 roth kernel: [ 729.016014] [a040253f] (ath_intr+0x0/0x3f59 [ath_pci]) Sep 3 21:37:09 roth kernel: [ 729.016014] Disabling IRQ #17 (IRQ 17 was used by the wireless chip). After that, I rebooted and everything works fine again with ath9k. Do you have any idea how to investigate this? Sorry, I have no idea what those messages signify. Thanks, Manuel. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
On Wed, 03 Sep 2008 23:14:46 +0200 mpg [EMAIL PROTECTED] wrote: Le (on) mercredi 03 septembre 2008 22:20, mpg a écrit (wrote) : which means my AP when down and my laptop on battery (don't know which one is responsible). Well, I did the test. When the AP gets down, I can see wlan0: No ProbeResp from current AP address - assume out of range which looks perfectly correct. The problem is, after this, when the AP is back, I can try ifdown wlan0; ifup wlan0 or whater using iwconfig, ifconfig and dhclient, it doesn't associate any more with the AP, and I get messages like ADDRCONF(NETDEV_UP): wlan0: link is not ready This line generally appears when the card comes on-line; if all goes well, it should soon be followed by something like 'ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready' From my dmesg (with the b43 driver, which also uses mac80211, like ath9k): ADDRCONF(NETDEV_UP): eth0: link is not ready eth0: direct probe to AP 00:17:5a:4f:31:c0 try 1 eth0 direct probe responded eth0: authenticate with AP 00:17:5a:4f:31:c0 eth0: authenticated eth0: associate with AP 00:17:5a:4f:31:c0 eth0: RX AssocResp from 00:17:5a:4f:31:c0 (capab=0x401 status=0 aid=53) eth0: associated ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready The only way I found to make the thing work again is to modprobe -r ath9k modprobe ath9k (that is, unload and relaod the driver). Then it authenticates and associates back with the AP and everything's fine. Is something wrong with my config, am I doing something wrong, or is it a problem with the driver? For what it's worth, the relavant section of my /etc/network/interfaces looks like: allow-hotplug wlan0 iface wlan0 inet dhcp wireless-essid myessid wireless-keythekey and I'm using WEP authentication. I'm not much of an expert, but here are a couple of suggestions: Try disabling WEP, and see if the problem persists. Try configuring the interface manually, without DHCP: ifconfig wlan0 up iwconfig wlan0 essid ifconfig wlan0 x.x.x.x Read the dmesg and syslog carefully, and perhaps post them here. Good luck, Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) mardi 02 septembre 2008 21:50, mpg a écrit (wrote) : 1. Use a more recent madwifi snapshot. Ok, I just tried this one. Apparently it doesn't help. 2. Try a 2.6.27 kernel with the new ath9k driver which is supposed to handle my chipset. Looks like it's time for me to compile my first kernel... Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
mpg wrote: Hi all, My new laptop (asus F80L-4P007C) comes with an Atheros AR5418 wifi chipset, which apparently doesn't work well with madwifi from current Lenny. This chipset is reported to work with madwifi at: http://madwifi.org/wiki/Compatibility/Atheros#AtherosAR5418 It's reported there to be working on an Apple Macbook. Is that what an asus F80L-4P007C is? AFAIK the madwifi drivers do not work with '802.11abgn' chipsets. Maybe with a newer kernel that includes the ath9k driver, it 'might' work. Wayne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) mardi 02 septembre 2008 22:40, Wayne Topa a écrit (wrote) : http://madwifi.org/wiki/Compatibility/Atheros#AtherosAR5418 It's reported there to be working on an Apple Macbook. Is that what an asus F80L-4P007C is? Not exactly. But I naively thought that the driver was for the chipset only, and didn't depend on the computer around the chipset. AFAIK the madwifi drivers do not work with '802.11abgn' chipsets. Bad news for me. Maybe with a newer kernel that includes the ath9k driver, it 'might' work. 2.6.27-rc5 is building right now. I'll see. Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
Le (on) mardi 02 septembre 2008 23:30, mpg a écrit (wrote) : Maybe with a newer kernel that includes the ath9k driver, it 'might' work. 2.6.27-rc5 is building right now. I'll see. Rebooted on the new kernel. Wireless networking looks working now. I still have a warning/error wmaster: unknown hardware address type 801 when running dhclient, but now 'Rx invalid nwid' stays at 0 in th output of iwconfig, and I don't loose packets any more. Hope it keeps working. Fingers crossed. Manuel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems with madwifi and Atheros AR5418
On Wed, 03 Sep 2008 00:12:08 +0200 mpg [EMAIL PROTECTED] wrote: ... Rebooted on the new kernel. Wireless networking looks working now. I still have a warning/error wmaster: unknown hardware address type 801 when running dhclient, but now 'Rx invalid nwid' stays at 0 in th output of I think this message is normal; I get it too with both my Atheros and Broadcom cards. Manuel. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
