It wasn’t PINN in the end, it was just that the 407.7 MB free space was no longer enough to expand the update in /storage before it gets written to /flash. I must have just been lucky in the past that updates have always worked no problem, but I suspect that maybe the Pi5 LibreELEC update image is larger than the Pi4 one I’d updated to most recently? Anyway… I used PINN to backup and restore to a larger SD card and now all is good. Update went just as expected. 1st reboot in the Pi4, let it expand and update then on second reboot, switch off and swap card to Pi5, and it boots up no problem.
Posts by rickwookie
-
-
On the RPi4:
Codetouch /storage/.update/.nocompat cd /storage/.update wget https://releases.libreelec.tv/LibreELEC-RPi5.arm-11.0.6.img.gz reboot
On reboot the RPi4 updates to the RPi5 image, and on completion and second reboot it attempts to boot the RPi5 image. This will either fail or half-work so it's best to pull power on the RPi4 as the second reboot starts. Now transfer the SD card to the RPi5 and things should work.
Or .. do a clean install and manual copy/paste migration of any essential content from the RPi4. The boards use different images so unlike previous RPi2 > RPi3 migrations you cannot simply swap the card.
Sorry to resurrect this old thread, but I finally got around to taking my Pi5 (that I ordered as an impulse purchase when they were first announced) out of its box. Trying to use this method to upgrade from my Pi4 to Pi5 without loosing all my config/settings, and on the first reboot I get the UPDATE IN PROGRESS screen, but "Decompressing image file..." never seems to complete, and instead it seems to just give up due to lack of space and boot normally and I still have to version 11.0.6 that runs on the Pi4 (but not on the Pi5, trying the SD card on that and it just gets into a reboot loop every time it tries to boot).
After issuing the wget command and the file downloads, if I do a df -h I get the following:
Since I'm dual-booting using PINN, I suspect PINN has messed about with the partition sizes on the (8 GB I think) SD card during the latest update (which was needed to get it to work on the Pi5).
If the 407.7 MB free in /storage isn't enough to decompress the update, How much do I need? I can probably do something with GParted to steal some space back from /flash or maybe even the retropie partition (since that won't be working on my Pi5 anyway).
-
Try adding video=HDMI-A-1:1920x720M@60
so long,
Hias
Thanks, yes it works now using:
video=HDMI-A-1:1920x720@60
video=HDMI-A-1:1920x720M@60
video=HDMI-A-1:1920x720R@60
but using video=HDMI-A-1:1920x720MR@60 gives me no video output (that the car’s display can show at least).
Also, the refresh rate is calculated at 59.94 Hz (for all three working lines above) instead of 60 Hz, but I can’t see any side effect of that, so all good
Thanks again.
-
-
I have a quirky setup whereby I'm running Kodi (booting via PINN Lite) on a Pi4 to by car's HDMI display that is 8:3 ratio with pixel dimensions 1920x720.
I use custom HDMI timing in each of the OS boot partition config.txt files thus:
Codehdmi_ignore_edid=0xA5000080 hdmi_timings=1920 0 88 44 148 720 0 4 5 36 0 0 0 60 0 100980000 8 hdmi_group=2 hdmi_mode=87
On LE9.2 this was working for me in that I would just get the one display resolution option of 1920x720 and the output would look great at the native resolution.
I've just tried upgrading to 9.95.5, and after putting my custom settings back in config.txt, I no longer get my special resolution option, but instead just get this:
Any idea why it's not working any more?
-
If you want to test the nightlies better use a separate SD card for now and do a fresh install with the img.gz.
Updating from 9.2 isn't something we support ATM, you'd manually need to at least replace config.txt with current version, maybe also cmdline.txt if you changed something there, as lot of things have changed, and there's no easy way going back to 9.2 except restoring a full backup.
so long,
Hias
Ok so let's assume I want to try this (on a cloned SD card), where can I get the replacement config.txt and cmdline.txt files from?
-
Hi all
I want to try out the latest nightly on my Pi4 (8 GB) to have a look at how HDR playback is coming on, and my current install uses PINN (a NOOBS spin-off) as I'm dual-booting to Retropie.
Which of these files would be the correct one to drop into the "Update" folder on the samba share?:
LibreELEC-RPi4.arm-9.80-nightly-20201106-9862821-noobs.tar
LibreELEC-RPi4.arm-9.80-nightly-20201106-9862821.img.gz
LibreELEC-RPi4.arm-9.80-nightly-20201106-9862821.tar
Many thanks.
-
Everything important from the .config and .kodi folders.
I mean, I’ve no idea what that includes, but I’ll give it a go. I’ll use a fresh SD card for the new image anyway so I can always use the old Pi with the old card again if I mess up.
-
Use the built-in Backup&Restore tool in the LibreELEC Settings Add-on.
Keep a separate copy of the guisettings.xml file, just in case.
Will that back up everything, including plugins etc.?
-
In the past when I got a new RPi, I always just moved the SD card from the old device to the new one. Since the builds for RPi 4 appear to be different from the RPi 2/3 builds, how can I upgrade my hardware while still keeping all my configuration/settings/database etc.?