piCore 13.1.0 released (32-bit)

[bmarkus]

Glad to announce that piCore-13.1.0 (32-bit) released. What is new:

• kernel updated to 5.10.77
• uPython updated
• hmac kernel module added to v6 architecture (v7, v7l have it built in)
• supports ZERO 2 W
• net/usb kernel driver modules added to ZERO's to make USB Ethernet boards working out of stock

As usual, there is only one SD card image which supports all boards, no hardware specific versions.

Kernel module TCZ's will follow in the next days.

[bmarkus]

I'm using this tp-link UE330 adapter with 1x Gbit Ethernet and 3x USB3 ports. Works fine with piCore 13.1.0 with any Zero out of stock, you need just an OTG cable.

[wthie]

Aloha

installing iptables I just ran into missing ipv6-netfilter-5.10.77-piCore-v7l.tcz , the repos for v7l still shows ipv6-netfilter-5.10.16-piCore-v7l.tcz present.

Mahalo, Werner

[boss]

It seems that v4l-dvb-5.10.77-piCore-v7.tcz is missing from the REPO

It only has the older (kernel) version of v4l-dvb-5.10.16-piCore-v7.tcz

[bmarkus]

All kernel modules are available on the server. You can extract what you need and make a TCZ, remaster piCore or just add it to backup.

[Juanito]

It seems that v4l-dvb-5.10.77-piCore-v7.tcz is missing from the REPO

It only has the older (kernel) version of v4l-dvb-5.10.16-piCore-v7.tcz

posted - thanks for pointing this out

[M]

tce-load -wi net-usb-KERNEL.tcz          fails

It seems that net-usb-5.10.77-piCore-v7.tcz is missing from the REPO

It only has the older (kernel) version of net-usb-5.10.16-piCore-v7.tcz

[Juanito]

net-usb-5.10.77-piCore-v7 added - thanks for reporting this

[Synerworks]

Not to bring up an old thread, however, the repo for piCore 13.x is still missing the rtc-5.10.77 modules for ARMv6, ARMv7, and ARMv7l. Was it posted and removed following mirror sync?

[Paul_123]

Probably never created.  You will have to make it yourself, all kernel modules are posted in these archives.

http://www.tinycorelinux.net/13.x/armv6/releases/RPi/src/kernel/5.10.77-piCore_modules.tar.xz
http://www.tinycorelinux.net/13.x/armv7/releases/RPi/src/kernel/5.10.77-piCore-v7_modules.tar.xz
http://www.tinycorelinux.net/13.x/armv7l/releases/RPi/src/kernel/5.10.77-piCore-v7l_modules.tar.xz

[Synerworks]

Unusual, that only the RTC driver was left out for piCore v13.1, but was posted for piCore64 v13.1. Are the release builds done by hand for each platform/target, namely ARMv6, ARMv7, ARMv7l, and ARMv8 or is it scripted for each of the 32-bit and 64-bit targets? Not that it is important, just found the inconsistencies between each release as application testing is being performed. Consideration for LTS kernel migration to address the numerous CVEs to date, going back to v13.x, but may drop off since kernel 5.10.x is expected to be EOL'd anytime soon after the next LTS kernel 7.x is announced.

[Paul_123]

We do not maintain old releases, files are kept for archival purposes..  If you want newer kernel and newer library/application support, please use the active version which is 17.0.

[Synerworks]

The question was not about maintenance but the absence of packages that are already present in the archived TARballs. Suggestion to migrate to 17.x does not replace the missing extensions for those that are bound to a specific kernel version of their applications. Nonetheless, corrected the failure to synchronize the time with the RTC for the piCore13.1 drop by sourcing the rtc-5.10.16 extensions for ARMv6, v7, and v7l or just taking the rtc-5.10.77 ARMv8 extension and retrofitting the existing objects from the posted source archives and repacking the individual extensions. The three extensions were unpacked using the 'squashfs-tools.tcz' addon, the module directory labels updated to reflect the actual 5.10.77 platform revision, the older existing 5.10.16 objects simply replaced with those from the kernel source archive TARballs, and then repacked with the squashfs tool.

Currently taking all LTS kernel incremental corrections to piCore13.x to piCore17.x and generating the kernel update extensions to address the CVEs for validation purposes and minimize risk exposure for TC connected devices. A single media SD/USB framework is being used containing the targeted X86 TinyCore, TinyCorePure64, piCore, and piCore64 distributions without alteration that permit application integration testing across multiple devices without having to cut and install components spread across numerous boot media in order to operate. So, if core components were missing, the test results yielded failures where there should not have been any.

Just wanted to clear up the nature of the inquiry.