Recent Posts

21

TCE Bugs / Re: solaar.tcz.dep missing libffi7.tcz in x86_64 repo

« Last post by Rich on July 03, 2026, 10:43:02 PM »

Hi GNUser
solaar.tcz.dep updated. See if it works any better now,

22

piCore Test Releases / Re: piCore 17 Beta Releases

« Last post by Paul_123 on July 03, 2026, 10:01:44 PM »

I doubt you are going to be able to have exclusive access to the GPU anymore, without doing a baremetal.  The firmware configuration of the gpu is no longer supported.  Raspi says they didnot remove it from the firmware, but will not do anything about it if it’s broken.

The fkms overlay without the vc4 drivers loaded is a bandaid to force the kernel to configure the framebuffer for a console.  But to really use the gpu you will need the vc4-kms-v3d overlay, and the graphics kernel module extension.

There is a chance the made some recent changes without any notes.  I’ll be updating the kernel before I release the final version.

23

TCE Bugs / solaar.tcz.dep missing libffi7.tcz in x86_64 repo

« Last post by GNUser on July 03, 2026, 09:22:33 PM »

Hi Juanito. solaar.tcz in TCL17.1 x86_64 is missing libffi7.tcz in its .dep file:

Code: [Select]

$ solaar &
$ Traceback (most recent call last):
  File "/usr/local/bin/solaar", line 54, in <module>
    import solaar.gtk
  File "/usr/local/lib/python3.9/site-packages/solaar/gtk.py", line 31, in <module>
    import solaar.cli as _cli
  File "/usr/local/lib/python3.9/site-packages/solaar/cli/__init__.py", line 25, in <module>
    import logitech_receiver.device as _device
  File "/usr/local/lib/python3.9/site-packages/logitech_receiver/device.py", line 25, in <module>
    import hidapi as _hid
  File "/usr/local/lib/python3.9/site-packages/hidapi/__init__.py", line 34, in <module>
    from hidapi.udev import close  # noqa: F401
  File "/usr/local/lib/python3.9/site-packages/hidapi/udev.py", line 37, in <module>
    import gi
  File "/usr/local/lib/python3.9/site-packages/gi/__init__.py", line 40, in <module>
    from . import _gi
ImportError: libffi.so.7: cannot open shared object file: No such file or directory

[1]+  Done(1)                    solaar

$ provides.sh libffi.so.7
libffi7.tcz
solaar is a great extension for logitech devices. Thanks for putting it in the repo

24

piCore Test Releases / Re: piCore 17 Beta Releases

« Last post by zharr on July 03, 2026, 09:14:34 PM »

Only did a quick test because some specifics of my programs broke, but I encountered no other issues I could attribute to piCore.

E.g. I need exclusive access to the 3D pipeline but the config.txt change (loading vc4-fkms-v3d) must have made the console render with the GPU/GPU, so even enabling the QPU failed. But even reverting that change, something is still submitting programs to the QPU / 3D pipeline, which prior versions didn't. lsmod shows no major differences except brcmfmac_cyw -> brcmfmac_wcc.
I don't suppose you might have an idea?

I'm not in a hurry to upgrade, though I did just encountered an issue with copy2fs.lst on 16 so I was hoping it might be fixed in 17.

25

TCB Talk / copy2fs.lst ignored by tc-config on boot, only works with tce-load

« Last post by zharr on July 03, 2026, 08:51:34 PM »

I'm using piCore and trying to have all auto-loaded extensions copied to RAM (to unmount the SD card during operation) but normally mount optional extensions loaded later.
However this only seems to work when using tce-load directly, on boot it always seems to mount the extensions (though the copy2fs.flg works).
Seeing how the /etc/init.d/tc-config script has it's own implementation handling copy2fs.lst (different from tce-load), the issue might lie there.
That's why I'm posting here - I don't think it's necessarily a piCore packaging issue.
Sadly, I have not found a good way to edit that script to iterate on (or even run it safely).
Any help would be appreciated!

26

TCB Q&A Forum / Re: Truncated core dumps with TC17

« Last post by Rich on July 03, 2026, 05:16:37 PM »

Hi dspence
I'm afraid I don't have any good answers for you, but maybe
a few ideas to try to make some progress on this.

Maybe the contents of dmesg can provide some insight by
saving a copy when the coredump occurs.

Maybe use  inotifywait  to monitor  /data/coredumps  for a
file to be created, and then trigger:

Code: [Select]

dmesg > dmesg$(date +%F-%T).txtThat should create  dmesgYYYYMMDD-HH:MM:SS.txt  every
time a coredump occurs.

If you need help with that, I can provide a sample of how I
used  inotifywait  to trigger a command when a file gets created.

I also found this about using  gdb  to generate a coredump file:
https://stackoverflow.com/a/79434751

27

TCB Q&A Forum / Truncated core dumps with TC17

« Last post by dspence on July 03, 2026, 09:53:19 AM »

Hi all,

I have been using the following settings on TC13 to get useful core dumps (thanks to Rich for helping me out):

This is in an application's startup script:
   # Set the core dump file size limit.
   # Limit each dump to 781250 blocks of 512 bytes, i.e. 400 MB.
   ulimit -c 781250

This is in bootlocal.sh:
   # Write all core dumps to /data/coredumps. Attach the name of the executable to the file name.
   # This way, the system will always store *only the latest* core dump of each executable.
   mkdir -p /data/coredumps
   chmod 1777 /data/coredumps
   sysctl -w kernel.core_pattern='/data/coredumps/core.%e'

The drive that the /data/ link points to has over 200 GB of free space, so the truncation is not happening because of limited space in the target location.

With Tiny Core 13 this worked well.  With Tiny Core 17 this results in small "truncated" core files.

I tried changing to use "ulimit -c unlimited" and that didn't help.

For comparison, the same program on TC13 generates a core file about 156 MB in size, and on TC17 it generates a file about 73 KB in size.  Maybe these weren't from the same crash but in general that's what the sizes look like.  With GDB I can see the stack trace on TC13 and on TC17 it gives messages like "warning: BFD: warning: /mnt/sda1/coredumps/core.test has a segment extending past end of file" and "warning: failed to parse execution context from corefile: Cannot access memory at address 0x7fffbba85fe0", "Failed to read a valid object file image from memory", "Backtrace stopped: Cannot access memory at address 0x7fffbba837f8", etc.

Is there another setting I have to change?

Thanks.

28

TCB Bugs / MOVED: mount tool not reading drive!

« Last post by Rich on July 03, 2026, 09:10:17 AM »

This topic has been moved to TCB Talk.

https://forum.tinycorelinux.net/index.php?topic=28200.0

29

TCB Talk / Re: mount tool not reading drive!

« Last post by Rich on July 03, 2026, 09:09:16 AM »

Hi JunkYard
First see if the system detected the floppy:

Code: [Select]

grep '/dev/fd' /etc/fstabIf grep doesn't give a response, then do this:

Code: [Select]

sudo modprobe floppy
sudo rebuildfstab
grep '/dev/fd' /etc/fstabGrep should print something like this:

Code: [Select]

/dev/fd0 /mnt/fd0 auto noauto,users,exec,umask=000 0 0 # Added by TCIf you get that response, start the mount tool.
It should now have a button labeled  fd0.
Insert a formatted floppy disk and click the  fd0  button.

30

Extension requests / Re: Notepadqq!

« Last post by Rich on July 03, 2026, 08:31:04 AM »

Hi meo
Juanito left compile notes and a source tarball here:
http://tinycorelinux.net/16.x/aarch64/tcz/src/pragtical