iron-alpine VS linux

Look into implementing container vulnerability scanning in your build pipeline. Iron alpine is another possibility to reduce risk. https://github.com/ironpeakservices/iron-alpine

If hardening is needed or not depends on your requirements. For a standard use case running a container based on default Alpine image should be secure enough. If you feel, you need to increase security a bit more - and are open to take the slightly increased risk of incompatibility with your setup aka effort - you may use all / parts of the additional hardening steps. See also https://github.com/ironpeakservices/iron-alpine for an actively maintained repo.

I'm looking for something like this, but for ansible. I'v been searching for a ansible hardning script for alpine, but only thing i have found so far is iron-alpine docker container. https://github.com/ironpeakservices/iron-alpine

Fan control generally involves hysteresis. This means a cooling fan turns on at one temperature, and then turns off once temperature has fallen to another lower temperature. This avoids cycling the fan on and off too much. The difference between those two temperatures is hysteresis. The default hysteresis is 10°C and maybe the fan never manages to cool the CPU to 45°C. A parameter has been added to change hysteresis: https://github.com/raspberrypi/linux/commit/fa390133fd17f2cc6aa5a7d2e472c073a1115fe1

I see that the PR against the Raspberry Pi linux repo is out [0]. Interestingly they are introducing a BCM2712 defconfig with a 64k default page size.

[0] - https://github.com/raspberrypi/linux/pull/5618

and can grab their patched kernel source here ( use the dtbs and overlays and kernel from your compiled version)

Also was your pi issue related to this? https://github.com/raspberrypi/linux/issues/3381 or what do you mean jittery, unstable?

Could be related to the driver load order/blacklisting (https://github.com/raspberrypi/linux/issues/435) Or couple of people report configuring the dtoverlay=imx477 in the boot config helped (https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README)

thanks, I also found this: https://github.com/raspberrypi/linux/issues/5398

And ready! :)

> It is the most basic task for Linux computer...

Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited:

https://github.com/raspberrypi/linux/issues/3010

Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless.

https://www.discomp.eu/wireless-minipci-cards_c14501412.html