I’m currently running Tumbleweed on an early RasPi, doing lightweight server stuff. On the whole, I quite like it: it seems stable and does what I need.
That said, it can be a bit sluggish, so I’m considering migrating to a 3 B+. The main blocker at this point is not wanting to go through the whole setup and configuration process again. I’m lazy like that.
Can I shortcut the process by booting my current armv6hl system on the new hardware, changing the repository to aarch64, and forcing zypper to reinstall all packages? That just seems simpler than installing from scratch, making sure I’ve got everything installed, and then configuring all of my software again.
Thanks in advance for any advice, suggestions, or recommendations.
On Tue 08 Jan 2019 08:46:06 PM CST, Knurpht wrote:
The Rpi3 is aarch64. The things you could do is backup /etc /home . But
AFAIK you cannot upgrade Rpi to Rpi3.
Hi
Different file structure, u-boot etc, so I doubt it… rsync your
files across perhaps? I have my Tumbleweed RPi3B (not a plus) booting
via 16GB USB. So could do that and insert the old SD card to copy files
over?
Is your disk structure similar?
fdisk -l /dev/sda
Disk /dev/sda: 14.8 GiB, 15854469120 bytes, 30965760 sectors
Disk model: Patriot Memory
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6e5f36a4
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 34815 32768 16M c W95 FAT32 (LBA)
/dev/sda2 34816 29961225 29926410 14.3G 83 Linux
/dev/sda3 29962240 30957254 995015 485.9M 83 Linux
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Disk /dev/mmcblk0: 15 GiB, 16070475776 bytes, 31387648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4f7380f7
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 34815 32768 16M c W95 FAT32 (LBA)
/dev/mmcblk0p2 34816 30378915 30344100 14.5G 83 Linux
/dev/mmcblk0p3 30380032 31374944 994913 485.8M 83 Linux
So, maybe do a clean install on the new hardware, then copy over everything on / leaving /boot/efi (aka p1) strictly alone. Fix up fstab, change the repository, and force the reinstall. Might have to work on grub a bit.
Yeah, I’m still hoping to minimize the configuration, getting the right things installed, the other right things uninstalled, services started, and so on.
If I can get the new hardware to boot (and my understanding was that the newer hardware could run, albeit inefficiently, on software built for armv6hl), it should be doable, like an in-place upgrade from one version of Leap to the next.
You can’t.
The original RPi and RPi Zero are ARMv6, all the other RPi are ARMv7
Consider scripting your install, it’s something you can do little bit by bit as you build your system.
It can also serve as another backup option, the ability to re-build your system from a generic image with one or only a few clicks.