Recent Posts

21

General TC Talk / Re: Serial Port

« Last post by Rich on February 13, 2026, 10:05:58 AM »

Hi MTCAT

... The file does not exist yet.
The second something gets written to  Temp.log , it gets created. ...

If nothing gets written to  Temp.log  (i.e. minicom failed for some reason) and
you try to read from  Temp.log , you'll get a file not found error. If you do it like
this, you will only need to deal with an empty file for the same situation:

Code: [Select]

ln -sf  $(date +"%y%m%d%H%M%S").log Temps.log && touch Temps.log; sudo microcom -s 9600 /dev/ttyACM0 > Temps.log
Without the touch command, you get a link to a file that doesn't exist:

Code: [Select]

tc@E310:~$ ln -sf  $(date +"%y%m%d%H%M%S").log Temps.log
tc@E310:~$ ls -l *.log
lrwxrwxrwx 1 tc staff 16 Feb 13 09:46 Temps.log -> 260213094621.log
With the touch command, you get a link to an empty file that does exist:

Code: [Select]

tc@E310:~$ ln -sf  $(date +"%y%m%d%H%M%S").log Temps.log && touch Temps.log
tc@E310:~$ ls -l *.log
-rw-r--r-- 1 tc staff  0 Feb 13 09:48 260213094817.log
lrwxrwxrwx 1 tc staff 16 Feb 13 09:48 Temps.log -> 260213094817.log
If you want to see what the current file is:

Code: [Select]

tc@E310:~$ readlink Temps.log
260213094817.log
If you need to test if the current file is empty:

Code: [Select]

tc@E310:~$ [ ! -s Temps.log ] && echo "$(readlink Temps.log) is empty"
260213094817.log is emptyor:

Code: [Select]

tc@E310:~$ [ -s Temps.log ] || echo "$(readlink Temps.log) is empty"
260213094817.log is empty

22

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by andyj on February 13, 2026, 07:48:06 AM »

From the Makefile:

Code: [Select]

objs/Makefile: test -d '$(DESTDIR)/var/log/nginx' \
objs/Makefile: || mkdir -p '$(DESTDIR)/var/log/nginx'

What I don't see is where you are using this path anywhere. It may be that there is a default behavior that is looking for "/var/log/nginx/whatever.log", but when there is no "whatever.log" then what is being checked is "/var/log/nginx" and because "nginx" is the last thing in the path it is being interpreted as a file and not as the directory that it is.

The configured error log path is "--error-log-path=/var/log/nginx/error.log", but "--http-log-path=/var/log/nginx" is given as a directory path and not a file name so it could be misinterpreted as above. I can recompile it with something like "--http-log-path=/var/log/nginx/access.log" and see if that changes what you are seeing.

23

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Zhe on February 13, 2026, 02:00:39 AM »

my nginx.conf works fine when /var/log/nginx is a file.

I suspect the problem might lie elsewhere—it could be that different versions of Nginx lead to different behaviors, or it might be a compilation issue.

24

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Zhe on February 12, 2026, 11:51:01 PM »

Hi Rich. When it’s a directory, the configuration check fails.

Hi,andyj

my nginx.conf:

Code: [Select]

user tc staff;
worker_processes  1;
error_log /tmp/nginx_error.log warn;
pid       /tmp/nginx.pid;
events {
    worker_connections  512;
}
http {
    include       mime.types;
    default_type  application/octet-stream;
    gzip on;
    gzip_vary on;
    gzip_min_length 1024;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_types
        text/plain
        text/css
        text/javascript
        application/json
        application/javascript
        application/xml+rss
        image/svg+xml;

    client_body_temp_path /tmp/nginx/client;
    server_tokens off;

    server {
        listen 80;
        listen [::]:80;
        server_name xxxxx;
        return 301 https://$host:xxx$request_uri ;
    }

    server {
        listen xxx ssl;
        listen [::]:xxx ssl;
http2 on;
        server_name xxxxx;

        root /xxxx/web;
        index index.html;
        charset utf-8;
        autoindex off;
        ssl_certificate     /etc/xxxx/server-cert.pem;
        ssl_certificate_key /etc/xxxx/server-key.pem;
        ssl_protocols TLSv1.2 TLSv1.3;
        ssl_prefer_server_ciphers on;

        add_header X-Content-Type-Options "nosniff";
        add_header Referrer-Policy "no-referrer-when-downgrade" always;
        if ($request_method !~ ^(GET|HEAD|OPTIONS)$ ) {
            return 405;
        }

        location ~ /\. {
            deny all;
            access_log off;
            log_not_found off;
        }
        location ~* \.\. {
            deny all;
            return 403;
        }

........

    }
}


25

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Rich on February 12, 2026, 11:34:02 PM »

Hi andyj
That was directed at Zhe, right?

26

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by andyj on February 12, 2026, 11:25:07 PM »

Try posting your nginx.conf file.

27

Micro Core / Re: AMD XDNA device driver is missing

« Last post by Rich on February 12, 2026, 11:03:18 PM »

Hi xLeaves
Editing the  .config  manually is discouraged:
1. Some options interact with other options.
2. Saying Y to some options may require some other options to be set to Y.
3. Saying M to some options may require some other options to be set to M.
4. Some  CONFIG_  options only become visible when options they depend on are enabled.

These interactions and dependencies get resolved by the many Kconfig files
in the kernel tree.

Use the correct tools for your project:

Code: [Select]

tce-load -i compiletc perl5 bash bc ncursesw-dev elfutils-dev

# Change these (and others) to match the version and architecture you are compiling for:
wget http://tinycorelinux.net/16.x/x86/release/src/kernel/linux-6.12.11-patched.tar.xz
wget http://tinycorelinux.net/16.x/x86/release/src/kernel/config-6.12.11-tinycore

tar xf linux-6.12.11-patched.tar.xz

cd linux-6.12.11

make mrproper

cp ../config-6.12.11-tinycore ./.config
make oldconfig

# This next step presents you with a menu driven way to make your changes correctly.

make menuconfig

# It also has a search function.
# Once the  menuconfig  menu is up, press  /  to call up the (case insensitive) search dialog.

# When you are done, select  Save  using the  right arrow  key and hit enter enter enter
# select  Exit  using the  right arrow  key and hit enter enter

# Then start you compilation.

28

TCE Bugs / Re: nginx log path ---core x86 16.x

« Last post by Rich on February 12, 2026, 10:20:16 PM »

Hi Zhe
I briefly fired up nginx under TC16 x86. These were my results:

Code: [Select]

tc@box:~$ ls -l /var/log/
total 212
-rw-r--r--    1 root     staff        58837 Feb 12 21:41 Xorg.0.log
-rw-r--r--    1 root     root             0 Feb 12 21:40 autologin
-rw-r--r--    1 root     root        148079 Feb 12 21:42 messages
drwxr-xr-x    2 root     root            40 Dec 12 02:09 nginx/
-rw-rw-r--    1 root     staff         2304 Feb 12 21:42 wtmp
tc@box:~$
tc@box:~$ sudo nginx
nginx: [emerg] open() "/usr/local/etc/nginx/nginx.conf" failed (2: No such file or directory)
tc@box:~$ ls -l /var/log/
total 212
-rw-r--r--    1 root     staff        58837 Feb 12 21:41 Xorg.0.log
-rw-r--r--    1 root     root             0 Feb 12 21:40 autologin
-rw-r--r--    1 root     root        148201 Feb 12 21:45 messages
drwxr-xr-x    2 root     root            60 Feb 12 21:45 nginx/
-rw-rw-r--    1 root     staff         2304 Feb 12 21:42 wtmp
tc@box:~$ ls -l /var/log/nginx/
total 4
-rw-r--r--    1 root     root           118 Feb 12 21:45 error.log
tc@box:~$
It shows  /var/log/nginx  is a directory.

29

Micro Core / Re: AMD XDNA device driver is missing

« Last post by xLeaves on February 12, 2026, 09:53:45 PM »

I am using the AMD64 architecture (x86_64).

Yes, I'm attempting to compile the kernel myself, but I only have a Debian 12 virtual machine with two virtual CPU cores, and the compilation process is extremely slow.

In fact, support for the AMD XDNA NPU driver wasn't introduced until Linux 6.14 and later versions. TinyCore 17 is the first distribution to include this capability, likely because the driver was stripped down. As a result, it only detects the PCIe device but cannot utilize it.

I made the following modifications to .config and hope to successfully enable the XDNA NPU:

# Enable the base acceleration framework (NPU driver dependency)
sed -i 's/# CONFIG_ACCEL is not set/CONFIG_ACCEL=y/' .config

# Remove any existing AMD_XDNA configuration entries to avoid redundant definitions
sed -i '/CONFIG_AMD_XDNA/d' .config

# Compile the NPU driver as a kernel module (m indicates compiling as a .ko module, not built-in)
echo "CONFIG_AMD_XDNA=m" >> .config

# Disable NPU debug mode (unnecessary in production, reduces compilation overhead)
echo "CONFIG_AMD_XDNA_DEBUG=n" >> .config

# Fallback to ensure PCI/cryptography dependencies are enabled (already included in official config, prevents accidental omission)
sed -i 's/# CONFIG_PCI is not set/CONFIG_PCI=y/' .config
sed -i 's/# CONFIG_CRYPTO is not set/CONFIG_CRYPTO=y/' .config

The compilation has been running for 12 hours and has failed once. I'm trying to obtain amdxdna.ko, though I'd much prefer to get vmlinuz64, which directly includes the required drivers 

30

General TC Talk / Re: Serial Port

« Last post by Rich on February 12, 2026, 05:30:56 PM »

Hi MTCAT

... I think method number one would be the easiest way of getting the temperature readings into the acquisition GUI (because we would be loading temp values from a file that always has the same name) but method number 2 would seem to be the most organized way of storing them for the future, if I wanted to look at the temp readings after the fact for example. ...

I have a fix for that too.

You don't say what that file name is, so I'll assume it's called Temps.log:

Code: [Select]

ln -sf  $(date +"%y%m%d%H%M%S").log Temps.log; sudo microcom -s 9600 /dev/ttyACM0 > Temps.logThis creates a link to a file with a  YYMMDDHHMMSS.log  date code name.
The file does not exist yet.
The second something gets written to  Temp.log , it gets created.
Plus, when you read from  Temp.log , you'll be reading from the current log.