Your message dated Fri, 4 Jan 2008 00:58:26 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410229: Is madwifi working with your current kernel?
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: 1:0.9.2+r1842.20061207-2
Severity: important
After upgrading from linux-image-2.6.18-4-686 2.6.18.dfsg.1-9 to
2.6.18.dfsg.1-10, wireless lan doesn't work any longer. The kernel
modules get loaded, ath0 and wifi0 devices are present, but iwlist
doesn't find any wireless networks.
I also tried 1:0.9.2+r2085.20070207-1, but it doesn't help.
Downgrading to 2.6.18.dfsg.1-9 fixes the problem, but I filed the bug
against madwifi-source because the Debian kernel team doesn't support
tainted kernel.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.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.42 helper programs for debian/rules
ii module-assistant 0.10.8 tool to make module package creati
madwifi-source recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Friday 04 January 2008 00:44:28 Norbert Tretkowski wrote:
> Am Donnerstag, den 03.01.2008, 23:41 +1000 schrieb Kel Modderman:
> > Does madwifi still have problems as described on #410229 ?
>
> No, with currently running linux-2.6 2.6.22-6 and madwifi 1:0.9.3.2-2,
> the problem doesn't exist any longer. Not sure when exactly the problem
> was fixed.
>
> Norbert
Thank you for feedback Norbert, I'm closing this report.
Kel.
--- End Message ---
