Recent Posts

21

Raspberry Pi / Re: mpg123 playing https radiostream

« Last post by Rich on February 16, 2026, 12:45:29 PM »

Hi opa

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:

[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.

22

Programming & Scripting - Unofficial / Re: Script to download extensions+dependencies on other Linux distros

« Last post by Rich on February 16, 2026, 12:34:10 PM »

Hi GNUser
A question from another thread gave me an idea.
Suppose you wanted to update to a newer version of Tinycore.
Then you decide to do this:

Code: [Select]

# Create your new tce directory:
mkdir NewTceOptional
cd NewTceOptional
# Download current version of FetchExt.sh:
wget https://forum.tinycorelinux.net/index.php?action=dlattach;topic=23034.0;attach=7078
# Make it executable:
chmod 755 FetchExt.sh
# Create list of currently installed extensions:
ls -1 /etc/sysconfig/tcedir/optional/*.tcz | cut -d '/' -f 6 > Ext.lst
# Fetch the extensions from the newer Tinycore repository:
for F in $(cat Ext.lst); do ./FetchExt.sh "$F"; done
Only problem is, when it encounters alsa-modules-6.12.11-tinycore64.tcz
when downloading from a repo with a 6.18.2 kernel, it fails.

Since you are limited to the kernel versions in a repo, it makes no sense
to specify a kernel version. As it is, the script currently downloads all
versions of a kernel module extension requested. This ensures the end
user has a version that matches their system. Then tce-load selects
the correct version when loading extensions.

So my idea is, when the script encounters an extension name with
a kernel version attached, we replace that part of the extension name
with  KERNEL  so the script can process it with available versions.

Do you (or anyone else) see a problem with this?
Comments requested.

23

Raspberry Pi / mpg123 playing https radiostream

« Last post by opa on February 16, 2026, 12:23:03 PM »

Hi together,

i have installed piCore 16 32-bit on raspberry pi3. Now im trying to play some radiostreams with mpg123.

Here is my command:

Code: [Select]

tc@radiobox:~$ mpg123 "https://liveradio.swr.de/sw282p3/swr3/play.mp3"
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
        version 1.23.4; written and copyright by Michael Hipp and others
        free software (LGPL) without any warranty but with best wishes
[src/libmpg123/readers.c:1182] error: Cannot open file https://liveradio.swr.de/sw282p3/swr3/play.mp3: No such file or directory
main: [src/mpg123.c:731] error: Cannot open https://liveradio.swr.de/sw282p3/swr3/play.mp3: File access error. (code 22)
I get "File access error"

    [Edit]: Added code tags.  Rich

24

Raspberry Pi / Re: ' The Lumi H5P Desktop Editor'

« Last post by geev03 on February 16, 2026, 12:07:02 PM »

Hi Rich
Thank you. It now makes it easy to try , https://github.com/Lumieducation/Lumi/releases/download/v1.0.2/Lumi-1.0.2-arm64.AppImage .on piCore.

25

TCB Talk / Re: CorePlus-13.1.iso can not boot on a UEFI only system.

« Last post by Juanito on February 16, 2026, 11:51:52 AM »

It’s also possible to install a 32bit uefi boot loader using the grub2-multi extension in the x86 repo.

26

TCB Talk / Re: CorePlus-13.1.iso can not boot on a UEFI only system.

« Last post by Rich on February 16, 2026, 11:43:37 AM »

Hi Elwood

I have an old ASUS T100-CHI tablet that is not Linux friendly.
It has a 64 bit Atom but 32 bit UEFI firmware.

I also found out this tablet would not boot a 32 bit kernel, so I used vmLinuz64 with
Core64 (not CorePure64) so I could still run 32 bit applications since this tablet only
has 2 Gig of soldered in non expandable RAM.

To create Core64:
Download  rootfs.gz  and  modules64.gz  from here:
http://tinycorelinux.net/17.x/x86/release/distribution_files/

Then:

Code: [Select]

cat rootfs.gz modules64.gz > Core64.gz
Download  vmlinuz64  from here:
http://tinycorelinux.net/17.x/x86/release/distribution_files/

Place  Core64.gz  and  vmlinuz64  in your boot directory and
point the boot loader at them.

If you have any  6.18.2-tinycore.tcz  extensions installed, you'll
need to run:

Code: [Select]

update-everythingso it fetches  6.18.2-tinycore64.tcz  versions of those extensions.

27

Final Releases / Re: Tiny Core v17.0

« Last post by Stefann on February 16, 2026, 11:43:00 AM »

Thanks!

Yes I updated all in one go.
Used the corebook to help me.
In “normal live” I work from the commandline by ssh. But for these update things I like using the gui for reason it requires me to do a lot of things I very rarely do. And be aware that I’m absolutely not an expert.
The reason I asked is that I only marginally did understood your guidance.
And… I prefer understanding what I do, as that helps a lot when things go wrong.
Still thanks. I did reread it 5 times and I think I start to understand it (lol). Learning is fun.

So…
I did the apps update from the gui.
As indicated by the corebook you can select all apps together by selecting the first, holding shift, and selecting the last.


All in all….
I’m doing a much better job than last year. TC15-to-16.
Last year I only updated core.gz and vmlinuz. I was totally not aware that I should have done something with the apps. The initial reply from @juanito did guide me to that (thanks).

It’s all a bit tricky as the systems are headless. So if I loose them I have to physically unmount them and get a keyboard and monitor from the attic.

28

Final Releases / Re: Tiny Core v17.0

« Last post by Rich on February 16, 2026, 11:20:00 AM »

Hi Stefann

... Question: so far so good? or do I need to revert back to step 2 and follow your guidance?

Sounds like you have it under control.You said you ran
apps, update. There's an  update-everything  command
that handles it all in one shot.

29

Final Releases / Re: Tiny Core v17.0

« Last post by Stefann on February 16, 2026, 10:31:28 AM »

oops...
Thanks @rich...
however... I found some time and already started.

On my HP510 thin client with Via Eden 1GHz dual core 64bit processor
Im using the 32bit iso because this is the staging system for my ultra low power Via Eden 500MHz single core 32bit system
Its a frugal install from the internal compact flash
Its a headless system reachable by ssh & VNC with samba file-service

What I did:
1/
- download the core-17.0.iso to my MacBook
- copied core.gz to /mnt/sda1/tce/boot/core17.gz
- copied vmlinuz to /mnt/sda1/tce/boot/vmlinuz17
- changed /mnt/sda1/tce/boot/extlinux/extlinux.conf to boot from core17.gz & vmlinuz17
sudo reboot

==> succesfull!
==> both ssh & VNC connection work, samba works

2/
made copy of the tce/optional folder to make sure I can revert back.

3/
Using the VNC gui:
- apps, update
- process
wait about 10 minutes.
==> All successfully updates BUT some apps require python3.14 (was running on 3.9, coming from TC15)

4/
installed python3.14.tcz
==> success

5 (still to be done)/
Now I need to update some python3.9 modules I installed myself, will do that later

Question: so far so good? or do I need to revert back to step 2 and follow your guidance?

30

Final Releases / Re: Tiny Core v17.0

« Last post by Rich on February 16, 2026, 09:57:07 AM »

Hi Stefann

... You can replace core.gz and vmlinuz to update, ...

In addition, you will need to replace any kernel module extensions you
are using, for example:

Code: [Select]

alsa-modules-KERNEL.tcz
filesystems-KERNEL.tcz
graphics-KERNEL.tcz
i2c-KERNEL.tcz
wireless-KERNEL.tcz
etc
Where the  KERNEL  part looks something like  6.12.11-tinycore.

A better plan would be to create a new tce directory as Juanito
suggested and download new copies of all of your extensions
from the TC17 repo.

You can simplify the process if you  cd  to the tce/optional/
directory you want to clone.
Then:

Code: [Select]

ls -1 *.tcz > Ext.lstThat's a  dash one  after  ls.
Move the  Ext.lst file to your new  tce/optional/  directory.

Grab a copy of the latest  FetchExt.sh  script from here:
https://forum.tinycorelinux.net/index.php/topic,23034.msg178902.html#msg178902
Place it in your new  tce/optional/  directory and make it executable.
Read the  Define Variables  section of the script, or run:

Code: [Select]

./FetchExt.sh -h
For  Intel  type processors run this:

Code: [Select]

KString="\-[0-9]+.[0-9]+.[0-9]+-tinycore.*.tcz"
sed -i -E 's|'$KString'|-KERNEL.tcz|g' Ext.lst
For  Arm  type processors run this:

Code: [Select]

KString="\-[0-9]+.[0-9]+.[0-9]+-piCore.*.tcz"
sed -i -E 's|'$KString'|-KERNEL.tcz|g' Ext.lst
Then run:

Code: [Select]

for F in $(cat Ext.lst); do ./FetchExt.sh "$F"; doneThat should populate your new  tce/optional/  directory with new
versions of all of your extensions.