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-key <thekey> 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> [<ffffffff8027342b>] > __report_bad_irq+0x30/0x72 > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff80273674>] > note_interrupt+0x207/0x26b > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff80273d4c>] > handle_fasteoi_irq+0xb1/0xdb > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff8020f5e5>] > do_IRQ+0x6d/0xd6 > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff8020c66e>] > ret_from_intr+0x0/0x29 > Sep 3 21:37:09 roth kernel: [ 729.016014] <EOI> [<ffffffff803bf45c>] > menu_reflect+0x0/0x61 > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffffa000c115>] > acpi_idle_enter_c1+0x14c/0x194 [processor] > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffffa000c0b1>] > acpi_idle_enter_c1+0xe8/0x194 [processor] > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff803be534>] > cpuidle_idle_call+0x94/0xd1 > Sep 3 21:37:09 roth kernel: [ 729.016014] [<ffffffff8020b0cf>] > 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] [<ffffffffa040253f>] > (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]