All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathy Vanhoef <vanhoefm@gmail.com>
To: James <bjlockie@lockie.ca>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Alfa AWUS036ACM (Mediatek MT7612U) AP problem
Date: Sun, 28 Jun 2020 22:24:40 +0400	[thread overview]
Message-ID: <CAFXAJYwgRPAbY4i8XHNGzcyJg-11BwOSdDS6098eh_CEzxeEUQ@mail.gmail.com> (raw)
In-Reply-To: <ba64416e-d34b-9bdd-d482-6ea722e3d6b9@lockie.ca>

I have similar issues with an AWUS036ACM when connected to a USB3.0
port. When connected to a USB2.0 port it seems to work fine.

In particular, on both kernel 5.5.0 and 5.6.13 on a USB3.0 port when
running an AP I get the error "mt76x2u: error: mt76x02u_mcu_wait_resp
failed with -108". On the same kernels but using a USB2.0 port the AP
seems to work properly.

On Fri, Jun 26, 2020 at 11:33 PM James <bjlockie@lockie.ca> wrote:
>
> I have an Alfa AWUS036ACM (Mediatek MT7612U).
> My AP keeps dieing.
> The error:
> mt76x2u: error: mt76x02u_mcu_wait_resp failed with -110
> seems to be common.
>
> I use it with a build of a OpenWrt on a Raspberry Pi 4 (Broadcom BCM2711
> SoC, ARM Cortex-A72 processor (64bit)).
> Linux OpenWrt 5.4.48 #0 SMP Thu Jun 25 00:36:19 2020 aarch64 GNU/Linux
> Loading modules backported from Linux version v5.7-rc3-0-g6a8b55ed4056
>
> # lsmod | grep mt76
> cfg80211              339968  5
> mt76x02_usb,mt76x02_lib,mt7603e,mt76,mac80211
> mac80211              589824  7
> mt76x2u,mt76x2e,mt76x02_usb,mt76x02_lib,mt7603e,mt76_usb,mt76
> mt76                   45056  7
> mt76x2u,mt76x2e,mt76x2_common,mt76x02_usb,mt76x02_lib,mt7603e,mt76_usb
> mt76_usb               24576  2 mt76x2u,mt76x02_usb
> mt7603e                53248  0
> mt76x02_lib            61440  4 mt76x2u,mt76x2e,mt76x2_common,mt76x02_usb
> mt76x02_usb            20480  1 mt76x2u
> mt76x2_common          20480  2 mt76x2u,mt76x2e
> mt76x2e                20480  0
> mt76x2u                20480  0
>
> I bought a powered USB3 hub and removed a USB3 cable in case that is
> related but the problem is still there.
>
> I've been documenting my problems:
> https://github.com/openwrt/mt76/issues/405#
> Are any of the tracebacks useful?
>
> I found this:
> https://github.com/openwrt/mt76/issues/403
> >
> >
> >       *LorenzoBianconi *commented on May 10
> >
> > @petrkalosthis conditions is used to reset the device in case of
> > necessary (it is in the vendor sdk). You can try to comment it out and
> > see what happen
> >
> I downloaded
> https://d86o2zu8ugzlg.cloudfront.net/mediatek-craft/drivers/MT7612U_DPO_LinuxSTA_3.0.0.1_20140718.tar.bz2
> and there is no "mcu_wait_resp".
>
> I also found this:
> https://github.com/raspberrypi/linux/issues/3014
>
>
> What 80211.ac USB adapter has the best (most open and compatible) now
> (or likely) linux kernel support?
>

  reply	other threads:[~2020-06-28 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 19:32 Alfa AWUS036ACM (Mediatek MT7612U) AP problem James
2020-06-28 18:24 ` Mathy Vanhoef [this message]
2020-06-29  2:08   ` James
2020-06-29  9:19     ` Lorenzo Bianconi
2020-06-29 16:43       ` James
2020-07-01 18:25       ` disable_usb_sg=1 James

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=CAFXAJYwgRPAbY4i8XHNGzcyJg-11BwOSdDS6098eh_CEzxeEUQ@mail.gmail.com \
    --to=vanhoefm@gmail.com \
    --cc=bjlockie@lockie.ca \
    --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 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.