After last upgrade (sid) thz connection wifi doesn't work

[zadig]

Hello,
After last upgrade (sid) my connection wifi doesn't work.
However the connection wifi works fine with puppy.

my laptop: acer aspire wmli 5102
kernel 2.6.26-1-amd64
Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

Can someone help me to solve the problem ?
tia.

--
Gérard


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[celejar]

On Mon, 25 Aug 2008 15:58:03 +0200
Gerard Robin <g.robin3@...> wrote:

> Hello,
> After last upgrade (sid) my connection wifi doesn't work.
> However the connection wifi works fine with puppy.
>
> my laptop: acer aspire wmli 5102
> kernel 2.6.26-1-amd64
> Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
>
> Can someone help me to solve the problem ?

We need more information; how does it fail?  Post 'ifconfig -a', a
relevant dmesg excerpt, the result of 'ifup ath0' or whatever command
you're using to bring the interface up, a relevant syslog excerpt, etc.


Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[zadig]

On Mon, Aug 25, 2008 at 10:44:15AM -0400, Celejar wrote:
>From: Celejar <celejar@...>
>To: debian-laptop@...
>Subject: Re: After last upgrade (sid) thz connection wifi doesn't work

>On Mon, 25 Aug 2008 15:58:03 +0200
>Gerard Robin <g.robin3@...> wrote:
>
>> Hello,
>> After last upgrade (sid) my connection wifi doesn't work.
>> However the connection wifi works fine with puppy.
>>
>> my laptop: acer aspire wmli 5102
>> kernel 2.6.26-1-amd64
>> Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

>We need more information; how does it fail?  Post 'ifconfig -a', a
>relevant dmesg excerpt, the result of 'ifup ath0' or whatever command
>you're using to bring the interface up, a relevant syslog excerpt, etc.

syslog: at 07:21
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #2 ath0, fe80::219:7dff:fe02:46aa#123 Enabled
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #3 lo, ::1#123 Enabled
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #4 eth0, fe80::216:d4ff:fe66:295d#123 Enabled
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #5 lo, 127.0.0.1#123 Enabled
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #6 eth0, 192.168.0.12#123 Enabled
Aug 25 07:21:14 mybox ntpd[3418]: Listening on interface #7 ath0, 192.168.0.11#123 Enabled

syslog: at 12:39
Aug 25 12:39:51 mybox avahi-daemon[3202]: Withdrawing address record for 192.168.0.11 on ath0.
Aug 25 12:39:51 mybox avahi-daemon[3202]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.0.11.
Aug 25 12:39:51 mybox avahi-daemon[3202]: Interface ath0.IPv4 no longer relevant for mDNS.
Aug 25 12:39:52 mybox dhclient: wifi0: unknown hardware address type 801
Aug 25 12:39:52 mybox dhclient: Listening on LPF/ath0/00:19:7d:02:46:aa
Aug 25 12:39:52 mybox dhclient: Sending on   LPF/ath0/00:19:7d:02:46:aa
Aug 25 12:39:52 mybox dhclient: Sending on   Socket/fallback
Aug 25 12:39:56 mybox dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67
Aug 25 12:40:00 mybox dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67
Aug 25 12:40:10 mauritiusGA dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
Aug 25 12:40:16 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
Aug 25 12:40:22 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16
Aug 25 12:40:38 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
Aug 25 12:40:58 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
Aug 25 12:41:05 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
Aug 25 12:41:11 mybox dhclient: No DHCPOFFERS received.
Aug 25 12:41:11 mybox dhclient: Trying recorded lease 192.168.0.11
Aug 25 12:41:11 mybox avahi-daemon[3202]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.0.11.
Aug 25 12:41:11 mybox avahi-daemon[3202]: New relevant interface ath0.IPv4 for mDNS.
Aug 25 12:41:11 mybox avahi-daemon[3202]: Registering new address record for 192.168.0.11 on ath0.IPv4.
Aug 25 12:41:11 mybox dhclient: bound: immediate renewal.
Aug 25 12:41:11 mybox dhclient: DHCPREQUEST on ath0 to 192.168.0.254 port 67
Aug 25 12:41:43 mybox last message repeated 4 times
Aug 25 12:42:54 mybox last message repeated 5 times
Aug 25 12:43:49 mybox last message repeated 4 times
Aug 25 12:44:55 mybox last message repeated 5 times
Aug 25 12:45:56 mybox last message repeated 5 times
Aug 25 12:46:56 mybox last message repeated 5 times
Aug 25 12:47:59 mybox last message repeated 4 times
Aug 25 12:49:00 mybox last message repeated 4 times
Aug 25 12:49:07 mybox dhclient: receive_packet failed on ath0: Network is down
Aug 25 12:49:07 mybox dhclient: receive_packet failed on ath0: Network is down

The problem occured just after an upgrade, I think it's a file of
config to modify or a bug, but I don't know in which package ;-)
(with puppy on a pendrive my connection wifi works fine on the same box)

--
Gérard


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[celejar]

On Mon, 25 Aug 2008 17:49:19 +0200
Gerard Robin <g.robin3@...> wrote:

> On Mon, Aug 25, 2008 at 10:44:15AM -0400, Celejar wrote:
> >From: Celejar <celejar@...>
> >To: debian-laptop@...
> >Subject: Re: After last upgrade (sid) thz connection wifi doesn't work
>
> >On Mon, 25 Aug 2008 15:58:03 +0200
> >Gerard Robin <g.robin3@...> wrote:
> >
> >> Hello,
> >> After last upgrade (sid) my connection wifi doesn't work.
> >> However the connection wifi works fine with puppy.
> >>
> >> my laptop: acer aspire wmli 5102
> >> kernel 2.6.26-1-amd64
> >> Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
>
> >We need more information; how does it fail?  Post 'ifconfig -a', a
> >relevant dmesg excerpt, the result of 'ifup ath0' or whatever command
> >you're using to bring the interface up, a relevant syslog excerpt, etc.

...

> syslog: at 12:39
> Aug 25 12:39:51 mybox avahi-daemon[3202]: Withdrawing address record for 192.168.0.11 on ath0.
> Aug 25 12:39:51 mybox avahi-daemon[3202]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.0.11.
> Aug 25 12:39:51 mybox avahi-daemon[3202]: Interface ath0.IPv4 no longer relevant for mDNS.
> Aug 25 12:39:52 mybox dhclient: wifi0: unknown hardware address type 801
> Aug 25 12:39:52 mybox dhclient: Listening on LPF/ath0/00:19:7d:02:46:aa
> Aug 25 12:39:52 mybox dhclient: Sending on   LPF/ath0/00:19:7d:02:46:aa
> Aug 25 12:39:52 mybox dhclient: Sending on   Socket/fallback
> Aug 25 12:39:56 mybox dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67
> Aug 25 12:40:00 mybox dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67
> Aug 25 12:40:10 mauritiusGA dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
> Aug 25 12:40:16 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
> Aug 25 12:40:22 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16
> Aug 25 12:40:38 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
> Aug 25 12:40:58 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7
> Aug 25 12:41:05 mybox dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
> Aug 25 12:41:11 mybox dhclient: No DHCPOFFERS received.
> Aug 25 12:41:11 mybox dhclient: Trying recorded lease 192.168.0.11
> Aug 25 12:41:11 mybox avahi-daemon[3202]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.0.11.
> Aug 25 12:41:11 mybox avahi-daemon[3202]: New relevant interface ath0.IPv4 for mDNS.
> Aug 25 12:41:11 mybox avahi-daemon[3202]: Registering new address record for 192.168.0.11 on ath0.IPv4.
> Aug 25 12:41:11 mybox dhclient: bound: immediate renewal.
> Aug 25 12:41:11 mybox dhclient: DHCPREQUEST on ath0 to 192.168.0.254 port 67
> Aug 25 12:41:43 mybox last message repeated 4 times
> Aug 25 12:42:54 mybox last message repeated 5 times
> Aug 25 12:43:49 mybox last message repeated 4 times
> Aug 25 12:44:55 mybox last message repeated 5 times
> Aug 25 12:45:56 mybox last message repeated 5 times
> Aug 25 12:46:56 mybox last message repeated 5 times
> Aug 25 12:47:59 mybox last message repeated 4 times
> Aug 25 12:49:00 mybox last message repeated 4 times
> Aug 25 12:49:07 mybox dhclient: receive_packet failed on ath0: Network is down
> Aug 25 12:49:07 mybox dhclient: receive_packet failed on ath0: Network is down

Try stopping the avahi-daemon; it can apparently muck things up.  What
does 'iwconfig ath0' give?

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[zadig]

On Mon, Aug 25, 2008 at 12:07:00PM -0400, Celejar wrote:
>From: Celejar <celejar@...>
>To: debian-laptop@...
>Subject: Re: After last upgrade (sid) thz connection wifi doesn't work

>Try stopping the avahi-daemon; it can apparently muck things up.  
same result.

>What does 'iwconfig ath0' give?
ath0      IEEE 802.11g  ESSID:"JAG76"  Nickname:""
           Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated  
           Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=1/1  
           Retry:off   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
           Rx invalid nwid:259252  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

--
Gérard


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[celejar]

On Mon, 25 Aug 2008 19:02:16 +0200
Gerard Robin <g.robin3@...> wrote:

> On Mon, Aug 25, 2008 at 12:07:00PM -0400, Celejar wrote:
> >From: Celejar <celejar@...>
> >To: debian-laptop@...
> >Subject: Re: After last upgrade (sid) thz connection wifi doesn't work
>
> >Try stopping the avahi-daemon; it can apparently muck things up.  
> same result.
>
> >What does 'iwconfig ath0' give?
> ath0      IEEE 802.11g  ESSID:"JAG76"  Nickname:""
>            Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated  
>            Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=1/1  
>            Retry:off   RTS thr:off   Fragment thr:off
>            Encryption key:off
>            Power Management:off
>            Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
>            Rx invalid nwid:259252  Rx invalid crypt:0  Rx invalid frag:0
>            Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Ok, so the card is apparently not associated with the AP.  What does
'iwlist ath0 scan' give?  Does 'ifconfig ath0 up' followed by 'iwconfig
ath0 essid nnnnnnnn' accomplish anything?

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[zadig]

On Mon, Aug 25, 2008 at 05:55:40PM -0400, Celejar wrote:
>From: Celejar <celejar@...>
>To: debian-laptop@...
>Subject: Re: After last upgrade (sid) thz connection wifi doesn't work

>On Mon, 25 Aug 2008 19:02:16 +0200
>Gerard Robin <g.robin3@...> wrote:
>
>> On Mon, Aug 25, 2008 at 12:07:00PM -0400, Celejar wrote:
>> >From: Celejar <celejar@...>
>> >To: debian-laptop@...
>> >Subject: Re: After last upgrade (sid) thz connection wifi doesn't work
>>
>> >Try stopping the avahi-daemon; it can apparently muck things up.  
>> same result.
>>
>> >What does 'iwconfig ath0' give?
>> ath0      IEEE 802.11g  ESSID:"JAG76"  Nickname:""
>>            Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated  
>>            Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=1/1  
>>            Retry:off   RTS thr:off   Fragment thr:off
>>            Encryption key:off
>>            Power Management:off
>>            Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
>>            Rx invalid nwid:259252  Rx invalid crypt:0  Rx invalid frag:0
>>            Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
>Ok, so the card is apparently not associated with the AP.  

You got me a good clue : I saw that Access Point: Not-Associated  
and I did :sudo ifconfig ath0 to get my HWaddr
after that I did: sudo iwconfig ath0 ap xx:xx:xx:xx:xx:xx
+ sudo dhclient ath0 and now the wifi works fine :-)

I don't understand truly why I lost my connection wifi.
Perhaps it happened when I changed my key WPA:
I changed it in /etc/network/interfaces but I forgot to change it
in /etc/wpa_supplicant.conf

>What does 'iwlist ath0 scan' give?  Does 'ifconfig ath0 up' followed by 'iwconfig
>ath0 essid nnnnnnnn' accomplish anything?

Many thanks for your help and sorry for the trouble.
--
Gérard


--
To UNSUBSCRIBE, email to debian-laptop-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...