Bug#571257: marked as done (ath5k and athros wireless fails to work since last kernel update)
Your message dated Thu, 6 Jun 2013 00:12:28 +0200
with message-id <20130605221227.GB5444@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #571257,
regarding ath5k and athros wireless fails to work since last kernel update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
571257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571257
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.30-2-amd64
Version: 2.6.32-5
I'm not sure where to report this.
Debian sqeeze
Fujitsu Lifebook A3130
uname -a reports: Linux WideBook 2.6.32-trunk-amd64 #1 SMP Sun Jan 10
22:40:40 UTC 2010 x86_64 GNU/Linux
The Athros wireless chip is built in on this notebook. All worked well
until the last kernel update. Now the athros chip associates during
boot, but deassociates later. From dmesg:
[ 428.084211] ath0: deauthenticating from 00:16:01:4a:c8:a3 by local
choice (reason=3)
lspci reports:
...
07:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless
Network Adapter (rev 01
...
This has a secondary effect in that both top and bottom panels in Gnome
don't work as long as there is no internet. If I plug in the hardware
port eth0, do an ifdown, then ifup on eth0 the banners start to work
after a while. This seems to be a very strange side affect!
Once I know where to send this report I can include the logs.
Regards,
Jim Ham
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
Reply to: