From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Vasa Shpatrov <vasily.shpatrov@queensu.ca>
Cc: "lorenzo.bianconi83@gmail.com" <lorenzo.bianconi83@gmail.com>,
"nbd@nbd.name" <nbd@nbd.name>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Linux bug report: mt76x0 driver for USB WiFi adapter does not support channel > 140 on 5Ghz band
Date: Fri, 29 Nov 2019 12:19:35 +0200 [thread overview]
Message-ID: <20191129101935.GC32696@localhost.localdomain> (raw)
In-Reply-To: <YQXPR0101MB146201584E8F6325CEC4531999470@YQXPR0101MB1462.CANPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 5166 bytes --]
[...]
> [3.] Keywords (i.e., modules, networking, kernel):
> networking, wifi, driver, USB
>
> [4.] Kernel information
> [4.1.] Kernel version (from /proc/version):
> Linux version 4.19.66-Re4son-v8+ (root@kali-pi-dev-v8) (gcc version 8.2.0 (Debian 8.2.0-12)) #1 SMP PREEMPT Sun Aug 18 12:14:35 UTC 2019
Hi Vasa,
IIUC you are running a pretty old version of the driver. According to the rpi
kernel tree, mt76x0u enables radio frequencies up to 5700MHz
https://github.com/raspberrypi/linux/blob/rpi-4.19.y/drivers/net/wireless/mediatek/mt76/mt76x0/init.c#L565
I guess you need to update the driver to latest stable one.
Regards,
Lorenzo
>
> [8.] Environment
> [8.1.] Software (add the output of the ver_linux script here)
> Linux kali 4.19.66-Re4son-v8+ #1 SMP PREEMPT Sun Aug 18 12:14:35 UTC 2019 aarch64 GNU/Linux
>
> GNU Make 4.2.1
> Binutils 2.32.51.20190727
> Util-linux 2.34
> Mount 2.34
> Module-init-tools 26
> E2fsprogs 1.45.3
> PPP 2.4.7
> Linux C Library 2.29
> Dynamic linker (ldd) 2.29
> Linux C++ Library 6.0.27
> Procps 3.3.15
> Net-tools 2.10
> Kbd 2.0.4
> Console-tools 2.0.4
> Sh-utils 8.30
> Udev 241
> Wireless-tools 30
> Modules Loaded arc4 bcm2835_codec bcm2835_mmal_vchiq bcm2835_v4l2 bluetooth
> brcmfmac brcmutil btbcm cfg80211 ecdh_generic evdev gpio_keys hci_uart ip_tables
> ipv6 mac80211 media mt76 mt76x0 rfkill sdhci_iproc serdev snd snd_bcm2835
> snd_pcm snd_timer uio uio_pdrv_genirq v4l2_common v4l2_mem2mem vc_sm_cma vchiq
> videobuf2_common videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_v
> malloc videodev x_tables
>
> [8.2.] Processor information (from /proc/cpuinfo):
> processor : 0
> BogoMIPS : 38.40
> Features : fp asimd evtstrm crc32 cpuid
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd03
> CPU revision : 4
>
> processor : 1
> BogoMIPS : 38.40
> Features : fp asimd evtstrm crc32 cpuid
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd03
> CPU revision : 4
>
> processor : 2
> BogoMIPS : 38.40
> Features : fp asimd evtstrm crc32 cpuid
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd03
> CPU revision : 4
>
> processor : 3
> BogoMIPS : 38.40
> Features : fp asimd evtstrm crc32 cpuid
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd03
> CPU revision : 4
>
> [8.3.] Module information (from /proc/modules):
> mt76x0 122880 0 - Live 0xffffffa3be4ab000
> mt76 49152 1 mt76x0, Live 0xffffffa3be3bc000
> mac80211 929792 2 mt76x0,mt76, Live 0xffffffa3be1b1000
> cfg80211 757760 4 mt76x0,mt76,brcmfmac,mac80211, Live 0xffffffa3bdda1000
> rfkill 32768 6 bluetooth,cfg80211, Live 0xffffffa3bdd69000
>
> [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> 00000000-3b3fffff : System RAM
> 00000000-00000fff : reserved
> 00080000-00a8ffff : Kernel code
> 00a90000-00d4ffff : reserved
> 00d50000-00f28fff : Kernel data
> 2eff9000-2effffff : reserved
> 39800000-399fffff : reserved
> 39b52000-3a9fffff : reserved
> 3aa70000-3ab70fff : reserved
> 3ab71000-3abd0fff : reserved
> 3abd3000-3abd6fff : reserved
> 3abd7000-3abfefff : reserved
> 3abff000-3abfffff : reserved
> 3ac00000-3b3fffff : reserved
> 3f006000-3f006fff : dwc_otg
> 3f007000-3f007eff : dma@7e007000
> 3f00a000-3f00a023 : watchdog@7e100000
> 3f00b840-3f00b87b : mailbox@7e00b840
> 3f00b880-3f00b8bf : mailbox@7e00b880
> 3f100000-3f100113 : watchdog@7e100000
> 3f101000-3f102fff : cprman@7e101000
> 3f104000-3f10400f : rng@7e104000
> 3f200000-3f2000b3 : gpio@7e200000
> 3f201000-3f2011ff : serial@7e201000
> 3f201000-3f2011ff : serial@7e201000
> 3f202000-3f2020ff : mmc@7e202000
> 3f212000-3f212007 : thermal@7e212000
> 3f215000-3f215007 : aux@7e215000
> 3f300000-3f3000ff : mmcnr@7e300000
> 3f980000-3f98ffff : dwc_otg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2019-11-29 10:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <YQXPR0101MB146201584E8F6325CEC4531999470@YQXPR0101MB1462.CANPRD01.PROD.OUTLOOK.COM>]
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=20191129101935.GC32696@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=nbd@nbd.name \
--cc=vasily.shpatrov@queensu.ca \
/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).