Tiny Core Base > piCore Final Releases

piCore 14.1 (32 and 64 bit) release

(1/3) > >>

Paul_123:
Team Tiny Core is happy to announce the release of piCore-14.0.  Both 32 and 64bit images are ready for download/testing.

Changes since 14.0
-rpi-kernel 6.1.68
-pi[5] support on the 64bit image.
    ******WARNING********
    You need to be running a bootloader on your pi[5] 2023-11-20 or newer or piCore will fail to boot on a pi[5]
    use rpi-imager to create an sdcard with the latest bootloader image, boot your device with that card, when you get a green screen, then you can write the piCore64-14.1 image and boot.

32bit - http://www.tinycorelinux.net/14.x/armv7/releases/RPi/piCore-14.1.0.zip  (This should run on all rpi boards except pi5)
64bit - http://www.tinycorelinux.net/14.x/aarch64/releases/RPi/piCore64-14.1.0.zip  (rpi zero2W, pi3, pi4, pi5)

elcouz:
Thanks Paul_123

zharr:
Hey, thanks for the updates!
I'm wondering in what extension I can find libvcsm.so with 14.x?
From 13.x to 14.x it seems to be gone from the package that previously had it.
libatomic was also missing but found in gcc_libs.tcz thanks to the forum.
libmmal and it's related libraries are also gone, though with MMAL being deprecated that is not too surprising.
But VCSM is still a crucial element of interacting with the hardware

The reason I'm trying to upgrade in the first place is because I'm facing a kernel wifi driver crash while checking the RSA SSH host keys that openssh generated itself on first boot - about half the time, my Pi Zero 2 boots without the wlan0 device because it's driver crashed (OpenSSH would then regenerate the RSA key on next boot, so I assume that's why it didn't crash).
FYI, it's the same error message+code on the same code line as this issue).

Any help finding libvcsm or resolving the crash is appreciated.
(Note I'm using armv6/v7 not aarch64 since I need compatibility with the Zero 1)
Thanks!

Paul_123:
The rpi-vc package should be available in 14.x, but yes all of that stuff is obsolete going forward.

The linked issue was resolved on our end before we released, so I've never seen the issue on piCore 12,13 or 14.   The crash would have nothing to do with ssh keys vs wifi, and is more likely something with your access points you are connecting to.

zharr:
Thanks for the reply!

I do indeed use the rpi-vc package, but now I checked them and in 13.x, it contains 23 libraries (in /usr/local/lib), including libvcsm, but in 14.x it only contains libbcm_host, libdebug_sym, libdtovl, libvchiq_arm and libvcos.
I can try to copy it from 13.x to see if it still works. I don't think libvcsm should be deprecated, in contrast to MMAL I don't know what it would be replaced with.
Though seeing how in this issue, VCSM had to be fixed for MMAL 64bit support, it does seem that VCSM and MMAL support is intrinsically linked. Which would be super unfortunate because I actually require VCSM+DMABUF even while using V4L2 instead of MMAL. So maybe it is "correct" that it's gone from aarch64, but I'm not sure about the 32bit OS yet. Maybe I'll check if the current 32Bit Rasberry Pi OS still has libvcsm.so.

EDIT: Can confirm, it doesn't, libraspberrypi installs libbcm_host.so but not mmal nor vcsm. Very unfortunate. Will try old libvcsm

As for the wireless crash, the device driver crashes and does not show up even when never connecting to any access point, so that's not it.
Boot once, let openssh create the host keys, reboot and dmesg has the crash in RSA key check, and wlan0 is not there. Maybe I am missing sha256sum or something similar as the issue suggests.
Alternatively, do you know of a way to prevent openssh from generating the RSA key on boot (or any key at all - can do manually)? Then it should respect that there's no RSA key and it should just work afaik.
Or maybe I'll just delete the RSA key after openssh starts and hope it's ok even when client wants to use RSA.

Navigation

[0] Message Index

[#] Next page