piCore-13.0.3 released (32-bit)

[bmarkus]

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/

[Yuriy]

Please, add ppp-modules-5.10.16-piCore-v7.tcz into the repository

[bmarkus]

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

[Yuriy]

Thanks a lot. Also missing is ipv6-netfilter-KERNEL.tcz, which some applications depend on, such as tcpdump.

[MrPorcine]

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?

[Rich]

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:

... server quits as it can't find a fbdev. ...

[togden]

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!

[Juanito]

The extension is called wireless-5.10.16-piCore.tcz

[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/, 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.

[MrPorcine]

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.

[Rich]

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/, 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.

... 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.

[MrPorcine]

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.

[Rich]

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 ?

[MrPorcine]

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.

[MrPorcine]

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?