Re: Processed: firmware-nonfree: Add brcm-bluetooth (for RaspberryPi)
> Bug #962038 [raspi-firmware] firmware-nonfree: Add brcm-bluetooth (for > RaspberryPi) that be very possible to add and create a firmware package for that, but first this https://github.com/RPi-Distro/bluez-firmware/tree/master/broadcom would have to land upstream in linux-firmware. Have you tried to submit them, phil? signature.asc Description: PGP signature
Bug#981181: linux-image-amd64: SiS chipset - USB stops working after update kernel to 4.9+80+deb9u12 and above
Package: linux-image-amd64 Version: 4.9+80+deb9u11 Severity: important Tags: upstream Dear Maintainer, * What led up to the situation? On old laptop RoverBook E514L (system chipset SiS 760) was installed Debian 10 + LXDE. Everything worked like a charm (including USB mouse and pendrives) until recent update via apt. After update all usb mices aren't recognised (dmesg shows no system reaction on plugging them in/out), usb flash drives sometimes are recognised, sometimes not. laspci shows found USB hubs meanwhile as usual * What exactly did you do (or not do) that was effective (or ineffective)? System reinstallation of the most recent Debian Buster 10.7 had no effect (no USB mouse again) as 10.7 seems to incorporate the most recent kernel already. The only way to render system usable again was to install Debian 9 iso image and then restrict kernel image from updtaing. All other packages were updated with no issues - mices and pendrives work as usual. * What was the outcome of this action? Other systems I have (different laptops and desktops, not SiS based) work with no issues on 10.7 and recent kernel, so I assume this bug is related to SiS chipset only * What outcome did you expect instead? I can guess that SiS based systems are not that widely used nowadays but I wanted to let others know that such an issue exists. -- System Information: Debian Release: 9.13 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-13-amd64 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.9.0-13-amd64 4.9.228-1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information
Bug#981186: linux: Enable CMN-600 interconnect on arm64
Source: linux Version: Please enable ARM CMN-600 power management on arm64 Severity: normal Tags: patch Current arm hardware such as graviton2 (AWS arm64 hardware) has 'Coherent Mesh Network' interconnect (between components in a soc). It's important that support for this is built in the kernel so it can be used. This requires CONFIG_ARM_CMN=y This explains what the feature is: https://www.arm.com/products/silicon-ip-system/corelink-interconnect/cmn-600 Graviton2: https://www.anandtech.com/show/15578/cloud-clash-amazon-graviton2-arm-against-intel-and-amd patch attached: --- debian/config/arm64/config~ 2021-01-27 04:34:51.359552398 + +++ debian/config/arm64/config 2021-01-27 04:53:11.922998842 + @@ -942,6 +942,7 @@ CONFIG_ARM_CCI400_PMU=y CONFIG_ARM_CCI5xx_PMU=y CONFIG_ARM_CCN=y +CONFIG_ARM_CMN=y CONFIG_QCOM_L2_PMU=y CONFIG_QCOM_L3_PMU=y CONFIG_XGENE_PMU=y --- debian/config/arm64/config~ 2021-01-27 04:34:51.359552398 + +++ debian/config/arm64/config 2021-01-27 04:53:11.922998842 + @@ -942,6 +942,7 @@ CONFIG_ARM_CCI400_PMU=y CONFIG_ARM_CCI5xx_PMU=y CONFIG_ARM_CCN=y +CONFIG_ARM_CMN=y CONFIG_QCOM_L2_PMU=y CONFIG_QCOM_L3_PMU=y CONFIG_XGENE_PMU=y
Bug#981005: linux-image-5.10.0-2-amd64: Bluetooth stopped working
Relevant part of 5.10.0 dmesg: [20164.000149] ata1.00: configured for UDMA/100 [20164.084110] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [20164.167454] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [20164.188123] usb 4-4: new full-speed USB device number 8 using ohci-pci [20164.382093] usb 4-4: New USB device found, idVendor=0930, idProduct=0220, bcdDevice= 0.01 [20164.382103] usb 4-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [20164.390243] usb 4-4: firmware: direct-loading firmware ar3k/AthrBT_0x3101.dfu [20164.429414] PM: suspend exit [20164.455974] usb 4-4: firmware: direct-loading firmware ar3k/ramps_0x3101_40.dfu [20164.466587] usb 4-4: USB disconnect, device number 8 [20165.036680] usb 4-4: new full-speed USB device number 9 using ohci-pci [20167.982738] wlp5s0: authenticate with 74:da:88:a9:c6:a6 [20168.014007] wlp5s0: send auth to 74:da:88:a9:c6:a6 (try 1/3) [20168.017540] wlp5s0: authenticated [20168.028507] wlp5s0: associate with 74:da:88:a9:c6:a6 (try 1/3) [20168.037597] wlp5s0: RX AssocResp from 74:da:88:a9:c6:a6 (capab=0x411 status=0 aid=2) [20168.037768] wlp5s0: associated [20168.054940] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready [20170.260959] usb 4-4: New USB device found, idVendor=0930, idProduct=0220, bcdDevice= 0.02 [20170.260970] usb 4-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [20170.264703] Bluetooth: hci0: don't support firmware rome 0x3101 [20171.105831] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [20171.117913] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [20171.802265] wlp5s0: AP 74:da:88:a9:c6:a6 changed bandwidth, new config is 2417.000 MHz, width 1 (2417.000/0 MHz)
Bug#977694: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Control: reassign -1 raspi-firmware 1.20210111+ds-2 Booting linux kernel 5.10.x from USB MSD needs either * loading reset-raspberrypi.ko in initramfs, * or rebuild kernel with CONFIG_RESET_RASPBERRYPI=y in .config Anyway, the combination of linux-image-arm64/sid and raspi-firmware/sid does not allow booting RPi4 from USB-MSD. Boot from USB-MSD was possible in Debian kernel 5.9 series. I think this boot failure should be fixed by echo reset-raspberrypi >/usr/share/initramfs-tools/modules.d/raspi-firmware.conf instead of CONFIG_RESET_RASPBERRYPI=y. If this is considered an issue in src:linux, please reassign this back. Best regards, Ryutaroh Matsumoto
Processed: Re: 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd
Processing control commands: > reassign -1 raspi-firmware 1.20210111+ds-2 Bug #977694 [src:linux] 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd Bug reassigned from package 'src:linux' to 'raspi-firmware'. No longer marked as found in versions linux/5.10.9-1. Ignoring request to alter fixed versions of bug #977694 to the same values previously set Bug #977694 [raspi-firmware] 5.10.4 Debian kernel does not boot on raspi 4 with ext4 rootfs and usb-msd Marked as found in versions raspi-firmware/1.20210111+ds-2. -- 977694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > unblock 980980 by 977694 Bug #980980 [src:linux] linux-image-5.10.0-2-arm64-unsigned: flood of false udev messages make udisks2 eat CPU usage on usb-booted raspi4 980980 was blocked by: 977694 980980 was not blocking any bugs. Removed blocking bug(s) of 980980: 977694 > tags 979187 - fixed-upstream Bug #979187 [src:linux] 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13 Removed tag(s) fixed-upstream. > quit Stopping processing here. Please contact me if you need assistance. -- 979187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979187 980980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
