New Raspberry Pi Kernels & Related Packages

ARM
371

Below are the contents of my current /usr/lib/firmware/brcm/ with the most current update:

$ ls -l /usr/lib/firmware/brcm

total 12024
lrwxrwxrwx 1 root root      17 Feb 10 08:26  BCM-0a5c-6410.hcd -> BCM-0bb4-0306.hcd
-rw-r--r-- 1 root root   54734 Feb 10 08:26  BCM-0bb4-0306.hcd
-rw-r--r-- 1 root root  269595 Feb 10 08:26  bcm4329-fullmac-4.bin
-rw-r--r-- 1 root root   96224 Feb 10 08:26  bcm43xx-0.fw
-rw-r--r-- 1 root root     180 Feb 10 08:26  bcm43xx_hdr-0.fw
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43012-sdio.bin -> ../cypress/cyfmac43012-sdio.bin
lrwxrwxrwx 1 root root      36 Feb 10 08:26  brcmfmac43012-sdio.clm_blob -> ../cypress/cyfmac43012-sdio.clm_blob
-rw-r--r-- 1 root root  397312 Feb 10 08:26  brcmfmac43143.bin
-rw-r--r-- 1 root root  385067 Feb 10 08:26  brcmfmac43143-sdio.bin
-rw-r--r-- 1 root root  348160 Feb 10 08:26  brcmfmac43236b.bin
-rw-r--r-- 1 root root  455745 Feb 10 08:26  brcmfmac43241b0-sdio.bin
-rw-r--r-- 1 root root  403855 Feb 10 08:26  brcmfmac43241b4-sdio.bin
-rw-r--r-- 1 root root  408682 Feb 10 08:26  brcmfmac43241b5-sdio.bin
-rw-r--r-- 1 root root  479232 Feb 10 08:26  brcmfmac43242a.bin
-rw-r--r-- 1 root root  253748 Feb 10 08:26  brcmfmac4329-sdio.bin
-rw-r--r-- 1 root root  222126 Feb 10 08:26  brcmfmac4330-sdio.bin
-rw-r--r-- 1 root root    1509 Feb 10 08:26  brcmfmac4330-sdio.Prowise-PT301.txt
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin
-rw-r--r-- 1 root root    1693 Feb 10 08:26  brcmfmac43340-sdio.meegopad-t08.txt
-rw-r--r-- 1 root root    1724 Feb 10 08:26  brcmfmac43340-sdio.pov-tab-p1006w-data.txt
-rw-r--r-- 1 root root  451566 Feb 10 08:26  brcmfmac4334-sdio.bin
-rw-r--r-- 1 root root  569291 Feb 10 08:26  brcmfmac4335-sdio.bin
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43362-sdio.bin -> ../cypress/cyfmac43362-sdio.bin
-rw-r--r-- 1 root root     803 Feb 10 08:26  brcmfmac43362-sdio.cubietech,cubietruck.txt
lrwxrwxrwx 1 root root      43 Feb 10 08:26  brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt
lrwxrwxrwx 1 root root      30 Feb 10 08:26  brcmfmac4339-sdio.bin -> ../cypress/cyfmac4339-sdio.bin
-rw-r--r-- 1 root root  382455 Feb 10 08:26  brcmfmac43430a0-sdio.bin
-rw-r--r-- 1 root root     951 Feb 10 08:26  brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt
-rw-r--r-- 1 root root     989 Feb 10 08:26 'brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt'
-rw-r--r-- 1 root root     875 Feb 10 08:26  brcmfmac43430-sdio.AP6212.txt
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43430-sdio.bin -> ../cypress/cyfmac43430-sdio.bin
lrwxrwxrwx 1 root root      36 Feb 10 08:26  brcmfmac43430-sdio.clm_blob -> ../cypress/cyfmac43430-sdio.clm_blob
-rw-r--r-- 1 root root     928 Feb 10 08:26  brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt
-rw-r--r-- 1 root root     831 Feb 10 08:26  brcmfmac43430-sdio.MUR1DX.txt
-rw-r--r-- 1 root root     874 Feb 10 08:26  brcmfmac43430-sdio.raspberrypi,3-model-b.txt
lrwxrwxrwx 1 root root      29 Feb 10 08:26  brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt
lrwxrwxrwx 1 root root      29 Feb 10 08:26  brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43455-sdio.bin -> ../cypress/cyfmac43455-sdio.bin
lrwxrwxrwx 1 root root      36 Feb 10 08:26  brcmfmac43455-sdio.clm_blob -> ../cypress/cyfmac43455-sdio.clm_blob
-rw-r--r-- 1 root root    2510 Feb 10 08:26 'brcmfmac43455-sdio.MINIX-NEO Z83-4.txt'
lrwxrwxrwx 1 root root      49 Feb 10 08:26  brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt -> brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
-rw-r--r-- 1 root root    1884 Feb 10 08:26  brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
-rw-r--r-- 1 root root    1883 Feb 10 08:26  brcmfmac43455-sdio.raspberrypi,4-model-b.txt
lrwxrwxrwx 1 root root      44 Feb 10 08:26 'brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model B.txt' -> brcmfmac43455-sdio.raspberrypi,4-model-b.txt
-rw-r--r-- 1 root root  623304 Feb 10 08:26  brcmfmac4350c2-pcie.bin
-rw-r--r-- 1 root root  626140 Feb 10 08:26  brcmfmac4350-pcie.bin
lrwxrwxrwx 1 root root      30 Feb 10 08:26  brcmfmac4354-sdio.bin -> ../cypress/cyfmac4354-sdio.bin
lrwxrwxrwx 1 root root      35 Feb 10 08:26  brcmfmac4354-sdio.clm_blob -> ../cypress/cyfmac4354-sdio.clm_blob
-rw-r--r-- 1 root root  557056 Feb 10 08:26  brcmfmac43569.bin
lrwxrwxrwx 1 root root      30 Feb 10 08:26  brcmfmac4356-pcie.bin -> ../cypress/cyfmac4356-pcie.bin
lrwxrwxrwx 1 root root      35 Feb 10 08:26  brcmfmac4356-pcie.clm_blob -> ../cypress/cyfmac4356-pcie.clm_blob
-rw-r--r-- 1 root root    2515 Feb 10 08:26  brcmfmac4356-pcie.gpd-win-pocket.txt
lrwxrwxrwx 1 root root      30 Feb 10 08:26  brcmfmac4356-sdio.bin -> ../cypress/cyfmac4356-sdio.bin
lrwxrwxrwx 1 root root      35 Feb 10 08:26  brcmfmac4356-sdio.clm_blob -> ../cypress/cyfmac4356-sdio.clm_blob
-rw-r--r-- 1 root root    2610 Feb 10 08:26  brcmfmac4356-sdio.vamrs,rock960.txt
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac43570-pcie.bin -> ../cypress/cyfmac43570-pcie.bin
lrwxrwxrwx 1 root root      36 Feb 10 08:26  brcmfmac43570-pcie.clm_blob -> ../cypress/cyfmac43570-pcie.clm_blob
-rw-r--r-- 1 root root  633817 Feb 10 08:26  brcmfmac4358-pcie.bin
-rw-r--r-- 1 root root  595472 Feb 10 08:26  brcmfmac43602-pcie.ap.bin
-rw-r--r-- 1 root root  635449 Feb 10 08:26  brcmfmac43602-pcie.bin
-rw-r--r-- 1 root root 1105361 Feb 10 08:26  brcmfmac4366b-pcie.bin
-rw-r--r-- 1 root root 1120971 Feb 10 08:26  brcmfmac4366c-pcie.bin
-rw-r--r-- 1 root root  623448 Feb 10 08:26  brcmfmac4371-pcie.bin
-rw-r--r-- 1 root root  479232 Feb 10 08:26  brcmfmac4373.bin
lrwxrwxrwx 1 root root      30 Feb 10 08:26  brcmfmac4373-sdio.bin -> ../cypress/cyfmac4373-sdio.bin
lrwxrwxrwx 1 root root      35 Feb 10 08:26  brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob
lrwxrwxrwx 1 root root      31 Feb 10 08:26  brcmfmac54591-pcie.bin -> ../cypress/cyfmac54591-pcie.bin
lrwxrwxrwx 1 root root      36 Feb 10 08:26  brcmfmac54591-pcie.clm_blob -> ../cypress/cyfmac54591-pcie.clm_blob

Below is what I had prior to the update, per my btfs snapshot:

$ ls -l

total 16636
lrwxrwxrwx 1 root root      17 Dec 20 21:48  BCM-0a5c-6410.hcd -> BCM-0bb4-0306.hcd
-rw-r--r-- 1 root root   54734 Dec 20 21:48  BCM-0bb4-0306.hcd
-rw-r--r-- 1 root root  269595 Dec 20 21:48  bcm4329-fullmac-4.bin
-rw-r--r-- 1 root root   96224 Dec 20 21:48  bcm43xx-0.fw
-rw-r--r-- 1 root root     180 Dec 20 21:48  bcm43xx_hdr-0.fw
-rw-r--r-- 1 root root  397312 Dec 20 21:48  brcmfmac43143.bin
-rw-r--r-- 1 root root  385067 Dec 20 21:48  brcmfmac43143-sdio.bin
-rw-r--r-- 1 root root  348160 Dec 20 21:48  brcmfmac43236b.bin
-rw-r--r-- 1 root root  455745 Dec 20 21:48  brcmfmac43241b0-sdio.bin
-rw-r--r-- 1 root root  403855 Dec 20 21:48  brcmfmac43241b4-sdio.bin
-rw-r--r-- 1 root root  408682 Dec 20 21:48  brcmfmac43241b5-sdio.bin
-rw-r--r-- 1 root root  479232 Dec 20 21:48  brcmfmac43242a.bin
-rw-r--r-- 1 root root  253748 Dec 20 21:48  brcmfmac4329-sdio.bin
-rw-r--r-- 1 root root  222126 Dec 20 21:48  brcmfmac4330-sdio.bin
-rw-r--r-- 1 root root    1509 Dec 20 21:48  brcmfmac4330-sdio.Prowise-PT301.txt
-rw-r--r-- 1 root root  400864 Dec 20 21:48  brcmfmac43340-sdio.bin
-rw-r--r-- 1 root root    1693 Dec 20 21:48  brcmfmac43340-sdio.meegopad-t08.txt
-rw-r--r-- 1 root root    1724 Dec 20 21:48  brcmfmac43340-sdio.pov-tab-p1006w-data.txt
-rw-r--r-- 1 root root  451566 Dec 20 21:48  brcmfmac4334-sdio.bin
-rw-r--r-- 1 root root  569291 Dec 20 21:48  brcmfmac4335-sdio.bin
-rw-r--r-- 1 root root  202107 Dec 20 21:48  brcmfmac43362-sdio.bin
-rw-r--r-- 1 root root     803 Dec 20 21:48  brcmfmac43362-sdio.cubietech,cubietruck.txt
lrwxrwxrwx 1 root root      43 Dec 20 21:48  brcmfmac43362-sdio.lemaker,bananapro.txt -> brcmfmac43362-sdio.cubietech,cubietruck.txt
-rw-r--r-- 1 root root  562183 Dec 20 21:48  brcmfmac4339-sdio.bin
-rw-r--r-- 1 root root  382455 Dec 20 21:48  brcmfmac43430a0-sdio.bin
-rw-r--r-- 1 root root     951 Dec 20 21:48  brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt
-rw-r--r-- 1 root root     989 Dec 20 21:48 'brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt'
-rw-r--r-- 1 root root     875 Dec 20 21:48  brcmfmac43430-sdio.AP6212.txt
-rw-r--r-- 1 root root  388739 Dec 20 21:48  brcmfmac43430-sdio.bin
-rw-r--r-- 1 root root     928 Dec 20 21:48  brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt
-rw-r--r-- 1 root root     831 Dec 20 21:48  brcmfmac43430-sdio.MUR1DX.txt
-rw-r--r-- 1 root root     874 Dec 20 21:48  brcmfmac43430-sdio.raspberrypi,3-model-b.txt
lrwxrwxrwx 1 root root      29 Dec 20 21:48  brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt
lrwxrwxrwx 1 root root      29 Dec 20 21:48  brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt
-rw-r--r-- 1 root root  488193 Dec 20 21:48  brcmfmac43455-sdio.bin
-rw-r--r-- 1 root root    2510 Dec 20 21:48 'brcmfmac43455-sdio.MINIX-NEO Z83-4.txt'
lrwxrwxrwx 1 root root      49 Dec 20 21:48  brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt -> brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
-rw-r--r-- 1 root root    1864 Dec 20 21:48  brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
-rw-r--r-- 1 root root    1863 Dec 20 21:48  brcmfmac43455-sdio.raspberrypi,4-model-b.txt
-rw-r--r-- 1 root root  623304 Dec 20 21:48  brcmfmac4350c2-pcie.bin
-rw-r--r-- 1 root root  626140 Dec 20 21:48  brcmfmac4350-pcie.bin
-rw-r--r-- 1 root root  605388 Dec 20 21:48  brcmfmac4354-sdio.bin
-rw-r--r-- 1 root root  557056 Dec 20 21:48  brcmfmac43569.bin
-rw-r--r-- 1 root root  648770 Dec 20 21:48  brcmfmac4356-pcie.bin
-rw-r--r-- 1 root root    2515 Dec 20 21:48  brcmfmac4356-pcie.gpd-win-pocket.txt
-rw-r--r-- 1 root root  526383 Dec 20 21:48  brcmfmac4356-sdio.bin
-rw-r--r-- 1 root root  550333 Dec 20 21:48  brcmfmac43570-pcie.bin
-rw-r--r-- 1 root root  633817 Dec 20 21:48  brcmfmac4358-pcie.bin
-rw-r--r-- 1 root root  595472 Dec 20 21:48  brcmfmac43602-pcie.ap.bin
-rw-r--r-- 1 root root  635449 Dec 20 21:48  brcmfmac43602-pcie.bin
-rw-r--r-- 1 root root 1105361 Dec 20 21:48  brcmfmac4366b-pcie.bin
-rw-r--r-- 1 root root 1120971 Dec 20 21:48  brcmfmac4366c-pcie.bin
-rw-r--r-- 1 root root  623448 Dec 20 21:48  brcmfmac4371-pcie.bin
-rw-r--r-- 1 root root  479232 Dec 20 21:48  brcmfmac4373.bin
-rw-r--r-- 1 root root  457994 Dec 20 21:48  brcmfmac4373-sdio.bin

Quite different.

372

The brcmfmac43455’s are the files that affect you.

373

Below are the current links that pacman complained about already existing on the file system, and that I manually deleted. I suspect something here as this was the only “non-standard” event I experienced. It caused me to do something I do not normally do. Since the normal updates did not result in a working wifi, the things done out of the ordinary would likely contain the “fix”.

lrwxrwxrwx 1 root root 31 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac43012-sdio.bin -> ../cypress/cyfmac43012-sdio.bin
lrwxrwxrwx 1 root root 36 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac43012-sdio.clm_blob -> ../cypress/cyfmac43012-sdio.clm_blob
lrwxrwxrwx 1 root root 36 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac43430-sdio.clm_blob -> ../cypress/cyfmac43430-sdio.clm_blob
lrwxrwxrwx 1 root root 44 Feb 10 08:26 '/usr/lib/firmware/brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model B.txt' -> brcmfmac43455-sdio.raspberrypi,4-model-b.txt
lrwxrwxrwx 1 root root 36 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob -> ../cypress/cyfmac43455-sdio.clm_blob
lrwxrwxrwx 1 root root 35 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac4354-sdio.clm_blob -> ../cypress/cyfmac4354-sdio.clm_blob
lrwxrwxrwx 1 root root 35 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac4356-pcie.clm_blob -> ../cypress/cyfmac4356-pcie.clm_blob
lrwxrwxrwx 1 root root 35 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac4356-sdio.clm_blob -> ../cypress/cyfmac4356-sdio.clm_blob
-rw-r--r-- 1 root root 2610 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac4356-sdio.vamrs,rock960.txt
lrwxrwxrwx 1 root root 36 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac43570-pcie.clm_blob -> ../cypress/cyfmac43570-pcie.clm_blob
lrwxrwxrwx 1 root root 35 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac4373-sdio.clm_blob -> ../cypress/cyfmac4373-sdio.clm_blob
lrwxrwxrwx 1 root root 31 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac54591-pcie.bin -> ../cypress/cyfmac54591-pcie.bin
lrwxrwxrwx 1 root root 36 Feb 10 08:26 /usr/lib/firmware/brcm/brcmfmac54591-pcie.clm_blob -> ../cypress/cyfmac54591-pcie.clm_blob
374

I went back to look the snapshot before I rolled back the linux-firmware, first time. I wanted to see what a “non-working” updated firmware looked like. And I do not see any different in the 43455 files from when wifi did not work and with wifi working.

I am stumped as to what “fixed” this firmware issue for me.

375

I have switched over to using my arm-testing as it is still “broken”. I can switch back and forth between the two linux-firmware versions with the expected working and broken wifi to try an figure out what I can change to get wifi to work on the new firmware. I do not yet have an answer, still fiddling with it.

What I can say is, this device is not created with the new linux-firmware:

/sys/devices/platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/

From comparing journalctl messages, this device is not found by rfkill.

Edit: Some notes here for myself, messages that do not occur on my arm-testing install.

$ journalctl -b

Feb 13 15:48:21 roulette NetworkManager[652]: <info>  [1613252901.0693] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver brcmfmac)

Feb 13 15:48:23 roulette systemd[1]: systemd-rfkill.service: Succeeded.

rfkill module used 6 times, only 4 on arm-testing
$ lsmod | grep cfg80211

cfg80211              876544  1 brcmfmac
rfkill                 36864  6 cfg80211

dmesg | grep 80211

[   11.568890] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled

This change in /lib/firmware/brcmfmac43455-sdio.raspberrypi,4-model-b.txt

Old firmware:

boardflags3=0x44200100

New firmware:

boardflags3=0x48200100

is what “breaks” wifi in the new firmware. Edit this file and replace it with the setting from the old firmware and wifi works. See this link, the wifi section.

My arm-unstable install is somehow using /usr/lib/firmware/updates/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt which has the correct boardflags3 for the RPi4. The file supplied by linux-firmware has boardflags3 for the RPi3.

Now to find out how/why is it using the correct file when my arm-testing continues to use the incorrect file?

I found the inconsistency, how my arm-unstable seemed to be fixed. It is not. I managed to get some old /lib/firmware/brcm/ files in /lib/firmware/updates/brcm/ with my bind mount snafu. After manually removing all files from /lib/firmware/updates/brcm/ and reinstalling, my arm-unstable now behaves just as my arm-testing. Which is odd given my current understanding of the firmware loading. I would have thought any files in the updates/brcm/ directory would have been ignored.

@Darksky The problem with the current linux-firmware is exactly as stated above, the incorrect boardflags3 setting, it is set as an rpi3, not an rpi4. The wifi can not be properly discovered, so the device is not created.

2 Likes
376

I am pushing new kernels after a while but am posting first as there are a lot of changes and want members to read first before upgrading:

linux 5.10.16 is now in the linux-rpi4 package and I will be pushing this package to the testing and unstable branch to get as much testing done on it before the new upcoming images are released.

linux 5.11.0 is now in the linux-rpi4-mainline package and will be pushed to the unstable branch.

The 2 new raspberrypi-bootloader packages I will be pushing to the testing and unstable branch.

As requested to stop custom config.txt and cmdline.txt files in /boot from being over written on every upgrade I have removed them from the kernel initial install phase. The old kernel will remove them before these new kernels get installed but I have made provisions in the .install files to look for these files in their respective .pacsave files in /boot and restore them back otherwise it will create the 2 files with their default values.

So if you have custom config.txt and cmdline.txt and want to keep them do this one time procedure below before upgrading to get past this transition period. If you have not changed these files then do nothing and do a kernel upgrade as normal.

sudo cp /boot/cmdline.txt /boot/cmdline.txt.pacsave
sudo cp /boot/config.txt /boot/config.txt.pacsave

New upgraded files:

linux-rpi4 5.10.16-1
linux-rpi4-headers 5.10.16-1
linux-rpi4-mainline 5.11.0-1
linux-rpi4-mainline headers-5.11.0-1
raspberrypi-bootloader 20210216-1
raspberrypi-bootloader-x 20210216-1
3 Likes
377

I made the .pacsave copies and then performed the update, including a mainline kernel update. However the copies were not restored. So I then switched to the linux-rpi4 kernel and this time the copies were restored, see below.

:: Processing package changes...
(1/2) removing linux-rpi4-mainline-headers                                                             [#############################################################] 100%
(2/2) removing linux-rpi4-mainline                                                                     [#############################################################] 100%
(1/2) installing linux-rpi4                                                                            [#############################################################] 100%
===> Restoring old cmdline.txt file...
===> Restoring old config.txt file...

I grabbed this after the switch back to the mainline, unfortunately I did not capture this from the first update. I did not know to look for it.

:: Processing package changes...
(1/2) removing linux-rpi4-headers                                                                      [#############################################################] 100%
(2/2) removing linux-rpi4                                                                              [#############################################################] 100%
(1/2) installing linux-rpi4-mainline                                                                   [#############################################################] 100%
===> Restoring old cmdline.txt file...
===> Restoring old config.txt file...

If it seems unlikely that it did not work the first time, I would not argue… been a very long day.

I really appreciate this change, thank you!

378

No external sound card hifiberry after linux-rpi4-rc 5.11.rc6-1 to linux-rpi4-mainline 5.11.0-1.
But aplay -l is correct with linux-rpi4-rc 5.11.rc6-1 and linux-rpi4 5.10.16-1

 aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: Headphones [bcm2835 Headphones], périphérique 0: bcm2835 Headphones [bcm2835  Headphones]
Sous-périphériques: 8/8
Sous-périphérique #0: subdevice #0
Sous-périphérique #1: subdevice #1
Sous-périphérique #2: subdevice #2
Sous-périphérique #3: subdevice #3
Sous-périphérique #4: subdevice #4
Sous-périphérique #5: subdevice #5
Sous-périphérique #6: subdevice #6
Sous-périphérique #7: subdevice #7
carte 1: sndrpihifiberry [snd_rpi_hifiberry_dacplus], périphérique 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
carte 2: vc4hdmi0 [vc4-hdmi-0], périphérique 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM vc4-hdmi-hifi-0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
carte 3: vc4hdmi1 [vc4-hdmi-1], périphérique 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM vc4-hdmi-hifi-0]
Sous-périphériques: 1/1
379

I have updated the linux-rpi4 and linux-rpi4-mainline kernels as they both had changes today that look important. They have been pushed to the testing and unstable branch when the mirrors sync.

Added missing IPV6 modules
Added display drm modules
Reverted i2c patch on kernel 5.11.0
Also I had a request on gitlab to add rpi-cm4 support

New kernels:

linux-rpi4 5.10.16-2
linux-rpi4-headers 5.10.16-2
linux-rpi4-mainline 5.11.0-2
linux-rpi4-mainline-headers 5.11.0-2
1 Like
380

I am stumped on this at the moment. All of the modules are enabled in the kernel. Try the new kernels I just posted above.

1

2

Added:

They did mess with the code 8 days ago. Maybe they put it to sleep permanently!

https://github.com/raspberrypi/linux/commit/656dc8295f67e3c4c475f76f10426fc358a952d0

381

I updated the mainline kernel and /dev/i2c-1 is back, my fan is operational again.

1 Like
382

The sound is back with 5.11.0-2 :slightly_smiling_face:
Another problem the cmdline.txt hasn’t the bluetooth modification ttyAMA0/serial0.
Tested with the last kernel after removing the old file (and .pacsave).

root=LABEL=ROOT_MNJRO rw rootwait console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 elevator=noop usbhid.mousepoll=8 snd-bcm2835.enable_compat_alsa=0 audit=0
383

What ever you had for cmdline.txt the 2 new kernels will not be replaced as I tried to explain above when I first posted the new kernels.

The .txt files has been removed so they will not be installed. This change was done so the config files do not get replaced on every kernel upgrade to help with people with custom configs.

There is a process after the package install that checks if .txt or .pacsave files are present. Depending on which is present it will either keep the config.txt file or move the .pacsave to .txt respectively or if none is present it will create new default .txt files.

So while using the new kernels you can make your custom configs within the .txt files and they will stay intact after each new kernel upgrade in the future.

If you go back to an older kernel before the change and switch back to the newer kernel with the change the older kernel when it gets uninstalled will remove config.txt and cmdline.txt as these files are part of it’s packages and the new kernel in it’s post install process will not see the files and will install the default .txt files.

384

Disregard that last post. I am leaving it there though as it is a good explanation. I found where I forgot to change to serial0 in post_upgrade(). I had only made the changes in post_install().

Thanks for pointing this out.

Uggg another compile and push on 2 kernels.

385

Thanks to @tartanpion running into an issue I made an correction involving the post_upgrade () section in the .INSTALL had not been changed to serial0 for the new packages code change for bluetooth to work. New packages pushed to testing and unstable:

linux-rpi4 5.10.16-3
linux-rpi4-headers 5.10.16-3
linux-rpi4-mainline 5.11.0-3
linux-rpi4-mainline-headers 5.11.0-3
386

@Darksky I ran across this link which I believe provides context for the serial0 change we made. I noticed on my SD image, that I used to help debug my A/V jack issue, had a /proc/cmdline that included ttyS0 rather than ttyAMA0.

Note: `/dev/serial0` and `/dev/serial1` are symbolic links which point to either `/dev/ttyS0` or `/dev/ttyAMA0`.
387

That is pretty much what the RPi people said when I asked when ttyAMA0 quit working in cmdline.txt. Something about some aliases and said ttyAMA0 was out dated in cmdline.txt. But in the end ttyAMA0 is used so it looks like from my end they are circling around the block when it’s easier to walk across the street. But what do I know…

388

I’ve seen that Archlinux is going to move to zstd for mkinitcpio :

https://archlinux.org/news/moving-to-zstandard-images-by-default-on-mkinitcpio/

Do you plan to do the same ?

389

edit:

I mis-read they are going to initramfs images with zst; not packages.

Looks like arch-arm has patched their mkinitcpio 30-1 so it still uses gzip. Thinking about it more they supposrt a lot of arm boards and some use kernels versions less than 5.10.

https://archlinuxarm.org/packages/any/mkinitcpio/files/0001-use-gzip-for-compression-by-default.patch

390

I have pushed the latest linux-rpi4 5.10.17 kernel files to the unstable branch when the mirrors sync.

Nothing new with our raspberrypi-bootloader packages in their git as of this post.

linux-rpi4 5.10.17-1
linux-rpi4-headers 5.10.17-1