Recent Posts

61

TCE Talk / Re: Source of wbar

« Last post by amplefiction on March 02, 2026, 11:17:52 AM »

Thanks Juanito and Rich

62

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by Paul_123 on March 02, 2026, 10:40:56 AM »

hid_multitouch is in the base os,  you just need to load it.  You also need the touchscreen extension.   The OS automatically loads the correct one, as long as you load touchscreen-KERNEL.tcz

63

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by lwhritner on March 02, 2026, 10:25:06 AM »

Thank you for your response!

When looking up "hid_multitouch" in our build, it doesn't appear. I am using the aarch64 version of piCore.

I found that the .tcz files compatible with aarch64 that are for the touchscreen are as follows:

Code: [Select]

touchscreen-6.12.15-piCore-v8-16k.tcz
touchscreen-6.12.15-piCore-v8.tcz
touchscreen-6.12.25-piCore-v8-16k.tcz
touchscreen-6.12.25-piCore-v8.tcz
Do you think these extensions would be beneficial to helping us resolve this issue?

64

TCB Bugs / Re: Module.symvers and System.map Missing for TC 17.x

« Last post by Paul_123 on March 02, 2026, 09:59:20 AM »

Did I not provide it to you Juanito?  I should have.    I normally provide it for piCore.

65

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by gadget42 on March 02, 2026, 09:49:47 AM »

as i am always trying to learn more about topics as they come along casually...i used duckduckgo-lite to search:

https://start.duckduckgo.com/lite/?q=pkill+udhcpc

and at least right now(post date/time) a tcl forum post is the first result listed:

https://forum.tinycorelinux.net/index.php/topic,20223.0.html

great that the forum continues to be present in search results!

66

TCB Talk / Re: Installing on a Tatung TWN-5213 CU

« Last post by gadget42 on March 02, 2026, 09:19:18 AM »

this might help others to follow along in the journey:

https://www.manualshelf.com/manual/tatung/twn5213/user-manual-english.html

67

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by Rich on March 02, 2026, 08:45:02 AM »

Hi patrikg
I know. I do tend to include the nodhcp boot code.
I leave the pkill in there for a couple of reasons:

1. I copy this script anytime I set up a new machine or TC version.
   The pkill protects me if I forget the nodhcp boot code.

2. I sometimes post this for new users wanting a static IP. The pkill
   ensures it will work regardless of the new users skill level, knowledge
   of boot loaders, and knowledge of boot codes. And, this way I don't
   have to try to walk them through boot loader and boot code changes.

68

TCB Bugs / Re: Module.symvers and System.map Missing for TC 17.x

« Last post by Juanito on March 02, 2026, 04:42:41 AM »

The Module.symvers file used to be useful to compile kernel modules quickly, but it seems this was dropped after linux-5.x.y.

It sounds like you didn't copy config-6.18.2-tinycore64 to .config and "make oldconfig" before you started?

69

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by patrikg on March 02, 2026, 02:18:43 AM »

You can remove the line:

Code: [Select]

pkill udhcpc
And add the kernel commmand line argument:

Code: [Select]

nodhcp
See:
https://distro.ibiblio.org/tinycorelinux/faq.html#bootcodes

To gain a little boot time.

70

TCB Talk / Re: : and keep getting overwritten — is there a clean, standard way to prevent thi

« Last post by Rich on March 02, 2026, 12:23:45 AM »

Hi _matthew_

... the bootsync file that is called before the bootlocal file, ...

Near the end of  /etc/init.d/tc-config , the system restores the files you
backed up. Shortly after that, bootsync is called and clobbers your hosts
file. Take a look at  /usr/bin/sethostname  and you'll see it too.

I haven't found what what alters resolv.conf yet.
On my systems, it's a script I use to set a static IP:

Code: [Select]

tc@E310:~$ cat /opt/eth0.sh
#!/bin/sh
pkill udhcpc
ifconfig eth0 192.168.1.35 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1
echo nameserver 192.168.1.1 > /etc/resolv.conf
echo nameserver 68.237.161.12 >> /etc/resolv.conf
tc@E310:~$

... So the first echo nameserver 192.168.1.151 >  /etc/resolv.conf sets it up
long enough for ntp to resolve the hosts it needs to start.  Sometime beteween
the first one and the second one, it gets plowed. ...

These 3 commands are the only thing run between the echo commands:

Code: [Select]

/usr/sbin/ntpd -p pool.ntp.org
/usr/sbin/crond -b
/usr/local/etc/init.d/openssh startRestart each one manually to figure out who the troublemaker is.