Processed: 981616 is fixed in 5.10.24-1

Processing control commands: > close -1 5.10.24-1 Bug #981616 [src:linux] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Marked as fixed in versions linux/5.10.24-1. Bug #981616 [src:linux] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Marked Bug as done -- 981616:

Bug#981616: 981616 is fixed in 5.10.24-1

Control: close -1 5.10.24-1 I recheck the situation with Debian kernel 5.10.24 and Debian firmware-brcm80211 20201218-3. 5GHz WiFi works fine with vc4 and without vc4. Debian package of firmware-brcm80211 newer than 20201218-3 has a severe issue with 5GHz WiFi as reported at

Processed: Re: Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

Processing control commands: > found -1 20210315-1 Bug #985632 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine Marked as found in versions firmware-nonfree/20210315-1. -- 985632:

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

Control: found -1 20210315-1 > I will re-check 20210315-1. The system boots with 20210315-1 and the reported symtom remains in the same way. Ryutaroh

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

Hi Maximilian, thank you again for your response. > but are you sure that these > bootflags are still adequate for the latest cypress firmware? What did you mean by "bootflags"?? Did you mean /proc/cmdline (i.e. cmdline.txt in Raspberry Pi)? > concerning bluetooth unfortunately this seems

Processed: Re: Bug#985740: firmware-brcm80211: broken symlink: /lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt

Processing commands for cont...@bugs.debian.org: > tags 985740 pending Bug #985740 [firmware-brcm80211] firmware-brcm80211: broken symlink: /lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt Added tag(s) pending. > End of message, stopping

Bug#985743: firmware-qcom-soc: broken symlink: /lib/firmware/qcom/sdm845/wlanmdsp.mbn -> ../../ath10k/WCN3990/hw1.0/wlanmdsp.mbn

Package: firmware-qcom-soc Version: 20210315-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m15.9s ERROR: FAIL: Broken

Bug#985740: firmware-brcm80211: broken symlink: /lib/firmware/brcm/brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt

Package: firmware-brcm80211 Version: 20210315-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m14.6s ERROR: FAIL: Broken

Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine

Dear Ryutaroh, > It is Raspberry Pi 4B 8GB model. I see thank you for all the dmesg. > > please show affected dmesg output working and non working, > > the difference between 20210208-3 20210208-4 is minimal, > > hence it should be easy to find out what broke? > > Not at all, unfortunately. >

Processed: tg

Processing commands for cont...@bugs.debian.org: > tag 962038 upstream Bug #962038 [firmware-nonfree] firmware-nonfree: Add brcm-bluetooth (for RaspberryPi) Added tag(s) upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 962038:

Bug#985687: linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m

Yikes, how did I miss that? I guess it was too late in the night ... We tried 5.10.13-1 a few weeks back, but it had a kernel panic on boot. Without time to debug, we just reverted to a working 5.9.15-1. I see a promising bug fix in 5.10.13-1 changelog. We'll try again. Thanks for the help and

Bug#985687: linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m

Hi Andrew, Le 2021-03-22 04:26, Andrew Balmos a écrit : > Package: src:linux > Version: 5.9.15-1~bpo10+1 > Severity: normal > > Dear Maintainer, > > Please consider setting kernel option "CONFIG_CAN_J1939=m" for at least > buster-backports armmp. Without this setting the CAN J1939 protocol can

Bug#985689: Needs CONFIG_UNICODE to mount ext4 fs with case-insensitivity feature

* On 3/22/21 9:40 AM, Bastian Blank wrote: > Control: tags -1 moreinfo > > On Mon, Mar 22, 2021 at 08:40:34AM +0100, Mihai Moldovan wrote: >> Currently, mounting an EXT4-formatted volume with the case-insensitivity >> feature >> is impossible since CONFIG_UNICODE is not enabled in the kernel >>

Processed: Re: Bug#985689: Needs CONFIG_UNICODE to mount ext4 fs with case-insensitivity feature

Processing control commands: > tags -1 moreinfo Bug #985689 [linux] Needs CONFIG_UNICODE to mount ext4 fs with case-insensitivity feature Added tag(s) moreinfo. -- 985689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985689 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#985689: Needs CONFIG_UNICODE to mount ext4 fs with case-insensitivity feature

Control: tags -1 moreinfo On Mon, Mar 22, 2021 at 08:40:34AM +0100, Mihai Moldovan wrote: > Currently, mounting an EXT4-formatted volume with the case-insensitivity > feature > is impossible since CONFIG_UNICODE is not enabled in the kernel configuration. Why would anyone want to do that? > My

Bug#985689: Needs CONFIG_UNICODE to mount ext4 fs with case-insensitivity feature

Package: linux Version: 5.10.19-1 Dear maintainers Currently, mounting an EXT4-formatted volume with the case-insensitivity feature is impossible since CONFIG_UNICODE is not enabled in the kernel configuration. Please consider enabling it. I'm leaving the severity at default, since the