Re: After last upgrade (sid) thz connection wifi doesn't work
On Mon, 25 Aug 2008 17:49:19 +0200
Gerard Robin <g.robin3@free.fr> wrote:
> On Mon, Aug 25, 2008 at 10:44:15AM -0400, Celejar wrote:
> >From: Celejar <celejar@gmail.com>
> >To: debian-laptop@lists.debian.org
> >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@free.fr> 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
Reply to: