Package: linux-headers-3.2.0-1-686-pae
Version: 3.2.4-1
Severity: important
File: ath9k
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Connecting to an adhoc (IBSS) node.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Connection to adhoc won't work. Booting the previous (3.1.0-1-686-pae) and it
works again. Although in 3.2.0-1-686-pae managed (router bound) connection DO
work.
* What was the outcome of this action?
Adhoc connections (at least to my other computer, which worked before since
months) do not work with the ATH9K, but managed connection are not affected by
this bug (if it's a bug).
* What outcome did you expect instead?
Espected to connect in adhoc mode.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-headers-3.2.0-1-686-pae depends on:
ii gcc-4.6 4.6.2-12
ii linux-headers-3.2.0-1-common 3.2.4-1
ii linux-kbuild-3.2 3.2.1-2
linux-headers-3.2.0-1-686-pae recommends no packages.
linux-headers-3.2.0-1-686-pae suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20120211200724.4922.88802.reportbug@totem.localdomain
