Today I was notified by the RPi people that my issue was resolved I opened regarding non working usb ports with the pi4 8G boards with the 5.8-rc kernel. When I first opened the issue the kernel was still in the rc status but now it has been upgraded to 5.8.1. Because of this the linux-rpi4-mainline 5.7.9-1 kernel/headers packages has now been upgraded in the unstable branch (when the mirrors sync):
In all of the new kernel packages here I have added “usbhid.mousepoll=8” to /boot/cmdline.txt to help with the mouse refresh rate which will help with some mouses that do not play well trying to use it’s default with the linux default config. The number 8 can be increased (or decreased) to your liking with the mouse movement.
Today the RPi folks bumped their kernel versions up to match kernel.org’s version updates over last weekend so I pushed the new kernel packages to the unstable branch. (when the mirrors sync)
With the linux-rpi4 kernel the RPi people added AppArmor support. If you want it enabled at boot you will have to add lsm=“apparmor” to the line in the /boot/cmdline.txt file.
configs: Include AppArmor support
AppArmor security has been a long-requested feature.
This commit adds the config settings necessary to allow
it to be enabled at boot time using the kernel command
line (cmdline.txt) - just include:
lsm="apparmor"
The commit also includes a few settings to give better
control over processes or containers.
Signed-off-by: Jean-Christophe Berthon <jcberthon@users.noreply.github.com>
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
Additional:
I also just pushed the 2 upgraded raspberrypi-bootloader packages to the unstable branch.
The RPi people add the 5.9.y tree to their github. I had a compile issue last night and opened an issue on their github and they had it fixed by the time I woke up. They also told me that they are aware of a few other issues and I will post an updated package when they are fixed. The issues they are aware of I believe does not affect most of us. Maybe we can find some other issues to make this kernel stable when it gets out of the -rc stage:
“Be aware that 5.9 has a lot of conflicts with downstream (as partial commits are appearing upstream). It’s in a state where you should be able to boot with working display, network and usb. But kms, codecs, camera, isp, vcsm are still being worked on and may not be functional currently.”
UPDATED 09-10-2020:
From looking at the commits this week it looks like they were working on their concerns that had above. They also upgraded to to kernel version to 5.9.0-rc4 to be inline with the current kernel.org version.
I guess you’re talking about 5.8.7 and not 5.9.7.
I wonder how to test the 5.9-rc3 and go back to 5.8.5 if it’s not ok. Could you please specify the procedure ?
Fat fingers here. It was supposed to be 5.9.y for their branch name (I corrected my post).
I tested the 5.9.0-rc3 here and it booted ok and every test I do here on a new kernel had no issues. I do not have a camera and by default we do not use kms because it is still listed as unstable.
If you want to switch back to 5.8.5-1install linux-rpi4-mainline in the unstable branch. Another option is install the linux-rpi4-mainline kernel/header packages from your pacman cache if you have not cleared them out. (/var/cache/pacman/pkg/)
Here is the latest linux-git 5.9.0-rc4-2 kernel packages. It looks like they have might fixed their concerns as mentioned above. They also found and fixed a bad patch for the wifi that upstream had accepted that would cause the wifi to stop working. There is also a kernel bump to match upstream and they added apparmor.
The RPi folks upgraded the other 2 kernels to match the current upstream versions today. They both now have apparmor also. Also the 2 raspberrypi-bootloader packages has been upgraded. I have built and pushed all these packages to the unstable branch when the mirrors sync.
I do not make those decisions and really do not know what it would involve.
By the way I have messed around and come up with a config for the upstream kernel (not rpi kernel) if you are up to really venture out and test it. I am waiting for Strit to test it and give some feed back at the moment. It is the latest 5.9.0-rc5 upstream commited yesterday.
All of the above kernels now have rspamd enabled if you are running a mail server.
The linux-rpi4-mainline 5.8.12-1 and linux-rpi4-rc 5.9-rc7-1 kernels now have modules enabled for running anbox. It crashes on a lot of programs I installed but from talking to @Strit today he said that it is still in it’s infancy but is being pushed by the pinephone community with it’s developtment so hopefully soon things will start improving at a faster rate in the development:
Well this will be short lived. They upgraded all branches today again to be current with upstream. I will update the kernel names here when I get all kernel packages built and pushed.
UPDATED:
This is the new linux-rpi4-rc-5.9.rc8-2 re-compiled to use the SCHEDUTIL govenor that has been maximized for aarch64 starting in kernel 5.9
Actually the 5.8.13 came out 5 days ago but I missed it, so I did it yesterday. But yea a lot of compiling kernels. Actually yesterday I compiled 7 kernels. I maintain a 32bit repo for all pi’s for a satellite form with added and patched modules for dvb/atsc/dvbt that are not in the mainline kernel also. So now 10 kernel compiles in 2 days. But it is what it is… lol
What is new is they enabled but it is not active to linux-rpi4 5.4.70 “Memory CGroup swap controller” for docker. It is supposed to stop this:
$ docker info
WARNING: No swap limit support
To make it active add this to /boot/cmdline.txt"
swapaccount=1
ADDED:
I forgot to mention I enabled anbox support in the linux-rpi4 5.4.70-1 above. I had not done it because the arch wiki said for kernels <= 5.7. I saw today in it’s .config where it looked like it could be enabled so I tried it and it seems to work at least as good as the other kernels, It is too flakey for me in it’s current stage of development.
I also forgot to post a link to the latest linux-rpi4-rc kernel:
