WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: piCore 17.0.0 Release  (Read 1228 times)

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1619
piCore 17.0.0 Release
« on: August 02, 2026, 01:51:58 PM »
Team Tiny Core is happy to announce the release of piCore-17.0.  Both 32 and 64bit images are ready for download.

Changelog for 17.0
* kernel updated to 6.18.37
* glibc updated to 2.42
* gcc updated to 15.2.0
* binutils updated to 2.45.1
* e2fsprogs base libs/apps updated to 1.47.3
* util-linux base libs/apps updated to 2.41.2
* Include XDG_RUNTIME_DIR in .profile
* Add copy2fs.lst capabilities to tce-bootload.
* Make tce-bootload act like tce-load in not overwriting existing files on the filesystem.
* Update zsync to 0.6.5

32bit - http://www.tinycorelinux.net/17.x/armhf/release/RPi/piCore-17.0.img.gz  (This should run on all rpi boards)
         - sha256: 97da51eb1091e8553fcde64b2774d72a302ee6dbc29f31fe5b4345cb3510b9d9  piCore-17.0.img.gz

64bit - http://www.tinycorelinux.net/17.x/aarch64/release/RPi/piCore64-17.0.img.gz  (rpi zero2W, pi3, pi4, pi5)
         - sha256: 13fe9d11fc8800177d4ed1b66c2ebff0460c4079c29172744c98794ca57c13de  piCore64-17.0.img.gz

Note: Image files are now just gzipped, you can just zcat the image if using dd to write your image, or some imaging tools support writing compressed images.
Note:  When using 32bit images, the pi4 and pi5 will use a 64bit kernel.  please make sure to look at uname if manually downloading kernel module extensions.


Offline meo

  • Hero Member
  • *****
  • Posts: 772
Re: piCore 17.0.0 Release
« Reply #1 on: August 03, 2026, 06:21:12 AM »
Hi Paul_123!

I have tested piCore64 17.0.0 now for a while adding what I commonly use and I haven't found any problems so it seems that it's a very good release with needed updates.

Kind regards,
meo
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline meo

  • Hero Member
  • *****
  • Posts: 772
Re: piCore 17.0.0 Release
« Reply #2 on: August 03, 2026, 06:46:41 AM »
Hello again!

I'm now on a Raspberry Pi 4 and there is a minor issuel If you want to use Xorg-3d a file is missing. It shows up in the prompt with the loaded packages. In the final it states that alsa-modules-6.18.37-piCore-v8.tcz is missing. I just started X and just downloaded the file. went back to the prompt and then Xorg-3d.tcz loaded without problems. So it's not a big deal but good to knowl

Kind Greetings,
meo
"All that is very well," answered Candide, "but let us cultivate our garden." - Francois-Marie Arouet Voltaire

Offline Synerworks

  • Newbie
  • *
  • Posts: 11
Re: piCore 17.0.0 Release
« Reply #3 on: August 21, 2026, 03:48:57 PM »
Unfortunately, the tinycore Xorg extension version '1.21.1.21' remains broken for piCore16/piCore17, with the last version still working for 32-bit PI0-2s was piCore15. Perhaps missing dependency or extension build fault in the recent Xorg version. For those that still need their minimal memory footprint desktop option, with lower cost PIs not subject to runaway memory price explosion will either need to stick with piCore15 or overlay the faulty Xorg extension by using the previous working Xorg version '1.21.1.13' as an interim solution.

Xorg.0.log.FAIL
Code: [Select]
[    12.434] Xorg.0.log.FAIL
X.Org X Server 1.21.1.21
X Protocol Version 11, Revision 0
[    12.434] Current Operating System: Linux box 6.18.37-piCore-v7 #41 SMP Mon Jul  6 13:05:12 EDT 2026 armv7l
[    12.434] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:87:46:7F vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  zswap.compressor=lz4 zswap.zpool=z3fold dwc_otg.fiq_fsm_mask=0xF dwc_otg.lpm_enable=0 console=tty1 root=/dev/ram0 rootwait fbcon=map:10 fbcon=font:VGA8x8 nortc loglevel=3 noembed
[    12.434]
[    12.434] Current version of pixman: 0.42.2
[    12.434] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[    12.434] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    12.434] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan  1 00:00:04 2000
[    12.435] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[    12.435] (==) No Layout section.  Using the first Screen section.
[    12.435] (==) No screen section available. Using defaults.
[    12.435] (**) |-->Screen "Default Screen Section" (0)
[    12.435] (**) |   |-->Monitor "<default monitor>"
[    12.438] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[    12.438] (**) |   |-->Device "kms"
[    12.438] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[    12.438] (**) Allowing byte-swapped clients
[    12.438] (==) Automatically adding devices
[    12.438] (==) Automatically enabling devices
[    12.438] (==) Automatically adding GPU devices
[    12.438] (==) Automatically binding GPU devices
[    12.438] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    12.438] (WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
[    12.438] Entry deleted from font path.
[    12.438] (WW) The directory "/usr/local/lib/X11/fonts/100dpi" does not exist.
[    12.438] Entry deleted from font path.
[    12.438] (==) FontPath set to:
/usr/local/lib/X11/fonts/misc,
/usr/local/lib/X11/fonts/TTF,
/usr/local/lib/X11/fonts/Type1,
/usr/local/lib/X11/fonts/75dpi
[    12.438] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[    12.438] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[    12.440] (II) Module ABI versions:
[    12.441] X.Org ANSI C Emulation: 0.4
[    12.441] X.Org Video Driver: 25.2
[    12.441] X.Org XInput driver : 24.4
[    12.441] X.Org Server Extension : 10.0
[    12.442] (II) no primary bus or device found
[    12.443] (II) LoadModule: "glx"
[    12.444] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    13.481] (II) Module glx: vendor="X.Org Foundation"
[    13.481] compiled for 1.21.1.21, module version = 1.0.0
[    13.481] ABI class: X.Org Server Extension, version 10.0
[    13.481] (II) LoadModule: "modesetting"
[    13.482] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    13.485] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: libgbm.so.1: cannot open shared object file: No such file or directory
[    13.485] (EE) Failed to load module "modesetting" (loader failed, 0)
[    13.485] (EE) No drivers available.
[    13.485] (EE)
Fatal server error:
[    13.485] (EE) no screens found(EE)
[    13.485] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
[    13.485] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    13.485] (EE)
[    13.485] (EE) Server terminated with error (1). Closing log file.

The previous version of 'xorg-server.tcz' from piCore15 is simply tarball'd, copied over to piCore16/piCore17 images and then overlayed into the existing TCE folder after extraction in order to get the desktop back.

piCore15.jpg
https://ibb.co/YF7WH99L

piCore17.jpg
https://ibb.co/bj32fKL5

While not optimal, it does address an existing problem. However, the process of extracting the generated Xorg tarball is not persistent for each instance that the piCore distribution is updated using 'tce-update'. The 'xorg-server.tcz' extension from the piCore15 distribution is always overwritten in the piCore16/piCore17 images during the update procedure and needs to be re-extracted for every upgrade prior to rebooting for the changes to take effect. If the older Xorg version from piCore15 is also used in the piCore16/piCore17 distribution folders, then this hack can be avoided all together.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12961
Re: piCore 17.0.0 Release
« Reply #4 on: August 21, 2026, 05:06:35 PM »
Hi Synerworks
... Xorg.0.log.FAIL
Code: [Select]
[    12.434] Xorg.0.log.FAIL
X.Org X Server 1.21.1.21
X Protocol Version 11, Revision 0
[    12.434] Current Operating System: Linux box 6.18.37-piCore-v7 #41 SMP Mon Jul  6 13:05:12 EDT 2026 armv7l
[    12.434] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:87:46:7F vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  zswap.compressor=lz4 zswap.zpool=z3fold dwc_otg.fiq_fsm_mask=0xF dwc_otg.lpm_enable=0 console=tty1 root=/dev/ram0 rootwait fbcon=map:10 fbcon=font:VGA8x8 nortc loglevel=3 noembed
 ----- Snip -----
[    13.482] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    13.485] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: libgbm.so.1: cannot open shared object file: No such file or directory
[    13.485] (EE) Failed to load module "modesetting" (loader failed, 0)
 ----- Snip -----
[    13.485] (EE) Server terminated with error (1). Closing log file.
...
Does installing  libEGL.tcz  change anything?

Offline Synerworks

  • Newbie
  • *
  • Posts: 11
Re: piCore 17.0.0 Release
« Reply #5 on: August 21, 2026, 09:12:14 PM »
No, both libEGL and libGLES were installed at one point including Xorg-3d.tcz, but considering that piCore64 ARMv8 distribution of Xorg is based  on version 1.21.1.21 and is working leads me to suspect missing dependency in the extension package or an exception raised due to incompatible instruction code generation, mixed ARMv6/v7/v8 objects perhaps. Will look into what the actual variances are between the two releases.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12961
Re: piCore 17.0.0 Release
« Reply #6 on: August 21, 2026, 10:47:33 PM »
Hi Synerworks
I suspect  libEGL.tcz  is present but not loaded. It's not listed in  xorg-server.tcz.dep.
This error:
Code: [Select]
[    13.485] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: libgbm.so.1: cannot open shared object file: No such file or directorysays it can't load  modesetting_drv.so  because it can't find  libgbm.so.1.
libgbm.so.1  is provided by  libEGL.tcz.

Try loading  libEGL.tcz:
Code: [Select]
tce-load -i libEGLThen:
Code: [Select]
startx

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15776
Re: piCore 17.0.0 Release
« Reply #7 on: August 22, 2026, 04:36:48 AM »
I don't have an RPi2 to test, but using an RPi3 and loading Xorg, flwm aterm and wbar, I can see that the problem is caused by /usr/local/share/X11/xorg.conf.d/20-noglamor.conf.

When 20-noglamor.conf is present, xorg-server tries to use the modesetting diver, which depends on libEGL. When libEGL is provided the xorg-server still doesn't start because it is looking for /dev/dri/card0 created by graphics-KERNEL.

When 20-noglamor.conf is not present, xorg-server tries to use fbdev, which works without libEGL and graphics-KERNEL being present.

Currently the xorg-server extension is providing 20-noglamor.conf, according to the results above, it looks like Xorg-3d should provide 20-noglamor.conf.

@Synerworks - perhaps you could test the above on an RPi2 and confirm that fixes things before I modify xorg-server and Xorg-3d?

Basically, you need to try the following:
Code: [Select]
tce-load -i Xorg flwm aterm wbar
sudo rm /usr/local/share/X11/xorg.conf.d/20-noglamor.conf
startx
« Last Edit: August 22, 2026, 04:55:11 AM by Juanito »

Offline Synerworks

  • Newbie
  • *
  • Posts: 11
Re: piCore 17.0.0 Release
« Reply #8 on: August 22, 2026, 12:48:33 PM »
Indeed, the 'xorg-server.tcz' for piCore15 and piCore64s do not contain the Xorg configuration file '20-glamor.conf', as verified with the 'provides.sh 20-glamor' tool, certainly needs to be present in 'Xorg-3d.tcz'. Looks like the artefact was included in the extension preparation and being posted for piCore16/piCore17. This seems similar to how both 'openssl*' and 'ca-certificates*' appears in the 'xorg-server.tcz' extension for piCore15 that keep overlapping the installation/downgrading and causing repeated updates to the mentioned add-ons, especially based on the order that they appear in the 'onboot.lst' file.

Do not have the classic v1.1 PI2 based on BCM2836 ARMv7 to test, v1.2 PI2s use BCM2837s now like the PI3s, and only a few bucks cheaper. Only verify the piCore-v7 images on a PI02W due to the memory footprint being smaller than the ARMv8 builds, after-all, need to squeeze as much out the platforms to keep the 'tiny' designation alive.