Where are PI 1 / 2 / 3 images

[AceTep]

Where are PI 1 / 2 / 3 images does image for pi 4 work on others? Also pi 4 doesnt have kali what happend?

[maxnet]

Pi 0/1/2 no longer supported. Pi 3 should work with Pi 4 image, but haven't tested it.

[AceTep]

Pi 0/1/2 no longer supported. Pi 3 should work with Pi 4 image, but haven't tested it.

Thanks! you know by any chance when will more os's be added to berryboot?

[createdbyjurand]

I have Pi 3 B+ berryboot-20201103-pi4.zip works, however there are problems with systems. Most of them freeze during boot or work very slow. I couldn't start OpenElec, LibreElec, Ubuntu, OpenSuse. After rollback to berryboot-20190612-pi0-pi1-pi2-pi3.zip everything started working fine.

[MichaIng]

The image should be named e.g. berryboot-XXXXYYZZ-rpi64. It supports all RPi models that have an 64-bit capable ARM, including down to RPi 2 v1.2 (when adjusting config.txt to use the shipped kernel in 64-bit mode). The problem is that it only contains the 64-bit kernel, means it cannot run the current Raspberry Pi OS 32-bit in a proper way, but only the Debian-based Raspberry Pi OS 64-bit that is still in beta stage. Otherwise several installers will see an ARMv8/aarch64 CPU (uname -m) while all system libraries and binaries are armv6hf and the APT repository (Raspbian) ships only armhf packages. It does not make much sense but only causes issues when running a 32-bit OS in 64-bit mode.

The same will be true for *ELEC, Ubuntu and OpenSUSE when using an armhf/32-bit OS image.

If RPi 0 - 2 (including the 64-bit capable RPi 2 v1.2) are not supported anymore, to avoid confusion, the old kernel + 32-bit mode option in the shipped config.txt could be probably removed to avoid confusion? https://github.com/maxnet/berryboot/blob/berryboot2018/output/config.txt

# 32-bit kernel for Pi 0 1 2
kernel=kernel_rpi0123_aufs.img

[pi3]
# 64-bit stuff for Pi 3
kernel=kernel_rpi64.img
arm_64bit=1

[pi4]
# 64-bit stuff for Pi 4
kernel=kernel_rpi64.img
arm_64bit=1

=>

# Load the 64-bit kernel in 64-bit mode
kernel=kernel_rpi64.img
arm_64bit=1

[maxnet]

LibreELEC doesn't want to be associated with Berryboot. For all other major operating systems aarch64 variants exist, and I see little point in supporting any 32-bit variants anymore.

[MichaIng]

For all other major operating systems aarch64 variants exist.

Raspberry Pi OS is only shipped as 32-bit Raspbian-based version currently, the 64-bit Debian-based version suffers a significant lack of features and is officially in beta stage, no available on any official download page.

I see little point in supporting any 32-bit variants anymore.

That is a different question and I can totally understand that with limited time that is a reasonable decision. However, it should be made clear, e.g. with renaming the file as I suggested, that this is a 64-bit kernel image to boot 64-bit OS images, i.e. the ones that are marked as such, like RPi_OS_2020.11_[64-bit].img (compared to Raspbian_Lite_2019.10.img192). Otherwise users will download "updated" images from here and wonder why this causes issues, then probably report the issues to the OS maintainers like LibreELEC which then blame Berryboot for it and don't want to be associated for such reasons 😉? No offence, such happens to us on another level (distro software implementations <> software manufacturers), but it makes sense to communicate limitations and supported cases clearly.

---

Not sure about the internals, but from the builds and configs for different device models it looks like it can be simply changed to an pi64 (already exist) and pi32 target separation, all using the current stable rpi-5.4.y branch (which supports both architectures). The build script would need to remove the arm_64bit=1 from the pi32 target config.txt, else there is no separation ([pi3]/[pi4]) required as the pi32 image runs on all RPi models and the pi64 image on 64-bit capable models only, of course, i.e. RPi 2 PCB v1.2 and up, which should be clear anyway. But if there are other aspects that cannot support RPi 32-bit, then the related targets could probably be removed and the example in the readme adjusted.

[h4de5]

i was trying to update my berryboot installation on my rpi3 with the newer rpi4 image - and noticed that there is no shared.tgz anymore, but the shared.img file. do I still need to copy the files into /mnt/shared like described here? https://github.com/maxnet/berryboot/issues/371#issuecomment-305324386

/apparently yes: unsquashfs -f -d /mnt/shared /boot/shared.img

[HinTak]

I have a pull for updating the readme, https://github.com/maxnet/berryboot/pull/674, after having done a 64-bit build.

The build is at https://github.com/HinTak/berryboot/releases

[HinTak]

Did a 32-bit build, plus adding all the patches needed to make it happen: https://github.com/HinTak/berryboot/releases

It is on a separate 32-bit branch, because the last change (in config.txt to revert back to 32-bit) is incompatible; but everything except the last incompatible change is in the pull https://github.com/maxnet/berryboot/pull/674 . The reason for going the trouble of doing a 32-bit build is that I suspect the scheduling bug in the respeaker driver is more trigger'able on the 64-bit kernel. I'll add a new doc at https://github.com/HinTak/RaspberryPi-Dev/ about how to customize Berryboot to include additional out-of-tree drivers in the next few days.

[HinTak]

The new doc is up as https://github.com/HinTak/RaspberryPi-Dev/blob/master/Customizing-Berryboot.md . If you find it useful, please feel free to donate using the links in https://hintak.github.io .

[macmpi]

Interesting 32bit platform may still have available solution. It seems your build is only with aufs patches on 32bit, whereas 64bit now relies on upstream overlay: why not having 32bit on overlay also?

[HinTak]

aufs is just the part of the older file name. I have sync'ed up the 32-bit build with the 64-bit build otherwise, and should behave the same. (other than the 32-bit build supporting older processors)

[edegraaff]

Support for the older pi types would be appreciated. I am using berryboot for a long long time, and i never realised i should save old berryboot images to secure my current systems. Please keep supporting the older pi's to. For projects that have a lot of disk ip this project is so valuable.

[edegraaff]

I have Pi 3 B+ berryboot-20201103-pi4.zip works, however there are problems with systems. Most of them freeze during boot or work very slow. I couldn't start OpenElec, LibreElec, Ubuntu, OpenSuse. After rollback to berryboot-20190612-pi0-pi1-pi2-pi3.zip everything started working fine.

Hi could you guide me here? i want to get my pi3b up and running with a new raspbian os with gui and without. In the past i used the standard berryboot with the 32bit raspbian os-es and i realy miss this, and want to tweak it so it is working. Berryboot did save me a lot of problems with sd cards. But now i am in the dark, so please enlight me ... Regards eelco

[AceTep]

I have Pi 3 B+ berryboot-20201103-pi4.zip works, however there are problems with systems. Most of them freeze during boot or work very slow. I couldn't start OpenElec, LibreElec, Ubuntu, OpenSuse. After rollback to berryboot-20190612-pi0-pi1-pi2-pi3.zip everything started working fine.

Hi could you guide me here? i want to get my pi3b up and running with a new raspbian os with gui and without. In the past i used the standard berryboot with the 32bit raspbian os-es and i realy miss this, and want to tweak it so it is working. Berryboot did save me a lot of problems with sd cards. But now i am in the dark, so please enlight me ... Regards eelco

I would recommend you using raspberry pi imager for rasbian install