Install report for the 32 bits core ISO, 2026-11-10 on my Neuf Cegetel OpenGate

hardware install iso

fsw · 2026-11-16 19:15 UTC

Here is the install report for the 32 bits core ISO, 2026-11-10 on my Neuf Cegetel OpenGate.
That's an almost 20 years old weird mini-PC/modem combo that I already described in more details in this reply:
https://maille.slitaz.org/thread/4?page=1#p50

Everything went fine, outside of 2 problems that are closely related to the hardware that it contains (although the 2nd might affect more users that the 1st):

1) The board might have been also used for some industrial appliance, because it has actually 2 graphic outputs, even if there is only a VGA port that is connected to the outside world!
So, kernel 3.16 didn't bother with that and always presented me only the VGA to configure, but kernel 6.12 seems much smarter and out of a sudden, I had 2 outputs, VGA and LVDS...
Now I understood better why there is a setting in the BIOS to select CRT, LFP (and even TV) or a combination of 2.
But even selecting "CRT only" didn't change it, so to get rid of this "ghost"  output and finally get my screen config the way I wanted, I ended fixing one and disabling the other by adding:
GRUB_CMDLINE_LINUX_DEFAULT="video=VGA-1:1280x800 video=LVDS-1:d"
to /etc/default/grub.
If anybody needs to force a resolution, and/or enable (with "e")/disable (with "d") an output, you can get the supported resolutions with xrandr, and get the real name of those outputs looking at /sys/class/drm.
This is very important, because in my case, xrandr saw those as "VGA-0" and "LVDS-0", and of course that didn't work...
That was very useful to solve this:
https://superuser.com/questions/636617/disabling-laptop-monitor-on-boot

2) As I use this small PC as an "over-engineered MP3 player" (on my 80's Hi-Fi, accessed headless with VNC), I tested the volume with the slider... and nothing happened!
After checking with alsamixer, it turned out that the "Master" does nothing at all, and what controls really the sound is either "Headphone" or "PCM".
On a classic LXDE desktop, that's not so much of a problem, as you can edit the panel file in:
etc/xdg/lxpanel/LXDE/panels/panel
to add some options to:
Plugin {
    type = volumealsa
}
But that is not so easy with the LXTaz panel as the volume slider doesn't have a separate entry, and it seems included in lxtaz-ctrl... So I ended adding:
Plugin {
  type=volumealsa
  Config {
    CardNumber=0
    MasterChannel=PCM
  }
}
in:
/home/user/.config/lxpanel/slitaz/panels/panel
and I have my own working volume slider ;-) but that's more a workaround than a real solution...

@pankso I saw you just pushed 9 days ago "lxtaz-ctrl: use the first sound card with a Master control, fixes #1033" to choose the correct soundcard in case there is more than one, but do you see any possibility to add a way for the user to pick something else than "Master" for controlling it, like in this case with "Headphone" or "PCM"?

There was also 2 smaller things:

3) I had to install the missing packages with "system language" to get the system fully in french, but the overlay text for the shortcuts of Toile and filature-report-gtk down the screen are still in english...

4) linux-lts-zram was automatically installed, and I know that with a new kernel, there won't be any script in /etc/init.d like the good old compcache, but it doesn't seems activated (zram.ko is not loaded) and the tips from Google IA look very sketchy to me...
I would rather have a good official Slitaz doc on that matter ;-)

Other than that, it looks fine for me, and it's up and running...
So kudos to the team for the hard work!

otrona · 2026-11-17 01:53 UTC

Hi fsw,

About 4) zram: I tried it on SliTaz 5.1 cooking x86_64 (in a VM), and it works by hand.
The module is there, it is only not set up at boot. As root:

modprobe zram
echo 256M > /sys/block/zram0/disksize
mkswap /dev/zram0 && swapon -p 100 /dev/zram0

Check with cat /proc/swaps: /dev/zram0 shows up with priority 100, and free -m shows the swap.

To have it at every boot, I added the same three lines at the end of /etc/init.d/local.sh
(with >/dev/null after mkswap to keep the boot quiet), and it was there again after a reboot.

Notes:
- cat /sys/block/zram0/comp_algorithm lists the compression methods of the kernel.
  Here it was [lzo-rle] lzo; lz4 is not built in, so I left the default.
- 256M is just what I tested. On a machine with little RAM, around a quarter to a half of the RAM is a common choice.
- I only tested x86_64, so the 32-bit kernel may differ; and this is a workaround, not official SliTaz docs.
1 thank you

linea moderator · 2026-11-17 10:50 UTC

@fsw If this works for you please let us know. This is the kind of thing we could have a wiki page for. Thanks

@otrona We need to kick-start the wiki pages for 5.1 and this seems a good place to start. Thanks for all your help.
1 thank you

fsw · 2026-11-17 19:33 UTC

@otrona Hi, yep that did it, thanks a lot!
Google IA had it almost right, after all ;-) but I'm really happy to have read that from somebody (human) that already successfully tested it...
I put 256M for my 512M of total RAM as you did, because the old compache always created /dev/zram0 and /dev/zram1 with 128M each before, and that was working well for me...
Now I have a single 256M /dev/zram0 with priority 100 after a reboot, and still 375.3M available at idle :-)

@linea Hi, yes you can put directly the tip of @otrona in the wiki pages for 5.1!
After testing the commands he noted in the post above, I just added:
modprobe zram
echo 256M > /sys/block/zram0/disksize
mkswap /dev/zram0 > /dev/null && swapon -p 100 /dev/zram0
at the end of /etc/init.d/local.sh and everything seems fine, even after a reboot...

Note 1: as my OpenGate is again headless in another room, I can only connect to it after automatic login to my session with autostarted x11vnc and I'm leazy to dismount everything again, so I couldn't test by myself the effect of having or not " > /dev/null" after mkswap, as I can't see the boot messages.
But I trusted the tip of @otrona and added it anyway, and I see no complains in dmesg, just:
zram: Added device: zram0
zram0: detected capacity change from 0 to 524288
So it seems OK to me...

Note 2: adding a few tips about how much percent of RAM to give to the zram, compared to the installed RAM, from somebody that understand much more on that topic than me would be a good idea too...
According to Google IA (and that seems to make sense), 50 to 100 % is the way for low RAM systems (4 GB or less), 50% for mid-range RAM (8 GB to 16 GB), and capped at 8 GB to 16 GB maximum, or even disabled for High RAM (16 GB to 32 GB+) "Because zram uses CPU cycles to compress and decompress data, allocating massive zram sizes on a system with plenty of raw memory yields diminishing returns."

fsw · 2026-11-17 21:41 UTC · edited 2026-11-17 21:42 UTC

About my soundcard/volume slider issue (point 2 in my first post), I noticed that the script alsa-info.sh was there, so I ran it and here are the results, in case that can be helpful:
https://paste.slitaz.org/?c90cc5e1c81627d2#5XfAsVwvHSBGF7E7AzEVwjDKFVKEUP5ZmxgAZvbtJACu

otrona · 2026-11-18 10:30 UTC

@fsw Glad it works, and thanks for testing it on 32-bit, that was the part I could not check. The > /dev/null only hides the "Setting up swapspace..." line mkswap prints at boot, so with or without it the result is the same.

On the size: for a machine with 512M, half of the RAM like you did is a common choice. The data is compressed, so 256M of zram usually holds more than 256M of memory, but it also uses some CPU, so on old machines I would not go much above that.

@linea If it helps, I can draft the zram page for the 5.1 wiki.
1 thank you

linea moderator · 2026-11-18 18:44 UTC

Hi @otrona, I kind of made a start on this yesterday: https://wiki.slitaz.org/en:guides5.1:zram Feel free to edit/modify this to your own tastes. The Wiki is yours! We're probably going to need a tiny Wifi and Bluetooth page at some stage. Maybe @pankso can lend a hand? (he still owes me 62k btw :))

otrona · 2026-11-19 00:19 UTC

Thanks @linea, nice start! I will add a few sections when I have tested them: how big to make it depending on RAM, how to turn it off again, and a short troubleshooting part. fsw already confirmed it works on 32-bit too. (And good luck with the 62k, I will stay out of that one :))

otrona · 2026-11-19 01:06 UTC

@linea I tried to register on the wiki to add the zram sections. The account was created (user “otrona”), but it says “Looks like there was an error on sending the password mail. Please contact the admin!”, so I never got a password. Could you or @pankso set a password for it or check the wiki mail? In the meantime, here are the sections I tested (turning it off, troubleshooting, size by RAM), feel free to paste them:

===== How big? =====

The size you set is how much swapped data zram can hold. That data is kept compressed, so it uses less real RAM than its size (often a third to a half), but compressing costs some CPU time. On old machines, don't make it too big. A common rule of thumb:

^ RAM in the machine ^ zram size ^
| 512M or less | about half of the RAM (256M on 512M) |
| 1G - 2G | half of the RAM |
| 4G | 1G - 2G |
| 8G and more | rarely needed |

Change the ''256M'' in the commands (and in ''/etc/init.d/local.sh'') to the size you want.

===== Turn it off again =====

<code>
swapoff /dev/zram0
echo 1 > /sys/block/zram0/reset
rmmod zram
</code>

To stop it at boot as well, remove the three zram lines from ''/etc/init.d/local.sh''.

===== Troubleshooting =====

**"sh: write error: Device or resource busy"** when setting the size: zram0 is already set up (''dmesg'' shows "zram: Cannot change disksize for initialized device"). Turn it off as above, then set it up again.

**Not there after a reboot:** check that the lines are at the end of ''/etc/init.d/local.sh'', and look at the messages:

<code>
dmesg | grep zram
</code>

**Live system:** on a live USB or CD, the change to ''local.sh'' is lost at reboot unless the system is installed.

Tested on SliTaz 5.1 cooking x86_64 (i486 reported working by fsw).

linea moderator · 2026-11-19 03:21 UTC

@otrona I tried deleting your account and adding a new one. Hopefully get an email at your slitaz address.

otrona · 2026-11-19 06:34 UTC

@linea Thank you! Still no mail. My slitaz address forwards fine (I tested it), and the wiki’s “Set new password” page shows the same error: “Looks like there was an error on sending the password mail.” So the wiki itself cannot send mail at the moment. Could you set a temporary password for “otrona” and send it to me by private message? I will change it after logging in. (@pankso in case the wiki mail setup needs a look.)

fsw · 2026-11-19 11:01 UTC

To everybody using Slitaz and reading this, please just don't post your issue on the forum, but do your part and use Tazhelper to test and report your hardware to the devs (no privacy or tracking concerns to have, it's just hardware)!

I did, with a description of the problem, and point 2 of my initial post (the volume slider problem) got assigned bug #1060, which was fixed today by lxtaz-ctrl 95.

Now, you can choose which ALSA control selector is really used by the volume slider (in my case "Headphone" or "PCM", but not "Master") and it works, so I could delete the extra plugin I added to the panel...
Kudos for the incredible reactivity!
1 thank you

Log in to reply Sign up