Tiny Core Linux

Tiny Core Base => TCB News => Alpha Releases => Topic started by: Juanito on January 17, 2023, 12:16:47 AM

Title: Tiny Core 14.0 Alpha 1 Testing
Post by: Juanito on January 17, 2023, 12:16:47 AM
Team Tiny Core is pleased to announce that Tiny Core 14.0 Alpha1 is available for public testing:

http://repo.tinycorelinux.net/14.x/x86/release_candidates/distribution_files
http://repo.tinycorelinux.net/14.x/x86_64/release_candidates/distribution_files

This is an alpha level cut. If you decide to help test, then please test carefully. We don't want anyone to lose data.

Since this is an alpha cut, we ask that only experienced users test. This cut is not for general use. The features in any alpha are not fixed and may change before a public release candidate is available.

We appreciate testing and feedback.

Changelog for 14.0 alpha1:
* kernel updated to 6.1.2
* glibc updated to 2.36
* gcc updated to 12.2.0
* binutils updated to 2.39
* e2fsprogs base libs/apps updated to 1.46.5
* util-linux base libs/apps updated to 2.38.1
* busybox updated to 1.36.0
* tce: allow script to exit normally without stdout from bdantas
* autologin: Remove unneeded lines from nick65go
* filetool.sh: having colors from alphons

Note:

* la files have been removed from *-dev extensions (thanks to @Rich)
* intel hd4400 graphics fails with the modesetting driver in x86
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: patrikg on January 17, 2023, 08:43:54 AM
Maybe this is silly question ??
Is it possible to make tc boot faster ??
I thinking of like bmarcus does with picore use the python capabilities to extract the extensions in one core each.
Have seen some problems with that because of not having control of the extractions order of the deps. 
But i think's it's work very well.

I don't know how that can be accomplished with the ordinary tc.
Maybe make some type of depending tree of how and what order the extensions extract.
I don't know how to run shell scripts and commands from each core.
What commands have the capabilities to do that.

Just having only one command in mind that spans the commands in separate cores.
Yes you are right, the make command with it's -j argument.
 
Thats all.
PS. And thx for this os
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 17, 2023, 09:36:12 AM
If you have several cores, TC probably already boots very fast? Move some rarely used extensions to ondemand, etc.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 17, 2023, 10:14:10 AM
Congratulations to the team on this upcoming release!

I'm using it now on my laptop. It is a pleasure to help with testing. It already seems to be in an advanced state of readiness. I've only found two issues so far:

1. The gcc.tcz extension loads but is unusable:
Code: [Select]
$ tce-status -i | grep gcc
gcc
gcc_libs
$ gcc
sh: gcc: not found

2. A handful of extensions (eight, see below) that are dependencies of some of my applications load and can be used (the applications that need them run just fine), but the extensions fail to create a file in /usr/local/tce.installed/

Here's a photo of my laptop's screen when booting with the showapps code, which shows some information that may be helpful:
(http://forum.tinycorelinux.net/index.php?action=dlattach;topic=26077.0;attach=6322)





Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 17, 2023, 04:12:59 PM
I deleted gcc.tcz and reinstalled it. That solved problem #1 in my previous post.
Problem #2 from previous post remains. I'll keep investigating.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 17, 2023, 06:31:54 PM
The 8 extensions impacted by problem #2 seemed too simple to be causing problems, so on a whim I removed the extension being loaded before them, namely gnumeric.tcz, from my onboot.lst file. Lo and behold, problem #2 went away.

I'm not sure what it is about gnumeric.tcz that's causing the "Permission denied" error for the handful of extensions that are loaded after it. I inspected the contents of gnumeric.tcz (including its tce.installed script) and nothing seems amiss. Very strange. I will just do without gnumeric for now.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 17, 2023, 11:33:49 PM
gnumeric.tcz's permissions for the tce.installed dir may be wrong, missing the group write permission?
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on January 18, 2023, 07:07:01 AM
Hi curaga
That happened when I removed the  .la  files from the extensions.

It turns out that the  unsquasfs (V4.2)  command on our server removed the
group write permission. The Tinycore  unsquasfs (V4.3)  command does not
do that.

There are 424 x86 and 458 x86_64 extensions affected. I will fix them tonight.
Attached are the lists of affected extensions.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 07:31:57 AM
Thanks, Rich. Mystery solved!
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 09:26:58 AM
On this alpha (64-bit) I can no longer create a 5 GHz 802.11ac hotspot on my router using hostapd.

I have confirmed that regulatory domain is set correctly. Whether I use the hostapd from the repo or one compiled for this version, result is the same: wireless clients can authenticate but have no internet connectivity, router becomes completely unresponsive after about 1 minute.

I will try creating a 5 GHz 802.11n hotspot: If that works, points to a problem with 802.11ac support; if that doesn't work, points to a problem with 5 GHz support.

curaga: Between TCL13.1 and TCL14-alpha1 is there any relevant change in kernel configuration options? All the hardware is the same on my end.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 18, 2023, 09:31:16 AM
No, I don't think any wifi-related config changed. Wifi drivers (among with graphics) do often have bugs though.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 09:35:21 AM
I am able to create a working 5 GHz 802.11n AP. The problem is with 802.11ac.

Thanks for that, curaga. Any troubleshooting ideas? I'd like to upgrade the router if possible, but not at the expense of my nice 802.11ac AP.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 11:10:01 AM
Crash seems to happen as soon as a device authenticates, suggesting a regression in wireless authentication/encryption.

So I tinkered some more and discovered that, indeed, there's no problem if using 802.11ac with WPA1. When using 802.11ac with WPA2, certain encryption algorithms (including what I've been using for years) now cause router to immediately become unresponsive when first client authenticates.

For 802.11ac and WPA2, these settings seem to work just fine (just relevant lines from hostapd.conf are shown):
Code: [Select]
driver=nl80211
country_code=US
channel=36
hw_mode=a
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=SecRetPasswOrd
wpa_key_mgmt=WPA-PSK
I realize that this is a very specific and very small regression, probably not affecting too many users. Sorry for the noise.

I'm very happy to be able to move past this and upgrade the router to TCL14-alpha1 :)
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 04:29:27 PM
No joy. Changing the encryption options lowers speed considerably.

- TCL13.1 with old hostapd.conf: link speed = 433 Mbps, speedtest.net download speed = 120 Mbps

- TCL14 with modified hostapd.conf: link speed = 54 Mbps, speedtest.net download speed = 20 Mbps (or use old hostapd.conf with the new kernel and be subject to immediate system crash when a wireless client authenticates).

The wireless device that creates my AP is the ALFA AWUS036ACHM, which uses mt7610u chipset. The kernel panic when using linux kernel 6.1.x and this chipset is a known issue, for which a kernel patch exists:
https://github.com/morrownr/USB-WiFi/issues/168

@curaga - Would it be possible to include this kernel patch in TCL14 release? This chipset is supposedly one of the superstar chipsets with best linux support (see https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md), so others who power their wireless router with TCL would also benefit from this patch.


Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on January 18, 2023, 09:22:00 PM
Hi GNUser
Gnumeric and any other extensions that had incorrect tce.installed permissions
have been corrected and new md5.txt files were generated.

Update your extensions and see if things act normally now.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on January 18, 2023, 10:34:44 PM
Hi GNUser
These are the extensions that were corrected:

x86
cpufreqd.tcz
fakeroot.tcz
gfortran.tcz
gnome-themes-standard.tcz
openldap.tcz

x86_64
gfortran.tcz
gnumeric.tcz
libfm-dev.tcz
libfm-extra-dev.tcz
openldap.tcz
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 18, 2023, 10:49:05 PM
Hi, Rich. Yes, I can confirm that loading gnumeric.tcz now causes no errors when loading downstream extensions.

Hi, curaga. I can confirm that v5 of the kernel patch (available at https://patchwork.kernel.org/project/linux-wireless/patch/20221230200747.19040-1-nbd@nbd.name/ and also attached) works as advertised.

I applied the patch to the TCL14 kernel source. Then I compiled the mac80211.ko module and repackaged wireless-6.1.2-tinycore64.tcz with it. Router is working perfectly now, creating the usual blazing-fast 802.11ac AP, crash-free.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 19, 2023, 12:16:48 AM
It takes some time to do a full kernel build, so generally we don't do a respin unless there's some serious bug. IMHO this is not big enough, and you're likely the only one using TC as a router with that wifi stick - but good to hear you have it working with a custom extension.

BTW it looks like Felix posted some mt76 fixes a week ago, if you hit other crashes they may be needed.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 19, 2023, 02:23:05 AM
Hi, curaga. Thanks for the tip regarding the mt76 fixes.

I just want to point out that only the one module in wireless-KERNEL (mac80211.gz) had to be swapped because that's all that the patch changes. I'm still using the kernel image (vmlinuz64) and modules initrd (modules64.gz) that you guys released as alpha version. I mention this here in the off chance that it is helpful to anyone.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: gadget42 on January 19, 2023, 05:24:16 AM
thanks for that clarification
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 20, 2023, 12:31:04 PM
Hi, curaga. Would you like me to submit wireless-6.1.2-tinycore64.tcz with no changes except patched mac80211.gz (I've tested it extensively and it's working perfectly)? If so, I'd be happy to. If not--e.g., because you want the kernel and all modules to come from same full kernel build--I totally understand.

Juanito, I submitted a bunch of refreshed networking-related packages for TCL14 64bit.

I hope TCL14 is the best release ever ;D
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 21, 2023, 12:11:58 AM
I do want to keep the original modules from one build, but you're welcome to submit it under another name. Then the info file can cover when it's useful and to rename it, etc.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 21, 2023, 07:29:30 AM
Hi, curaga. I submitted it under another name, with an info file as you suggested. Thanks.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: mocore on January 22, 2023, 12:57:29 AM
... how to run shell scripts and commands from each core.
What commands have the capabilities to do that.
...
numactl or taskset command's
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 23, 2023, 01:59:00 AM
Maybe this is silly question ??
Is it possible to make tc boot faster ??
...
Just having only one command in mind that spans the commands in separate cores.
IMHO, to boot TC faster, I used to combine tcz for onboot. ex: all tcz+deps for Xorg-server (100+ tcz) into one Xorg-full.tcz; same for gtk3-full.tcz, ffmpeg4-full.tcz etc. I gain 10+ seconds in boot speed. What target gain (in seconds) do you aim for?

Another idea could be to improve the awk "golden engine" of "tce-load" for loading tcz. Because this engine first builds a full list of dependencies (for all tcz to be loaded) and then it loads / unsquashes them sequentially. So test for cpu-cores and then the loading list (of independent tcz) can be split-ed for total CPU cores.

PS:TC aims for CPU 486 compatibility, so it was no interest for multi-core. But in year 2023, and 64 bits era, then SMP (symmetric multi-processing) rises its head.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: patrikg on January 23, 2023, 04:47:51 AM
I am not aiming for booting faster, just saying that we can use our multi-core CPU more efficient.
And use the parallell, could maybe be some good solution, but what i think you need to make some kind of dep tree, to see whats the system need to extract first, and like you sayed you could combined the extensions together, just extract them all first into some tmp directory and then compress them all into one piece.

Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 23, 2023, 05:05:14 AM
@patrikg: I am glad that you agree with the idea to combine tcz into one big for huge tcz+deps (like Xorg server)  :)

Regarding multi-core CPU: It is a waste of (expensive) electricity to have 100 cores and NOT use all together for 1 second, instead of one core for 100 seconds (the 99 cores just sleeping). But it is a say, like "double of nothing is nothing!". 
Because I am not a programmer/developer, for me the Pareto principle apply, 80% efficiency with 20% work. So spending (2-3 hours ) time to "improve" tce-load, just to recover them in 2-3 years, is not worth for my time. ex: 365 days/year x 3 years / (10 sec / 60 sec/min / 60 min /hour => 3.04 hours.

PS: the "deep" tree can be seen from TC appls, or from /tmp/tcload/extensions.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: CNK on January 24, 2023, 06:12:34 AM
Quote
Regarding multi-core CPU: It is a waste of (expensive) electricity to have 100 cores and NOT use all together for 1 second, instead of one core for 100 seconds (the 99 cores just sleeping). But it is a say, like "double of nothing is nothing!". 
Because I am not a programmer/developer, for me the Pareto principle apply, 80% efficiency with 20% work. So spending (2-3 hours ) time to "improve" tce-load, just to recover them in 2-3 years, is not worth for my time. ex: 365 days/year x 3 years / (10 sec / 60 sec/min / 60 min /hour => 3.04 hours.

The kernel does most of the work, the "mount" and "cp -ais" commands called from tce-load largely just tell the Linux kernel what to do. The kernel already multi-threads itself. You can list all the kernel threads currently running with:
Code: [Select]
ps | grep '\['

Currently I've got 86 kernel threads, so if I had 100 CPU cores I might have some to spare, but as it is I've only got four. If I run top and press "1" to see all the CPU cores while loading an extension with many dependencies at the same time, all four cores show an increased "sys" usage, so the kernel must be having some success at splitting the mount and symlink tasks over all four cores.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 24, 2023, 06:35:03 AM
@CNK: I have also just 4 cores ( maybe 2 cores , 4 threads?) on my AMD APU,  so will be no big deal if (or not) tce-load will load TCZs in parallel.  But I saw a big difference using a manually made Xorg-full.tcz , because CPU was not switching to each thread/ tc-loop. Or maybe reading each tcz from rotational/slow HDD when faster cores are already sleeping waiting for I/O data not in RAM / cache.

It was all theoretically. I understand that a 4-core CPU will split the workload in maxim 4 threads for the same command ( to load one tcz). The possible improvement discussed was about loading many (100) tcz in parallel. Be cause the B-two tcz have to wait (is a sequential list of dependency) until A-one.tcz finish (loaded by 4 threads in parallel), even if (in the mean time) 3 cores finish A-one.tcz but 4-th core still process the last thread of A-one.tcz. [so I think]. So was about few n-1 core sleeping because at least one core still process the initial command.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 24, 2023, 07:54:23 AM
Maybe another option, for faster 100 tcz loading, could be to have a tce-load switch /parameter on boot, to on-demand bypass loading 100 md5 files (tcz checksum) from a slow HDD, plus then implicit bypassing 100 calculation + comparisons of those md5. Or maybe ordering index/files in squash tcz, because Xorg will not show until all .so are loaded from many tcz.

PS: I wonder how many programs (as % from total) still run under Xvesa /Xfbdev in today tc14. Because most of them ask for gtk3, which in turn ask for Xlibs -> Xorg. Any proper (modern) browser  asks for Xorg.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 24, 2023, 09:32:51 AM
md5 files are not checked on boot, only on download. This has always been so, specifically because it would make boot very slow on old cpus.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: CNK on January 24, 2023, 02:02:01 PM
PS: I wonder how many programs (as % from total) still run under Xvesa /Xfbdev in today tc14. Because most of them ask for gtk3, which in turn ask for Xlibs -> Xorg. Any proper (modern) browser  asks for Xorg.

I think you're mixing up the X server and Xlib. Xvesa/Xfbdev were always supposed to work with Xorg's Xlib, they're separate things (Xlib allows programs to talk to the X server).

You might be interested to look at Nano Linux, as it's a Tiny Core based distro that uses a "nano" version of both the X server and Xlib.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 24, 2023, 03:26:01 PM
I love 32 bits software. But unfortunately (for me) my UEFI-64bits booting in 32 bits will show only 2GB RAM, out of 8 GB RAM. So no go for Xvesa and 32 bits kernel, only for chroot. Neither mixture kernel 64 bits and Xfbdev, because insane radeon luminosity without xf86-video-radeon. [I hate Dell /HP firmware for (L)users]

So, to summarize:
1. OK, md5 route for onboot.lst was already implemented in TC, sorry that I overlook it (-1). But the merge for 100 tczs into one Xorg-full.tcz for fast speed was not yet challenged (+1).

2. Sorting/indexing files inside squashfs-ed tcz for speed was not challenged (+1). Neither "parallel" processing /piping (even with naive "interval halving method" like sub-call in sub-call) (+1)

3. from distrowatch -> Nano Linux has status discounted from 2015-12-26 (-1). My mistake to say (talk about) Xlib.(-1). Not interested.

4. All online-banking ask for "modern"/bloated browser WITH java-script. So dillo / links / netsurf etc are dead for this task. The main point was about GTK3! and no up-to-date (security concerns) browser runs without gtk3 and Xorg.(+1).

5. May I repeat the question again to (long experience) users: How many programs (as % from total) still run under Xvesa /Xfbdev in today tc14?
Title: Tiny Core 14.0 Alpha 1 Testing - bug in filetool
Post by: nick65go on January 25, 2023, 10:28:32 AM
Testing TC14 alpha 64 bits, I found a small bug in filetool for backup/restore (png attached). The ESC-characters (maybe for colors?) are not interpreted, instead they are shown ad-literal, like " ^ [ [ ".
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on January 25, 2023, 12:08:25 PM
Hi, nick65go. That's a screenshot of /usr/local/bin/filetool (GUI frontend to filetool.sh) (included in Xprogs.tcz). It seems that it does not support colors.

filetool.sh was colorized recently. I'm actually finding the colors a bit jarring since it's the only command I use over SSH that does colors. I could get used to it, but if the colors are creating problems for the GUI frontend then maybe the colors should be scrapped?
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 25, 2023, 11:02:23 PM
Oh, if it causes trouble for the GUI, indeed should be reverted. Will revert.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on January 28, 2023, 09:09:55 PM
Hi nick65go
fltk-1.3 has been patched to recognized ANSI color escape sequences.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 28, 2023, 11:25:42 PM
Un-reverting the script change.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 29, 2023, 05:50:12 AM
Hi Tinycore Team! Thank you very much, I confirm that in TC14 alpha1 64 bits:

- the FLWM windows-manager now has the corner arrows (thanks Rich)
- the filetool.sh runs with colors, same as is its GUI filetool. (thanks curaga)
- Xfe file-manager was updated to version 1.45 (thanks GNUnuser)

-Xorg-server (1.21.1.6), kernel (6.1.2), busybox (1.36) are up-to-date as in other Linux-distributions.
Maybe there are other good news (not discovered yet by me versus tc13).
PS: I am not picky, just say that filetools, shell versus gui, has different output text colors (see attach).
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 29, 2023, 10:21:58 AM
I have a problem with Xorg-3D. My laptop has an APU (=CPU+GPU). The kernel sees an AMDGPU (so core GCN 2.x?), but UEFI console and Xorg want RADEON.

I exit from Xorg and I instaled from condole the graphics-6.1.2-tinycore64.tcz, without instaling xf86-video-ati.tcz, neither xf86-video-amdgpu.tcz.
Then /var/log/Xorg.0.log is:
Code: [Select]
[   660.876] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/drm/card0
[   660.961] (WW) Warning, couldn't open module ati
[   660.961] (EE) Failed to load module "ati" (module does not exist, 0)[   661.171] (II) modeset(0): glamor X acceleration enabled on KABINI (, LLVM 13.0.0, DRM 2.50, 6.1.2-tinycore64)
[   661.289] (II) modeset(0): [DRI2] Setup complete
[   661.289] (II) modeset(0): [DRI2]   DRI driver: radeonsi
[   661.289] (II) modeset(0): [DRI2]   VDPAU driver: radeonsi
[   664.064] (II) modeset(0): Modeline "1600x900"x0.0  128.78  1600 1648 1680 2298  900 902 907 934 -hsync -vsync (56.0 kHz eP)
[   664.162] (EE)
[   664.162] (EE) Backtrace:
[   664.162] (EE) 0: /usr/local/lib/xorg/Xorg (xorg_backtrace+0x56) [0x5609e30bfd3f]
...
[   664.162] (EE) 2: /lib/libc.so.6 (0x7f6a3f66a000+0x36870) [0x7f6a3f6a0870][   660.876] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/drm/card0
[   660.961] (WW) Warning, couldn't open module ati
[   660.961] (EE) Failed to load module "ati" (module does not exist, 0)[   661.171] (II) modeset(0): glamor X acceleration enabled on KABINI (, LLVM 13.0.0, DRM 2.50, 6.1.2-tinycore64)
[   661.289] (II) modeset(0): [DRI2] Setup complete
[   661.289] (II) modeset(0): [DRI2]   DRI driver: radeonsi
[   661.289] (II) modeset(0): [DRI2]   VDPAU driver: radeonsi
[   664.064] (II) modeset(0): Modeline "1600x900"x0.0  128.78  1600 1648 1680 2298  900 902 907 934 -hsync -vsync (56.0 kHz eP)
[   664.162] (EE)
[   664.162] (EE) Backtrace:
[   664.162] (EE) 0: /usr/local/lib/xorg/Xorg (xorg_backtrace+0x56) [0x5609e30bfd3f]
...
[   664.162] (EE) 2: /lib/libc.so.6 (0x7f6a3f66a000+0x36870) [0x7f6a3f6a0870]
...
[   664.164] (EE) 10: /usr/local/lib/libLLVM-13.so (LLVMBuildInBoundsGEP2+0x51) [0x7f6a3a6cbc7d]
[   664.164] (EE) 11: /usr/local/lib/dri/radeonsi_dri.so (0x7f6a3d971000+0x924823) [0x7f6a3e295823]
[   664.165] (EE)
Fatal server error:
[   664.165] (EE) Caught signal 6 (Aborted). Server aborting
...
[   664.164] (EE) 10: /usr/local/lib/libLLVM-13.so (LLVMBuildInBoundsGEP2+0x51) [0x7f6a3a6cbc7d]
[   664.164] (EE) 11: /usr/local/lib/dri/radeonsi_dri.so (0x7f6a3d971000+0x924823) [0x7f6a3e295823]
[   664.165] (EE)
Fatal server error:
[   664.165] (EE) Caught signal 6 (Aborted). Server aborting

So the Xorg is focused on radeon driver, even if in dmesg I have

Code: [Select]
cat 1.txt | grep -i amd
smpboot: CPU0: AMD A6-6310 APU with AMD Radeon R4 Graphics (family: 0x16, model: 0x30, stepping: 0x1)
Performance Events: AMD PMU driver.
perf: AMD IBS detected (0x000000ff)
amd_uncore: 4  amd_nb counters detected
amd_uncore: 4  amd_l2 counters detected
AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
ehci-pci 0000:00:12.0: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
ehci-pci 0000:00:13.0: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[drm] amdgpu kernel modesetting enabled.
amdgpu: Virtual CRAT table created for CPU
amdgpu: Topology: Add CPU node
amdgpu 0000:00:01.0: vgaarb: deactivate vga console
amdgpu 0000:00:01.0: amdgpu: get invalid ip discovery binary signature from vram
amdgpu 0000:00:01.0: amdgpu: amdgpu_discovery is not set properly
amdgpu 0000:00:01.0: amdgpu: failed to read ip discovery binary from file
[drm:0xffffffffa0295938] *ERROR* amdgpu_discovery_init failed
amdgpu 0000:00:01.0: amdgpu: Fatal error during GPU init
amdgpu 0000:00:01.0: amdgpu: amdgpu: finishing device.
amdgpu: probe of 0000:00:01.0 failed with error -22
ATOM BIOS: AMD

Code: [Select]
cat 1.txt | grep -i radeon
smpboot: CPU0: AMD A6-6310 APU with AMD Radeon R4 Graphics (family: 0x16, model: 0x30, stepping: 0x1)
[drm] radeon kernel modesetting enabled.
radeon 0000:00:01.0: vgaarb: deactivate vga console
radeon 0000:00:01.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
radeon 0000:00:01.0: GTT: 2048M 0x0000000040000000 - 0x00000000BFFFFFFF
[drm] radeon: 1024M of VRAM memory ready
[drm] radeon: 2048M of GTT memory ready.
[drm] radeon: dpm initialized
radeon 0000:00:01.0: WB enabled
radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c
radeon 0000:00:01.0: radeon: using MSI.
[drm] radeon: irq initialized.
[drm] radeon atom DIG backlight initialized
[drm] Radeon Display Connectors
fbcon: radeondrmfb (fb0) is primary device
radeon 0000:00:01.0: [drm] fb0: radeondrmfb frame buffer device
[drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0

PS: To avoid any old firmaware bug, I tried both with firmware-radeon and firmware-amdgpu from TC original then from Alpine.
But I have the same problem, for Xorg-3D.
EDIT: I does not help the fact that in http://tinycorelinux.net/14.x/x86_64/release/src/kernel/config-6.1.2-tinycore64 we have
Code: [Select]
CONFIG_DRM_AMDGPU=m
# CONFIG_DRM_AMDGPU_SI is not set
# CONFIG_DRM_AMDGPU_CIK is not set
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 29, 2023, 11:02:26 AM
To avoid any doubts about mixing firmware + drivers etc, in a console I did:
Code: [Select]
ls /tmp/tcloop/ | grep xf86-video
xf86-video-ati/
xf86-video-fbdev/
xf86-video-vesa/
and
Code: [Select]
lsmod | grep amdoutput nothing, only kernel-radeon drv is loaded
and
Code: [Select]
cat onboot.lst
kmaps.tcz
regdb.tcz
HP-radeon.tcz
graphics-6.1.2-tinycore64.tcz
Xorg-7.7-3d.tcz
flwm.tcz
aterm.tcz
wbar.tcz
wifi.tcz
acpid.tcz
So, at least for RADEON case: I suspect /usr/local/lib/dri/radeonsi_dri.so has a linking problem.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Juanito on January 29, 2023, 09:53:07 PM
If you don't load xf86-video-amdgpu or xf86-video-ati, but do load graphics-KERNEL, does the modesetting driver work?
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on January 29, 2023, 10:44:05 PM
There is no problem with ati/radeon vs amdgpu. Your card is supported by ati/radeon, and the optional/experimental amdgpu support for it is correctly disabled. X failed to start because llvm called abort(), meaning you are hitting a llvm or mesa bug. You can disable 3d in your xorg.conf or try older versions.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 30, 2023, 02:01:28 AM
There is no problem with ati/radeon vs amdgpu. Your card is supported by ati/radeon, and the optional/experimental amdgpu support for it is correctly disabled. X failed to start because llvm called abort(), meaning you are hitting a llvm or mesa bug. You can disable 3d in your xorg.conf or try older versions.
Right I hit a bug in LLVM  or mesa.
So for clarity, lets forget ALL future discussion about amdgpu, and concentrate only on radeon.

Xorg-3D without graphics-KERNEL works OK, using xorg-FBDEV (so is not accelerated).
If you don't load xf86-video-amdgpu or xf86-video-ati, but do load graphics-KERNEL, does the modesetting driver work?
1. After exit xorg and loading (in console) the graphics-KERNEL, then the console/prompter is frozen and I must do cold reset the laptop.

2.Fresh boot.After exit xorg and loading (in console) FIRST the firmware-radeon.tcz and THEN the graphics-KERNEL, now I stay console/prompter. When I start Xorg now, it shows briefly (1 second) the Xorg-window + mouse cursor, then it quickly quits back in console.
The less /var/log/Xorg.0.log shows that Xorg successfully loaded modeset-drv +llinput etc and then Xorg spits (EE) about libLLVM-13.so + radeonsi_dri.so.

3. Fresh boot.After exit xorg and loading (in console), first firmare-radeon, then Xf86-video-ati then graphics-kernel. And now I have the same briefly Xorg shown and then it quickly quits back in console. The less /var/log/Xorg.0.log shows that Xorg successfully loaded RADEON-drv +llinput etc, and then it spits (EE) about libLLVM-13.so + radeonsi_dri.so, right afler "RADEON (0): Modeline "1600x900" etc.


Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 30, 2023, 02:24:48 AM
For the case loading firmware-radeon + xf86-video-ati + graphics-kernel, all there tcz loaded from console before starting xorg, here is attached the full /var/log/Xorg.0.log. You can see the (EE) from libLLVM-13.so + radeonsi_dri.so.
FYI: I know is in alpha1 stage so work in progress. but to use Xorg-3D without acceleration is a NOT-go for anyone with a laptop [so I think].
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Juanito on January 30, 2023, 02:55:10 AM
The update from tc-13 -> tc-14 is about updating the base libs - i.e. glibc, gcc, zlib, etc - and the kernel.

It doesn't look like the kernel graphics drivers are causing your problem, so it must be some combination of mesa, xorg-server and llvm.

Due to problems with intel hd4400 graphics, in tc-14 mesa was updated from 21.3.4 - > 22.3.3 and xorg-server to the latest version, but this did not fix the problem and the problem differs between 32bit/64bit.

The release notes for mesa-22.3.4 show one radeon fix, but it doesn't look like your issue.

You could try using tc-13 mesa extensions in tc-14 or try recompiling mesa-22.3.3 with debug flags to see if you learn more - I don't believe any of us has the hardware to test.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 30, 2023, 03:24:29 AM
I  tried using tc-13 extensions in tc-14, and it works! I am lucky.
The only thing that I replaced (in the end, after many try and errors) was Xorg--7.7-3d.tcz
so the problem is on /tmp/tcloop/Xorg-7.7-3d/usr/local/lib/dri/radeonsi_dri.so
It seems that llvm-lib, xf86-video-ati, firmware-radeon, all are OK.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 30, 2023, 07:38:12 AM
Compiling / debuging is over my "pay grade". I could grab Alpine/Archlinux and I am done. But I still love tinycore.
So, for any good samaritean, here is the info need:

[ANNOUNCE] mesa 22.3.3 https://lists.freedesktop.org/archives/mesa-dev/2023-January/225908.html
 radeonsi: rewrite si_update_ps_colorbuf0_slot to fix crashes and recursions
 radeonsi/vcn: av1 film_grain output fix

or [ANNOUNCE] mesa 22.3.4 https://lists.freedesktop.org/archives/mesa-dev/2023-January/225916.html
 radeonsi: respect smoothing_enabled
 radeonsi/gfx11: fix ge_cntl programming
 radeonsi: report 0 block size for Polaris HEVC encoding
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on January 30, 2023, 10:05:40 PM
Hi nick65go
... PS: I am not picky, just say that filetools, shell versus gui, has different output text colors (see attach).
There are a couple of things going on here. The blue background of the GUI contrasts differently
than the black background of the terminal. The color commands from tc-functions also force
the text to bold, which fltk reacts to differently than regular text. I made a fake filetool.sh
script to show how the colors react for bold and regular text, with blue, white, and black
backgrounds:
(https://forum.tinycorelinux.net/index.php?action=dlattach;topic=26077.0;attach=6334)

I attached the fake filetool.sh script in case anyone wants to play with it. Copy it to /usr/bin/
and use the Dry Run option in the filetool GUI.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on January 31, 2023, 02:39:37 AM
@Rich: Thank you for the clear visual comparison. My main preference is for strong contrast foreground vs. background, instead of bold text. Because I can not see very well fade colors (ex: grey on back, green on blue, etc). In the end, I could modify the colors myself, but I try to do be synchronized with original tinycore.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: alphons on January 31, 2023, 02:43:05 AM
Was a few days off, building linux from scratch.
Today i had the pleasure to do some testing on the TinyCore 14 Alpha.

Results: https://github.com/alphons/TinyCore/blob/main/TestingTinyCore14Alpha.md (https://github.com/alphons/TinyCore/blob/main/TestingTinyCore14Alpha.md)

Summary:


By compiling the same kernel again on the just booted 14.alpha involves all the steps of compiling kernel, making modules, making new iso etc. So i think it was a good test  8)

When samba works, a whole lot of extensions must work also, because it is a beast to run.

cheers.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: FlyingDutchman on February 04, 2023, 12:36:46 AM
Hi,

Congrats on the new release. I tested TCL pure64 release 14 on my installation and it works fine. I also did a quick check on the dependency files and found some files listed as dependency, that do not exist in the package folder (http://tinycorelinux.net/14.x/x86_64/tcz/). I don't use these packages, so no issue for me, but maybe someone else may benefit if these issues are resolved. Please note that these issues are in the x86_64 packages. I didn't check the x86 packages.
Code: [Select]
dependency perl_archive_zip.tcz in file auto-multiple-choice.tcz.dep not found
dependency gst-plugins-good-dev.tcz in file gstreamer-editing-services-dev.tcz.dep not found
dependency enchant-dev.tcz in file gtkhtml-dev.tcz.dep not found
dependency perl_xml_simple.tcz in file icon-naming-utils.tcz.dep not found
dependency perl_xml_simple.tcz in file icontool.tcz.dep not found
dependency icu65-dev.tcz in file js68-dev.tcz.dep not found
dependency python-olefile.tcz in file python-pillow.tcz.dep not found
dependency linux-5.10_api_headers.tcz in file tcc.tcz.dep not found
dependency xtables-addons-6.1.2-tinycore64.tcz in file xt_geoip_LE_IPv4.tcz.dep not found

Cheers.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 04, 2023, 05:48:45 AM
Hi FlyingDutchman
Perl extensions are version specific and were not copied over because perl was recompiled.
gst-plugins-good-dev.tcz and gst-plugins-ugly-dev.tcz were both last seen in TC10-x86_64.
enchant-dev.tcz likely needs to be changed to enchant2-dev.tcz.
icu67-dev.tcz is listed in js52-dev.tcz.dep and js78-dev.tcz.dep.
python-olefile.tcz was last seen in TC11-x86_64.
linux-5.10_api_headers.tcz should now be linux-6.1_api_headers.tcz. FIXED
xtables-addons-5.10.3-tinycore64.tcz was last seen in TC12-x86_64.

Thank you for reporting this.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 05, 2023, 11:08:25 AM
Hi nick65go
I did some more work on the ANSI color escape sequence patch.
I have not posted it to the repo yet.

The person that created the patch didn't do a good job on the
color handling, so I thought I'd try to fix that.

I displayed the pre-defined normal and bright colors in aterm, took
a screenshot, and used gimp2 to get their RGB values.

Then I wrote a new routine to handle escape sequences that
match a terminal as closely as possible.

The text colors now display correctly:
(https://forum.tinycorelinux.net/index.php?action=dlattach;topic=26077.0;attach=6338)

Text with default, white, and black background:
(https://forum.tinycorelinux.net/index.php?action=dlattach;topic=26077.0;attach=6339)

This one should be self explanatory:
(https://forum.tinycorelinux.net/index.php?action=dlattach;topic=26077.0;attach=6340)

Supported escape codes include:
8 normal colors for foreground and background.
Enable bold text, selects bright colors for foreground.
Disable bold text, selects normal colors for foreground.
Enable underlined text.
Disable underlined text.
Reset all settings to default values.

Differences between terminal and fltk behavior are:
terminal:
foreground defaults to white.
background defaults to black.
escape sequences remain in effect until another escape sequence changes something.

fltk:
foreground defaults to black.
background defaults to a light blue.
escape sequences get reset to default values when a newline character is encountered.

Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: adb014 on February 06, 2023, 01:22:33 AM
I noticed in the file http://tinycorelinux.net/14.x/x86/release/src/busybox/compile_busybox the comment "need to compile in tc-11.x as glibc >= 2.32 does not support rpc".. Wouldn't it be better to either

1) Remove support for NFS in tinycore and no longer need RPC at all, or
2) link busybox against libtirpc.so

Have the shell compiled on a different version of the glibc seems to me to be a horrible hack
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: alphons on February 06, 2023, 05:54:09 AM
1) Remove support for NFS in tinycore and no longer need RPC at all, or

I agree to remove the NFS mount option from busybox, also the more modern SMB (CIFS) option is enabled, should be a good alternative for most file sharing options.

Code: [Select]
sed -i 's/CONFIG_FEATURE_MOUNT_NFS=y/CONFIG_FEATURE_MOUNT_NFS=n/' busybox-1.36.0_config_suid

Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 06, 2023, 06:08:57 AM
Hi alphons
That would break the  NFS  option in  /etc/init.d/tc-config.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 06, 2023, 06:13:09 AM
@alphons: You test TC in VMware (not free software), but I use poor-man Qemu (free software).
- what you MEASURABLLY gain (in speed, size) using SMB versus NFS ?
- I think qemu NBD (network block device) allows loops still fast enough. YMMV.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: adb014 on February 06, 2023, 06:59:05 AM
If NFS is needed, busybox can be linked against libtirpc.so.. If you want a self-contained binary link it against libtirpc.a
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: adb014 on February 06, 2023, 07:04:49 AM
There is also at least 3 CVE with a CVSS of 7.5 in glibc (https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-767/GNU-Glibc.html) impacting glibc prior to 2.32.. So this older glibc is already a problem, and a problem that is only going to get worse
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 06, 2023, 07:33:11 AM
The busybox build is not static, old glibc CVEs are not affecting anything. It's simply dynamic linking to code that still exists in the current glibc, but is just not allowed to be linked against anymore.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: adb014 on February 06, 2023, 12:34:29 PM
Reading a bit, it seems that removing CONFIG_FEATURE_MOUNT_NFS won't stop NFS from working with kernels move recent than 2.6.23. See http://lists.busybox.net/pipermail/busybox/2017-September/085848.html where the busybox developer seem to have MOUNT_NFS desactivated by default
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: CNK on February 06, 2023, 05:15:19 PM
Quote
Reading a bit, it seems that removing CONFIG_FEATURE_MOUNT_NFS won't stop NFS from working with kernels move recent than 2.6.23. See http://lists.busybox.net/pipermail/busybox/2017-September/085848.html where the busybox developer seem to have MOUNT_NFS desactivated by default

The "If im reading the docs correctly" bit of the post at that link makes one wonder where those docs are. After some searching it turns out the CONFIG_FEATURE_MOUNT_NFS has been depreciated and removed from the BusyBox config docs. You can see the old description in this git commit (https://git.busybox.net/busybox/commit/util-linux/Config.src?id=a86e02492d7700ce8cb4108f53646dfb025c2dff):

Quote
-     Enable mounting of NFS file systems.
+   Enable mounting of NFS file systems on Linux kernels prior
+     to version 2.6.23. Note that in this case mounting of NFS
+      over IPv6 will not be possible.
+
+       Note that this option links in RPC support from libc,
+          which is rather large (~10 kbytes on uclibc).

But in the same year someone on the Debian mailing list described it here (https://lists.debian.org/debian-boot/2011/02/msg00492.html) as if it were more of a behaviour changing option, and suggested turning it on (without anyone raising objections):

Quote
- # CONFIG_FEATURE_MOUNT_NFS is not set
+ CONFIG_FEATURE_MOUNT_NFS=y

this enables mounting of nfs filesystems just like
old mount from util-linux did (now it all is moved
to nfs-common with a helper mount.nfs).  This is to
support nfs root.  NFS mount needs rpc library, which
is not very large.  RFC.

The BusyBox mailing list thread also mentions a solution for building with newer glibc versions when  CONFIG_FEATURE_MOUNT_NFS is set:
Quote
The cause of this is that rpc.h is no longer included in glibc-2.26. See
the announcement and release notes here:

https://sourceware.org/ml/libc-alpha/2017-08/msg00010.html

* Sun RPC is deprecated. The rpcgen program, librpcsvc, and Sun RPC
headers will only be built and installed when the GNU C Library is
configured with --enable-obsolete-rpc.  This allows alternative RPC
implementations, such as TIRPC or rpcsvc-proto, to be used.

So there are workarounds that work (enable obsolete-rpc).

That seems like the safest/easiest option if it still works, but my aim is just to clarify the facts for the TC developers.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 06, 2023, 05:44:03 PM
Hi CNK
I think  --enable-obsolete-rpc  may have been removed:

Quote
Deprecated and removed features, and other changes affecting compatibility:

* Remove configure option --enable-obsolete-rpc.  Sun RPC is removed
  from glibc.  This includes the rpcgen program, librpcsvc, and the Sun
  RPC header files.  Backward compatibility for old programs is kept
  only for architectures and ABIs that have been added in or before
  glibc 2.31.  New programs need to use TI-RPC
  < http://git.linux-nfs.org/?p=steved/libtirpc.git;a=summary > and
  rpcsvc-proto < https://github.com/thkukuk/rpcsvc-proto >.

Dated 6 Aug 2020 for GNU C Library version 2.32 found here:
https://lwn.net/Articles/828210/

Similar information plus a little history:
https://stackoverflow.com/a/71976359
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 06, 2023, 11:39:16 PM
If the option were disabled, NFS mounting would require the nfs-utils mount.nfs and helpers. Having minimal NFS support (nolock and ipv4) without bloat is good.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: CNK on February 07, 2023, 05:26:38 PM
Sounds like the current build tricks are the best for full features with the smallest size then.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: alphons on February 09, 2023, 08:12:58 AM
@alphons: You test TC in VMware (not free software), but I use poor-man Qemu (free software).
- what you MEASURABLLY gain (in speed, size) using SMB versus NFS ?
- I think qemu NBD (network block device) allows loops still fast enough. YMMV.

I am sorry but i do not use NFS any more myself, since ... 1996 !!
Stopped when not using Sun sparc stations anymore.
Seen implementations in de wild, preferable version NFS 4.0

I use Qemu also. But, most of my systems all are running esxi (vmware), tesing can be done on the free vmware player, and then you can copie 1 on 1 over to the esxi environment.
For personal usage, esxi is also free.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 10, 2023, 01:13:29 AM
@alphons: Lets not confuse "free" to use (close source) software (like VMware) with "open source" software (like qemu). Then, at lest for me, is important:
1. FLEXIBILITY (to change arch 32/64 on the fly, or use libc and musl in-parallel). to have access to various apps.
2. perceived SECURITY, in isolated environment, especially network exposed  (ex: firefox in separateVM). With "security" I can even run Kolibri-OS in a small VM, to have txt / pdf / audio / video etc.

The main goal is to use apps which ask for less RAM in VM. Because it is hard to upgrade my RAM on old machine. And qemu has snapshot storage (layer over layer). to reuse same "hdd" micro-core in simultaneous VM, etc.
PS: I am sorry to deviate from the main topic, which is TC14-alpha.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 14, 2023, 09:13:12 PM
Hi nick65go
I did some more work on the ANSI color escape sequence patch.
I have not posted it to the repo yet.

The person that created the patch didn't do a good job on the
color handling, so I thought I'd try to fix that. ...
Sorry, I've been kind of busy.

Fltk-1.3 has been updated in TC10 through TC14, both x86 and x86_64 to better
match the colors displayed in a terminal.
 
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 15, 2023, 05:06:16 AM
Hi nick65go
If you or anyone else wants to review the changes, a tarball containing the
source package, patches, AnsiMode.H, and build script can be found here:
http://tinycorelinux.net/14.x/x86/tcz/src/fltk/
and here:
http://tinycorelinux.net/14.x/x86_64/tcz/src/fltk/
Both of tarballs are the same.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 15, 2023, 08:09:42 AM
http://tinycorelinux.net/14.x/x86_86/tcz/src/fltk/ (http://tinycorelinux.net/14.x/x86_86/tcz/src/fltk/)
Both of tarballs are the same.
Hi Rich, Thank you!
PS: should be _64/ not _86 :)
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 15, 2023, 12:42:48 PM
feed-back for TC14 64 bits alpha (and tc13 64):
from aterm I run mntool, it works OK, but I see:
Code: [Select]
tc@box:tc@box:~$ mnttool
XOpenIM() failed
mntools works OK.

now I define a file-manager variable, FILEMGR , and mntool can unmount many disks. OK.
I try to mount any disk, it will do it, BUT it will crash /close instant! Lucky it works correctly and mount that disk/partition.
in aterm I see
Code: [Select]
tc@box:~$ export FILEMGR=fluff
tc@box:~$ mnttool
XOpenIM() failed
sh: fluff: not found
tc@box:~$
so the bug is that mntool will "uselessly" search for this variable FILEMGR, and allow just one partition/disk to be mounted before it exit.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 15, 2023, 01:20:07 PM
I forgot to mention that even if I load the fluff.tcz is the same behavior for mntool, with (or not) fluff opened, as long as FILEMGR is not an empty string. Which of course I can empty in the $user./profile.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 15, 2023, 02:15:19 PM
Hm, I think I got it:
IF a variable FILEMGR is defined in environment, then mnttool  will mount the slected partition AND open that file-manager (fluff, xfe, whatever) with that partition already selected AND it close itself. Nice.

However, if no FILEMGR is defined (is empty string) then mnttool will mount the partition AND stay alive for next command (mount another partition). Very clever, but nowhere explained in the wiki neither in forum, book etc.

PS: "strings which (mnttool)" found another variable, MNTTOOL. I wonder what it will do undocumented.
      From source code it seams that it defines position (x y) to show on desktop, maybe from top-left (found by try and error).
PS2: in aterm, the message "XOpenIM() failed" remains.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 15, 2023, 02:29:40 PM
Hi nick65go
... PS: should be _64/ not _86 :)
Thanks, fixed.  :)
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 15, 2023, 11:00:43 PM
You can ignore the IM warning. It's about Chinese (etc) input.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 20, 2023, 09:35:30 AM
The exfat module location doesn't matter for loading it etc, putting all those in the same dir was simpler in sorter.sh. As for virtio disks, it's quite possible some scripts are missing vda* cases.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: patrikg on February 20, 2023, 09:47:24 AM
Maybe you should ask some good person to let you in in the wiki, to add some section and text in the wiki what nice you doing. To add support for virtio device recognition in the tc.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on February 23, 2023, 08:42:38 AM
Hi nick65go
The Qemu discussion has been split into a separate thread:
https://forum.tinycorelinux.net/index.php/topic,26118.0.html
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 24, 2023, 02:19:12 PM
I was looking over one of the "main" function for me, tce-load. I re-aranged and commented a little the script, so it seems more compacted and quick tree logic from first words/test.ex: instead of
Code: [Select]
copyInstall() {
    [ -d /mnt/test ] || sudo /bin/mkdir -p /mnt/test
    sudo /bin/mount $1 /mnt/test -t squashfs -o loop,ro
    if [ "$?" == 0 ]; then
        if [ "$(ls -A /mnt/test)" ]; then
            yes "$FORCE" | sudo /bin/cp -ai /mnt/test/. / 2>/dev/null
            [ -n "`find /mnt/test/ -type d -name modules`" ] && MODULES=TRUE
        fi
        sudo /bin/umount -d /mnt/test
    fi
    [ "$BOOTING" ] || rmdir /mnt/test
}
I wrote it like
Code: [Select]
# $1=THISAPP, ex: abc.tcz; mount it on /mnt/test; then copy its files into / ; eventualy set flag MODULES
_copyInstall() {
    [ -d /mnt/test ] || sudo /bin/mkdir -p /mnt/test
    [ "$(sudo /bin/mount $1 /mnt/test -t squashfs -o loop,ro)" ] && ( [ "$BOOTING" ] || rmdir /mnt/test ) || break
    [ "$(ls -A /mnt/test)" ] ( yes "$FORCE" | sudo /bin/cp -ai /mnt/test/. / 2>/dev/null || ( [ -n "`find /mnt/test/ -type d -name modules`" ] && MODULES=TRUE )
    sudo /bin/umount -d /mnt/test
}


same for
Code: [Select]
update_system() {
    if [ "$BOOTING" ]; then
        [ "$MODULES" ] && sudo /bin/touch /etc/sysconfig/newmodules
    else
        [ "$THISAPP" != "$EXTENSION" ] || [ "$DOWNLOAD_ONLY" ] || [ "$LOAD_ONLY" ] || echo "$THISAPP" >> ../$ONBOOTNAME
        if [ "$MODULES" ]; then
            sudo /sbin/depmod -a 2>/dev/null
            sudo /sbin/udevadm trigger
        fi
        sudo /sbin/ldconfig 2>/dev/null
    fi
   
    if [ -x "$TCEINSTALLED"/$2 ]; then
        if [ "$BOOTING" ] ; then
            echo "$TCEINSTALLED"/$2 >> /tmp/setup.lst
        else
            sudo "$TCEINSTALLED"/$2
        fi
    else
        touch "$TCEINSTALLED"/$2
    fi
}
which became like this
Code: [Select]
# $1=THISAPP; $2=THISAPP_without_EXTENSION; $BOOTING is used one time only
update_system() {
    if  [ "$BOOTING" ]; then
        [ "$MODULES" ] && sudo /bin/touch /etc/sysconfig/newmodules
        [ -x "$TCEINSTALLED"/$2 ] && echo "$TCEINSTALLED"/$2 >> /tmp/setup.lst
    else
        sudo /sbin/ldconfig 2>/dev/null
        [ "$MODULES" ] && (sudo /sbin/depmod -a 2>/dev/null || sudo /sbin/udevadm trigger)
        [ -x "$TCEINSTALLED"/$2 ] && sudo "$TCEINSTALLED"/$2
        touch "$TCEINSTALLED"/$2
        [ "$THISAPP" != "$EXTENSION" ] || [ "$DOWNLOAD_ONLY" ] || [ "$LOAD_ONLY" ] || echo "$THISAPP" >> ../$ONBOOTNAME
    fi
}


for example I can quickly see what $BOOTING will do in update_system(), or what copyInstall() is about.
The original functions are already fast, so is not about extra speed. Any chance that this type of main tree and branches to be used in TC14?
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 25, 2023, 01:00:22 AM
I guess this is mainly about clarity? At least for me, a long line with embedded && || conditions is a bit harder to read than the existing version.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 25, 2023, 01:10:37 AM
I guess this is mainly about clarity? At least for me, a long line with embedded && || conditions is a bit harder to read than the existing version.
yes, mainly for clarity; it is a pain without script commented .
but I study / prefer if focus will shift to more parallel execution, or piping, avoiding external commands/programs/scripts, maybe more xarg /awk etc.
in a real machine is no big difference, in a not-accelerated virtual the scale is 2x - 4x slower than real.
maybe all is for pin-nuts, it depends of the frequency of running those programs, and in them what is the possible bottle-neck.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 25, 2023, 05:00:30 AM
Hi, in /usr/bin/select (of 1332 bytes), searching for string "15" will give results:
Code: [Select]
Search "15" (5 hits in 1 file of 1 searched)
   Line 34:       for (l=1; l<=15; l++) {
   Line 39:       if ( NR > 15 ) printf ", (n)ext, (p)revious: "
   Line 44:          if ( j > 15 )
   Line 52:             j = j - 15
   Line 56:       if (selection+0 < 1 || selection+0 > NR ) j = j - 15

These will limit search shown list to max 15 lines / items. Most machines/PC have (even in console) 25 horizontal lines / rows. Subtracting 3 row (header) + 2 rows (footer) from 25, still allows for 20 lines to list.
May we have the changed "j" counter to max 20?
or maybe tce-ab could check for an external variable ($LEN=), so we can summon it like:
Code: [Select]
LEN=50; tce-ab
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 25, 2023, 05:26:06 AM
I saw that tc14-x86_64 does not enable parallel processing for xarg.
Code: [Select]
https://mirrors.dotsrc.org/tinycorelinux/14.x/x86_64/release/src/busybox/busybox-1.36.0_config_nosuidCONFIG_XARGS=y
# CONFIG_FEATURE_XARGS_SUPPORT_PARALLEL is not set
Maybe for 64 bits, it could be enabled.
Even for 486 CPU compatibility, we can have a test for $BUILD=`uname -m` before calling xarg -P$NrCpu etc.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on February 25, 2023, 06:04:11 AM
The idea for "xargs -P 4" is about mounting lets say 100 SquashFs tcz from local disk /tce/optional using a list. Or not waiting for each tcz to be "wget"-it; so will be downloads in parallel from $MIRROR when using tce-fetch.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: curaga on February 25, 2023, 07:50:28 AM
Mirrors usually limit traffic by IP, so putting several downloads at once will get you no faster total results. It's also considered abusive to open a lot of connections since it ties up resources.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 01, 2023, 07:50:03 AM
Do we have a beta or final release coming soon? IMHO the alpha has been well tested.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Juanito on March 01, 2023, 12:17:31 PM
Maybe next week - real life has been getting in the way..
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 01, 2023, 12:22:20 PM
Got it. I hope all is well. Real life has that tendency...
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 04, 2023, 07:19:55 PM
SNIP
x86_64
libfm-dev.tcz
libfm-extra-dev.tcz

Hi Rich, I can see the corrected dep files
http://tinycorelinux.net/14.x/x86_64/tcz/libfm.tcz.dep
http://tinycorelinux.net/14.x/x86_64/tcz/libfm-dev.tcz.dep

but can not spot where I went wrong in build script
Quote
P=libfm
SNIP
echo 'libfm.tcz
menu-cache-dev.tcz
gtk2-dev.tcz
libexif-dev.tcz '> $P-dev.tcz.dep

echo 'gtk2.tcz
menu-cache.tcz
libexif.tcz  ' > $P.tcz.dep

except for the change in order for the running dependency I am clueless what I did wrong.  :-[

The reason I ask is, I plan to submit updates for this and pcmanfm
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 04:18:02 AM
Hi  Rich
2 possible issues?

I have a tower but have  a dongle that I used to use with  wicd but that does not work for me at the moment
Code: [Select]
wicd
/usr/local/sbin/wicd: exec: line 3: /usr/local/bin/python: not found

I have a permission denied loading wifi-manager which looks like a fine replacement for wicd

Code: [Select]
tce-load -i wifi-manager
yad.tcz: OK
wireless-6.1.2-tinycore64.tcz: OK
find: /tmp/tcloop/eiwd/var/lib/iwd: Permission denied
eiwd.tcz: OK
libnl.tcz: OK
iw.tcz: OK
libdb.tcz: OK
db.tcz: OK
iproute2.tcz: OK
wifi-manager.tcz: OK

ls -al /tmp/tcloop/eiwd/var/lib/
total 0
drwxr-xr-x 3 1000 staff 26 Jan 18 02:44 ./
drwxr-xr-x 3 1000 staff 26 Jan 18 02:44 ../
drwx------ 2 1000 staff  3 Jan 18 02:44 iwd/

Hope that I am on the right path....often wrong more than right
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 08:13:55 AM
Hi aus9
... Hi Rich, I can see the corrected dep files ...
See reply #7:
https://forum.tinycorelinux.net/index.php/topic,26077.msg167313.html#msg167313
Not dep files. I corrected permissions in a bunch of extensions.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 08:36:10 AM
Hi aus9
...
Code: [Select]
wicd
/usr/local/sbin/wicd: exec: line 3: /usr/local/bin/python: not found
...
I think you might have the wrong python installed. You did install one of them, right?
python.tcz provides  /usr/local/bin/python
python3.x.tcz provides  /usr/local/bin/python3
 
Quote
...
Code: [Select]
----- Snip -----
ls -al /tmp/tcloop/eiwd/var/lib/
total 0
drwxr-xr-x 3 1000 staff 26 Jan 18 02:44 ./
drwxr-xr-x 3 1000 staff 26 Jan 18 02:44 ../
drwx------ 2 1000 staff  3 Jan 18 02:44 iwd/  <-------
It looks like user 1000 has read permission, but if you are user tc, that is user 1001.
staff has no permissions at all.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 04:11:07 PM
Rich

corrected deps reply.....I have no idea how my brain works.
a brain ....a brain....half my kingdon for a brain ;)

2) correct I am tc so umm will eiwd need a rebuild?

3) wicd python question
Code: [Select]
tc@box:/mnt/sda3/tce/optional$ ls python*
python.tcz        python3.6-setuptools.tcz
python.tcz.dep        python3.6-setuptools.tcz.dep
python.tcz.md5.txt        python3.6-setuptools.tcz.md5.txt
python3.6-dev.tcz        python3.6-xlib.tcz
python3.6-dev.tcz.dep        python3.6-xlib.tcz.dep
python3.6-dev.tcz.md5.txt        python3.6-xlib.tcz.md5.txt
python3.6-distutils-extra.tcz        python3.6.tcz
python3.6-distutils-extra.tcz.dep      python3.6.tcz.dep
python3.6-distutils-extra.tcz.md5.txt  python3.6.tcz.md5.txt
python3.6-pip.tcz        python3.7.tcz
python3.6-pip.tcz.dep        python3.7.tcz.dep
python3.6-pip.tcz.md5.txt        python3.7.tcz.md5.txt
python3.6-psutil.tcz        python3.9-dev.tcz
python3.6-psutil.tcz.dep        python3.9-dev.tcz.dep
python3.6-psutil.tcz.md5.txt        python3.9-dev.tcz.md5.txt
python3.6-pulsectl.tcz        python3.9.tcz
python3.6-pulsectl.tcz.dep        python3.9.tcz.dep
python3.6-pulsectl.tcz.md5.txt        python3.9.tcz.md5.txt
tc@box:/mnt/sda3/tce/optional$

Maybe I need to delete them and start afresh?
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 04:26:18 PM
nick65go

I have read your posts 38 39 and I have an AMD APU
I am not using flwm nor an xorg file and glxgears fails for me. Now it may be my desktop, a private update to icewm.

Can you exit FLWM to prompt and report any error messages please.

for me I see something like....but icewm loads okish
Quote
Error opening display
[GFX-1] glxtest libEGL initialize failed
[GFX-1] glxtest GLX Extension missing

I need to solve this myself but interested to see if you get similar message.

slightly off topic, I did not build icewm on pure 14x....I may have to
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 05, 2023, 07:31:21 PM
Hi aus9. Yes, it looks like eiwd needs to be repackaged. I'll take care of it.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 07:38:29 PM
Hi GNUser
I just did that. The repo has been updated.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 07:45:39 PM
Hi aus9
... 2) correct I am tc so umm will eiwd need a rebuild? ...
eiwd has been repackaged. Update your system and try again.

Quote
... Maybe I need to delete them and start afresh?
It sounds like maybe you just didn't load python.tcz:
Code: [Select]
tce-load -i python
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 05, 2023, 08:19:29 PM
Hi Rich. Your updated eiwd.tcz will not work for me or other users who use user=foo boot code.

Changing ownership of files and directories to tc (uid 1001), which you did, only fixes one of two problems with the extension. The second problem is lack of group permissions on /var/lib/iwd.

Please change permissions of /var/lib/iwd from 700 to 770. Then any user who is part of the staff group is good to go.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 08:20:43 PM
Hi GNUser
Will do.  :)
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 08:26:51 PM
Hi GNUser
Done.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 05, 2023, 08:29:45 PM
Looks good now, Rich. Thank you.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 09:07:25 PM
Hi Rich

I deleted eiwd* from tcedir and attempted
Code: [Select]
tce-load -w eiwd but might need server to update repo so will try again tomorrow thanks
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 09:10:18 PM
Hi aus9
The Tinycore server is updated. If you are using one of the downstream
servers they can take up 24 hours to update.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 09:22:39 PM
Hi Rich
eiwd updated thanks.

I am going to give up on wicd but first here was how my brain worked?

tce.install script for wicd unpack tarball to root of system but my unpack shows
Code: [Select]
tar xvf files.tar.gz
usr/
usr/local/
usr/local/bin/
usr/local/bin/python2.7
usr/local/bin/python2-config
usr/local/bin/python2
usr/local/bin/pydoc
usr/local/bin/idle
usr/local/bin/2to3
usr/local/bin/smtpd.py
usr/local/bin/python2.7-config

right so I use root powers to delete wicd-gtk and edit real copy under usr loc bin adding 2.7 so it reads
Quote
exec /usr/local/bin/python2.7 -O /usr/local/share/wicd/gtk/wicd-client.py $@

Then Juanito's info says start dbus then wicd daemons but only dbus wants to play with me.
Code: [Select]
/usr/local/etc/init.d/dbus status
dbus is running.
sudo /usr/local/etc/init.d/wicd start
Starting wicd daemon
tc@box:/usr/local/bin$ sudo /usr/local/etc/init.d/wicd status
wicd daemon is not running.

Lets give up on wicd at the moment....I will try wifi-manager after I compile the kernel for 8188eu for 14x later.....much later ;)

Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: Rich on March 05, 2023, 09:39:19 PM
Hi aus9
Looks like python changed since TC10
from:
Code: [Select]
/usr/local/bin/pythonto:
Code: [Select]
/usr/local/bin/python2
...
Code: [Select]
wicd
/usr/local/sbin/wicd: exec: line 3: /usr/local/bin/python: not found
...
Try changing line 3 to  /usr/local/bin/python2
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: aus9 on March 05, 2023, 11:31:30 PM
hi Rich I did python2 for executables *cli curses and gtk but no matter whether I make python2 or python2.7,
the wicd daemon starts and then immediately borks.

I can not find a wicd log anywhere.

At the risk of being rude.....lets forget wicd please
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: nick65go on March 06, 2023, 02:13:21 AM
I have read your posts 38 39 and I have an AMD APU
I am not using flwm nor an xorg file and glxgears fails for me. Now it may be my desktop, a private update to icewm.
Can you exit FLWM to prompt and report any error messages please.

I am currently successfully using TC14 with 3D acceleration. Using TC14 kernel ver. 6.1 I have no choice but to use the radeon console, and xf86-video-ati in Xorg. So for kernel/dri I load only radeon, not amdgpu And I use the old Xorg-3D acceleration from TC13 , because in tc14 is a BUG, even for radeonsi. So talk about AMDGPU is closed (for me) in TC14 for my 8 years old APU: AMD A6-6310 APU with AMD Radeon R4 Graphics (family: 0x16).

IF you use another kernel (which has CONFIG_DRM_AMDGPU_{SI, CK} =yes in kernel config), like Alpine-Linux kernel has,
and also on grub you give the proper parameters for SI/CIK, then you may have success in Xorg-3D with xf86-video-amdgpu. BUT, all new 3D drivers are (in almost all distributions) linked with LLVM15+ -libs (a monstrous 125 MB size), instead of llvm13 in TC14.
Title: Re: Tiny Core 14.0 Alpha 1 Testing
Post by: GNUser on March 06, 2023, 04:10:29 AM
I will try wifi-manager after I compile the kernel for 8188eu for 14x later.....much later ;)
Hi aus9. I am interested in your experience with wifi-manager when you get around to it. If you post about it in the forum and I don't respond, please send me a PM. Sometimes I might miss a post about an extension that I maintain, but I always respond to PMs.

My main goals for wifi-manager are these:
  - config file format must be obvious
  - usage must be dead-simple
  - user should never be surprised at what happens

If you find any deviation from the above, I would consider it to be a serious bug that must be fixed.