At this point, we've had all the necessary firmware blobs for numerous
releases and I'm reasonably convinced that the remaining AC wifi issues
are largely related to incorrect regulatory domain, because we don't
provide a friendly way of setting this on desktop (see LP: #1951586 for
more on this).
There were some missing fw blobs added a while ago and I think the
problem is solved now. Can this ticket be closed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
Status: Won't Fix => New
** Changed in: linux-raspi2-5.3 (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are
https://bugs.launchpad.net/netplan/+bug/1951586
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on our raspi images
Status in
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1862760/comments/29
Was that on desktop or server?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Somewhat related: LP: #1908951
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on our raspi images
Status in linux-firmware
Hi all, I found that adding the correct region to the /etc/default/crda
file resolved my 5GHZ woes on the raspi4b ubuntu 20.10. After a reboot
it finally connected to my 5GHZ network. Just putting this out there if
it helps anyone.
--
You received this bug notification because you are a member
What kernel and firmware versions? 20.04.1 is quite old. Have you tried
updating?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection
I just tried to set up Ubuntu 20.04.1 LTS Focal Fossa on a Raspberry Pi
3 B+ and ran into this bug. I used the ARM 64-bit image from this page:
https://cdimage.ubuntu.com/releases/20.04/release/
I was able to use my 2.4Ghz SSID just fine. Tried switching back to the
5Ghz and failed. Went back to
** Tags added: fr-374
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on our raspi images
Status in linux-firmware package in
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: netplan.io (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux-firmware (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux-raspi2-5.3 (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
Maybe related? https://github.com/raspberrypi/linux/issues/3378
** Bug watch added: github.com/raspberrypi/linux/issues #3378
https://github.com/raspberrypi/linux/issues/3378
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Think the regulatory domain is not being set anywhere as
/etc/default/crda has REGDOMAIN= and sudo cat /run/netplan/wpa-
wlan0.conf has
ctrl_interface=/run/wpa_supplicant
network={
ssid="SHEW-DB9990"
key_mgmt=WPA-PSK
psk="nope"
}
Might explain 'ieee80211 phy0: brcmf_escan_timeout: timer
I'm not able to reproduce this issue but I can't restrict my router to
use 802.11ac only, it also uses 802.11n in the 5GHz spectrum. Is there a
way to check which standard is in use for a connection or is it possible
to restrict which standard to use on the client side?
Brian, are you still
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-raspi (Ubuntu Bionic)
** No longer affects: linux-raspi (Ubuntu Eoan)
** No longer affects: linux-raspi2-5.3 (Ubuntu Focal)
** No longer affects: linux-raspi2-5.3 (Ubuntu)
** Also
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on
Looks like the ssid_scan= is being addressed upstream
https://github.com/CanonicalLtd/netplan/pull/132
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable
Think this might relate to how netplan constructs its
/run/netplan/wpa-.conf file(1). In raspbian(2) users set the
country= line in its wpa_supplicant.conf file before starting the
service. Perhaps netplan's 'wifis' section could grow the ability to add
the country= and (2)ssid_scan= lines based
I went ahead and ran through the Raspbian setup again and this time I
said I was in the UK. After that and rebooting I ran 'iw reg get' and
the results showed "country GB: DFS-ETSI".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Based on some quick googling, I think there's some localization set up
on raspbian that must also cause it to set the regulatory domain.
https://www.raspberrypi.org/documentation/configuration/wireless/desktop.md
--
You received this bug notification because you are a member of Kernel
Packages,
Just to be clear this is what iw reg get shows on Rasbian:
pi@raspberrypi:~$ iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @
Generally speaking we don't know what country a device is operating in,
so we default to the world domain which should be safe throughout the
world. The AP may send a hint to the client as to what regulatory domain
to use, but many APs do not do this.
Also note that on many desktop systems now
On Raspbian the output of "iw reg get" matches what I saw after setting
"iw reg set US".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac
Here's the "iw reg get" output from a 20.04 laptop.
[ 10:58AM 10014 ] [ bdmurray@speedy:~ ]
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A),
I managed to get my RPi4 to connect to the 802.11ac access point by
setting the regulatory domain to US - "iw reg set US". Here's a before
and after output of "iw reg get".
ubuntu@ubuntu:~$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @
** Tags added: id-5e42d5f1bfa3f21352dd8e14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on our raspi images
Status in
** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac
This bug was fixed in the package linux-firmware-raspi2 -
1.20200212-0ubuntu1
---
linux-firmware-raspi2 (1.20200212-0ubuntu1) focal; urgency=medium
* New upstream release, 1.20200212
* Updated wifi firmware to support 802.11ac wifi (LP: #1862760)
* Added diversions to override
I decided to test this with the armhf version of 20.04 given that
Raspbian is armhf only and the results were the same.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
I've tested this today on both 20.04 (with linux-firmware-raspi2
1.20200212-0ubuntu1~ppa1) and 19.10.1 (with linux-firmware-raspi2
1.20200212-0ubuntu1~19.10.1~ppa1) and neither of them were able to
connect to the 802.11ac access point.
I see the same journal entries mentioned previously:
Mar 10
> Perhaps we should test this on 19.10.1 so we aren't adding the
additional variable of running Focal.
I've added an Eoan version of the package to the same PPA
(https://launchpad.net/~waveform/+archive/ubuntu/firmware/+packages).
--
You received this bug notification because you are a member
I flashed the focal preinstalled image for arm64 and put in an RPi4. I
then did a dist-upgrade, setup a netplan config, rebooted (an
undocumented step?) and I am not able to connect to the access point. I
confirmed that the right firmware is being used:
[9.005150] brcmfmac: F1 signature read
A package with the latest firmware is available from the following PPA:
https://launchpad.net/~waveform/+archive/ubuntu/firmware/+packages
I've now tested this booting and operating wifi on a 3B+ and a 4B
against "classic" 2.4GHz wifi, and 5GHz wifi but only 802.11n (as that's
all I've got
The only other Pi that I currently have is a 3B which does not have
802.11ac capabilities.
https://www.raspberrypi.org/documentation/faqs/#hardware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
@juergh given the Pi 3A+, 3B+, and 4B share the same wifi chipset (but
not the 3B) I'd expect similar behaviour across those three models, if
indeed the firmware is the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware
Is this a problem with the Pi 4 only or across the whole fleet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1862760
Title:
Unreliable 802.11ac connection on our raspi images
I'm actually getting good results using the updated brcmfmac43455
firmware files which Raspbian is using. To use them I first removed
'/lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi*' then put the
brcmfmac43455-sdio* files in the same directory and rebooted.
ubuntu@ubuntu:~$ cat
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-firmware-raspi2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-raspi2-5.3 (Ubuntu Focal)
Importance: High
Status: New
--
You received
41 matches
Mail list logo
