sudo dpkg -i chromium_89.0.4389.114-1~deb10u1_arm64.deb chromium-common_89.0.4389.114-1~deb10u1_arm64.deb chromium-sandbox_89.0.4389.114-1~deb10u1_arm64.deb

Unfortunately the output was:

Selecting previously unselected package chromium.
(Reading database ... 106751 files and directories currently installed.)
Preparing to unpack chromium_89.0.4389.114-1~deb10u1_arm64.deb ...
Unpacking chromium (89.0.4389.114-1~deb10u1) ...
Selecting previously unselected package chromium-common.
Preparing to unpack chromium-common_89.0.4389.114-1~deb10u1_arm64.deb ...
Unpacking chromium-common (89.0.4389.114-1~deb10u1) ...
Selecting previously unselected package chromium-sandbox.
Preparing to unpack chromium-sandbox_89.0.4389.114-1~deb10u1_arm64.deb ...
Unpacking chromium-sandbox (89.0.4389.114-1~deb10u1) ...
dpkg: dependency problems prevent configuration of chromium:
 chromium depends on libevent-2.1-6 (>= 2.1.8-stable); however:
  Package libevent-2.1-6 is not installed.
 chromium depends on libicu63 (>= 63.1-1~); however:
  Package libicu63 is not installed.
 chromium depends on libjsoncpp1 (>= 1.7.4); however:
  Package libjsoncpp1 is not installed.
 chromium depends on libminizip1 (>= 1.1); however:
  Package libminizip1 is not installed.
 chromium depends on libre2-5 (>= 20160901); however:
  Package libre2-5 is not installed.
 chromium depends on libvpx5 (>= 1.6.0); however:
  Package libvpx5 is not installed.
 chromium depends on libxslt1.1 (>= 1.1.25); however:
  Package libxslt1.1 is not installed.

dpkg: error processing package chromium (--install):
 dependency problems - leaving unconfigured

This downgrading stuff is all a bit new to me. Am I doing anything wrong?

I assume I was just meant to downgrade chromium ... not Devuan also?!

(I'm going to apt purge and apt autoremove to get rid of all this.)

PS: I notice the Devuan arm64 version of chromium ticked over to 99.0.4844.84-1~deb11u1 ... but it is still smashes those stacks.

dtoverlay=gpio-fan,gpiopin=14,temp=60000

The fan starts when the temp is 60 degC or above.
The fan cuts out when the temp drops to/below 60 - 10 degC.

Just thought I'd answer my own question about betting the official case + official fan combination to work on an RPi 4B ...

Edit file:

/boot/config.txt

and add (at the bottom):

dtoverlay=gpio-fan,gpiopin=14,temp=50000

This assumes the fan GPIO lead is plugged into GPIO14; it will turn the fan off when the CPU gets to/below 50 degrees Celsius.

Tested and works on the  rpi-4-devuan-chimaera-5.10.95-v8-ext4-2022-03-27.zip installation.

Edit:  Once the fan is off, it stays off until the temp reaches 50 + 10 deg C.  Not sure if that can be adjusted.

I've been using the following:

chromium_90.0.4430.212-1_arm64.deb
chromium-common_90.0.4430.212-1_arm64.deb
chromium-sandbox_90.0.4430.212-1_arm64.deb

You can find them here

I hit this ARM64 Chromium bug when I upgraded from Beowulf (debian:buster) to Chimaera (debian:bullseye).

It seems to be a Chromium bug [Bug#1004368] introduced due to something about the differences between the "clang-11" vis the "clang-13" or "clang-14" compilers. It's over my head...

Since I knew the Beowulf version had worked, I tried downgrading it back to the Beowulf/Buster version.  And it works...

You might try manually downloading the 89.0.4389.114-1 version of chromium and chromium-common from the repositories:
  https://packages.debian.org/buster/arm6 … m/download
  https://packages.debian.org/buster/arm6 … n/download

And then manually installing them.

First:  A test ( --simulate ) run using the downloded files:
  sudo dpkg --simulate -i  chromium_89.0.4389.114-1~deb10u1_arm64.deb chromium-common_89.0.4389.114-1~deb10u1_arm64.deb

And then if it looks good, re-run it without the --simulate.  :-)

You might want to apt-hold chromium until they get this straightened out, or apt will keep trying to upgrade to the current version.  It looks like there is a 99.0.4844.84 ( vis the .74 which has our stack-smashing problem) in the works.  Hopefully this will fix our problem ?  [ Yes, '?' ]

Good Luck.

FYI, I tried:
  devuan_chimaera_4.0.0_arm64_rpi4.img.zip
and then:
  rpi-4-devuan-chimaera-5.10.95-v8-ext4-2022-03-27.zip

Standard installation + xfce4 + xfce4-goodies + chromium (+ others)

So far they both work well ...  except for Chromium:
chromium/stable,stable-security,now 99.0.4844.74-1~deb11u1 arm64  (chimaera-5.10.95)

Chromium doesn't even get to the GUI:
...
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[5901:5901:0329/135843.805763:ERROR:gpu_process_host.cc(972)] GPU process exited unexpectedly: exit_code=6
...

But it looks to be somewhat similar to a recent upstream Debian bug with Chromium:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1004368

So I won't report it as a Devuan bug.

Anyone concur?  (Or found a workaround?)
[Edit: Hmmm ... probably not related to the Debian bug.]

Chimaera:
devuan_chimaera_4.0.0_arm64_rpi3.img.zip           19-Oct-2021 01:26    593M
devuan_chimaera_4.0.0_arm64_rpi4.img.zip           19-Oct-2021 03:37    589M
devuan_chimaera_4.0.0_armel_rpi0.img.zip            19-Oct-2021 05:47    502M
devuan_chimaera_4.0.0_armel_rpi1.img.zip            19-Oct-2021 05:47    502M
devuan_chimaera_4.0.0_armhf_rpi2.img.zip            19-Oct-2021 02:31    494M
devuan_chimaera_4.0_arm64_pool1.iso                  03-Dec-2021 01:40      4G

How can I get the fan-cpu temperature control working after installation?  (Like how it works in raspi-config.)

Those Devuan builds are very well crafted and (in my case) have replaced Raspbian (32bit Buster and 64bit Beta). The 64bit Raspbian does (as per today) not have a working hardware accelerated X server, hardware accelerated web browser (I am using chromium), and also no hardware video decoding (for almost two years)... Devuan has all of it... I am impressed.

If testing or some other form of contribution or feedback is needed, let me know.

-Alex

https://github.com/pyavitz/rpi-img-builder
https://github.com/pyavitz/debian-image-builder

Cheers

>They need testing: https://github.com/pyavitz/binary/releases/tag/images

Here to tell you that the  rpi-devuan-chimaera-5.10.76-ext4-2021-10-30.img.xz  image worked a charm for my RaspberryPi Zero W stick.
I had to comment out the hardline lan eth0 stanza before the wifi worked, but after that it worked well.
Kudos to you on providing those images. Thanks much.

I tried your rpi-img-builder, but it refused to install/run on my Ceres box, said 'The OS you are running is not supported'.   
I'll install Chimaera and try again.  I'd be good to generate my own images with your tool to help.

I'm not sure why eth0 would be interfering with it, considering it doesn't have an ethernet port, but I'm happy you got it working.

As for the builder, because of the different versions of GCC and compilers it currently supports and will support in the future, I ended up moving it over to Ubuntu as the Host. Debian and Devuan stable for example only support GCC-9/10. The builder currently supports GCC-8/9/10 and by the start of next year will also support GCC-11 and CLang-13. Basically, Ubuntu unfortunately provides more options.

If need be docker is an option?

You can also install depends manually on Debian and Devuan, but just know certain options won't be available to you. Such as Clang and anything gcc-8 related if building on Bullseye or Chimaera.

Here to tell you that the  rpi-devuan-chimaera-5.10.76-ext4-2021-10-30.img.xz  image worked a charm for my RaspberryPi Zero W stick.
I had to comment out the hardline lan eth0 stanza before the wifi worked, but after that it worked well.
Kudos to you on providing those images. Thanks much.

I tried your rpi-img-builder, but it refused to install/run on my Ceres box, said 'The OS you are running is not supported'.   
I'll install Chimaera and try again.  I'd be good to generate my own images with your tool to help.

I also included support for the Zero 2 W, but as I don't own the board yet, I'm not sure it boots and if it does, how well it works.