Your message dated Tue, 17 Oct 2006 00:25:01 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386951: restarting router helped
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: madwifi-source
Version: 0.svnr1697.0.9.2-1
Severity: important
Ever since I upgraded to the madwifi-ng driver, it's become mostly
unusable. I am using the latest 2.6.17 kernel from unstable. From
time to time I get it to work, but most of the time it cannot
establish an association with the access point, even after reloading
the driver. I am using WPA, and with -D madwifi, wpasupplicant says:
<2>Trying to associate with 00:12:cf:01:4a:d6 (SSID='krafft' freq=2447 MHz)
<2>Association request to the driver failed
<2>Associated with 00:12:cf:01:4a:d6
<2>WPA: Key negotiation completed with 00:12:cf:01:4a:d6 [PTK=TKIP GTK=TKIP]
<2>CTRL-EVENT-CONNECTED - Connection to 00:12:cf:01:4a:d6 completed (reauth)
[id=0 id_str=]
<2>WPA: Group rekeying completed with 00:12:cf:01:4a:d6 [GTK=TKIP]
<2>WPA: Group rekeying completed with 00:12:cf:01:4a:d6 [GTK=TKIP]
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
If I switch to -D wext, it's even worse:
<2>Trying to associate with 00:12:cf:01:4a:d6 (SSID='krafft' freq=2447 MHz)
<2>Authentication with 00:00:00:00:00:00 timed out.
As said, from time to time it *does* work with the same
configuration (-D madwifi, I never actually got it to work with
wext). Also, other machines are associating fine with the AP, so it
really seems to be an atheros problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages madwifi-source depends on:
ii bzip2 1.0.3-6 high-quality block-sorting file co
ii debhelper 5.0.37.3 helper programs for debian/rules
ii module-assistant 0.10.6 tool to make module package creati
madwifi-source recommends no packages.
-- no debconf information
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
--- Begin Message ---
On Thursday 14 September 2006 01:15, martin f krafft wrote:
> This just a FYI: after a day of not being able to associate,
> I restarted my router and then the association worked, even without
> the patch you told me to apply. I guess what this means is that it's
> probably not just the driver's fault.
Ok, closing.
PS. please try suspend again with current package based on r1710. It is
reported to be working for a few people.
Thanks, Kel.
--- End Message ---
