Sd from pi3 to pi4 ?

MoreBloodWine · August 30, 2019 at 9:31 AM

Going by the above, the Pi4 uses 9.1.002

I'm guessing the answer will be no... but figured why the hell not, just ask.

But since I have that same version running on a Raspberry Pi 3, can I take that SD card and plug it into the Raspberry Pi 4 basically having it work right out of the gate?

**CvH** · August 30, 2019 at 4:11 PM Official Post

afaik you can update (while SD at your RPi) to the RPi4 image, then change the SD

Backups are your friend

MoreBloodWine · August 30, 2019 at 5:51 PM

I backup previous to any change, but how do you upgrade the architecture like that on a Raspberry Pi 3 making it gtg for the Pi 4 ?

Almost sounds like it'd be simpler to do a fresh install and then take a backup and reload it that way since the backup is, afaik, addons etc. / non core conflicting code.

**CvH** · September 1, 2019 at 1:03 PM Official Post

gosh, sry had a brain bug and forgot half of the sentence

Put SD card at your RPi3, drop the LE RPi4 image to your update folder and also add an .nocompat file (empty file is enough) at this folder then restart. After successful update you use the RPi4 image at RPi3 -> switch cards and everything !should! be okay.

MoreBloodWine · September 1, 2019 at 5:59 PM

sounds good in theory, thx.

Give that a go when the Pi4 arrives.

As for the file. Like a .nocompat to file so ends .txt

Or mod a file so it ends .nocompat if ya follow me. So blank name.

MoreBloodWine · September 3, 2019 at 11:28 PM

?

Sorry. Just looking for clarification to avoid possible issues when the new Pi arrives, ty.

**CvH** · September 4, 2019 at 10:59 AM Official Post

.nocompat

could be tricky at windows

ssh would be this (not tested)

touch /storage/.update/.nocompat

MoreBloodWine · October 1, 2019 at 5:08 AM

Pi showed up today, original order got a little whatever but anyway, on 9.1.501 or whatever the hell it is. For the RPI 4, using the above suggested methods. Up and running like a charm.

Only been playing with it for maybe 30 minutes. But as far as I can tell, no issues found doing that no compatible upgrade or whatever you want to call it on the rpi3 and then moving the card to the 4 keeping all addons and settings in place.

Megachip · March 15, 2020 at 10:49 PM

Quote from CvH

gosh, sry had a brain bug and forgot half of the sentence

Put SD card at your RPi3, drop the LE RPi4 image to your update folder and also add an .nocompat file (empty file is enough) at this folder then restart. After successful update you use the RPi4 image at RPi3 -> switch cards and everything !should! be okay.

Sounds easy. But for me, after updating (9.2.1) and reboot it stucks on libreelec boot screen

Code

● kodi.service - Kodi Media Center
   Loaded: loaded (/usr/lib/systemd/system/kodi.service; disabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Sun 2020-03-15 23:48:30 CET; 950ms ago
  Process: 3785 ExecStartPre=/usr/lib/kodi/kodi-config (code=exited, status=0/SUCCESS)
  Process: 3790 ExecStart=/usr/lib/kodi/kodi.sh --standalone -fs $KODI_ARGS $KODI_DEBUG (code=exited, status=255/EXCEPTION)
  Process: 3810 ExecStopPost=/usr/lib/kodi/kodi-safe-mode (code=exited, status=0/SUCCESS)
 Main PID: 3790 (code=exited, status=255/EXCEPTION)

Code

dcat /storage/.kodi/temp/kodi.log | grep ERROR
2020-03-16 00:01:07.695 T:3011928080   ERROR: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
2020-03-16 00:01:07.780 T:3011928080   ERROR: CWinSystemGbm::InitWindowSystem - failed to initialize Atomic DRM
2020-03-16 00:01:07.795 T:3011928080   ERROR: CWinSystemGbm::InitWindowSystem - failed to initialize Legacy DRM
2020-03-16 00:01:07.810 T:3011928080   ERROR: CWinSystemGbm::InitWindowSystem - failed to initialize off screen DRM

Adding the following to coonfig.txt solves the issue:

Code

[all]
include distroconfig.txt