From: Hans de Goede <email@example.com> To: Arend van Spriel <firstname.lastname@example.org> Cc: "open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER" <email@example.com>, linux-wireless <firstname.lastname@example.org> Subject: Re: brcmfmac4356-pci device not seeing 2.4Ghz channel 12 and 13 Date: Wed, 30 Aug 2017 15:39:07 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi, On 06-07-17 21:43, Arend van Spriel wrote: > On 06-07-17 21:23, Hans de Goede wrote: >> Hi, >> >> On 28-06-17 14:35, Arend Van Spriel wrote: >>> Op 28 jun. 2017 12:07 schreef "Hans de Goede" <email@example.com >>> <mailto:firstname.lastname@example.org>>: >>> > >>> > Hi, >>> > >>> > I noticed today that my GPD Win (x86 clamshell mini laptop) >>> > which uses a brcmfmac4356-pci wifi does not see an APs which >>> > is using channel 13. >>> > >>> > I've tried updating brcmfmac4356-pci.txt changing "ccode=US" >>> > to "ccode=EU" and then rebooted, but that does not help. >>> >>> Some variables may be stored on the device. However, EU may not be >>> valid. Could you try NL instead? >> >> Yes changing it to NL fixes this. This is still a bit problematic >> though. Because what are we going to put in the nvram file we want >> to put in linux-firmware ? > > Agree. I am surprised (not pleasantly) that these devices are not > properly programmed and thus need nvram for the country code. > >>> > I believe that the Linux wifi stack is supposed to automatically >>> > figure out the country settings based on AP provided info ? >>> >>> That depends. The device runs its own wifi stack which should have >>> 802.11d support for what you describe. >>> >>> > But that does not seem to be working here ? Any hints on howto >>> > debug this further would be appreciated. >>> >>> You could try doing "country" iovar get somewhere in >>> brcmf_bus_started() to check country setting in firmware. >> >> Let me know if you still want me to do this given that ccode=NL fixes this. > > Well. Could you try it with ccode commented out in nvram file. That does not work, so then I looked at some of my other brcm nvram files which use: ccode=XY ccode=0 ccode=ALL I tried both 0 and ALL, which both don't work with the brcmfmac4356-pci controller / firmware. Then I decided to do a duckduckgo search for this problem and found: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211 Which says: "This generation of chips contain additional regulatory support independent of the driver. The devices use a single worldwide regulatory domain, with channels 12-14 (2.4 GHz band) and channels 52-64 and 100-140 (5 GHz band) restricted to passive operation. Transmission on those channels is suppressed until appropriate other traffic is observed on those channels. Within the driver, we use the ficticious country code “X2” to represent this worldwide regulatory domain." So I tried: ccode=X2 And that works :) So case closed. I also tried another device which has a brcmfmac43430a0 and the stock nvram from the OS image from the manufacturer uses: ccode=ALL And again no joy for accessing an AP on channel 13, switching to: ccode=X2 Fixed things there too. Regards, Hans
prev parent reply other threads:[~2017-08-30 13:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-06-28 10:07 Hans de Goede [not found] ` <CAF7Mx6pPmsZektpdEVphqUzBtbGGiMh7cedexTDsGOC8myFemail@example.com> [not found] ` <CAF7Mx6rUwR9TLDZuQ0pDkj0xG_j+d31w7LKBuv9q9A2V0gN7mw@mail.gmail.com> [not found] ` <CAF7Mx6oVrjxYApXbO2dV8JGY7QrYy+uF6-QH=M67RW_wBM7GGA@mail.gmail.com> 2017-07-06 19:23 ` Hans de Goede 2017-07-06 19:43 ` Arend van Spriel 2017-08-30 13:39 ` Hans de Goede [this message]
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: brcmfmac4356-pci device not seeing 2.4Ghz channel 12 and 13' \ /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
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).