Confirmation: RpiCore 3 image resize on 3+

[jenskastensson]

Hi,
I have an image created with RevPi Core3.
After flashing this image on a RevPi Core3+ , I see a new behaviour while running revpi-factory-reset
All seems to work, but better safe than .... can you confirm this is the expected output given the use case?
Best regards
Jens @ ProKNX


Using username "pi".
pi@192.168.1.10's password:
Linux RevPi 4.9.76-rt60-v7+ #1 SMP PREEMPT RT Wed, 04 Sep 2019 16:19:42 +0200 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
pi@RevPi:~ $ sudo revpi-factory-reset core aaaa BBBBBB
Partition #1 contains a vfat signature.
Partition #2 contains a ext4 signature.
resize2fs 1.43.4 (31-Jan-2017)
Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
The filesystem on /dev/mmcblk0p2 is now 1896448 (4k) blocks long.

/usr/sbin/revpi-factory-reset: line 49: /usr/bin/dtoverlay: No such file or directory
Password: nnnnnn
Hostname: RevPinnnnnnn
MAC Address eth0: nnnnnnnnnnn
Reboot to activate the MAC Address
Be sure to write down the password if you have lost the sticker
on your RevPi!

[lukas]

/usr/sbin/revpi-factory-reset: line 49: /usr/bin/dtoverlay: No such file or directory

I assume by "new behaviour" you refer to the above-quoted error message?

That message means that the devicetree overlay for the RevPi Core could not be loaded. The most likely explanation is that the /boot partition is not mounted for some reason. That is unexpected, normally it should be mounted if you're using our image. However, once you reboot the machine the devicetree overlay will be loaded by the bootloader and passed to the kernel, regardless whether the kernel later on mounts the /boot partition. But you'll not be able to use the RTC and other peripherals on the Core until you reboot.

[zhan]

/usr/sbin/revpi-factory-reset: line 49: /usr/bin/dtoverlay: No such file or directory

I assume by "new behaviour" you refer to the above-quoted error message?

That message means that the devicetree overlay for the RevPi Core could not be loaded. The most likely explanation is that the /boot partition is not mounted for some reason. That is unexpected, normally it should be mounted if you're using our image. However, once you reboot the machine the devicetree overlay will be loaded by the bootloader and passed to the kernel, regardless whether the kernel later on mounts the /boot partition. But you'll not be able to use the RTC and other peripherals on the Core until you reboot.

Another possibility before missing of /boot is the absence of /usr/bin/dtoverlay, which is belong to the debian packet "libraspberrypi-bin". Also it is a symbol link to /opt/vc/bin/dtoverlay. As you said your image is created based on a RevPi Core3, it is probably that the packet "libraspberrypi-bin" has been removed from the RevPi Core3, which you used to create the image. Or the symbol link mentioned above has been destroyed.