Tiny Core Linux

Tiny Core Base => Raspberry Pi => piCore Final Releases => Topic started by: Paul_123 on October 29, 2024, 01:42:24 PM

Title: piCore 15.0 Release
Post by: Paul_123 on October 29, 2024, 01:42:24 PM
Team Tiny Core is happy to announce the release of piCore-15.0.  Both 32 and 64bit images are available.

rpi-kernel 6.6.47
gcc 13.2.0
binutils 2.42
glibc 2.39
busybox 1.36.1
micropython 1.19
openssl 3.2.0.

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

A couple of notes:

Changes since Beta3:
 - Reduced partition1 back to 80MB
 - updated udev script for proper rpi serial port symlinks.

Known Issues:
 - Internal Wifi on some Raspi chipsets, there is a driver problem with wpa_supplicant 2.11 (Add brcmfmac.feature_disable=0x82000 to cmdline.txt on the boot drive)
Title: Re: piCore 15.0 Release
Post by: leg on November 13, 2024, 03:33:29 AM
Thank you very much for the release! I would need the -T option for the ps command, but BusyBox does not include it. Can I get help with this issue?
Title: Re: piCore 15.0 Release
Post by: Juanito on November 13, 2024, 05:30:58 AM
If you use the "provides" function of the apps gui it suggests the procps extension.
Title: Re: piCore 15.0 Release
Post by: gadget42 on November 13, 2024, 05:52:51 AM
If you use the "provides" function of the apps gui it suggests the procps extension.
i like to follow-along and discover different/new things through forum progression over time.

when i use the "provides" function and search for "ps" it reports many results. how would the uninitiated decide which to use?

i figured out that it was procps-ng via the man page found here:

https://www.man7.org/linux/man-pages/man1/ps.1.html
Title: Re: piCore 15.0 Release
Post by: Rich on November 13, 2024, 09:56:14 AM
Hi gadget42
... it reports many results. how would the uninitiated decide which to use? ...
How to narrow down the results returned by provides:
https://forum.tinycorelinux.net/index.php/topic,27363.0.html
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 13, 2024, 10:53:30 AM
The GUI fails to launch when following "tce-load -wi TC" on PI0-3s, specifically VC4s, and works on PI4-5s. Looking at the DMESG logs, the PI4-5s use simple framebuffer, whereas the earlier VC4s are not. The Xorg log shows it dies out when attempting to load the frame buffer. Anyhow, the short term interim resolution was to WGET the "xorg-server.tcz.*" files from the 14.x repository and replace the components on the 15.x media in the optional folder or copy over the files from your previous piCore14.x image. Need to see what has changed between these releases to identify why it fails.
Title: Re: piCore 15.0 Release
Post by: Paul_123 on November 13, 2024, 02:04:33 PM
VC4 (With Xorg-3d) works on a 2B+, other than needing to added a delay, or wait for the VC4 driver to initialize at the beginning of .xsession.
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 13, 2024, 02:39:26 PM
Already dealing with the kernel 6.6.x difference to deal with the annoying 'waitforX' timeouts, this is moreso with piCore64 though with the v8 kernels, but the reported issue is strictly with Xorg on VC4 boards, namely PI0-3, not using the v8 kernels. The problem remains with piCore15 no matter how long one waits for the driver initialization to complete. Dropping down to piCore14 'xorg-server.tcz' on piCore15 remedies to problem for now, until the actual variance is found. Just loading TC to any base piCore15 image easily generates the issue on PI0-3s, due to their VC4 graphics, not for PI4-5 since they are VC6-7, and using the simple framebuffer 'fbdev' as reported in Xorg.log.
Title: Re: piCore 15.0 Release
Post by: Juanito on November 13, 2024, 03:39:35 PM
This works:
Code: [Select]
tce-load -i Xorg flwm aterm wbar
sudo rm /usr/local/share/X11/xorg.conf.d/20-noglamor.conf
startx

The noglamor file needs to be loaded by the Xorg-3d extension rather than xorg-server - I'll fix things tomorrow.
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 13, 2024, 08:31:20 PM
Added the configuration file removal command to 'bootlocal.sh' for now due to the failure to launch the GUI on each boot until the 'xorg-server.tcz.*' repo is updated. Thanks for the heads-up, missed the configuration file changes between the two packages after noticing the library versions had changed.
Title: Re: piCore 15.0 Release
Post by: Juanito on November 14, 2024, 04:27:18 AM
xorg-server and Xorg-3d updated - Xorg and Xorg-3d tested on an RPi3 running piCore-15.x 32bit
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 14, 2024, 08:54:14 PM
The piCore64 repo would need to be corrected for 'xorg-server.tcz' and 'Xorg-3d.tcz' since '/usr/local/share/X11/xorg.conf.d/20-noglamor.conf' is also showing up on 'tce-load's for PI02-5s with v8 kernels as well and dropping out with 'waitforX'. Looking into why only a blank desktop starts on the PI02-3s without the 'wbar' but works on PI4-5s.
Title: Re: piCore 15.0 Release
Post by: Juanito on November 15, 2024, 05:29:10 AM
xorg-server is patched in piCore-15.x - I need to check the patch works in piCore64-15.x.

In the meantime, if you need a gui for an RPi3 using piCore64-15.x, you can use a wayland compositor like labwc or weston - imho the wayland gui works better on RPix anyway.
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 15, 2024, 02:35:26 PM
Still can manage to address these issues by pulling the extension from the previous 14.x release and/or adding a removal command to the startup file, just that unsuspecting individuals may also trip over this anomaly unless there has been foresight to scan the forums for answers to the unexpected behaviour. Was tripped up by it due to migrating forward from several previous generations of piCore(64)s.
Title: Re: piCore 15.0 Release
Post by: yvs on November 15, 2024, 04:07:55 PM
> The GUI fails to launch ... on PI0-3s, specifically VC4s, and works on PI4-5s.

try it with vc4-fkms on older piNs instead of vc4-kms
Title: Re: piCore 15.0 Release
Post by: Juanito on November 16, 2024, 04:45:09 AM
xorg-server and Xorg-3d updated on piCore64-15.x

Xorg and Xorg-3d tested on an RPi4 running piCore64, @Synerworks maybe you could test on an RPi3
Title: Re: piCore 15.0 Release
Post by: Synerworks on November 16, 2024, 04:14:52 PM
All good now with Xorg and Xorg-3d on piCore64-15.x, verified on PI02-5s!
Title: Re: piCore 15.0 Release
Post by: Synerworks on December 14, 2024, 01:32:47 PM
While testing on PI0-1s, found that extensions containing the 'vcgencmd' tools are both located in 'rpi-vc.tcz' and 'raspi-utils.tcz', with some that overlap each other. However, for piCore 14.x and 15.x, the command generates an 'Illegal instruction' with this command from the 'rpi-tc.tcz' extension, but works from the 'raspi-utils.tcz' extension. The 'vcgencmd' from 'rpi-vc.tcz' repo on piCore 13.x does work as expected, even though they use the additional libraries. Inspecting the 'ldd' results for each of the 'vcgencmd's from each of the repos shows that they were generated against different libraries.

Code: [Select]
tc@box:~$ ldd `which vcgencmd`
libc.so.6 => /lib/libc.so.6 (0xb6d5b000)
/lib/ld-linux-armhf.so.3 (0xb6ee1000)
tc@box:~$ # From repo 'raspi-utils.tcz' for piCore 14.x, and 15.x

Code: [Select]
tc@box:~$ ldd `which vcgencmd`
libvchiq_arm.so => /usr/local/lib/libvchiq_arm.so (0xb6f30000)
libvcos.so => /usr/local/lib/libvcos.so (0xb6f00000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb6f83000)
libdl.so.2 => /lib/libdl.so.2 (0xb6f5d000)
librt.so.1 => /lib/librt.so.1 (0xb6f5a000)
libc.so.6 => /lib/libc.so.6 (0xb6dab000)
/lib/ld-linux-armhf.so.3 (0xb6f8e000)
tc@box:~$ # From repo 'rpi-vc.tcz' from piCore 13.x, 14.x, and 15.x

The 'temp.tcz' repo depends on the 'rpi-vc.tcz' extension, even though it could use the 'raspi-utils.tcz' extension instead, so the application fails due to this exception. As an interim correction, loading the 'raspi-utils.tcz' extension in the 'onboot.lst' enables the 'temp' command to function when the 'rpi-vc.tcz' repo is renamed/removed from the 'optional' folder after installation when using the 'tce-load -wi temp' command. However, this approach would not facilitate those that depend on the additional commands from the 'rpi-vc.tcz' extension that are not in the 'rasp-utils.tcz' repo though.

    [Edit]: Added code tags.  Rich
Title: Re: piCore 15.0 Release
Post by: Paul_123 on December 14, 2024, 01:56:26 PM
rpi-vc is mostly obsolete, raspi is no longer maintaining any tools in that extension.    raspi-utils is the current maintained extension.

You do not even need temp.tcz or raspi-utils to get temperatures.

Code: [Select]
cat /sys/devices/virtual/thermal/thermal_zone0/temp

or printed nicer
Code: [Select]
cat /sys/devices/virtual/thermal/thermal_zone0/temp | awk '{ printf "%2.1fC\n", $1/1000 }'

Title: Re: piCore 15.0 Release
Post by: Rich on December 14, 2024, 02:32:14 PM
Hi Synerworks
Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

Quote
[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:
Code: [Select]
[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.
Title: Re: piCore 15.0 Release
Post by: Synerworks on December 14, 2024, 03:05:02 PM
Will do. I only used the 'temp.tcz' dependency to illustrate a use case, so if the 'rpi-vc.tcz' extension is obsoleted, the repo dependency should switch over to 'raspi-utils.tcz' instead. Nonetheless, the issue manifests itself when attempting to use the VC tools and the incorrect repo is loaded or both and then throws the exception. Also, the superseded objects could be copied from the working 'raspi-utils.tcz' repo into the obsoleted extension to avoid this inconsistency when using the required component but picking the wrong 'provides.sh' result. Just attempting to avoid caveats as they come up.
Title: Re: piCore 15.0 Release
Post by: rhbvkleef on December 17, 2024, 07:42:00 AM
Are there any plans for updating node.tcz in the future? By now I really have to jump through hoops to get JS and TS applications to work.
Title: Re: piCore 15.0 Release
Post by: Juanito on December 17, 2024, 08:02:07 AM
In armhf or aarch64?

The node.js extensions (as opposed to the node extensions) seem quite recent?
Title: Re: piCore 15.0 Release
Post by: DrRob on December 21, 2024, 09:35:29 AM
Known Issues:
 - Internal Wifi on some Raspi chipsets, there is a driver problem with wpa_supplicant 2.11 (Add brcmfmac.feature_disable=0x82000 to cmdline.txt on the boot drive)

Which Raspi chipsets please?  Or better still, which Pi models?  By trial and error it seems to include the Pi Zero?
Title: Re: piCore 15.0 Release
Post by: Paul_123 on December 21, 2024, 09:56:42 AM
I don’t have every combination to test.  It may just be the zero based product.   They all use the same driver.  Just different firmware.
Title: Re: piCore 15.0 Release
Post by: dohnjoe on January 05, 2025, 03:23:30 PM
Quote
- Internal Wifi on some Raspi chipsets, there is a driver problem with wpa_supplicant 2.11 (Add brcmfmac.feature_disable=0x82000 to cmdline.txt on the boot drive)

Despite adding this line, the WiFi connection drops intermittently and there are periods of no connectivity, making it virtually unusable. I'm on a RasPi Zero 2W. What else can be done to assuage this?
Title: Re: piCore 15.0 Release
Post by: Paul_123 on January 05, 2025, 03:31:18 PM
Raspi WiFi Cho’s have very weak reception,  especially in a case.  They are also very sensitive to poor power conditions.  You should check signal strength.
Title: Re: piCore 15.0 Release
Post by: dohnjoe on January 05, 2025, 03:58:36 PM
Quote
Raspi WiFi have very weak reception,  especially in a case.  They are also very sensitive to poor power conditions.  You should check signal strength.

Done. Checked multiple times. For the same location, this works perfectly fine on piCore 14.x, so it's less likely that this is a signal problem. This happens only on piCore 15.0.
Title: Re: piCore 15.0 Release
Post by: Paul_123 on January 05, 2025, 05:33:48 PM
Well I don’t have connection problems with 5 or so different devices (zeros to pi5) So perhaps it’s something with your setup.

Anything output in dmesg by the kernel drivers?  Otherwise, you may need to monitor wpa_supplicant for potential causes of disconnects. Does hour router support wpa3?  If seen issues trying to run wpa2/3 compatibility, but works fine in pure wpa2 or wpa3

Title: Re: piCore 15.0 Release
Post by: rhbvkleef on January 07, 2025, 09:37:08 AM
In armhf or aarch64?

The node.js extensions (as opposed to the node extensions) seem quite recent?

aarch64. The current version is 16.14.0, which was released in 2022-02-08. You're right that armhf is slightly more recent (although still quite old: 2023-08-09).

Software that I use has dropped support for v16.x completely, as the Nodejs project has not maintained it for quite some time now.

Is there any way I can assist in upgrading the node extension?

Edit: The node.js extensions are not more recent. They use version 12.18.3, which wash released on 2020-07-22.
Title: Re: piCore 15.0 Release
Post by: gadget42 on January 07, 2025, 11:45:57 AM
these probably aren't specific to any certain current difficulties but still good to keep in mind

https://rachelbythebay.com/w/2022/12/22/wpa3/
https://rachelbythebay.com/w/2024/01/24/wpa3/
https://rachelbythebay.com/w/2024/01/24/fail/
Title: Re: piCore 15.0 Release
Post by: piran on January 09, 2025, 08:56:05 AM
Quote
- Internal Wifi on some Raspi chipsets, there is a driver problem with wpa_supplicant 2.11 (Add brcmfmac.feature_disable=0x82000 to cmdline.txt on the boot drive)

Despite adding this line, the WiFi connection drops intermittently and there are periods of no connectivity, making it virtually unusable. I'm on a RasPi Zero 2W. What else can be done to assuage this?
I was having this issue with my Zero 2w before Christmas.
I've just done a :
Code: [Select]
tce-update and now my WiFi is really stable