Your message dated Sun, 27 Aug 2017 14:07:21 +0100 with message-id <1503839241.3688.82.camel@decadent.org.uk> and subject line Re: stable: 20161130-3 breaks raspberry pi3 has caused the Debian Bug report #866882, regarding stable: 20161130-3 breaks raspberry pi3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 866882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866882 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: stable: 20161130-3 breaks raspberry pi3
- From: Benoit Panizzon <panizzon@woody.ch>
- Date: Sun, 2 Jul 2017 15:28:54 +0200
- Message-id: <20170702152854.79abb2ec@krup.woody.ch>
Package: firmware-brcm80211 Version: 0.43+rpi5 Severity: important Dear Maintainer, After upgrading my RPi3 from 'jessie' to the actual stable, the wlan module could not initialize anymore. Well first I filed a bug agains the BRCM driver in kernel 4.9.35-v7+ as I belived this was a problem of said driver with the actual firmware. As this problem massively bothered me, I went on an installed a fresh 'actual' Raspbian on a separate SD card and bootet. WLAN works fine, so not a hardware issue. But I noted that Raspbian uses 'jessie' as release tag and changed this to stable, as I want to stay with stable. Did a dist-upgrade. And again, the WLAN device was gone. I investigated further into the problem and noticed, the MD5 sums of the files in /lib/firmware/brcm had changed. I did a downgrade to firmware-brcm80211=0.43+rpi5 and the WLAN device is back. My search on google, revealed that a lot of other RPi 3 users run into that problem and apparently I am the first to figure out the cause. So I suggest that the firmware-brcm80211=20161130-3 in the raspbian repository should be checked and made sure the correct firmware version for the 'stable' kernel ins included. -Benoit- -- System Information: Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.0 (stretch) Release: 9.0 Codename: stretch Architecture: armv7l Kernel: Linux 4.9.35-v7+ (SMP w/4 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.130 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 866882-done@bugs.debian.org
- Subject: Re: stable: 20161130-3 breaks raspberry pi3
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sun, 27 Aug 2017 14:07:21 +0100
- Message-id: <1503839241.3688.82.camel@decadent.org.uk>
- In-reply-to: <20170702152854.79abb2ec@krup.woody.ch>
- References: <20170702152854.79abb2ec@krup.woody.ch>
Since you're using Raspbian, you should report this to that project, not to Debian. (It's possible that this affects Debian too, but then it's also possible that this is a result of driver changes in the Raspbian kernel. I'm not able to determine that.) Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---