On Tue, Sep 18, 2018 at 01:36:51PM -0400, Sid Hayn wrote:

On Tue, Sep 18, 2018 at 7:56 AM Stanislaw Gruszka [off-list ref] wrote:

quoted

On Mon, Sep 17, 2018 at 11:18:57PM -0400, Sid Hayn wrote:

quoted

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 ?

quoted

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