From: Priit Laes <plaes@plaes.org>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: [REGRESSION] Trouble seeing some wireless networks in latest git
Date: Sun, 27 Apr 2008 12:24:58 +0300 [thread overview]
Message-ID: <1209288298.3851.12.camel@localhost> (raw)
Hey,
There seems to be some kind of regression in wireless drivers that makes
it not possible to see some wireless networks.
This can be seen with both b43 and iwl3945 drivers.
Using Kismet wireless scanner these networks were visible under latest
git.
All the networks rendered invisible seem to be from channels: 1 (one
network visible), 3, 8, 12 and 13. Visible networks are in channels 1,
4, 6, 9 and 11.
Any hints how to debug this further?
--
Priit
next reply other threads:[~2008-04-27 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 9:24 Priit Laes [this message]
2008-04-27 15:43 ` [REGRESSION] Trouble seeing some wireless networks in latest git Larry Finger
2008-04-27 15:48 ` Michael Buesch
2008-04-27 17:00 ` Priit Laes
2008-04-27 17:04 ` Brian Morrison
2008-04-28 17:38 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209288298.3851.12.camel@localhost \
--to=plaes@plaes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).