idontknowit
Posts: 1
Joined: Wed Feb 07, 2018 9:09 pm

upgrade Feb 2018 kills all my Raspberrypi'S

Thu Feb 08, 2018 12:10 am

well, I have lost three 2 version 3 and one version 1 to the lastest command
sudo apt-get upgrade... Had to re-image and yes, I was stupid enough to try again. below are the packages

Take my advice and DO NOT Upgrade your RPI's for the moment

$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
base-files bluez-firmware dbus firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek iproute2 libcurl3-gnutls libdbus-1-3 libdns-export162 libicu57
libisc-export160 libisccc140 libpython2.7-minimal libpython2.7-stdlib libsqlite3-0 libssl1.0.2 libxml2 openssh-client openssh-server openssh-sftp-server pi-bluetooth python2.7 python2.7-minimal
raspberrypi-sys-mods raspi-config rsync sensible-utils ssh tzdata
32 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.2 MB of archives.
After this operation, 97.3 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian stretch/main armhf bluez-firmware all 1.2-3+rpt2 [89.7 kB]
Get:3 http://archive.raspberrypi.org/debian stretch/main armhf firmware-atheros all 1:20161130-3+rpt1 [3,132 kB]
Get:2 http://mirror.de.leaseweb.net/raspbian/raspbian stretch/main armhf base-files armhf 9.9+rpi1+deb9u3 [67.4 kB]
Get:11 http://archive.raspberrypi.org/debian stretch/main armhf firmware-brcm80211 all 1:20161130-3+rpt1 [3,613 kB]
Get:17 http://mirror.de.leaseweb.net/raspbian/raspbian stretch/main armhf iproute2 armhf 4.9.0-1+deb9u1 [559 kB]
Get:20 http://archive.raspberrypi.org/debian stretch/main armhf firmware-libertas all 1:20161130-3+rpt1 [2,950 kB]
Get:18 http://mirror.de.leaseweb.net/raspbian/raspbian stretch/main armhf dbus armhf 1.10.24-0+deb9u1 [190 kB]
Get:23 http://mirror.de.leaseweb.net/raspbian/raspbian stretch/main armhf libcurl3-gnutls armhf 7.52.1-5+deb9u4 [259 kB]
Get:25 http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian stretch/main armhf libdns-export162 armhf 1:9.10.3.dfsg.P4-12.3+deb9u4 [767 kB]
Get:28 http://archive.raspberrypi.org/debian stretch/main armhf firmware-misc-nonfree all 1:20161130-3+rpt1 [2,321 kB]
Get:29 http://archive.raspberrypi.org/debian stretch/main armhf firmware-realtek all 1:20161130-3+rpt1 [342 kB]
Get:6 https://ftp.heikorichter.name/raspbian/raspbian stretch/main armhf libpython2.7-stdlib armhf 2.7.13-2+deb9u2 [1,830 kB]
Get:30 http://archive.raspberrypi.org/debian stretch/main armhf raspberrypi-sys-mods armhf 20180103 [8,932 B]
Get:31 http://archive.raspberrypi.org/debian stretch/main armhf pi-bluetooth all 0.1.7 [3,782 B]
Get:32 http://archive.raspberrypi.org/debian stretch/main armhf raspi-config all 20171201 [19.9 kB]
Get:4 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf python2.7 armhf 2.7.13-2+deb9u2 [285 kB]
Get:5 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libsqlite3-0 armhf 3.16.2-5+deb9u1 [493 kB]
Get:7 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf python2.7-minimal armhf 2.7.13-2+deb9u2 [1,178 kB]
Get:8 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libpython2.7-minimal armhf 2.7.13-2+deb9u2 [389 kB]
Get:9 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf openssh-sftp-server armhf 1:7.4p1-10+deb9u2 [32.9 kB]
Get:10 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libssl1.0.2 armhf 1.0.2l-2+deb9u2 [893 kB]
Get:12 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf openssh-server armhf 1:7.4p1-10+deb9u2 [301 kB]
Get:13 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf openssh-client armhf 1:7.4p1-10+deb9u2 [697 kB]
Get:14 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf ssh all 1:7.4p1-10+deb9u2 [189 kB]
Get:15 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf sensible-utils all 0.0.9+deb9u1 [10.8 kB]
Get:16 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf tzdata all 2017c-0+deb9u1 [262 kB]
Get:19 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libdbus-1-3 armhf 1.10.24-0+deb9u1 [173 kB]
Get:21 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libicu57 armhf 57.1-6+deb9u1 [7,426 kB]
Get:22 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libxml2 armhf 2.9.4+dfsg1-2.2+deb9u2 [806 kB]
Get:24 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libisc-export160 armhf 1:9.10.3.dfsg.P4-12.3+deb9u4 [314 kB]
Get:26 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf libisccc140 armhf 1:9.10.3.dfsg.P4-12.3+deb9u4 [196 kB]
Get:27 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian stretch/main armhf rsync armhf 3.1.2-1+deb9u1 [356 kB]
Fetched 30.2 MB in 16s (1,832 kB/s)
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 39907 files and directories currently installed.)
Preparing to unpack .../base-files_9.9+rpi1+deb9u3_armhf.deb ...
Unpacking base-files (9.9+rpi1+deb9u3) over (9.9+rpi1+deb9u1) ...
Setting up base-files (9.9+rpi1+deb9u3) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 39907 files and directories currently installed.)
Preparing to unpack .../python2.7_2.7.13-2+deb9u2_armhf.deb ...
Unpacking python2.7 (2.7.13-2+deb9u2) over (2.7.13-2) ...
Preparing to unpack .../libsqlite3-0_3.16.2-5+deb9u1_armhf.deb ...
Unpacking libsqlite3-0:armhf (3.16.2-5+deb9u1) over (3.16.2-5) ...
Setting up libsqlite3-0:armhf (3.16.2-5+deb9u1) ...
(Reading database ... 39907 files and directories currently installed.)
Preparing to unpack .../0-libpython2.7-stdlib_2.7.13-2+deb9u2_armhf.deb ...
Unpacking libpython2.7-stdlib:armhf (2.7.13-2+deb9u2) over (2.7.13-2) ...
Preparing to unpack .../1-python2.7-minimal_2.7.13-2+deb9u2_armhf.deb ...
Unpacking python2.7-minimal (2.7.13-2+deb9u2) over (2.7.13-2) ...
Preparing to unpack .../2-libpython2.7-minimal_2.7.13-2+deb9u2_armhf.deb ...
Unpacking libpython2.7-minimal:armhf (2.7.13-2+deb9u2) over (2.7.13-2) ...
Preparing to unpack .../3-openssh-sftp-server_1%3a7.4p1-10+deb9u2_armhf.deb ...
Unpacking openssh-sftp-server (1:7.4p1-10+deb9u2) over (1:7.4p1-10+deb9u1) ...
Preparing to unpack .../4-libssl1.0.2_1.0.2l-2+deb9u2_armhf.deb ...
Unpacking libssl1.0.2:armhf (1.0.2l-2+deb9u2) over (1.0.2l-2+deb9u1) ...
Preparing to unpack .../5-openssh-server_1%3a7.4p1-10+deb9u2_armhf.deb ...
Unpacking openssh-server (1:7.4p1-10+deb9u2) over (1:7.4p1-10+deb9u1) ...
Preparing to unpack .../6-openssh-client_1%3a7.4p1-10+deb9u2_armhf.deb ...
Unpacking openssh-client (1:7.4p1-10+deb9u2) over (1:7.4p1-10+deb9u1) ...
Preparing to unpack .../7-ssh_1%3a7.4p1-10+deb9u2_all.deb ...
Unpacking ssh (1:7.4p1-10+deb9u2) over (1:7.4p1-10+deb9u1) ...
Preparing to unpack .../8-sensible-utils_0.0.9+deb9u1_all.deb ...
Unpacking sensible-utils (0.0.9+deb9u1) over (0.0.9) ...
Setting up sensible-utils (0.0.9+deb9u1) ...
(Reading database ... 39907 files and directories currently installed.)
Preparing to unpack .../00-tzdata_2017c-0+deb9u1_all.deb ...
Unpacking tzdata (2017c-0+deb9u1) over (2017b-1) ...
Preparing to unpack .../01-iproute2_4.9.0-1+deb9u1_armhf.deb ...
Unpacking iproute2 (4.9.0-1+deb9u1) over (4.9.0-1) ...
Preparing to unpack .../02-dbus_1.10.24-0+deb9u1_armhf.deb ...
Unpacking dbus (1.10.24-0+deb9u1) over (1.10.22-0+deb9u1) ...
Preparing to unpack .../03-libdbus-1-3_1.10.24-0+deb9u1_armhf.deb ...
Unpacking libdbus-1-3:armhf (1.10.24-0+deb9u1) over (1.10.22-0+deb9u1) ...
Preparing to unpack .../04-libicu57_57.1-6+deb9u1_armhf.deb ...
Unpacking libicu57:armhf (57.1-6+deb9u1) over (57.1-6) ...
Preparing to unpack .../05-libxml2_2.9.4+dfsg1-2.2+deb9u2_armhf.deb ...
Unpacking libxml2:armhf (2.9.4+dfsg1-2.2+deb9u2) over (2.9.4+dfsg1-2.2+deb9u1) ...
Preparing to unpack .../06-bluez-firmware_1.2-3+rpt2_all.deb ...
Unpacking bluez-firmware (1.2-3+rpt2) over (1.2-3+rpt1) ...
Preparing to unpack .../07-firmware-atheros_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-atheros (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Preparing to unpack .../08-firmware-brcm80211_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-brcm80211 (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Preparing to unpack .../09-firmware-libertas_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-libertas (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Preparing to unpack .../10-firmware-misc-nonfree_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-misc-nonfree (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Preparing to unpack .../11-firmware-realtek_1%3a20161130-3+rpt1_all.deb ...
Unpacking firmware-realtek (1:20161130-3+rpt1) over (1:20161130-3+rpi2) ...
Preparing to unpack .../12-libcurl3-gnutls_7.52.1-5+deb9u4_armhf.deb ...
Unpacking libcurl3-gnutls:armhf (7.52.1-5+deb9u4) over (7.52.1-5+deb9u2) ...
Preparing to unpack .../13-libisc-export160_1%3a9.10.3.dfsg.P4-12.3+deb9u4_armhf.deb ...
Unpacking libisc-export160 (1:9.10.3.dfsg.P4-12.3+deb9u4) over (1:9.10.3.dfsg.P4-12.3+deb9u3) ...
Preparing to unpack .../14-libdns-export162_1%3a9.10.3.dfsg.P4-12.3+deb9u4_armhf.deb ...
Unpacking libdns-export162 (1:9.10.3.dfsg.P4-12.3+deb9u4) over (1:9.10.3.dfsg.P4-12.3+deb9u3) ...
Preparing to unpack .../15-libisccc140_1%3a9.10.3.dfsg.P4-12.3+deb9u4_armhf.deb ...
Unpacking libisccc140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u4) over (1:9.10.3.dfsg.P4-12.3+deb9u3) ...
Preparing to unpack .../16-raspberrypi-sys-mods_20180103_armhf.deb ...
Unpacking raspberrypi-sys-mods (20180103) over (20171127) ...
Preparing to unpack .../17-pi-bluetooth_0.1.7_all.deb ...
Unpacking pi-bluetooth (0.1.7) over (0.1.6) ...
Preparing to unpack .../18-rsync_3.1.2-1+deb9u1_armhf.deb ...
Unpacking rsync (3.1.2-1+deb9u1) over (3.1.2-1) ...
Preparing to unpack .../19-raspi-config_20171201_all.deb ...
Unpacking raspi-config (20171201) over (20171109) ...
Setting up firmware-realtek (1:20161130-3+rpt1) ...
update-initramfs: deferring update (trigger activated)
Setting up bluez-firmware (1.2-3+rpt2) ...
Setting up raspberrypi-sys-mods (20180103) ...
Setting up libisc-export160 (1:9.10.3.dfsg.P4-12.3+deb9u4) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for install-info (6.3.0.dfsg.1-1+b1) ...
Setting up libcurl3-gnutls:armhf (7.52.1-5+deb9u4) ...
Setting up tzdata (2017c-0+deb9u1) ...

Current default time zone: 'Europe/Berlin'
Local time is now: Thu Feb 8 00:57:44 CET 2018.
Universal Time is now: Wed Feb 7 23:57:44 UTC 2018.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up pi-bluetooth (0.1.7) ...
Setting up libicu57:armhf (57.1-6+deb9u1) ...
Setting up iproute2 (4.9.0-1+deb9u1) ...
Setting up libxml2:armhf (2.9.4+dfsg1-2.2+deb9u2) ...
Setting up rsync (3.1.2-1+deb9u1) ...
Setting up raspi-config (20171201) ...
Setting up libssl1.0.2:armhf (1.0.2l-2+deb9u2) ...
Setting up libisccc140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u4) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Setting up firmware-libertas (1:20161130-3+rpt1) ...
Processing triggers for systemd (232-25+deb9u1) ...
Setting up firmware-misc-nonfree (1:20161130-3+rpt1) ...
update-initramfs: deferring update (trigger activated)
Setting up firmware-atheros (1:20161130-3+rpt1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libpython2.7-minimal:armhf (2.7.13-2+deb9u2) ...
Setting up firmware-brcm80211 (1:20161130-3+rpt1) ...
Setting up openssh-client (1:7.4p1-10+deb9u2) ...
Setting up libpython2.7-stdlib:armhf (2.7.13-2+deb9u2) ...
Setting up libdbus-1-3:armhf (1.10.24-0+deb9u1) ...
Setting up python2.7-minimal (2.7.13-2+deb9u2) ...
Setting up libdns-export162 (1:9.10.3.dfsg.P4-12.3+deb9u4) ...
Setting up python2.7 (2.7.13-2+deb9u2) ...
Setting up openssh-sftp-server (1:7.4p1-10+deb9u2) ...
Setting up dbus (1.10.24-0+deb9u1) ...
A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
Setting up openssh-server (1:7.4p1-10+deb9u2) ...
Setting up ssh (1:7.4p1-10+deb9u2) ...
Processing triggers for initramfs-tools (0.130) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...

User avatar
PeterO
Posts: 5009
Joined: Sun Jul 22, 2012 4:14 pm

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Thu Feb 08, 2018 8:53 am

idontknowit wrote:
Thu Feb 08, 2018 12:10 am
well, I have lost three 2 version 3 and one version 1 to the lastest command
sudo apt-get upgrade..
Where have you looked for them ? ;)

What has actually happened to them ?

PeterO
Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson

jahboater
Posts: 4681
Joined: Wed Feb 04, 2015 6:38 pm

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Thu Feb 08, 2018 9:17 am

Well I just upgraded a Pi3 and a Pi Zero, both worked fine.

With 18+ million Pi's around and most of them using Raspbian, it quickly gets wide exposure.
Had to re-image and yes, I was stupid enough to try again.
I didn't try that. Can you list what changes you made between imaging and the upgrade (you did run "sudo apt update" first?)

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23665
Joined: Sat Jul 30, 2011 7:41 pm

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Thu Feb 08, 2018 9:33 am

What are the symptoms? Any error messages? Will be difficult to figure out the issue without more information.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

mkob
Posts: 1
Joined: Mon Feb 19, 2018 11:38 am

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Mon Feb 19, 2018 11:45 am

I also encountered my Raspberry Pi Zero W killed (kernel panic after boot) after the February upgrade.
And managed to restore by replacing the 'brcmfmac43430-sdio.bin' in /lib/firmware/brcm with the one included in

http://cdn-fastly.deb.debian.org/debian ... -1_all.deb

I don't know what was changed with the firmware, but I hope that helps something.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23665
Joined: Sat Jul 30, 2011 7:41 pm

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Mon Feb 19, 2018 3:48 pm

mkob wrote:
Mon Feb 19, 2018 11:45 am
I also encountered my Raspberry Pi Zero W killed (kernel panic after boot) after the February upgrade.
And managed to restore by replacing the 'brcmfmac43430-sdio.bin' in /lib/firmware/brcm with the one included in

http://cdn-fastly.deb.debian.org/debian ... -1_all.deb

I don't know what was changed with the firmware, but I hope that helps something.
That's odd. I have no idea of the provenance of that firmware.

We have just released a new version of the wireless firmware (this comes from Cypress not us) which showed no issues in testing.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

User avatar
alx_nearphuture
Posts: 1
Joined: Mon Feb 19, 2018 4:38 pm
Location: France
Contact: Website Twitter

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Mon Feb 19, 2018 4:58 pm

mkob wrote:
Mon Feb 19, 2018 11:45 am
I also encountered my Raspberry Pi Zero W killed (kernel panic after boot) after the February upgrade.
And managed to restore by replacing the 'brcmfmac43430-sdio.bin' in /lib/firmware/brcm with the one included in

http://cdn-fastly.deb.debian.org/debian ... -1_all.deb

I don't know what was changed with the firmware, but I hope that helps something.
Thanks it fixed the problem on my side both on Raspberry Pi 3 and Raspberry Pi Zero W.

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 9:53 am

jamesh wrote:
Mon Feb 19, 2018 3:48 pm
We have just released a new version of the wireless firmware (this comes from Cypress not us) which showed no issues in testing.
This is indeed quite worrisome! Especially, since the FW I already have is far more recent.

1. Can someone please explain why you are pushing out firmware "updates" with compile dates from 2 years ago?
2. And what does "rpt2" and "rpi2" mean here?

Code: Select all

$ uname -a
Linux xxx 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

$ apt list --upgradable
...
firmware-atheros/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-brcm80211/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-libertas/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-misc-nonfree/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-realtek/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
...
with:

Code: Select all

$ ./brcmFW.sh
Extracted the following info from the binary blob:
Name:         43430a1-roml
Capabilities: sdio-g-p2p-pool-pno-pktfilter-keepalive-aoe-mchan-tdls-proptxstatus-ampduhostreorder-lpc-sr-bcmcps
Version:      7.45.41.46 (r666254 CY)
CRC:          970a33e2
Date:         Mon 2017-08-07 00:48:36 PDT
Ucode Ver:    1043.206
FWID:         01-ef6eb4d3
Or did I miss something we should know about?
Last edited by E3V3A on Tue Mar 06, 2018 11:48 am, edited 2 times in total.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 23665
Joined: Sat Jul 30, 2011 7:41 pm

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 11:44 am

E3V3A wrote:
Tue Mar 06, 2018 9:53 am
jamesh wrote:
Mon Feb 19, 2018 3:48 pm
We have just released a new version of the wireless firmware (this comes from Cypress not us) which showed no issues in testing.
This is indeed quite worrisome! Especially, since the FW I already have is far more recent.

1. Can someone please explain why you are pushing out firmware "updates" with compile dates from 2 years ago?
2. And what does "rpt2" and "rpi2" mean here?

Code: Select all

$ uname -a
Linux xxx 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

$ apt list --upgradable
...
firmware-atheros/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-brcm80211/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-libertas/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-misc-nonfree/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
firmware-realtek/stable 1:20161130-3+rpt2 all [upgradable from: 1:20161130-3+rpi2]
...
with:

Code: Select all

$ ./brcmFW.sh
Extracted the following info from the binary blob:
Name:         43430a1-roml
Capabilities: sdio-g-p2p-pool-pno-pktfilter-keepalive-aoe-mchan-tdls-proptxstatus-ampduhostreorder-lpc-sr-bcmcps
Version:      7.45.41.46 (r666254 CY)
CRC:          970a33e2
Date:         Mon 2017-08-07 00:48:36 PDT
Ucode Ver:    1043.206
FWID:         01-ef6eb4d3
Or did I miss something we should know about?
OK, here's what happened (explained already in other threads)

We received a new wireless chip firmware release from Cypress. We tested it, we had others test it, but no problems found, so we released it. However, since release some issues have come to light (Hidden SSID's cause issues, turning off/on AP causes issues). So whilst we are fixing that we rolled back to an earlier firmware.

We think we know what the issue is, so hopefully all will be resolved in the next week or so.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 11:50 am

@jamesh Thanks for the feedback!

I now see that Broadcom FW are using a very stupid versioning scheme of not actually using one! Instead just an old date with some letters, like the "rpt2".

EDIT: (Actually, it may not be Broradcom's fault as they clearly have a good versioning scheme embedded in FW, but the package repository maintainers, or whoever, decide how to version the apt packages we get.)

Indeed the FW is new:

Code: Select all

Name:         43430a1-roml
Capabilities: sdio-g-pool-p2p-idsup-idauth-pno-pktfilter-wowlpf-keepalive-aoe-lpc-swdiv-srfast-fuart
Version:      7.45.98.38 (r674442 CY)
CRC:          ffb2ee5a
Date:         Mon 2017-10-23 03:58:00 PDT
Ucode Ver:    1043.2099
FWID:         01-e58d219f
DVID:         01-3b702d60
But the FW capabilities seem to have changed dramatically.
Perhaps some developer could shed some light on the capabilities that have changed?
Last edited by E3V3A on Tue Mar 06, 2018 11:55 am, edited 1 time in total.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5963
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 11:53 am

E3V3A wrote:
Tue Mar 06, 2018 11:50 am
I now see that Broadcom FW are using a very stupid versioning scheme of not actually using one! Instead just an old date with some letters, like the "rpt2".
Not being familiar with it doesn't make it stupid. This has nothing to do with Broadcom.
http://www.fifi.org/doc/debian-policy/p ... sions.html

The version number scheme is determined by Debian and is perfectly sensible (the +rpt2 bit is added by us).

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 11:57 am

@ShiftPlusOne
Just realized! (And edited previous post while you were writing.)
Thank you!

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 12:03 pm

Would it be possible for you guys to push for a change in the packages info to actually show what firmware is in it?

Since, doing "apt show firmware-brcm80211" doesn't show anything useful (in this regard) at all!

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5963
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Tue Mar 06, 2018 12:09 pm

That file is one of many firmware files in that binary package. That binary package is one of many generated by the firmware-nonfree source package. The source package is what determines the version number for all the binary packages. You can't put the version of every single file in the version number, nor would it make sense to make this one file special, since we may also add or modify other ones.

Edit: I guess the package description could be modified to specify the version. I'll consider it for the next update.

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Wed Mar 07, 2018 9:59 am

ShiftPlusOne wrote:
Tue Mar 06, 2018 12:09 pm
That file is one of many firmware files in that binary package.
I think there are various options here:
  • Provide a proper changelog
  • Provide a better package description, saying at least the version numbers for each FW (one actually has it: 4354)
  • Put the compiler or release date, as the package "Version" shown
  • Provide a separate FW package for the Raspberries. I understand the Debian system, but it just doesn't make sense to install all FWs for a device that will never ever use those other FW's.
A changelog would be great, so that the following, actually show something:

Code: Select all

$ apt-get changelog firmware-brcm80211
E: Failed to fetch changelog:/firmware-nonfree.changelog  Changelog unavailable for firmware-nonfree=1:20161130-3+rpt2
Thanks for your response.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5963
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Wed Mar 07, 2018 10:34 am

E3V3A wrote:
Wed Mar 07, 2018 9:59 am
ShiftPlusOne wrote:
Tue Mar 06, 2018 12:09 pm
That file is one of many firmware files in that binary package.
I think there are various options here:
  • Provide a proper changelog
  • Provide a better package description, saying at least the version numbers for each FW (one actually has it: 4354)
  • Put the compiler or release date, as the package "Version" shown
  • Provide a separate FW package for the Raspberries. I understand the Debian system, but it just doesn't make sense to install all FWs for a device that will never ever use those other FW's.
A changelog would be great, so that the following, actually show something:

Code: Select all

$ apt-get changelog firmware-brcm80211
E: Failed to fetch changelog:/firmware-nonfree.changelog  Changelog unavailable for firmware-nonfree=1:20161130-3+rpt2
Thanks for your response.
The changelog could be improved, but we can't host them wherever raspbian downloads them from.

Package description could be improved, yes.

The release date of 99% of the firmware files IS the version shown.

The other FW files are used on a raspberry pi like they are on any other system (for example, when using USB devices).

I understand that there are other alternatives, but consider some of the factors that might not be obvious when looking at it from the outside:
There are only a few people involved here. That isn't the only or even the primary thing they do. Each extra bit adds long term maintenance burden and reduces how much we can do in the future.
Creating a whole new package to override files which exist in another package is kludgy and would need to be done to many other packages.
When people install firmware-brcm80211, they expect that to work for all broadcom devices, not all except the one that's actually on-board.
Very few users read changelogs or package descriptions when updating packages (I would argue that nobody does).
There are other things we could do and are doing that would benefit more people.
There are many other packages which ship versioned components where the version is not reflected in the changelog or package description.

I could go on and on, but it just doesn't add up to any major overhauls. Improved package description and changelog... sure, maybe.

User avatar
E3V3A
Posts: 26
Joined: Sun Apr 17, 2016 7:13 am
Location: -∇φ

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Wed Mar 07, 2018 2:03 pm

ShiftPlusOne wrote:
Wed Mar 07, 2018 10:34 am
The release date of 99% of the firmware files IS the version shown.
Surely 20161130 is not the release date that was pushed to us, only a few days ago! :D

Ok, I'm done trying to argue for a good cause here... Anyway, it was worth a try.

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5963
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: upgrade Feb 2018 kills all my Raspberrypi'S

Wed Mar 07, 2018 2:15 pm

E3V3A wrote:
Wed Mar 07, 2018 2:03 pm
ShiftPlusOne wrote:
Wed Mar 07, 2018 10:34 am
The release date of 99% of the firmware files IS the version shown.
Surely 20161130 is not the release date that was pushed to us, only a few days ago! :D

Ok, I'm done trying to argue for a good cause here... Anyway, it was worth a try.
20161130 is the correct upstream version of the package. If you want to change how the upstream version is determined, it would need to be taken up with Debian developers.

Return to “Raspbian”