Recent Posts

21

General TC Talk / Re: Serial Port

« Last post by MTCAT on February 25, 2026, 02:39:22 PM »

Hi Rich,

Oh, okay, thanks for the explanation, when I get the system finalized I'll give those commands a try!

Thanks a lot,

David

22

Corepure64 / Chrony Tcz Request

« Last post by gharig on February 25, 2026, 01:20:28 PM »

Hi All,

I'm looking to install Chrony so my machines can act as time servers on my private air-gapped network.  I looked for Chrony.tzc, but it might be named something diffrently.  If it is not on avaiable then I would like to request a tcz for it.

Thanks
gharig

23

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by Rich on February 25, 2026, 12:41:09 PM »

Hi lwhritner
Welcome to the forum.

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.

24

TCE Talk / Re: Source of wbar

« Last post by Rich on February 25, 2026, 12:32:51 PM »

Hi Juanito
Well that matches my x86/x86_64 hardware.

I suspect the armv6/tcz/src/wbar-2.3.4.tgz was saved but never
incorporated.

25

Tiny Core Netbooks / Re: Please recommend a version of Linux Ttimy Core for Asus EeePC.

« Last post by Rich on February 25, 2026, 12:28:55 PM »

Hi DiAno
Welcome to the forum.

The light side:
I would suggest trying a 32 bit version (X86) because of your limited RAM.
Try something relatively recent, like TC14, 15, or 16.

The dark side:
I have an Asus T100 netbook with an Atom Z3775.
It has 2 Gig RAM soldered in, not expandable.
It refused to boot a 32 bit kernel, only 64 bit booted.
I had to config and compile a new kernel.

A new hope:
I did eventually get most things working, including the touch screen.
I settled on running Core64 (32 bit apps on 64 bit kernel).
My kernel config changes were added to later TC versions.

If your Asus EeePC is anything like my T100, go to the search page:
https://forum.tinycorelinux.net/index.php?action=search
And set the  Search for:  field to  asus t100
You'll see more information I've posted on this device.

26

Raspberry Pi / piCore TouchScreen Not Working Properly

« Last post by lwhritner on February 25, 2026, 12:12:28 PM »

Hi there, I am a student interning for a small company that uses piCore for its embedded systems. I've been running into a problem with the touchscreen that neither I nor my coworker/supervisor can figure out.

The issue is that while the screen detects touch, it processes it as a touch that occurs on the bottom right of the screen and nowhere else. Specifically, we are using a screen that is 1024x600, and the touch is processed at the point 1023x599. See below the log when using libinput debug-events:

Code: [Select]

-event0   DEVICE_ADDED                 QDtech MPI7003 Touchscreen        seat0 default group1  cap:t ntouches 1 calib
-event1   DEVICE_ADDED                   RPI Wired Keyboard 4            seat0 default group2  cap:k
-event2   DEVICE_ADDED                   RPI Wired Keyboard 4            seat0 default group2  cap:k
-event3   DEVICE_ADDED                 vc4-hdmi-0                        seat0 default group3  cap:k
-event5   DEVICE_ADDED                 vc4-hdmi-1                        seat0 default group4  cap:k
-event0   TOUCH_DOWN                   +0.000s -1 (0) 99.90/99.83 (1024.00/600.00mm)
 event0   TOUCH_FRAME                  +0.000s
 event0   TOUCH_UP                     +0.097s -1 (0)
 event0   TOUCH_FRAME                  +0.097s
 event0   TOUCH_DOWN                   +2.173s -1 (0) 99.90/99.83 (1024.00/600.00mm)
 event0   TOUCH_FRAME                  +2.173s
 event0   TOUCH_UP                     +2.323s -1 (0)
event0   TOUCH_FRAME                  +2.323s
We are using a QDtech MPI7003 Touchscreen and a Raspberry Pi CM4. This occurs on both PiCore 13 and 16.

We have flwm_topside.tcz and all of its dependencies installed, as well as libXrandr.tcz and Xorg-3d.tcz and their respective dependencies. Through our research, I came across using xinput a lot, though I cannot seem to find a way to install it (if it'll even be helpful in the first place).

Our guess is that there's something up with how the transformations are being processed. It could also be a kernel issue, but I wanna exhaust any and all further options before debugging the kernel. I am also going to try using other hardware such as a mouse, a CM5, and a different touchscreen once I get them from my supervisor. I am also very new to Linux, so this could even be a simple fix I am overlooking.

Any further insight would be greatly appreciated. I can provide more info to this forum if need be to help troubleshoot.

    [Edit]: Added code tags.  Rich

27

TCE Talk / Re: Source of wbar

« Last post by Juanito on February 25, 2026, 11:57:22 AM »

On piCore64:

Code: [Select]

wbar --version
Version of wbar 2.3.0

I don't have access to an RPi running piCore at the moment to check.

28

Tiny Core Netbooks / Re: Please recommend a version of Linux Ttimy Core for Asus EeePC.

« Last post by gadget42 on February 25, 2026, 11:51:53 AM »

currently a forum search for "Asus EeePC"(without quotation marks) has 41 results including this thread

keep us posted on your progress!

29

Off-Topic - Tiny Core Lounge / Re: XLibre - a fork of Xorg

« Last post by GNUser on February 25, 2026, 11:41:34 AM »

I'm not sure I made a conclusion 

Thanks for clarifying. Your suggestions make sense.

While I don't like the idea of moving any architecture to wayland only, I understand that there are many things that TCL as a distro--and I as a user--have to deal with that are outside our control.

P.S. Rant follows.
   Pardon if I vent for just a second. Software such as systemd and wayland have caused a lot of fragmentation, uncertainty, and wasted precious resources (namely, human time and energy). I would know about wasted time and energy: I have invested well over 100 hours to make my TCL+labwc+sfwbar setup as productive as my TCL+fluxbox setup. I did that only to be prepared for the possibility of a future without Xorg. Truth be told, I was perfectly happy with fluxbox and actually prefer it over labwc+sfwbar.
    TCL really does a tremendous job of creating beauty and order out of the chaos that is all-things-linux. For as long as I use linux, TCL is the distro for me. But on some days, the BSDs (which don't have systemd or wayland, and don't suffer from nearly the same degree of fragmentation as linux) sure look attractive. As long as TCL enables me to stay productive and relatively sane, I have no plans on ditching linux for one of the BSDs. Thank you for all you do, Juanito.

30

TCE Talk / Re: Firefox

« Last post by gadget42 on February 25, 2026, 11:19:59 AM »

https://librewolf.net/