Those of you who use BerryBoot for its ability to boot multiple OS and applications with just a single SD card may have been disappointed a while back after installing RasPlex 0.7.0, as that resulted in choppy/jittery playback for some videos. It is this problem that has now been fixed by the new release of BerryBoot.
BerryBoot’s ability to handle multiple boot setups is based on making all those Apps and OS use a kernel function set of BerryBoot, so as to redirect their boot partition access into the various squashfs-type image files. This method can fail though, when there is a big gap in kernel version between the kernel the apps were compiled for and the one used by BerryBoot, and that is what caused the incompatibility with RasPlex 0.7.0.
If you use the previous BerryBoot version with an active Internet connection you should be offered to upgrade ‘internally’, which is what I did with good results. This should preserve all installed OS, whether on SD card or external drives. But those who wish to start a new card, as well as new BerryBoot users, can download the new version as “berryboot-20150808-pi2-only.zip” from the BerryBoot home pages. (http://www.berryterminal.com/doku.php/berryboot)
This is the first time I’ve played with BerryBoot and it appears to be an impressive dual boot solution. I now have RasPlex and OpenELEC happily coexisting.
And it’s not just a ‘dual boot’ solution, but a true ‘multiple OS boot’ implementation.
I’m using a USB HDD for storage of the OS installed under BerryBoot, which include Fedora 21 Linux, Ubuntu 15.04 Mate Linux, Raspbian Linux, the latest OpenELEC and several versions of RasPlex (for reference purposes in my RasPlex beta testing).
The new Berryboot version has some major problems with my WiFi dongle, so I’ll either need to wait for an update or use the old version. Were the problems with the previous version really bad or will I be able to manage?
@Fireprufe15:
Some mp4 files would suffer horrible jitter/jerkiness. Not the usual bandwidth-induced stutter from when the software can’t cope with the bitrate, but some entirely different jerkiness having to do with an incorrect rendering method. Apparently this is due to a difference in some kernel lib routine, with the newer RasPlex version needing a kernel of the same generation it was made for (or newer), such as the kernel supplied with the newer BerryBoot version.
The problem did not affect all files. Some mp4 files with almost identical codec usage were not affected at all, so it is possible (though not likely) that none of your media files would even be affected.
