Recent Posts

21

TCE Bugs / The TCC package dependency on Tinecore 17 has issues.

« Last post by xLeaves on February 12, 2026, 01:58:33 AM »

The contents of the dep file are as follows:
glibc_base-dev.tcz
linux-6.12_api_headers.tcz
make.tcz
flex.tcz

Note that linux-6.12_api_headers.tcz no longer exists. The correct file should be linux-6.18_api_headers.tcz.

22

General TC Talk / Re: Serial Port

« Last post by MTCAT on February 11, 2026, 11:05:51 AM »

Hi Rich,

Thanks a lot for the help getting a timestamp into the log file, I'll give your suggestions a try next time I have the system up and running!

Thanks,

David

23

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by xor on February 11, 2026, 03:51:01 AM »

Someone wrote a script,
but who commissioned this script?!

24

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by Zhe on February 11, 2026, 03:38:48 AM »

Fine,  I misunderstood.

25

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by xor on February 11, 2026, 03:29:51 AM »

Off-Topic - Tiny Core Lounge

Conspiracy Theory: The Simpsons' "Power Outage"

Possible negative scenario on a global scale.

The problem is systems that can't be updated even though there's an update available!!!

26

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by Zhe on February 11, 2026, 03:08:20 AM »

Hi xor, do you have any specific cases you can discuss?

I suggest you sanitize the information before discussing it.

As far as I know, in the kernel config at:
http://tinycorelinux.net/16.x/x86/release/src/kernel/config-6.12.11-tinycore

These security-related features are not enabled, which may cause security concerns:

Code: [Select]

CONFIG_STACKPROTECTOR
CONFIG_RANDOMIZE_BASE
CONFIG_FORTIFY_SOURCE
CONFIG_SECURITY

However, some features are disabled. I guess this might be a compromise made for extreme size reduction.

PS: TinyCore’s architecture — consisting of a base system, read-only TCZ extensions, a modular ‘build-block’ style, and running entirely in RAM — effectively avoids most persistent threats, file tampering, malware residue, and permanent compromise.

However, it cannot mitigate runtime memory exploits, kernel vulnerabilities, network service flaws, TCZ supply chain attacks, or configuration issues.

Because the system and data reside in RAM, a successful exploit can compromise the session immediately without needing persistence.

It provides strong resilience against long-term infection, but not absolute security.

27

Off-Topic - Tiny Core Lounge / Re: Conspiracy Theory: The Simpsons' "Power Outage"

« Last post by xor on February 11, 2026, 01:44:45 AM »

{I'm writing this using translation as usual}

I'm not a software security expert;
I'm a meticulous computer user who only focuses on details.

Out of curiosity, I asked the AI ​​to create a script that would detect known vulnerabilities in my system.

Artificial intelligence;
He noted that he could more easily find overlooked security patches if I provided a full breakdown with 32 and 64 bit version information.
When I ran the prepared script and sent all the version information to the artificial intelligence for analysis, I was shocked by the report I saw.

I hope this is an AI hallucination

28

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by MrPorcine on February 10, 2026, 08:50:06 PM »

Rich,
Yes, thanks for the heads up. This is an embedded system where the Pi power is supplied via the GPIO pins. It's been working well for several years. Maybe only marginally working   . I don't think we've ever actually monitored the voltage drop across the GPIO pins.

So we've got some work to do. The test setup I've been using to solve this problem has a 40-wide flat cable that is probably twice as long as the one in the actual product. Hopefully this is the issue. TBD.

29

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by Rich on February 10, 2026, 08:39:23 PM »

Hi MrPorcine

... I wonder if by specifing rpi-ft5406 separately in config.txt I got two instances that were quarrelling.

Whatever it was, it sounds like it caused the hardware to work very
hard and seriously increase its power consumption.

30

Raspberry Pi / Re: piCore 16.0 and Raspi Touchscreen.

« Last post by Rich on February 10, 2026, 08:10:22 PM »

Hi MrPorcine
These lines caught my attention:

...

Code: [Select]

[    6.504608] edt_ft5x06 10-0038: supply iovcc not found, using dummy regulator
 ----- Snip -----
[    8.545320] hwmon hwmon1: Undervoltage detected!
 ----- Snip -----
[   11.014762] lan78xx 1-1.1.1:1.0 eth0: Link is Down
 ----- Snip -----
[   12.573423] hwmon hwmon1: Voltage normalised
 ----- Snip -----
[   14.085177] lan78xx 1-1.1.1:1.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
 ----- Snip -----


I would check to make sure your power supply is strong enough to
supply your hardware.

Double check your wiring/cabling to make sure all connections are solid.
No clip leads allowed.

Just because it says "Voltage normalised" and the network claims it
recovered, doesn't mean the rest of the hardware is properly configured.