Tiny Core Linux

Tiny Core Base => Raspberry Pi => piCore Final Releases => Topic started by: bmarkus on March 09, 2021, 08:46:08 AM

Title: piCore-13.0.3 released (32-bit)
Post by: bmarkus on March 09, 2021, 08:46:08 AM
piCore-13.0.3 (32-bit)

- BusyBox traceroute bug fixed


piCore-13.0.2 (32-bit)

- BusyBox updated to 1.33.0


piCore-13.0.1 (32-bit)

- CPU identification issue fixed, now the correct repository used.


piCore-13.0 (32-bit) is released which is expected work with all RPi boards. Main components:

- kernel 5.10.16
- glibc 2.32
- gcc 10.2.0
- util-linux 2.36.2
- e2fsprogs 1.46.1
- libffi 3.3
- micropython 1.14-72

There is only one SD card image for all boards which can be downloaded from

http://tinycorelinux.net/www/13.x/armv6/releases/RPi/

Picore-13.0.1 (32-bit)

CPU identification issue fixed, now the correct repository used.


Picore-13.0 (32-bit) is released which is expected work with all RPi boards. Main components:

- kernel 5.10.16
- glibc 2.32
- gcc 10.2.0
- util-linux 2.36.2
- e2fsprogs 1.46.1
- libffi 3.3
- micropython 1.14-72

There is only one SD card image for all boards which can be downloaded from

http://tinycorelinux.net/www/13.x/armv6/releases/RPi/
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Yuriy on April 26, 2021, 11:26:29 AM
Please, add ppp-modules-5.10.16-piCore-v7.tcz into the repository
Title: Re: piCore-13.0.3 released (32-bit)
Post by: bmarkus on April 26, 2021, 09:59:05 PM
Please, add ppp-modules-5.10.16-piCore-v7.tcz into the repository

Hi Yuriy

I will add it in the next days.

Béla
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Yuriy on April 27, 2021, 09:43:36 AM
Thanks a lot. Also missing is ipv6-netfilter-KERNEL.tcz, which some applications depend on, such as tcpdump.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 06, 2021, 06:37:30 PM
I need an Xorg server running on a 3B+. I don't need a window manager or a desktop - just an X11 server.
It looks like xf86-video-fbturbo breaks the 3B+. If I just add xorg-server and xorg-fonts the server quits as it can't find a fbdev. If I then add xf86-video-fbturbo (the only fb device I could find in the repository), piCore hangs. If I start again and just add Xorg, xf86-video-turbo is added as a dependency and piCore hangs.

Suggestions?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 06, 2021, 07:09:16 PM
Hi MrPorcine
... If I start again and just add Xorg, xf86-video-turbo is added as a dependency and piCore hangs.

Suggestions?
You could remove  xf86-video-fbturbo.tcz  from your  Xorg.tcz.dep  file, but then you'll probably still have this problem:
Quote
... server quits as it can't find a fbdev. ...
Title: Re: piCore-13.0.3 released (32-bit)
Post by: togden on May 06, 2021, 08:12:34 PM
Greetings,

Followed this protocol perfectly to try to load piCore onto a Pi Zero W, from a person who seems extremely savvy.    Got to "Step One" in his Installing Wifi Module.  (Around 7:10 in his YouTube companion video).  Entered "tce-load -i wifi"  Everything checked "OK" except got this returned:

"wireless-5.10.16-piCore-v71.tcz not found!"   I'm using piCore-13.0.3.img downloaded May 6.   


https://www.novaspirit.com/2018/01/09/tiny-core-raspberry-pi-zero-w-install/
https://www.novaspirit.com/2018/01/09/tiny-core-raspberry-pi-zero-w-install/

If there's a work around it'd be great to know.  Thanks everyone!
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on May 06, 2021, 11:02:13 PM
The extension is called wireless-5.10.16-piCore.tcz
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 12, 2021, 04:13:14 PM
The kernel in the 13.0.3 release is 5.10.16. In the source folder http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/ (http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/), the kernel is indeed 5.10.16. However, the .config and the module files are all 5.10.13. Can I use the 5.10.13 config to generate new modules? I'm trying to wake up the touch screen and it looks like handling of the official 7" touch screen has changed. There is no more a module called rpi-ft5406, but one called raspberrypi-ts. There may be more to this, but at least that is obvious.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 12, 2021, 06:32:16 PM
Well, that didn't work. :( I compiled the modules on a RPi 4 running Rasbarian. Here is the diff of the .config from the repository and the one after I ran "make xconfig". I did add the -v7 to localversion:
Code: [Select]
diff .config ../5.10.13-piCore_.config
3c3
< # Linux/arm 5.10.16 Kernel Configuration
---
> # Linux/arm 5.10.13 Kernel Configuration
5c5
< CONFIG_CC_VERSION_TEXT="gcc (Raspbian 8.3.0-6+rpi1) 8.3.0"
---
> CONFIG_CC_VERSION_TEXT="gcc (piCore) 10.2.0"
7,8c7,8
< CONFIG_GCC_VERSION=80300
< CONFIG_LD_VERSION=231010000
---
> CONFIG_GCC_VERSION=100200
> CONFIG_LD_VERSION=234000000
24c24
< CONFIG_LOCALVERSION="-piCore-v7"
---
> CONFIG_LOCALVERSION="-piCore"
I then copied the raspberrypi-ts.ko module to the appropriate place on a running piCore-13.0.3 on a pi 3b+. I hand modified modules.dep so that modprobe could find the module. When I ran "sudo modprobe raspberrypi-ts" I got the following message:
Code: [Select]
sudo modprobe raspberrypi-ts
modprobe: can't load module raspberrypi-ts (kernel/drivers/input/touchscreen/raspberrypi-ts.ko): invalid module format
I tried this after gzipping and before gzipping. Same message each time. I know this all will disappear on the next reboot, but I thought it would work as a test. Clearly I am out of my depth. Comments please.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 12, 2021, 07:10:31 PM
Hi MrPorcine
The kernel in the 13.0.3 release is 5.10.16. In the source folder http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/ (http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/), the kernel is indeed 5.10.16. However, the .config and the module files are all 5.10.13. ...
You'll have to wait for bmarkus to sort that out.

Quote
... There is no more a module called rpi-ft5406 ...
I did a little digging, and I think I can shed a little light on that one. I downloaded and unpacked  5.10.13-piCore_modules.tar.xz.
Searching for  ft5406  in the included  modules.alias  file returned  edt-ft5406  among many others being handled by
kernel/drivers/input/touchscreen/edt-ft5x06. Maybe that's the driver you want?

Unfortunately, you won't be able to use anything from that modules file. I checked the  vermagic  value of the  edt-ft5x06
driver and it is 5.10.13 so you won't be able to load it.  You'll have to wait for bmarkus for this one too.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 13, 2021, 03:08:20 PM
I modified the .config file and recompiled so the vermagic strings are the same on my newly compiled raspberrypi-ts.ko module and any other module that I checked in the 13.0.3 image. This is still not enough - apparently there is a check for identical data structures between the module and the kernel. So unless someone can suggest a path forward it looks like I'll have to wait for bmarcus.

I have X running, I'm not sure what the problem was earlier. Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. One could still ssh in. Now, other than the touch screen not working, everything I need has worked so far.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 13, 2021, 04:58:25 PM
Hi MrPorcine
... Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. ...
I think sometimes loading the graphics extension can cause that. Were you loading  graphics-5.10.16-piCore.tcz ?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 13, 2021, 05:43:49 PM
Hi MrPorcine
... Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. ...
I think sometimes loading the graphics extension can cause that. Were you loading  graphics-5.10.16-piCore.tcz ?
I don't think so. Symptoms were that the screen would flash once with the default background, then the UI would hang. I could either ssh in, or turn the machine off. I did add "dtoverlay=rpi-ft5406" to the config.txt file. Since the handling of the touchscreen has changed, this may have broken the system. I'm not doing that now.

My onboot.lst is pretty short:
Code: [Select]
openssh.tcz
Xorg.tcz
busybox-httpd.tcz
minicom.tcz
inetutils.tcz
coreutils.tcz
Xorg.tcz brings in a ton of dependencies. The display works now other than the touchscreen. My core app is working with a mouse. Next on my list is to get the HTTP server and the FTP server working.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 17, 2021, 03:46:51 PM
I have X running (no touchscreen) on the 7" official Raspberry Pi touchscreen. I have seen some strange filesystem behavior, perhaps someone can explain what is going on.

The display uses xf86-video-fbturbo.tcz. This tcz adds two files, "/usr/local/share/X11/xorg.conf.d/fbturbo.conf" and "/usr/local/lib/xorg/modules/drivers/fbturbo_drv.so". So far so good. I need to add a few font files, so I added the folders 100dpi and 75dpi to the X font folder "/usr/local/lib/X11/fonts"  Both the new folders only have a few fonts, so are pretty small. I restarted the X server and it restarted fine and found the new fonts.

I added these folders to "/opt/.filetool.lst", did a "filetool.sh -b" and rebooted. Xorg now failed because it couldn't find the fbturbo driver! When I looked at the filesystem, fbturbo.conf was present, but fbturbo_drv.so was not. I then checked "/tmp/tcloop/ xf86-video-fbturbo" and both files were present in the overlay. I rebooted a few time, it was always the same.

I then removed the 100dpi and 75dpi folders from .filetool.lst, did a filetool.sh -b and rebooted. fbturbo_drv.so reappeared so Xorg starts fine! So it appears that restoring files via the tcz mechanism and restoring files via the filetool mechanism sometimes interfere with each other. Is this known? Did I do something wrong?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 17, 2021, 06:09:37 PM
Hi MrPorcine
... Did I do something wrong?
I don't know. What does this return:
Code: [Select]
cat /opt/.filetool.lst
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 18, 2021, 11:33:50 AM
Sorry, the forum refuses to accept the contents of .filetool.lst. It first trips up on etc dot group. But I have not modified the file - it is the default from the piCore13 image.

More strangeness since the last post. After backing out the two font folders from .filetool.lst, I added the same two font folders to Xorg-fonts.tcz. This tcz is added as a dependency of Xorg.tcz. After reboot, the system exhibited the same behavior as described in my previous post. Xorg hung because it couldn't find the turbo driver. I then restored the original Xorg-fonts.tcz and now Xorg would start OK once again.

I modified the Xorg-fonts.tcz file on a RPi4 running Rasbian as the on piCore the squashfs utility is missing some of its dependencies. Squashfs-tools is in the repository. I found and added lzo and liblz4, also in the repository and needed but not brought in automatically. There is at least one more library needed (libzstd) that is not in the repository.

Next I copied the two font folders to /opt, modified bootsync.sh to create simlinks from the Xorg fonts folder to the two folders now in opt and once again did a filetool.sh -b. Now on reboot Xorg starts and finds the fonts that I added. So I have a work-around to the two standard methods that did not work.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 18, 2021, 12:44:45 PM
I wanted to rule out hardware issues, so I ran f3write and f3read on on the SD card that has piCore on it - no problems found. I also slipped in a Rasbian SD card on the RPi3b and ran memtester overnight. Also no problems found.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 18, 2021, 10:08:34 PM
At this point the whole system is working OK, except that the touchscreen is inop. A USB mouse works fine. We are using a RPi 3B+. Actually I find piCore pretty amazing. The SDcard image is only about 500MB. It uses about 100MB of the 1GB RAM. It boots to our splash screen in about 9 seconds and the final app appears in about 18 seconds. You can turn off the system any time without worrying about file system corruption.

We do need the touchscreen to work. If we can help with the touchscreen interface in 13.0.3 let us know. If someone could post the .config used to compile the RPi 3B+ kernel we could just compile it with the modules that we need. If I remember correctly, there is a script that separates the modules that are include in the kernel image from the ones that are in the module image. Or maybe it's more complicated than that. Anyway, any help is welcome.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 19, 2021, 06:50:03 AM
Hi MrPorcine
The kernel in the 13.0.3 release is 5.10.16. In the source folder http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/ (http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/), the kernel is indeed 5.10.16. However, the .config and the module files are all 5.10.13. ...
I just checked, bmarkus fixed that. Everything is now  5.10.16.

... We do need the touchscreen to work. If we can help with the touchscreen interface in 13.0.3 let us know. ...

Fetch the kernel modules package:
http://tinycorelinux.net/13.x/ARM/releases/RPi/src/kernel/
Replace the word  ARM  with the results of the  getBuild  command.

Unpack it using the  tar xf FileName.tar.xz  command.

Then see if  edt-ft5x06.ko  works for you:
Code: [Select]
tc@E310:~/Downloads$ ls -l modules/lib/modules/KERNEL/kernel/drivers/input/touchscreen/
total 176
-rw-r--r-- 1 tc staff 25104 Feb 17 05:46 ads7846.ko
-rw-r--r-- 1 tc staff 26988 Feb 17 05:46 edt-ft5x06.ko
-rw-r--r-- 1 tc staff  8992 Feb 17 05:46 egalax_ts.ko
-rw-r--r-- 1 tc staff 12532 Feb 17 05:46 exc3000.ko
-rw-r--r-- 1 tc staff 22960 Feb 17 05:46 goodix.ko
-rw-r--r-- 1 tc staff 14824 Feb 17 05:46 ili210x.ko
-rw-r--r-- 1 tc staff  9712 Feb 17 05:46 raspberrypi-ts.ko
-rw-r--r-- 1 tc staff 10828 Feb 17 05:46 stmpe-ts.ko
-rw-r--r-- 1 tc staff 27300 Feb 17 05:46 usbtouchscreen.ko
tc@E310:~/Downloads$
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 19, 2021, 03:11:40 PM
Wonderful! Touchscreen now works. New module for the official 7" Raspberry Pi touchscreen is called raspberrypi_ts.ko, found in the kernel/drivers/input/touchscreen folder. The URL to the v7 files is slightly different than the one Rich posted: http://tinycorelinux.net/www/13.x/armv7/releases/RPi/src/kernel/ (http://tinycorelinux.net/www/13.x/armv7/releases/RPi/src/kernel/)

Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 19, 2021, 06:15:36 PM
Hi MrPorcine
... The URL to the v7 files is slightly different than the one Rich posted: ...
Since I don't know what  ARM  version the end user is running, it is up to them to complete the URL.

As stated:
 ... Replace the word  ARM  with the results of the  getBuild  command. ... [/quote]
Run the command:
Code: [Select]
getBuildReplace the word  ARM  in the URL with the value returned by the command.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 20, 2021, 02:25:44 PM
It appears that while booting maybe 1/2 the time piCore doesn't assemble the overlay file system correctly. The symptom is that some important file is missing. Sometimes it is a driver, sometimes it is a library or something else. When I examine the system, the tcz files are mounted on /tmp/tcloop, but the simlink from the ultimate location if at least one of the files contained in a tcz is missing. Looking back at some of the previous problems I had, this could explain all. Recall that I needed to add two font directories to /usr/local/lib/X11/fonts. Adding them with the filetool mechanism did not work. Adding them to Xorg-fonts.tcz did not work. What finally did work was to copy the directories to /opt, and then create the simlinks in bootsync.sh. I now suspect that this worked as all the init scripts have finished by the time bootsync.sh runs.

Here is the contents of my /tmp/tcloop:
Code: [Select]
/tmp/tcloop$ ls
Xorg/                libXdamage/          libxcb/
Xorg-fonts/          libXdmcp/            libxkbfile/
busybox-httpd/       libXext/             libxshmfence/
bzip2-lib/           libXfixes/           mesa/
ca-certificates/     libXfont2/           mtdev/
expat2/              libXxf86vm/          ncurses/
freetype/            libdrm/              openssh/
gamin/               libelf/              openssl/
gcc_libs/            libepoxy/            pcre/
glib2/               libevdev/            pixman/
graphite2/           libfontenc/          xf86-input-libinput/
harfbuzz/            libinput/            xf86-video-fbturbo/
inetutils-servers/   libpciaccess/        xkbcomp/
libX11/              libpng/              xkeyboard-config/
libXau/              libudev/             xorg-server/
And the contents of my /mnt/mmcblk0p2/tce/onboot.lst:
Code: [Select]
cat /mnt/mmcblk0p2/tce/onboot.lst
openssh.tcz
Xorg.tcz
busybox-httpd.tcz
inetutils-servers.tcz
I removed Xprogs.tcz from the list of dependencies in Xorg.tcz.dep. This made the above list somewhat shorter than by default.

The contents of .filetool.lst is the default.

This behavior is intermittent. Sometime piCore completes correctly, sometime it will miss some file. As far as I know, there are no external asynchronous processes that could affect the init scripts. Any hints as to what might be going on are welcome.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on May 20, 2021, 08:20:10 PM
Hi MrPorcine
Maybe try a different memory card ?  I think there have been 2 or 3 instances of strange intermittent behavior caused
by marginal memory cards.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 20, 2021, 09:24:15 PM
Hi MrPorcine
Maybe try a different memory card ? 
I've tried two memory cards and two RPi3+ cards - no difference. I have previously run memtester on the 3b+ and f3 write/f3read on the SD card. No trouble found.

I did find an undocumented command line argument that puts more output in /tmp/forklog.txt - "debugbootlog". While the additional text in forklog.txt doesn't expose the problem directly, the boot problem goes for maybe 1 in 2 times to maybe 1 in 10. So it looks to me as if there is a race problem in /usr/bin/tce-bootload or something that it calls. From forklog.txt it appears that the process of mounting the tce files is multi-threaded. At this time I believe that I have found a bug in tinyCore. I'm not sure how to proceed. The following is from a successful boot. The unsuccessful ones are not much different.
forklog.txt:
Code: [Select]
cat /tmp/forklog.txt
PID:428 Started for openssh.tcz
PID:429 Started for Xorg.tcz
PID:431 Started for busybox-httpd.tcz
PID:433 Started for inetutils-servers.tcz
PID:429 Finished, exit code: 0
PID:440 Started for openssl.tcz
PID:428 Finished, exit code: 0
PID:443 Started for xorg-server.tcz
PID:431 Finished, exit code: 0
PID:444 Started for xf86-video-fbturbo.tcz
PID:433 Finished, exit code: 0
PID:449 Started for xf86-input-libinput.tcz
PID:440 Finished, exit code: 0
PID:452 Started for xkeyboard-config.tcz
PID:443 Finished, exit code: 0
PID:455 Started for xkbcomp.tcz
OS Error code xkey:65280

PID:444 Finished, exit code: 0
PID:458 Started for Xorg-fonts.tcz
OS Error code xkey:65280

PID:449 Finished, exit code: 0
PID:462 Started for ncurses.tcz
PID:455 Finished, exit code: 0
PID:465 Started for ca-certificates.tcz
PID:458 Finished, exit code: 0
PID:469 Started for mesa.tcz
PID:462 Finished, exit code: 0
PID:474 Started for pixman.tcz
Successful Retry on xkey

PID:452 Finished, exit code: 0
PID:478 Started for libXfont2.tcz
PID:469 Finished, exit code: 0
PID:479 Started for libepoxy.tcz
PID:465 Finished, exit code: 0
PID:484 Started for libinput.tcz
PID:474 Finished, exit code: 0
PID:487 Started for libxkbfile.tcz
PID:478 Finished, exit code: 0
PID:490 Started for libdrm.tcz
PID:479 Finished, exit code: 0
PID:493 Started for libXdamage.tcz
PID:484 Finished, exit code: 0
PID:496 Started for libXxf86vm.tcz
PID:487 Finished, exit code: 0
PID:499 Started for expat2.tcz
PID:490 Finished, exit code: 0
PID:503 Started for libxshmfence.tcz
PID:493 Finished, exit code: 0
PID:505 Started for freetype.tcz
PID:499 Finished, exit code: 0
PID:508 Started for libfontenc.tcz
PID:496 Finished, exit code: 0
PID:512 Started for mtdev.tcz
PID:503 Finished, exit code: 0
PID:515 Started for libevdev.tcz
PID:505 Finished, exit code: 0
PID:518 Started for libudev.tcz
PID:512 Finished, exit code: 0
PID:522 Started for libX11.tcz
PID:508 Finished, exit code: 0
PID:524 Started for libpciaccess.tcz
PID:515 Finished, exit code: 0
PID:527 Started for libXfixes.tcz
PID:518 Finished, exit code: 0
PID:530 Started for libXext.tcz
PID:524 Finished, exit code: 0
PID:533 Started for libpng.tcz
PID:522 Finished, exit code: 0
PID:536 Started for harfbuzz.tcz
PID:527 Finished, exit code: 0
PID:539 Started for bzip2-lib.tcz
PID:530 Finished, exit code: 0
PID:542 Started for glib2.tcz
PID:536 Finished, exit code: 0
PID:545 Started for libxcb.tcz
PID:533 Finished, exit code: 0
PID:548 Started for graphite2.tcz
PID:539 Finished, exit code: 0
PID:551 Started for gamin.tcz
PID:542 Finished, exit code: 0
PID:555 Started for libelf.tcz
PID:545 Finished, exit code: 0
PID:556 Started for pcre.tcz
PID:548 Finished, exit code: 0
PID:561 Started for libXau.tcz
PID:551 Finished, exit code: 0
PID:563 Started for libXdmcp.tcz
PID:555 Finished, exit code: 0
PID:566 Started for gcc_libs.tcz
PID:556 Finished, exit code: 0
PID:561 Finished, exit code: 0
PID:563 Finished, exit code: 0
PID:566 Finished, exit code: 0
PID:571 Started for openssh.tcz
PID:572 Started for Xorg.tcz
PID:574 Started for busybox-httpd.tcz
PID:576 Started for inetutils-servers.tcz
PID:572 Finished, exit code: 0
PID:579 Started for openssl.tcz
PID:574 Finished, exit code: 0
PID:580 Started for xorg-server.tcz
PID:571 Finished, exit code: 0
PID:582 Started for xf86-video-fbturbo.tcz
PID:576 Finished, exit code: 0
PID:585 Started for xf86-input-libinput.tcz
PID:579 Finished, exit code: 0
PID:587 Started for xkeyboard-config.tcz
PID:580 Finished, exit code: 0
PID:588 Started for xkbcomp.tcz
PID:585 Finished, exit code: 0
PID:590 Started for Xorg-fonts.tcz
PID:582 Finished, exit code: 0
PID:592 Started for ncurses.tcz
PID:588 Finished, exit code: 0
PID:595 Started for ca-certificates.tcz
PID:592 Finished, exit code: 0
PID:597 Started for mesa.tcz
PID:590 Finished, exit code: 0
PID:599 Started for pixman.tcz
PID:597 Finished, exit code: 0
PID:601 Started for libXfont2.tcz
PID:599 Finished, exit code: 0
PID:603 Started for libepoxy.tcz
PID:587 Finished, exit code: 0
PID:605 Started for libinput.tcz
PID:601 Finished, exit code: 0
PID:606 Started for libxkbfile.tcz
PID:603 Finished, exit code: 0
PID:609 Started for libdrm.tcz
PID:606 Finished, exit code: 0
PID:611 Started for libXdamage.tcz
PID:605 Finished, exit code: 0
PID:613 Started for libXxf86vm.tcz
PID:609 Finished, exit code: 0
PID:615 Started for expat2.tcz
PID:611 Finished, exit code: 0
PID:617 Started for libxshmfence.tcz
PID:613 Finished, exit code: 0
PID:428 Started for openssh.tcz
PID:429 Started for Xorg.tcz
PID:431 Started for busybox-httpd.tcz
PID:433 Started for inetutils-servers.tcz
PID:429 Finished, exit code: 0
PID:440 Started for openssl.tcz
PID:428 Finished, exit code: 0
PID:443 Started for xorg-server.tcz
PID:431 Finished, exit code: 0
PID:444 Started for xf86-video-fbturbo.tcz
PID:433 Finished, exit code: 0
PID:449 Started for xf86-input-libinput.tcz
PID:440 Finished, exit code: 0
PID:452 Started for xkeyboard-config.tcz
PID:443 Finished, exit code: 0
PID:455 Started for xkbcomp.tcz
OS Error code xkey:65280

PID:444 Finished, exit code: 0
PID:458 Started for Xorg-fonts.tcz
OS Error code xkey:65280

PID:449 Finished, exit code: 0
PID:462 Started for ncurses.tcz
PID:455 Finished, exit code: 0
PID:465 Started for ca-certificates.tcz
PID:458 Finished, exit code: 0
PID:469 Started for mesa.tcz
PID:462 Finished, exit code: 0
PID:474 Started for pixman.tcz
Successful Retry on xkey

PID:452 Finished, exit code: 0
PID:478 Started for libXfont2.tcz
PID:469 Finished, exit code: 0
PID:479 Started for libepoxy.tcz
PID:465 Finished, exit code: 0
PID:484 Started for libinput.tcz
PID:474 Finished, exit code: 0
PID:487 Started for libxkbfile.tcz
PID:478 Finished, exit code: 0
PID:490 Started for libdrm.tcz
PID:479 Finished, exit code: 0
PID:493 Started for libXdamage.tcz
PID:484 Finished, exit code: 0
PID:496 Started for libXxf86vm.tcz
PID:487 Finished, exit code: 0
PID:499 Started for expat2.tcz
PID:490 Finished, exit code: 0
PID:503 Started for libxshmfence.tcz
PID:493 Finished, exit code: 0
PID:505 Started for freetype.tcz
PID:499 Finished, exit code: 0
PID:508 Started for libfontenc.tcz
PID:496 Finished, exit code: 0
PID:512 Started for mtdev.tcz
PID:503 Finished, exit code: 0
PID:515 Started for libevdev.tcz
PID:505 Finished, exit code: 0
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Paul_123 on May 21, 2021, 05:15:42 AM
Its not a race condition, but for some reason the kernel is not creating loop devices fast enough to satisfy mount.   This error also is seen with tce-load, but mainly on the slower single core pies.   This was fixed in git, The pull request is still sitting open, So it appears to not be in 13.x.   The 64 bit version does have this fixed in 13.....which reminds me, I need to move this from Beta.

As a work around, add to your command line "max_loop=64"   (Or a little bigger than the number of extensions you are loading.  The kernel will create the loop devices during boot.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 21, 2021, 02:01:10 PM
As a work around, add to your command line "max_loop=64"
This works to get rid of the errors that forklog.txt reports. Also the undocumented command line argument is debugbootload, not debugbootlog.

I still see problem of missing files. Not very often now, but maybe 1 in 20 boots. It just happened again, the file is present in /etc/tcloop file tree but the simlink is missing in the file system. It's not always the same file. I suspect that the behavior is present more often than I know as not all missing files will prevent X or my app from starting.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 21, 2021, 05:17:45 PM
I decided to try to reproduce this behavior with the stock image. I was successful. Here is what I did:
1)Flashed the piCore13 image to an 8G SD card. Expanded partition 2 to max with gparted.
2)booted a RPi 3B+ with the new card. Added "syslog max_loop=50" to the end of cmdline.txt. Made the following changes to config.txt:
Code: [Select]
disable_overscan=1
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on
[PI3]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-kms-v3d
dtoverlay=disable-bt
dtoverlay=sdio,poll_once
3)Used tce to install Xorg and busybox-httpd.
4)Commented out the last few lines of dot profile so Xorg will not start.
5)wrote a script "findMissingFile" to check for missing simlinks and put it in /home/tc. Did a filetool.sh -b, then a sudo reboot.  I've attached the script (the forum won't let me put it in-line).
6)After the boot the script found several missing simlinks:
Code: [Select]
/usr/local/lib/xorg/modules/drivers/fbturbo_drv.so  does not exist!
....................................................................................
/usr/local/share/pixmaps/screenshot.png  does not exist!

/usr/local/share/pixmaps/services.png  does not exist!

/usr/local/share/pixmaps/settime.png  does not exist!
...............................................................
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 21, 2021, 05:37:46 PM
OK, never mind. You should just remove that last post. It turn out the max_loop=50 is too small. On my custom image I removed the Xprogs extension which eliminates a few dependencies, so 50 is big enough. Also ash seems to treat -e as something other that "exists". The png files are present, but fail the -e test.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Paul_123 on May 21, 2021, 07:19:04 PM
Yes, busybox apps have some odd behavior when compared to full versions.

I've done a lot of testing trying to speed up the boot process.   In general 1 thread per CPU has worked really well.  The mount errors happen if you run multi threaded or not.

I experimented with checking for a free loop device and creating it before mount, but that slowed things way down, since during boot it always needed to created a new loop device.  In the end, I opted to just retry the mount if it fails....With a max number of retries, in case of a real error.   That seems to be the best of both worlds, speed vs reliability.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 23, 2021, 01:42:38 PM
Recall that I have been having intermittent problems with missing files after extensions are loaded. I think I have a test for this that is simple enough that anyone can reproduce the error.  Recall that I am using a Raspberry Pi 3 model B+. I'm using an generic 8G SD card, nothing special. During testing I have used several different SD cards.
1)Flash the card with piCore-13.0.3.img. Use gparted to expand the second partition to fill the card.
2)Boot the Pi, change the password, run filetool.sh -b. Reboot
3)Use tce to install Xorg.tcz. Comment out the last few lines of .profile so startx is not called. Run filetool.sh -b again.
4)Copy the attached script as /home/tc/findMissingFile. Use chmod to allow execution. Insert "/home/tc/findMissingFile" as the last line in /opt/bootlocal.sh. Run filetool.sh -b once again.

findMissingFile looks that the file tree at /mnt/tcloop and checks to see if the simlinks in the root file system were created.
On my system, findMissingFile always reports 3 missing .png files. They are missing, but it doesn't matter for our purposes.

About every 2 or 3 reboots findMissingFile finds that the turbo driver "fbturbo_drv.so" is missing. This important as Xorg will not run without this driver. Sometimes findMissingFile finds other files missing as well.

I am very curious if anyone else can reproduce this problem.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 23, 2021, 05:52:38 PM
Maybe I found something. In tce-bootload, line 206, the simlink from the root file system is created with "'sudo busybox cp -r -f -s ' + root + '/tmp/tcloop/' + p[:-4] + '/* ' + root + '/'". When I look to see the effect of the "-f" here is what I find:
Quote
-f, --force
              if an existing destination file cannot be opened, remove
              it and try again (this option is ignored when the -n
              option is also used)
What happens if another thread is creating the same directory tree? Could you get a write block until the other thread is finished?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 23, 2021, 10:38:36 PM
I was probably a little to short in my explanation of what possibly is going wrong here. Recall that in Unix, if a process has a handle open to a file, and that file is deleted by another process, the file is not deallocated until the first process closes the handle to the file.  I've never seen an explanation of what happens with directories, but it it's similar to files perhaps the following scenario applies:

Process #1 creates a directory. "mydir" The kernel is in process of creation but has not finished.
Process #2 tries to create the same directory, "mydir". It can't as the kernel is still busy with process #1
Process #2, being root, deletes the directory "mydir" and creates a new one with the same name.
Process #1 can't tell that its original directory "mydir" has been deleted, so continues to create the whole path to the file it needs to create.
Process #1 completes. Its copy of the original "mydir" directory is deallocated along with all the files that depend on that directory.

Seems plausible to me.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: MrPorcine on May 24, 2021, 11:03:46 AM
Here's a patch to tce-bootload. I'm no python expert, but it does seem to work.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: jefferee on May 25, 2021, 10:05:56 AM
Thanks, everyone.

One request--can you please add libmodbus and libmodbus-dev?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: bmarkus on May 25, 2021, 08:31:05 PM
Thanks, everyone.

One request--can you please add libmodbus and libmodbus-dev?

Do you mean https://github.com/stephane/libmodbus ?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: jefferee on May 31, 2021, 04:54:26 PM
Thanks, everyone.

One request--can you please add libmodbus and libmodbus-dev?

Do you mean https://github.com/stephane/libmodbus ?

That's the one. (at least I *think* that was the tcz available in piCore 9.03).
I've actually managed to compile it from source in the meantime, so no rush.

Thanks!
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on June 01, 2021, 12:09:39 AM
libmodbus doesn't have any deps, so the extension from piCore 9.x will probably work in 13.x
Title: Re: piCore-13.0.3 released (32-bit)
Post by: dacarman on June 06, 2021, 04:27:37 AM
Is the newest PiCore 13 distro able to run accelerated graphics???

Last time I tested it (previous beta version), it was not able to load the required graphics modules properly, probably because of certain "CEC" dependencies.

Graphics modules (graphics-KERNEL) fails showing ELF errors and "vc4: Unknown symbols for cec_xxxxx...".
/dev/dri was not created, so SDL dependant programs can't be run.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on June 06, 2021, 04:35:11 AM
Have you tried again with the latest graphics-KERNEL extension?

What is the exact error message you get?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: dacarman on June 06, 2021, 04:47:11 AM
Last time I tried previous beta version with the last graphics kernel extension with no luck...   

I didn't tried this distro and newer modules, so I was asking because I didn't see an update from Markus related to that fix needed, and it requires some time for me to compose all the needed steps to create the SD card, download modules and copy my test programs...    I did it several times with previous 13 versions until I understood that some modifications or additional modules are required to be included for 13 and its latest kernel, but those requirements were ever fullfilled in previous PiCore versions like 12, 11, etc. even in beta versions without significant problems.

The errors shown, as I said are the ones related to ELF and "vc4: Unknown symbols for cec_xxxxx"...   when the system is booting.

When I try to run a program which requires accelerated graphics it does not work showing that /dev/dri does not exists or SDL related fails because the libraries can't be loaded properly.


Title: Re: piCore-13.0.3 released (32-bit)
Post by: dacarman on June 06, 2021, 04:51:58 AM
I think the key is the missing CEC modules which Paul refers here:

http://forum.tinycorelinux.net/index.php/topic,24762.msg157850.html#msg157850 (http://forum.tinycorelinux.net/index.php/topic,24762.msg157850.html#msg157850)
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on June 06, 2021, 07:09:32 AM
I don't believe the appropriate 5.10.x-piCore-v7_modules.tar.xz file is available for the missing modules for piCore-13.0.3 (I might be wrong) so you'll need to either:

*wait until @bmarkus posts them
*use piCore-12.x where 3d acceleration works for armv6/armv7/aarch64
Title: Re: piCore-13.0.3 released (32-bit)
Post by: dacarman on June 06, 2021, 08:53:26 AM
Thanks you.

Yes, I'm using PiCore 12 for the moment, as it looks like those modules are a new requirement difficult to have ready.

Regards.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: jefferee on June 14, 2021, 08:32:14 AM
tcpdump is missing one of its required dependencies,
ipv6-netfilter-5.10.16-piCore-v7.tcz (this is on a 3B+ board).
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on August 21, 2021, 10:37:26 AM
Hi,

I just noticed that Motion seems to be gone from the piCore 13.03 (32 bits) repository.
I know there were some problems with libnettle.so.7.0 not being present but as far as I know this was resolved (or could be resolved by explicitely loading it from 12.x). And after the fix it was working very very well, at least on PI400, PI3B, PI3B+!

Can you please re-upload it to the repository?

Kind Regards,
Pengo
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on August 21, 2021, 11:17:37 AM
Hi Pengo
I see it's listed here:
http://tinycorelinux.net/13.x/armv7/tcz/
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on August 22, 2021, 12:21:29 AM
Hi Rich,

Strangely enough if I use tce-ab then my pi400 can find it but on the newly installed piZero it does not appear (other packages do).
I checked the mirror (tcemirror file) and it appears to be the same.

Diving a bit deeper I see that the motion package is not in the armv6 repo. I guess the piZero looks there whereas the pi400 installation looks at the armv7 repo where the package is?





Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on August 22, 2021, 12:54:56 AM
I think the reasoning was that motion depends on libavdevice, which has a recursive dep on x265, which didn't compile for armv6 at the time.

Maybe you could manually download motion and test it on your RPi0?
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on August 22, 2021, 05:47:37 AM
Hi Juanito,

After installation of the necessary build packages (from the repo),  I can compile the latest motion directly from source if I exclude ffmpeg support. The resulting executable seems to work (e.g. detects motion and saves the .JPG images)

In order to compile with ffmpeg support the following packages are needed (but not part of the  piCore repo yet)
Required ffmpeg packages 'libavutil-dev libavformat-dev libavcodec-dev libswscale-dev libavdevice-dev"

Compilation was done on my piZero.

Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on August 22, 2021, 06:23:55 AM
Hi Pengo
I think Juanito meant manually downloading:
http://tinycorelinux.net/13.x/armv7/tcz/motion.tcz
http://tinycorelinux.net/13.x/armv7/tcz/motion.tcz.dep
to your RPi0 and then:
Code: [Select]
tce-load -wi motionto pull in the dependencies and load it.

The required dependencies appear to be present, even:
http://tinycorelinux.net/13.x/armv6/tcz/x265.tcz.info
which states:
Quote
Current:        2020/11/13 recompiled for armv6 (juanito)
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on August 22, 2021, 10:27:33 AM
Great Rich & Juanito!

It now works!

Thanks for your help!
Recording a video 640x480  (15fps) is working on the piZero (via motion which will call ffmpeg)

Title: Re: piCore-13.0.3 released (32-bit)
Post by: Rich on August 22, 2021, 10:42:56 AM
Hi Pengo
Thanks for confirming  motion.tcz  works on  armv6.  The  motion  extension has been copied to the  armv6  repository.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on October 09, 2021, 07:44:15 AM
Hi,

While piCOre 13.03 runs flawlessly, I did notice a few issues with some of the extentions.

- gdb is complaining about missing a shared library (libmpfr.so.4)

- motion dependencies are not correct. Once it is installed it will complain about libp11-kit missing (with can only be corrected by installing the p11-kit-dev after which it will complain about libnettle.so.8  (which then can be loaded seperately to fix that isse also.)

Not urgent but two packages that I really miss
- nmap
- vmstat

Kind regards,
Pengo
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 10, 2021, 12:51:28 AM
gdb was built against an earlier version of mpfr last present in piCore-11.x - it will need re-compiling.

For motion, it sounds like you need to update the dep file for gnutls, which previously didn't contain p11-kit or nettle7.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 10, 2021, 11:16:26 PM
Updated gdb posted
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 11, 2021, 01:41:24 AM
nmap and procps (contains vmstat) posted
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Pengo on October 12, 2021, 02:30:31 AM
Thank you Juanito!

I tested gdb, vmstat, nmap on several different PI's  (0, 2B, 3B+, 400).
They all work as expected!

Great!



Title: Re: piCore-13.0.3 released (32-bit)
Post by: CJ on October 25, 2021, 09:38:30 AM
I realize "There is only one SD card image for all boards which can be downloaded from" for the raspberry pi. But I understand there are certain files for the different pi models that can be removed/deleted before setting up the OS.

Specifically I'm talking about the Pi Zero W. Since it has only half gig memory and I'd like to install WiFi , blue tooth and maybe just one app (I usually use my pi zero w's for one application cause it's cheap and works well but should work better without the buster OS bloated software) so It all can run in memory and not be so bloated.

Thanks for any help from anyone.

A video from 2018 from Novaspirittech (which was a few versions back) recommend removing a file for the pi zero w that is used for a Pi model 3 but the file is not on the new version 13.0.3 so I don't want to delete the wrong file and waste a lot of time with trial and error).
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 25, 2021, 10:42:31 AM
You can save some space on the sd card by deleting the init.rd relevent to armv7 and armv7l, but piCore runs in ram and will only load the init.rd relevent to armv6 into ram.

The standard image will run fine on an RPi0 without needing any editing.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Greg Erskine on October 25, 2021, 12:38:12 PM
IIRC, people only started to delete files from the FAT partition on the SD card because they needed a little more space to transfer some extensions between a Windows PC and the second partition on the SD card in one go.

There is no need or advantage to remove files otherwise.
Title: Re: piCore-13.0.3 released (32-bit)
Post by: CJ on October 25, 2021, 02:23:22 PM
So since I am only worried about what is getting loaded into RAM and not the SD card as you stated I really don't need to delete any files as it only loads what it needs in RAM per the CPU type? And since I'm using at least a 16GB SD card I should have no problem. What I'm doing is (currently in Buster lite) just installing what is needed to use the PiZero W's as RTSP and send the files to another Pi 4 (8GB via Ethernet) running a NVR called Shinobi. I'm hoping that the lag I see sometimes with the wifi lag will be better with everything loaded in RAM. I'm hoping that the RTSP software gets loaded in RAM also or am I wrong or have to investigate it? All the video and/or .jpg files should be sent to the RPI4 (with an SSD of 480GB mounted). This setup with Buster Lite has been running well for over a year except sometimes I see a lag I'm assuming is due to the WiFi in combination with reading and writing stuff from the SD card on the Zero W's. The Pi4 is not using an SD card , all the OS and everything is on the SSD drive.
Any comments or help would be greatly appreciated as always.

Will I need to install a WiFi package to the PiZeroW's or is it included with the 13.0.3 (32-bit image)?

Again I appreciate the time you took to research and answer and will post my results and even instructions if anyone is interested in a low cost NVR security system. So far I have 4 Pi Zero W's in the Buster setup.
Other questions that come to mind is where do I load the Static IP address and WiFi credentials on the PiZeroW unless it's the same files as with Buster lite. I don't mind looking for the answers myself as long as you point me in the right directions.

Again, much thanks.

CJ
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 26, 2021, 04:49:07 AM
The wifi extension and its dependencies are not included in the piCore image.

I burnt a new piCore-13.0.3 sd card for an RPi0W about ten days ago, added wifi and everything worked first try  :)

Basically:

* burn the image to sd card
* extend the second partition (I also added a third swap partition)
* copy the firmware-rpi-wifi and wifi extensions (*tcz, *tcz.dep, *tcz.md5.txt) and their dependencies to /mnt/mmcblk0p2/tce/optional
* add firmware-rpi-wifi and wifi to /mnt/mmcblk0p2/tce/onboot.lst
* add "wifi.sh -a" to /opt/bootlocal.sh
* create ~/wifi.db for your access point
* make a backup
* reboot
Title: Re: piCore-13.0.3 released (32-bit)
Post by: CJ on October 26, 2021, 07:10:31 AM
I appreciate the help.
However I'm not a Linux person so I'm really lost on most of the things you listed here.
Plus I don't see where I put my Wifi creds and static ip etc.
Does anyone have a detailed step by step on how to do this?

Thanks again
Title: Re: piCore-13.0.3 released (32-bit)
Post by: Juanito on October 26, 2021, 07:38:31 AM
It’s probably better to go step by step - start here:

http://tinycorelinux.net/12.x/armv6/releases/RPi/README

..but download the image from here:

http://tinycorelinux.net/13.x/armv6/releases/RPi/
Title: Re: piCore-13.0.3 released (32-bit)
Post by: CJ on October 26, 2021, 07:44:08 AM
Truly appreciate it. I'll try it.

Thanks!