Tiny Core Base > Alpha Releases

Tiny Core 16.0 Alpha 1 Testing

<< < (9/16) > >>

Rich:
Hi MikeLockmoore

--- Quote from: Juanito on February 22, 2025, 10:32:46 AM --- ... corepure64.gz = rootfs64.gz + modules64.gz ...
--- End quote ---
You can create corepure64.gz like this:

--- Code: ---cat rootfs64.gz modules64.gz > corepure64.gz
--- End code ---

MikeLockmoore:
Thanks Rich and Juanito.  I did get it to boot!  I'm having networking issues and I notice that screen & window repainting is much slower than normal.  A big window takes about 1 to 2 seconds... you can see the repaint flow down the window.  :o

I have to take a break now for some family activities, but I'll probably work on this later today.  Thanks again!

andyj:
Bind 9.20 needs liburcu-dev, which is available for 64 bit but not 32 bit. I'm also building against Tcl/Tk 9.0 which is not ABI compatible with 8.6. Other updates will include MariaDB 11.4, PHP 8.4, and Postgresql 17.

MikeLockmoore:
Minor update: I did a boot with 16 RC with a "base" boot parameter to avoid any release 15 extensions being loaded or anything from my version 15 home.  The graphic repaint is working much better.  Maybe not as snappy as regular version 15, but you can't see redrawing flow.  If you quickly move a GUI window like the text editor, there is more graphical tearing than version 15, but nowhere near as bad as I was seeing with a bunch of extensions loading, including thinkpad_acpi.tcz which I think includes some graphics drivers for DRM mode, etc.  Maybe some of the version 15 extensions don't play nice with v.1.4.1 FLTK built into the new version of FLWM? 

I do need to build back up a developer's set of extensions for the version 16 RC boot mode to maybe do some refinement of FLWM or apps.  I'm not sure if I am supposed to be able to do this, but I thought the GUI apps (e.g. Control Panel and Editor) should be scalable now with Ctrl Plus or Ctrl Minus key combos, but I didn't see it work so far.

As far as running extensions in this 16 RC environment, can I just use the normal Apps tool and pull in the regular extensions and have them run "on boot" as normal, or will I need special extensions?  I think there's a wireless library that wants kernel 6.12-specific stuff that won't work with the wiresless kernel modules extension for release version 15.

Rich:
Hi MikeLockmoore
I would avoid mixing extensions from different versions. Kernel
modules shouldn't be an issue. Dependency files don't include
kernel versions. They include entries like wiresless-KERNEL.tcz.
Then, tce-load uses uname -r to determine the running kernel
and uses that to replace KERNEL with the kernel version and
load the matching kernel module extension.

Problems can occur when extensions and or dependencies are
updated to different versions across releases.

What I do is set up separate partitions for different versions. I
make them between 2 and 4 Gigabytes. That's plenty of space
for extensions as well as a persistent home and opt directories.

Navigation

[0] Message Index

[#] Next page

[*] Previous page