Or just run raspbian on a Pi 3B, I've got 4 of them. omxplayer and other things that utilize the GPU make it quite livable.
On 3/1/21, Arnd Bergmann <a...@kernel.org> wrote: > On Mon, Mar 1, 2021 at 9:40 AM LinAdmin <linad...@quickline.ch> wrote: >> >> Bullseye 64 Bit does more or less work. There arise problems when you >> install a desktop with media players which deliver audio and should give >> output to the headphone plug and HDMI. >> >> I also had to find out that all 64 Bit versions of all distributions are >> much less powerful than the 32 Bit solution of the same software. The >> benchmark by T. Kaiser shows that some performances of 64 Bit are only >> about half of the values compared to the 32 Bit installation :-( >> >> Unfortunately the Bullseye 32 Bit kernel seems not to boot, because the >> support of USB looks broken: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981586 >> I just wonder why this bug has not got any answers? > > Presumably nobody has tried debugging it ;-) > > There is really no good reason to run a 32-bit /kernel/ on the Pi 4, > especially the version > with 8GB RAM. While the bug should get fixed in principle to make the > default kernel > work and allow installing a 32-bit distro, the best setup for this > machine (especially > the versions with less than 4GB) is to use an armhf user space with a > 64-bit kernel. > > You can get that today by installing a multiarch system starting with > an armhf install > (if you get its kernel to boot) and then running 'dpkg > --add-architecture arm64' to > allow installing the arm64 version of the kernel image. It would be > nice to actually > package the arm64 kernel image for armhf to make it easier to run this > way without > having to set up a multiarch system. This is how mipsel kernels work as > well, so > there is definitely precedence. > > Arnd > > -- ------------- Education is contagious.