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, dcaratti@redhat.com
Subject: Re: mt76x0 bug report
Date: Wed, 19 Sep 2018 13:15:26 +0200 [thread overview]
Message-ID: <20180919111525.GD22689@redhat.com> (raw)
In-Reply-To: <CAM0KTbDq7v6phbr72LXEoYzu9iQ9L-MN85Zzn5Oz9kGsuVCV_Q@mail.gmail.com>
On Tue, Sep 18, 2018 at 01:36:51PM -0400, Sid Hayn wrote:
> On Tue, Sep 18, 2018 at 7:56 AM Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> >
> > On Mon, Sep 17, 2018 at 11:18:57PM -0400, Sid Hayn wrote:
> > > Sorry to bump the one thing that we both agreed was low priority but....
> > >
> > > So was testing all of my dongles that use the driver you are working
> > > on, and running them through my connect scripts. I moved the AP to
> > > maybe <5ft from the clients and something wierd happened. The t1u
> > > tried to connect to one of the 2.4GHz only networks. It failed, but
> > > it actually got enough scan data back to attempt authentication with a
> > > valid 2.4GHz only bssid. Which means in short, that the eeprom isn't
> > > lying and your parsing of it is correct. Something obviously makes
> > > this a 5GHz only device, as the connection failed and most of the time
> > > nothing at all is seen on 2.4GHz, but clearly it's some filter or
> > > antenna or some other mechanism which makes it 5GHz only. So probably
> > > hardware lying to you is now even lower on your list since this safely
> > > rules out the driver parsing the eeprom incorrectly.
> >
> > First of all would be good to check if problem is not already solved,
> > latest version of the driver can be found here:
> > https://github.com/nbd168/wireless
>
> Booting that kernel gets me instant to near instant kernel panics, so
> I am unable to test much.
This has to be fixed as well, can you provide kernel messages ?
> > Second, is there vendor driver available for this particular device?
> > Perhaps there are some tweeks needed that are not provided by generic
> > driver.
>
> No clue, haven't even tried to look. This hardware was all sitting on
> a shelf till it looked like a real driver was being merged into the
> kernel.... so um, thanks :-)
Why do you think device is 5GHz only? This is very unusual. I know
only single-band 2.4GHz or dual-band 2.4GHz & 5GHz devices.
Regards
Stanislaw
next prev parent reply other threads:[~2018-09-19 16:52 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
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 [this message]
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=20180919111525.GD22689@redhat.com \
--to=sgruszka@redhat.com \
--cc=dcaratti@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).