The sound is back with 5.11.0-2 
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=0What 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.
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.
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@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`.
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ā¦
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 ?
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.
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-1kernel-5.11 + kms, firefox freeze.
kernel-5.10 +fkms, firefox smoothly.
ps. plasma
I do not know ehen RPi will add it to their tree but keep an eye on it and let me know when it gets fixed. I will hold off until we know.
Thanks. No telling when they will add it to their tree. They seem to be dragging their feet on 5.10 and 5.11 also.
The latest linux-rpi4 and raspberrypi-bootloader packages have been pushed to the unstable branch when it syncs.
Kernel modifications made for @johntdavis84 and @nielsblack moving out and in modules with the kernel for their respective devices.
linux-rpi4 5.10.20-1
linux-rpi4-headers 5.10.20-1
raspberrypi-bootloader 20210225-1
raspberrypi-bootloader-x 20210225-1
Updated and rebooted without issue. journalctl and dmesg look clear.
Thanks! What does āout and back inā mean?
I did not say that.
In your case this so you can build the DKMS module that gets placed in /usr/lib/modules/5.10.20-1-MANJARO-ARM/updates which gets picked up first:
CONFIG_USB_RTL8152=y ==> CONFIG_USB_RTL8152=m
I wonder if this is something we want to try on kernel 5.12?
https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.12-Clang-LTO-Merged