I did an update with the combo installation and it worked well; I even think the menus are faster now. I just wanted to know if there may occur problems with either the card or the stick if they weren’t updated correctly.
Unlight
I see no reason for concern, especially now that you've verified you setup as working well after the update.I did an update with the combo installation and it worked well; I even think the menus are faster now. I just wanted to know if there may occur problems with either the card or the stick if they weren't updated correctly.
This being the case, I see no real reason for me to repeat that test at my end (still haven't had time for it).
But I will perform the corresponding test for a BerryBoot installation, starting with rc5 and updating to 0.4.1.
That's an entirely different case (different basic filesystems even), so it needs separate testing.
Best regards: dlanor
I have now performed the BerryBoot test mentioned in my previous post, with successful results.
I first installed RasPlex 0.4.0 rc4 through the BerryBoot edit menu to a USB3 stick (with another USB stick as source), after which I restarted and chose the new OS in the BerryBoot boot menu. Once I reached the RasPlex menu I waited for its 'wizard' and simply skipped through its settings, after which I waited some more for the auto update download to finish (it had already started, though that is not visible in wizard or main menu). When I got the popup message that the update was ready for install I used the special menu command to start the install procedure.
This is where things may get a little confusing for some users, as the RasPlex updater can't just install everything at once. The currently running program and its libs and service routines can't just be replaced while they're all in use. So RasPlex needs to reboot not just once, but twice, before everything is in its proper place (there are strong technical reasons for this). With a normal RasPlex setup this rebooting would occur automatically without user intervention. But with a BerryBoot setup the boot menu will appear for each reboot, and it's up to the user to select the correct OS image each time. This must be done twice before again reaching RasPlex main menu, at which time the updating is complete. (The first reboot is to replace some system files, and these need to be in place before a proper RasPlex boot, which is why it has to reboot the second time.)
After reaching the main menu I performed all normal configuration of RasPlex, during which I also checked that it showed the proper current version 0.4.1 in the update menu. And with all configuration done I also tested that the new movie 'Extras' features work properly (definite proof of an update to RasPlex 0.4.1).
I tested this with both the rc4 and the rc5 releases of RasPlex, to make sure that users both of the old RPi B and of the new RPi B+ can use the same update method.
(Though B+ owners may need a patched/updated version of BerryBoot in order for it to work properly with B+ hardware.)
Some more things need to be mentioned about BerryBoot use with recent RasPlex versions:
1: In every boot there will be an error message about a 'swapon' attempt failing.
This happens because BerryBoot has to preempt some system functions, so as to make the virtual filesystem work properly.
That is the stuff which allows us to store and run multiple OS images on a single drive, so it's rather important.
To my knowledge this 'swapon' failure doesn't cause any trouble. RasPlex doesn't really need it...
2: If you want to use an older version of RasPlex, then you will need to do it with auto-update disabled.
But a new install image always has it enabled, and some you may have installed earlier may also have it enabled.
To avoid downloading a new update you can disconnect network before launching an image, and then disable auto-update in its menus.
This way you can continue to test both old and new versions from the same BerryBoot setup, for feature and bug comparison.
Best regards: dlanor
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
