That patch looks to be @ a year old. Although I do not see that error here I do see it in a lot of dmesgâs posted when people have other various issues and it shows up so I do not know what to think about it. Wonder if it is just running a check of sorts when something else get enabled.
Plasma depends on pulseaudio and gstreamer, so I have not tried. I expect that once all the parts are there and working, the Plasma packages will switch⌠so I wait.
I finally remembered to remove /boot/{cmdline,config}.txt prior to updating linux-rpi-mainline today, so I got a copy of the latest iterations of the defaults. However, I noted while watching the update that only config.txt was mentioned in the upgrade messages:
Concerning the rpi-eeprom updates, I think they are overwriting /etc/default/rpi-eeprom-update. I just changed the file from critical to stable, pretty sure I have set that several times in the past⌠but I am old, I have slept, and have too many installs to be positive.
And to get the most current version, we want it set to âstableâ, correct?
$ rpi-eeprom-update -a
BOOTLOADER: up to date
CURRENT: Thu Apr 29 04:11:25 PM UTC 2021 (1619712685)
LATEST: Thu Apr 29 04:11:25 PM UTC 2021 (1619712685)
RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
The package updated but no newer version downloaded⌠odd.
To get their current what they consider stable yes. Eventually they will move a version from stable â critical at some point. The current critical version will be used if one has to reflash using a recovery image if something goes haywire so the critical version is their go to version to weed out possible issues with the other newer versions as I understand it.
I noticed today some where in time I had accidently pushed an older rpi-eeprom package to core instead of community so I removed it today to not have 2 versions in the repo; so probably a result of that.
$ sudo modprobe sha2_ce
modprobe: ERROR: could not insert 'sha2_ce': No such device
I have tried booting with both UEFI and firmware, same error. If you can not load it either, would you consider changing sha2_ce=m to sha2_ce is not set in the new rc kernel?
ARM64 Accelerated Cryptographic Algorithms â SHA-224/SHA-256 digest algorithm
I do not think it is implemented in the RPi4 and may be the cause of my issue with booster.
I have no clue when the 5.13.y tree will hit the RPi repo but would you consider making the changes in the current linux-mainline kernel and recompiling the packages and test if it works. The module CONFIG you want to disable is:
# CONFIG_CRYPTO_SHA2_ARM64_CE is not set
I do not see SHA-224 anywhere in the config. Maybe activate it via make menuconfig it it exists.
git clone https://gitlab.manjaro.org/manjaro-arm/packages/core/linux-rpi4-mainline.git
cd linux-rpi4-mainline
export MAKEFLAGS="-j4"
#make changes in the config file and generate new cheksums and build with:
makepkg -g >> PKGBUILD
makepkg -si
The kernel rebuild removed the sha2_ce module and now the boot process does not abort, it simply hangs. I think it is waiting for something that is not occurring, the RPi4 does respond to ctrl-alt-del at that point, so progress.
Edit: I have now been successful booting with booster.
