WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Raspberry Pi / Re: bluetooth startup script
« Last post by Paul_123 on August 17, 2026, 06:42:21 AM »
The hdmi is a soundcard, not an audio backend.   You need something like pulse audio or bluealsa to do that.
22
Off-Topic - Tiny Core Lounge / Full Linux on your Android device
« Last post by vinceASPECT on August 17, 2026, 05:28:48 AM »
Hello Forum,

If it is any help to people that want a simple fast Linux
Desktop on their Android device , then there is

"Local Desktop".  Free. App. 7 megs

Just get that free app mentioned above and run it.....no other human
Interactions are required and in around 10 mins you
Will have a full Arch Linux desktop on your Android device.

https://localdesktop.github.io/

The .apk file version 2.1.1

Here is a video of Local Desktop.

https://m.youtube.com/watch?v=doKHsg9TeFg&t=209s

Thanks
C

23
Here's some background: https://gitlab.freedesktop.org/mesa/mesa/-/work_items/12733

I've been wondering if we shouldn't revert to mesa-24.1.7 and the way things were for x86. We could perhaps eliminate the llvm dependency if we assume that nobody uses software acceleration, but if I understand correctly some graphics adapters need that to function.

I don't think we should revert for x86_64 or armhf/aarch64 otherwise we will lose the support for newer hardware.

Mesa aside, the linux kernel no longer supports 32-bit, so perhaps we could consider a "sunset" x86 version with the last lts kernel supporting 32-bit and mesa-24.1.7.
24
Raspberry Pi / Re: Raspberry Pi Zero Wireless and piCore14.x LAN Connectivity
« Last post by Juanito on August 17, 2026, 04:36:27 AM »
Assuming you're speaking of getting wifi working?

I have an RPi0w - I'm guessing an RPi02w will work in the same way.

You will need to put the RPi0 sd card into another machine to copy files to it.

Copy the *tcz, *tcz.dep and *tcz.md5.txt files from here to the sd card tce/optional folder: http://tinycorelinux.net/17.x/armhf/tcz/wifi.tcz.tree and additonally copy firmware-rpi-wifi.tcz{,md5.txt}

Put the sd card back into the RPi0, connect it to a keyboard and monitor and boot.

Next:
Code: [Select]
tce-load -i firmware-rpi-wifi
tce-load -i wifi
wifi.sh
[connect to your wifi]

Add firmware-rpi-wifi.tcz and wifi.tcz to onboot.list

Add the following to bootlocal.sh:
Code: [Select]
cat /opt/bootlocal.sh
...
# ------ Put other system startup commands below this line
wifi.sh -a

Make a backup:
Code: [Select]
filetool.sh -b
Now you should be able to reboot and have wifi connect automatically - my RPi0w has done this without being touched for at least 2 years...
25
Raspberry Pi / Re: bluetooth startup script
« Last post by meo on August 17, 2026, 04:04:38 AM »
Hi Paul_123!

Thanks for your comment. The sound is tied automatically to hdmi0. I never saw in the inctructions on the internet anything about any command about the sound. Maybe there should be. I'm just trying something that I saw on the internet about RPi and bluetooth.

Kind Regards,
meo
26
Raspberry Pi / Re: Raspberry Pi Zero Wireless and piCore14.x LAN Connectivity
« Last post by cybercat on August 17, 2026, 01:20:48 AM »
Bump. I'm also trying to get a zero 2 w working.

The messages on the forum are somewhat contradictory, confusing, and scattered. Is there a final document on getting the zero 2 w running?

Thanks
27
The difference is noticeable in dep files:

For 17.x, http://tinycorelinux.net/17.x/x86_64/tcz/libEGL.tcz.dep:
Code: [Select]
mesa.tcz
wayland.tcz
The 16.x one is the same.

For 15.x, http://tinycorelinux.net/15.x/x86_64/tcz/libEGL.tcz.dep:
Code: [Select]
libGL.tcz
wayland.tcz
and dependencies of the libGL are:
Code: [Select]
libXdamage.tcz
libXxf86vm.tcz
libdrm.tcz
libxshmfence.tcz
No mesa is required.

I’m asking this question because the mesa.tcz required in the new version takes up more space, at least 30M adding its dependency llvm22-lib.tcz!

However, I just intend to run an application in TCL, which is considered a sandboxed environment. And I install TCL in VirtualBox without either graphic hardware acceleration enabled or graphic driver installed. The app is built on the electron, which embeds a browser and depends on libEGL forcefully (AFAIK). But it can function normally even if "GLX initialization error" emerged in terminal output (both on 15.x and 17.x). That is to say, this app doesn't rely on libEGL actually, and for me, after migrating to the 17.x version, the mesa is probably redundant and only makes TCL bloat.

Back to the main point, what changes lead to this? The changelog of libEGL
Code: [Select]
Change-log:     2014/02/14 first version
                2014/10/28 updated 9.2.1 -> 10.3.2
                2015/12/17 updated 10.3.2 -> 11.0.7
                2016/08/01 updated 11.0.7 -> 12.0.1
                2017/02/19 updated 12.0.1 -> 13.0.4
                2017/09/14 updated 13.0.4 -> 17.2.0
                2018/03/30 updated 17.2.0 -> 18.0.0
                2019/04/04 updated 18.0.0 -> 19.0.1
                2019/11/11 updated 19.0.1 -> 19.2.3
                2019/11/23 recompiled
                2020/12/06 updated 19.2.3 -> 20.3.0
                2020/12/27 updated 20.3.0 -> 20.3.1
                2022/01/16 updated 20.3.1 -> 21.3.4
                2023/01/12 updated 21.3.4 -> 22.3.3
                2023/04/13 updated 22.3.3 -> 22.3.7
                2025/03/04 updated 22.3.7 -> 24.1.7
                2025/10/16 updated 24.1.7 -> 25.2.5
Current:        2026/05/24 updated 25.2.5 -> 26.0.7
only list an array of version codes (also for libGL). The thread about mesa updating in TCE News
Due to changes in the structure of the mesa graphics libraries several graphics extensions have been updated in the tc-16.x x86_64 repo.
only mentions there are changes in the structure of the mesa graphics libraries. So what exactly is it? Can I replace libEGL with the old version to get rid of the large mesa?
28
Raspberry Pi / Re: bluetooth startup script
« Last post by Paul_123 on August 16, 2026, 05:58:22 PM »
what are you using for your audio backend.

bluez just negotiates the connection, if there is no backend configuring audio, then it wont connect.
29
Extension requests / Sound ripper perhaps abcde!
« Last post by meo on August 16, 2026, 01:06:35 PM »
Hi guys!

I don't know if there is an audio ripper but abcde seems to be OK:

Kind Regards,
meo
30
Extension requests / Re: OMXPlayer for piCore32.
« Last post by meo on August 16, 2026, 01:04:36 PM »
Hi Juanito!

aplay -l gives me:

**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have found out that the card that works is vc4hdmi0df.

Kind greetings,
meo
Pages: 1 2 [3] 4 5 ... 10