piCore 16.0 Release

[Paul_123]

Team Tiny Core is happy to announce the release of piCore-16.0.  Both 32 and 64bit images are ready for download.

Changelog for 16.0.0:
* rpi-kernel and firmware 6.12.25
* glibc updated to 2.40
* gcc updated to 14.2.0
* binutils updated to 2.43.1
* e2fsprogs base libs/apps updated to 1.47.1
* util-linux base libs/apps updated to 2.40.2
* Micropython updated to 1.24.1
* OpenSSL updated to 3.4.1
* OpenSSH updated to 9.9p2 (DSA keys are no longer generated by default)
* CoreScripts updated to latest in git(piCore Branch).
* Removed Old module config file for 8192 driver.
* Update module config for rpi wireless (brcmfmac)
* Fix udev rules for proper serial console configuration.
* Updated udev rule for pi5 to not use cma.
* Added symlink from /lib/firmware -> /usr/local/lib/firmware

32bit - http://www.tinycorelinux.net/16.x/armhf/release/RPi/piCore-16.0.0.img.gz  (This should run on all rpi boards)
         - sha256: 92efe99b4e821a6a0c469b119db520d1e9347b04ad8c7f586614085ea7d25dd6  piCore-16.0.0-beta1.img.gz

64bit - http://www.tinycorelinux.net/16.x/aarch64/release/RPi/piCore64-16.0.0.img.gz  (rpi zero2W, pi3, pi4, pi5)
         - sha256: 797773e1c3228cf1ead52b736442becabb1bd20d6d560a6582d63d3892bbb478  piCore64-16.0.0.img.gz

Note: Image files are now just gzipped, you can just zcat the image if using dd to write your image, or some imaging tools support writing compressed images.
Note:  When using 32bit images, the pi4 and pi5 will use a 64bit kernel.  please make sure to look at uname if manually downloading kernel module extensions.

[zharr]

Seems something is broken with the wifi, packages and kernel modules appear to all load, but dmesg shows two failures that a prior 14.x image did not have (no 15.x dmesg log lying around, sorry):

Code: [Select]

[   10.970348] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   10.970374] cfg80211: failed to load regulatory.db
[   11.032375] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   11.038169] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   11.038318] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin failed with error -2
[   11.038395] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2
[   11.038732] usbcore: registered new interface driver brcmfmac
[   12.043494] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50Edit: Forgot to mention, the symptom is the wlan0 device is missing. And thanks for the release!

[Paul_123]

Update your firmware packages.  I change piCore16 to standardize firmware locations with Core.....(so we can share most firmware packages)   I changed the piCore images in the release, but didn't realize the tce-load would not handle the symlink.  I've fixed the common firmware files...

[zharr]

Thanks a bunch, now it works perfectly!
Will observe how it looks with wifi stability, even with the boot param, 15.x dropped a few packets, enough to freeze the ssh every once in a while. 16.x still drops packets at about the same rate (once every 2 seconds), but SSH feels solid, unlike 15.x. So idk if SSH just learned to cope with it better or the drops (as reported by ifconfig) are not relevant. No idea if 14.x had no dropped packets or if this is normal.

 (also, I still have one bug across 13-16 left to fix but that's almost certainly specific to my program)

[neonix]

Links on this site are broken.
http://tinycorelinux.net/ports.html

http://tinycorelinux.net/16.x/aarch64/releases/RPi
http://tinycorelinux.net/16.x/aarch64/test_releases

http://tinycorelinux.net/16.x/armhf/releases/RPi
http://tinycorelinux.net/16.x/armhf/test_releases

[Rich]

Hi neonix
I think Paul_123 fixed the links:

http://tinycorelinux.net/16.x/aarch64/release/RPi
http://tinycorelinux.net/16.x/aarch64/release_candidates/RPi

http://tinycorelinux.net/16.x/armhf/release/RPi
http://tinycorelinux.net/16.x/armhf/release_candidates/RPi

[daab]

Hi,
I've noticed a discrepancy between the arhmf and aarch64 releases in terms of SDL2 packages
The package names are inconsistent and there are fewer packages on armhf

AFAICT for release 16.x the aarch64 packages are
sdl2-dev.tcz
sdl2-image-dev.tcz
sdl2-image.tcz
sdl2-mixer-dev.tcz
sdl2-mixer.tcz
sdl2-net-dev.tcz
sdl2-net.tcz
sdl2.tcz
sdl2-ttf-dev.tcz
sdl2-ttf.tcz

and for armhf
SDL2-dev.tcz
SDL2_image-dev.tcz
SDL2_image.tcz
sdl2_mixer-dev.tcz
sdl2_mixer.tcz
SDL2.tcz

Please can we have the full set of packages for armhf with the same names as aarch64?

Many thanks.

[Juanito]

posted

[Paul_123]

Looks like some consistency issues.  Some extensions are capitalized SDL and others are lower case?   Should we rename them all lower case?

[Juanito]

If you could, that would be great 

[Paul_123]

No problem, done

[daab]

No problem, done

Thank you,
Keep well

[daab]

Hi,
Thanks for the fixes,
sorry to be a pain, but some package names are slightly different between aarch64 and armhf.

Best expressed by this diff

Code: [Select]

$ diff /tmp/aarch64 /tmp/armhf
2,5c2,5
< sdl2-image-dev.tcz
< sdl2-image.tcz
< sdl2-mixer-dev.tcz
< sdl2-mixer.tcz
---
> sdl2_image-dev.tcz
> sdl2_image.tcz
> sdl2_mixer-dev.tcz
> sdl2_mixer.tcz

It would be useful if the package names are the same for aarch64 and armhf

Thanks for your help.
Keep well.

[Paul_123]

I looked at the repos, Looks like the sdl2_xxx is the pattern to standardize to.  Should be resolved.

[daab]

Thank you.