linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sid Hayn <sidhayn@gmail.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@nbd.name>,
	linux-mediatek@lists.infradead.org
Subject: Re: mt76x0 bug report
Date: Thu, 6 Sep 2018 11:32:14 +0200	[thread overview]
Message-ID: <20180906093213.GB16539@redhat.com> (raw)
In-Reply-To: <CAM0KTbAbjDYNOzivxMdLmYrV9QHgwkLp7zXpdCvn1Kf1uEcQTQ@mail.gmail.com>

On Wed, Sep 05, 2018 at 08:52:18PM +0000, Sid Hayn wrote:
> On Tue, Sep 4, 2018 at 5:11 PM Lorenzo Bianconi
> <lorenzo.bianconi@redhat.com> wrote:
> >
> > >
> > > I have one mt76x2u (Alfa AWUS036ACM) and a few mt76x0.
> > >
> > > I've noticed two additional issues in my testing.
> > >
> > > First issue, is that it appears the mt76x0 devices don't work properly
> > > in monitor mode.  Sometimes they seem to monitor one channel properly,
> > > but nothing else.  The mt76x2u works great, channel control, lots of
> > > packets, etc.
> >
> > Could you elaborate a little bit please? how can you reproduce the issue?
> > just add an interface in monitor mode and run a scan?
> 
> Correct, standard stuff, use iw to create a monitor mode interface,
> use iw to remove managed mode interface, run some tool such as kismet
> or airodump-ng or even wireshark.

But what exactly are the syptomps, I don't understand what you mean by
"mt76x0 devices don't work properly in monitor mode" ?

> > I guess it depends on eeprom values. Could you please enable debug
> > messages a paste
> > syslog output?
> 
> I don't see a mediatek specific debug near the driver selection in
> menuconfig, what debug messages do you want me to enable and how?

You need to uncomment this line:

# ccflags-y := -DDEBUG

in drivers/net/wireless/mediatek/mt76/mt76x0/Makefile

Thanks
Stanislaw

  reply	other threads:[~2018-09-06 14:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 17:33 mt76x0 bug report Sid Hayn
2018-09-04 21:04 ` Lorenzo Bianconi
2018-09-05 20:52   ` Sid Hayn
2018-09-06  9:32     ` Stanislaw Gruszka [this message]
2018-09-06 15:39       ` Sid Hayn
2018-09-06 15:42         ` Lorenzo Bianconi
2018-09-06 15:53           ` Sid Hayn
2018-09-07  8:24             ` Lorenzo Bianconi
2018-09-07 19:55               ` Sid Hayn
2018-09-14 15:32                 ` Sid Hayn
2018-09-14 15:42                   ` Davide Caratti
2018-09-14 15:47                   ` Lorenzo Bianconi
2018-09-14 15:51                     ` Sid Hayn
2018-09-18  3:18                       ` Sid Hayn
2018-09-18 11:56                         ` Stanislaw Gruszka
2018-09-18 17:36                           ` Sid Hayn
2018-09-19 11:15                             ` Stanislaw Gruszka
2018-09-19 18:01                               ` Sid Hayn
2018-09-06 16:51       ` Sid Hayn
2018-09-06 17:13         ` Lorenzo Bianconi
2018-09-06 22:37           ` Lorenzo Bianconi

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=20180906093213.GB16539@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sidhayn@gmail.com \
    /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).