Thanks for sharing details.
Once finally qualified, shall we expect it will be released under Foundation's repo within firmware-brcm80211 package as in here?
Thanks for confirmation.
Thanks for sharing details.
It seems like Foundation's firmware-brcm80211 package was where it usually ended-up so far...
Jut spoken with the distro guys, that repo you linked is deprecated and is going to be removed (it's out of date, and no longer needed). The firmware will go in the apt repo, I suspect there will be a specific URL that points to it.macmpi wrote: ↑Fri Jan 26, 2018 10:28 amIt seems like Foundation's firmware-brcm80211 package was where it usually ended-up so far...
Would definitely be helpful to get confirmation which specific package will be current, so that custom disto maintainers can plan & adjust accordingly (sometimes firmware packages contents are hard to track across repos...).
Thanks.
Code: Select all
uname -a
Linux berck 4.9.63-v7+ #1052 SMP Sat Nov 18 21:50:59 GMT 2017 armv7l GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
A reboot fixed PulseAudio. So nothing to do with the firmware.
Hmm, perhaps another corner case that is still present. Any errors in the logs?Beachdog wrote: ↑Wed Feb 07, 2018 8:27 pmI've been running the new firmware for about 11 days now but sadly it has NOT fixed my WIFI dropouts.
There doesn't seem to be any pattern, but on average it still fails about once a day.
I'm sure I've copied the new firmware to the right place, and nothing else seem to have been adversely affected.
Code: Select all
sudo apt-get update
sudo apt-get upgrade
No, that's just the result of how debian packaging works. There's a source package which produced a number of binary (.deb) packages, which all inherit the same version number. So any change in the source package will result in all of the binary packages being updated, even if they're otherwise identical to the previous version.
Couldn't find anything of interest in the logs, so I've done an apt-get update etc and will see if that improves things.Hmm, perhaps another corner case that is still present. Any errors in the logs?
I've done some further troubleshooting on the issues encountered with this latest firmware laballed as "firmware-brcm80211 (1:20161130-3+rpt1)" that you can read under viewtopic.php?f=63&t=204882&p=1277124#p1277124.ShiftPlusOne wrote: ↑Fri Feb 16, 2018 5:16 pmInteresting. It would be the firmware-brcm80211 package.
Maybe leave a comment here:
viewtopic.php?t=203508