From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [mt76x2e] minipcie card is not working
Date: Tue, 5 Feb 2019 16:10:23 +0100 [thread overview]
Message-ID: <20190205151022.GE7510@redhat.com> (raw)
In-Reply-To: <CAKxU2N9choD2mdQd+Qwf5047VNWdwKOPB_YRXvw4i6BtLn6vxQ@mail.gmail.com>
On Mon, Jan 28, 2019 at 12:14:49PM -0800, Rosen Penev wrote:
> I have a full height production sample mt7612e card that does not work
> in either Access Point or Client mode. Monitor mode does not work
> either (no packets received/transmitted).
>
> dmesg shows everything to be fine:
>
> [ 5.801993] mt76x2e 0000:2b:00.0: enabling device (0000 -> 0002)
> [ 5.802122] mt76x2e 0000:2b:00.0: ASIC revision: 76120044
> [ 6.466527] mt76x2e 0000:2b:00.0: ROM patch build: 20141115060606a
> [ 6.468999] mt76x2e 0000:2b:00.0: Firmware Version: 0.0.00
> [ 6.469000] mt76x2e 0000:2b:00.0: Build: 1
> [ 6.469001] mt76x2e 0000:2b:00.0: Build Time: 201507311614____
> [ 6.496042] mt76x2e 0000:2b:00.0: Firmware running!
> [ 6.497999] mt76x2e 0000:2b:00.0 wlp43s0: renamed from wlan0
>
> This is on 5.0-rc3.
>
> Tested with a desktop running Ubuntu 18.04 (custom kernel) and an
> mvebu device (Turris Omnia) running OpenWrt on kernel 4.14.
I have access to similar device and it does not work for me.
You can check latest mt76 driver https://github.com/openwrt/mt76 ,
some users reported success with mt76x2e problems, but I can
not confirm that with my device.
Do you have Mediatek driver for it (i.e. received driver on associated
CD with the device) or know about such driver. If so, does it work?
Thanks
Stanislaw
next prev parent reply other threads:[~2019-02-05 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 20:14 [mt76x2e] minipcie card is not working Rosen Penev
2019-02-05 15:10 ` Stanislaw Gruszka [this message]
2019-02-05 21:06 ` Rosen Penev
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=20190205151022.GE7510@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rosenp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.