Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13
Hi, > reportbug linux-image-5.9.0-5-arm64 > while booted with this kernel and select the option to Follow-Up to this > bug (you might want to have the bug number handy), so that reportbug can > collect more information about your system. I wanted to do that, but as the kernel does not boot with the problematic USB MSD, I cannot use reportbug on it. Did you mean that I should boot linux-image-5.9.0-5-arm64 on an sdcard or another usb msd, and run reportbug on it? As I wrote in another email, screenshot of failing boot is placed at https://photos.app.goo.gl/gCHUEXJB74hsWQtTA Ryutaroh
Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13
On Lu, 04 ian 21, 18:40:44, Ryutaroh Matsumoto wrote: > Hi, > > > reportbug linux-image-5.9.0-5-arm64 > > while booted with this kernel and select the option to Follow-Up to this > > bug (you might want to have the bug number handy), so that reportbug can > > collect more information about your system. > > I wanted to do that, but as the kernel does not boot with the > problematic USB MSD, I cannot use reportbug on it. > Did you mean that I should boot linux-image-5.9.0-5-arm64 > on an sdcard or another usb msd, and run reportbug on it? If possible that might be very helpful. You could also try asking on one of Debian's support channels, in case there is some workaround. https://www.debian.org/support Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages signature.asc Description: PGP signature
firmware-nonfree 20201022-1 upload
Happy 2021 everyone. Today will upload this release. sorry for short notice, anything falling through cracks will be in the following nov release. best, -- maks signature.asc Description: PGP signature
Bug#977645: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard
Control: reassign -1 src:linux 5.10.1-1~exp1 Control: found -1 5.10.2-1~exp1 Control: found -1 5.10.4-1 Control: retitle -1 5.10.x Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard On Mon, 04 Jan 2021 09:24:09 +0900 (JST) Ryutaroh Matsumoto wrote: > Control: reassign -1 linux-image-5.10.0-1-arm64 5.10.4-1 If you want to record in the BTS that a certain bug is also present in another version, you shouldn't use 'reassign' but 'found'. Using reassign also has side-effects, like clearing that this bug was present in previous 5.10.x versions as well, which is useful to know. > Control: severity -1 important If you change severity it is custom to specify *why* you changed it. Doubly so if a maintainer has changed/set the severity. It was changed to the previous value, so it had no effect, but wanted to point this out nonetheless. signature.asc Description: This is a digitally signed message part.
Processed: Re: 5.10.1 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard
Processing control commands: > reassign -1 src:linux 5.10.1-1~exp1 Bug #977645 [linux-image-5.10.0-1-arm64] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Bug reassigned from package 'linux-image-5.10.0-1-arm64' to 'src:linux'. No longer marked as found in versions linux-signed-arm64/5.10.4+1. Ignoring request to alter fixed versions of bug #977645 to the same values previously set Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Marked as found in versions linux/5.10.1-1~exp1. > found -1 5.10.2-1~exp1 Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Marked as found in versions linux/5.10.2-1~exp1. > found -1 5.10.4-1 Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Marked as found in versions linux/5.10.4-1. > retitle -1 5.10.x Debian kernel does not boot on raspi 4 with ext4 rootfs and > sdcard Bug #977645 [src:linux] 5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Changed Bug title to '5.10.x Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard' from '5.10.2 Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard'. -- 977645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of firmware-nonfree_20201022-1_amd64.changes
firmware-nonfree_20201022-1_amd64.changes uploaded successfully to localhost along with the files: firmware-nonfree_20201022-1.dsc firmware-nonfree_20201022.orig.tar.xz firmware-nonfree_20201022-1.debian.tar.xz firmware-amd-graphics_20201022-1_all.deb firmware-atheros_20201022-1_all.deb firmware-bnx2_20201022-1_all.deb firmware-bnx2x_20201022-1_all.deb firmware-brcm80211_20201022-1_all.deb firmware-cavium_20201022-1_all.deb firmware-intel-sound_20201022-1_all.deb firmware-intelwimax_20201022-1_all.deb firmware-ipw2x00_20201022-1_all.deb firmware-ivtv_20201022-1_all.deb firmware-iwlwifi_20201022-1_all.deb firmware-libertas_20201022-1_all.deb firmware-linux-nonfree_20201022-1_all.deb firmware-linux_20201022-1_all.deb firmware-misc-nonfree_20201022-1_all.deb firmware-myricom_20201022-1_all.deb firmware-netronome_20201022-1_all.deb firmware-netxen_20201022-1_all.deb firmware-nonfree_20201022-1_amd64.buildinfo firmware-qcom-media_20201022-1_all.deb firmware-qcom-soc_20201022-1_all.deb firmware-qlogic_20201022-1_all.deb firmware-realtek_20201022-1_all.deb firmware-samsung_20201022-1_all.deb firmware-siano_20201022-1_all.deb firmware-ti-connectivity_20201022-1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#975726: marked as done (firmware-iwlwifi: bluetooth hci0: firmware: failed to load intel/ibt-19-32-0.sfi (-2))
Your message dated Mon, 04 Jan 2021 11:04:45 + with message-id and subject line Bug#975726: fixed in firmware-nonfree 20201022-1 has caused the Debian Bug report #975726, regarding firmware-iwlwifi: bluetooth hci0: firmware: failed to load intel/ibt-19-32-0.sfi (-2) 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 ow...@bugs.debian.org immediately.) -- 975726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-iwlwifi Version: 20200918-1 Severity: important Recently I helped a user getting their Bluetooth working the missing firmware was: bluetooth hci0: firmware: failed to load intel/ibt-19-32-0.sfi (-2) Searching for this missing firmware provided no results we were able to download the sfi and ddc file from: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel After placing said files in /lib/firmware/intel/ the Bluetooth started working. Please include these firmware files in the firmware-iwlwifi. --- End Message --- --- Begin Message --- Source: firmware-nonfree Source-Version: 20201022-1 Done: maximilian attems We believe that the bug you reported is fixed in the latest version of firmware-nonfree, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems (supplier of updated firmware-nonfree package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Jan 2021 11:21:55 +0100 Source: firmware-nonfree Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity Architecture: source all Version: 20201022-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: maximilian attems Description: firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-cavium - Binary firmware for Cavium Ethernet adapters firmware-intel-sound - Binary firmware for Intel sound DSPs firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (metapack firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netronome - Binary firmware for Netronome network adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qcom-media - Binary firmware for Qualcomm graphics/video (dummy package) firmware-qcom-soc - Binary firmware for Qualcomm SoCs firmware-qlogic - Binary firmware for QLogic HBAs firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters firmware-samsung - Binary firmware for Samsung MFC video codecs firmware-siano - Binary firmware for Siano MDTV receivers firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and BT/FM/GPS adapters Closes: 975726 Changes: firmware-nonfree (20201022-1) unstable; urgency=medium . * New upstream version: - linux-firmware: Update Marvell Switchdev firmware with ABI changes - l
firmware-nonfree_20201022-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 04 Jan 2021 11:21:55 +0100 Source: firmware-nonfree Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity Architecture: source all Version: 20201022-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: maximilian attems Description: firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-cavium - Binary firmware for Cavium Ethernet adapters firmware-intel-sound - Binary firmware for Intel sound DSPs firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (metapack firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netronome - Binary firmware for Netronome network adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qcom-media - Binary firmware for Qualcomm graphics/video (dummy package) firmware-qcom-soc - Binary firmware for Qualcomm SoCs firmware-qlogic - Binary firmware for QLogic HBAs firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters firmware-samsung - Binary firmware for Samsung MFC video codecs firmware-siano - Binary firmware for Siano MDTV receivers firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and BT/FM/GPS adapters Closes: 975726 Changes: firmware-nonfree (20201022-1) unstable; urgency=medium . * New upstream version: - linux-firmware: Update Marvell Switchdev firmware with ABI changes - linux-firmware: move i915 firmware symlinks to WHENCE - linux-firmware: Update firmware patch for Intel Bluetooth 7265 (D1) - QCA : Updated firmware files for WCN3991 - linux-firmware: Add new VPDMA firmware 1b8.bin - amdgpu: update navi10 firmware for 20.40 - amdgpu: update navi12 firmware for 20.40 - amdgpu: update navi14 firmware for 20.40 - amdgpu: update picasso firmware for 20.40 - amdgpu: update raven firmware for 20.40 - amdgpu: update raven2 firmware for 20.40 - amdgpu: update renoir firmware for 20.40 - amdgpu: update vega10 firmware for 20.40 - amdgpu: update vega12 firmware for 20.40 - amdgpu: update vega20 firmware for 20.40 - copy-firmware: Always write Link: entries - ice: Add comms package file for Intel E800 series driver - qcom : updated venus firmware files for v5.4 - i915: Add DG1 DMC v2.02 - iwlwifi: update 3168, 7265D, 8000C and 8265 firmwares - iwlwifi: update and add new FWs from core56-54 release - QCA : Updated firmware file for WCN3991 - mediatek: separate venc service thread - ice: update package file to 1.3.16.0 - ath10k: add SDIO firmware for QCA9377 WiFi - rtl_bt: Update RTL8821C BT FW to 0xAA6C_A99E - cypress: add Cypress firmware and clm_blob files * Update to linux-support 5.9.0-5. * iwlwifi: add Intel Bluetooth AX201 (var 32 rev 0) (closes: 975726) Checksums-Sha1: 1f4b0711c7fb3fdf08baa2df0cc470ff8acb8f6f 3937 firmware-nonfree_20201022-1.dsc 972bfd245366e4931d41e149454f63f7378d7357 85359724 firmware-nonfree_20201022.orig.tar.xz 91c6a29583e4b56f897fe8244934b57b75cebc19 785584 firmware-nonfree_20201022-1.debian.tar.xz 9b7b260e08ab1ed8bbd09e6690c5eb36c66ca188 5027296 firmware-amd-graphics_20201022-1_all.deb 10a9b822e7a7d0b228c1eee9b6c584bddb7e71e8 5911716 firmware-atheros_20201022-1_all.deb 7fb69a6bfe4aad59cb65bc6f35a08c5d4723d38d 106440 firmware-bnx2_20201022-1_all.deb 33e55af43ffcb022f0b9bdf79cc04bd99362f381 3400728 firmware-bnx2x_20201022-1_all.deb 5f49e34dca477553a81ef1b3efb4aa984344c9e8 5984404 firmware-brcm80211_20201022-1_all.deb 7f95032ecca9f2d0852cd1afe9925e81661fea69 653500 firmware-cavium_20201022-1_all.deb 4c222004983cdc06daef1a38c1e4e1
Processed: closing 970634
Processing commands for cont...@bugs.debian.org:
> close 970634 5.10.4-1
Bug #970634 {Done: Ryutaroh Matsumoto }
[src:linux] linux-image-5.8.0-1-arm64: Kernel image misaligned at boot on raspi
4B
Marked as fixed in versions linux/5.10.4-1.
Bug #970634 {Done: Ryutaroh Matsumoto }
[src:linux] linux-image-5.8.0-1-arm64: Kernel image misaligned at boot on raspi
4B
Bug 970634 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 977694 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 977694 src:linux Bug #977694 [linux-image-5.10.0-1-arm64] 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd Bug reassigned from package 'linux-image-5.10.0-1-arm64' to 'src:linux'. No longer marked as found in versions linux-signed-arm64/5.10.4+1. Ignoring request to alter fixed versions of bug #977694 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 977694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 977645 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 977645 src:linux Bug #977645 [src:linux] 5.10.x Debian kernel does not boot on raspi 4 with ext4 rootfs and sdcard Ignoring request to reassign bug #977645 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 977645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966218: firmware: failed to load iwl-debug-yoyo.bin (-2)
I have the same problem: "firmware: failed to load iwl-debug-yoyo.bin (-2)" in the log. I am using Debian linux-image-5.9.0-5-amd64-unsigned (= 5.9.15-1). I am no expert but i don't think this log message is pressent in Linux mainline, only in Debian. The upstream patch [0] that Jeremy mentions is not for this message but for the upstream debug message: "Direct firmware load for iwl-debug-yoyo.bin failed with error -2" This message is now not shown anymore. The message that this bug report handles is "firmware: failed to load iwl-debug-yoyo.bin (-2)" This message is not in upstream Linux but instead comes from an ancient Debian kernel patch from 2012 that is still applied on debian kernel 5.10.4-1.(firmware_class-log-every-success-and-failure.patch [1]) While the mainstream Linux logging evolved a lot since 2012 i doubt that this patch which duplicates error logging is still wise to use. [0]: https://patchwork.kernel.org/patch/11625759/ [1]: https://sources.debian.org/src/linux/5.10.4-1/debian/patches/bugfix/all/firmware_class-log-every-success-and-failure.patch/
Re: devicetrees overlays support
Ping ? On Sun, 13 Dec 2020 07:57:24 +, Vincent Pelletier wrote: > (please keep me CC'ed, I'm not subscribed) > > I am using the (non-official) Debian port for raspberry pi from > raspi.debian.net , and have a device connected to the SPI bus pins on > the 40-pins extension connector. In my understanding, the proper > approach to interfacing with such device is to write a devicetree > overlay declaring the device. > So I wrote one, but then when I tried to confirm it would apply over > the package-provided dtb (using the fdtoverlay command as a simulation > of what would happen during boot), I realised it would not: it fails > with FDT_ERR_NOTFOUND, which I traced to the absence of any __symbols__ > in the base dtb. > > Rebuilding the devicetree from source, just adding "-@" to the cmd_dtc > rule in scripts/Makefile.lib, and the overlay could be applied by > fdtoverlay, and worked as expected after a reboot on this new dtb. > > Given the widespread use of such devices (SPI or otherwise) in the > raspberry pi ecosystem and the widespread use of overlays to interface > with them, wouldn't it be better to provide devicetrees with > __symbols__ ? > > Sadly, the commonly available overlays do not expect a Debian kernel, > so they may not apply cleanly. I did not try any myself, but the > raspberrypi.org kernel do contain symbols and elements not present in > vanilla, so this seems likely to happen. Which means either these would > need to be adapted to vanilla dtb (hopefully Debian will not customise > the vanilla dtb), or the vanilla dtb extended to meet the needs. IMHO, > both are out of Debian responsibility, but I thought I should mention > this family of possible issues. > > Another possible issue may be that the produced device tree is > substantially larger than without __symbols__: +40% on the "pi zero > wifi". Which seems huge, but this is in fact an increase of only a bit > above 5kB, which, once put next to a kernel image, seems really not > much. > > Would there be a particular reason __symbols__ are not output by the > kernel build command ? > Maybe making it optional if the size increase matters for some very > tightly constrained platforms ? -- Vincent Pelletier
