antiX-23-alpha1-runit-full (64bit) for testing

[Member Xunzi_23]

Helpful

Up

0

::

May I politely reaquest that some posters read up what a memory leak is.
After stabilizing I see no change in used memory over 80 plus hours, same findings come from other forum members.

This is NOT a slight on anticapitalista who posted after a short test.

I have experienced real memory leak from gogle browser, not UngoogledChromium. Result was system becoming sluggisg then completely unusable.

Present situation is slightly more memory usage in a stable highly responsive system.

Fact is, why memory usage initialy increases is at present not fully understood. Some is due logfiles but that does not completely explain the
increase.

Back to connman:

Online check can be turned off in /etc/connman/main.conf
[General]
EnableOnlineCheck=false

If a laptop is used following setting is useful.
[General]
PreferredTechnologies=ethernet,wifi

/var/lib/connman/settings
[Bluetooth]
Enable=false #Will test set to manual or maybe true.
Tethering=false
Tethering.Freq=2412

[global]
OfflineMode=false
TimeUpdates=false # set to false, it is true in the alpha. Maybe 22 also, not yet checked.
TimezoneUpdates=false # set to false as NTP is running

Will try and find time to remove NTP and check if connman can completely take over time updates
on the test system.

For those having trouble connecting bluetooth devices following from https://wiki.archlinux.org/title/ConnMan
may be of interest.

Warning: connman grabs rfkill events. It is most likely impossible to use rfkill or bluetoothctl to (un)block
devices, yet hardware keys may still work.

Always use connmanctl enable|disable

Now I know more about headphone users fighting with windmills.

• This reply was modified 2 months, 3 weeks ago by Xunzi_23.

[Member Xunzi_23]

Helpful

Up

0

::

Noticing runit always busy.

$ ps -ef | grep runsvdir
root 5228 1 0 08:01 ? 00:00:00 runsvdir -P /etc/service log: ate directory ‘/var/log/runit/ntpsec’: No such file or directory mkdir: cannot create directory ‘/var/log/runit/connman’: No such file or directory mkdir: cannot create directory ‘/var/log/runit/ntpsec’: No such file or directory mkdir: cannot create directory ‘/var/log/runit/connman’: No such file or directory mkdir: cannot create directory ‘/var/log/runit/ntpsec’: No such file or directory

Have hundreds of entrys in startup log but as yet not found a way to satisfy the system. Ideas, enlightenment very welcome.
At this early stage and running live I am loathe to setup the propriety nvidia drivers as the stick will no longer be portable.

Repeated hundreds of times in log.

sh: 1: nvidia-settings: not found

[Member Xunzi_23]

Helpful

Up

0

::

Still seeing a lot of seemingly never ending network activity, iftop shows
majority to be to NTP servers. Also still some connections to an ipv6 connman.com
adress.
Using $ sudo iftop at present.

All ideas on how to calm things down welcome. Maybe some NTP config problem.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Try purging ntpsec-*

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member calciumsodium]

Helpful

Up

0

::

Hello Xunzi_23,

When I first started testing antiX23 a1, I noticed that connman logs were enabled at startup. Using runit service manager, I saw that it was the only service that had been enabled logging at startup. So I disabled connman log at startup but kept the service on at startup using the runit service manager. Now my diskwrites are very quite when the system is idle.

Incidentally, at the beginning of testing, I also saw that getty-ttyS0 was also doing so diskwrites even though the log was disabled for that service at startup based on the runit service manager. But after a while the getty-ttyS0 logging went away.

[Member calciumsodium]

Helpful

Up

0

::

I saw that the iso snapshot tool has been upgraded.

It looks really cool. It works great with the alpha-1 test system. I like the description of each of the compression tools.

iso-snapshot 23.02.13
iso-template-antix 23.03.14

Thank you so much.

A happy user.

[Member Xunzi_23]

Helpful

Up

0

::

@ calciumsodium, please tell me how to corectly turn off the connman logging I still see
logging attempts listed in htop after renaming the logging instructions in /etc/services.

anticapitalista, thanks for advice, at present I have left the secure time servers setup and
turned off time updates in connman. To get further I will need to setup a testing installed
system in a couple of days time. I read on arch forums NTP is pretty much a rats nest, very
difficult to debug.
The question I can not answer is whether using connman capabilitys as both time server and for
dns resolution advantageous and in line with antiX or if they should be switched off as far as
possible in settings or better disabled before compile.

Further question, how do I set default desktop correctly. I struggle with the present file manager
setup and want to set pure ICEWM for myself and my latest new user friends family who after some
trials feel same as me.

Either I am doing something wrong or at present live setting then F8 save is not working as I expect.
I run live a lot, would like an obvious set default desktop possibility that reliably survives reboots
and remastering.

[Member calciumsodium]

Helpful

Up

1

::

Xunzi_23 wrote:

please tell me how to corectly turn off the connman logging I still see
logging attempts listed in htop after renaming the logging instructions in /etc/services.

This is what I do:

Start runit-service-manager: Applications > Preferences > runit service manager.
It should open the runit service manager. Please see screenshot2. jpg. Here, the connman service is highlighted.

You will notice that for connman service, the status is up and the startup is up.

You will also see that for the connman log, the status is down and the startup is down.

This is how I have set it up.

To the right of the Log Startup, you can toggle enable or disable.

If you have the Log Startup down, then you can enable to enable it.

But if you have the Log Startup up, then you can disable it by clicking disable.

Does this make sense? This is what Xecure had taught me several years ago.

After this change, when I do sudo iotop (you have to install iotop),

then I don’t see any input output diskwrites. Please see screenshot.jpg.

Attachments:

1. 

   screenshot2-1.jpg
   

2. 

   screenshot-6.jpg
   

[Member Xunzi_23]

Helpful

Up

0

::

@calciumsodioum, Many thanks, have system in German language as used daily, I am not native speaker
and the menu says protokoll. I did not associate that correctly.

Had seen a terminal application, I think from void which seems to my 2 working Neurons or so left head
easier to understand than the tick boxes, anyway now I know.
Better use in english, I would have understood log or logging immediately.

[Moderator caprea]

Helpful

Up

0

::

Xunzi_23 wrote:

Either I am doing something wrong or at present live setting then F8 save is not working as I expect

This works here, setting icewm with F6 and the F8 for save. After reboot on the bootscreen the desktop under F6 is named default, but it boots into icewm.

I also changed the setting for connman in runit-service-manager like Calciumsodium, This might could be the default.

[Member calciumsodium]

Helpful

Up

1

::

Xunzi_23 wrote:

how do I set default desktop correctly

There are other ways, but I manually change the file:

/etc/slimski.local.conf

In that file, find the default_sessiontype.
Here I changed it to rox-icewm. Save and reboot.

## Available sessiontypes
## (first one listed shall be the default selection).
## THE VALUE FOR sessiontypes SHOULD BE COMMA-SEPARATED, NO SPACES
sessiontypes rox-icewm,zzz-icewm,minimal-icewm,icewm,kodi

## You can also set here the default sessiontype
default_sessiontype     rox-icewm

[Moderator Brian Masinick]

Helpful

Up

0

::

electing previously unselected package linux-image-6.1.10-antix.1-amd64-smp.
(Reading database … 158211 files and directories currently installed.)
Preparing to unpack …/linux-image-6.1.10-antix.1-amd64-smp_6.1.10-antix.1-amd64-smp-1_amd64.deb …
Unpacking linux-image-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) …
Setting up linux-image-6.1.10-antix.1-amd64-smp (6.1.10-antix.1-amd64-smp-1) …
dkms: running auto installation service for kernel 6.1.10-antix.1-amd64-smp:Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf)
Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf)
Sign command: /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file
Binary /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file not found, modules won’t be signed
Error! Your kernel headers for kernel 6.1.10-antix.1-amd64-smp cannot be found at /lib/modules/6.1.10-antix.1-amd64-smp/build or /lib/modules/6.1.10-antix.1-amd64-smp/source.
Please install the linux-headers-6.1.10-antix.1-amd64-smp package or use the –kernelsourcedir option to tell DKMS where it’s located.
Deprecated feature: MODULES_CONF (/etc/dkms/framework.conf)
Sign command: /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file
Binary /lib/modules/6.1.10-antix.1-amd64-smp/build/scripts/sign-file not found, modules won’t be signed
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1/source/dkms.conf)
Error! Your kernel headers for kernel 6.1.10-antix.1-amd64-smp cannot be found at /lib/modules/6.1.10-antix.1-amd64-smp/build or /lib/modules/6.1.10-antix.1-amd64-smp/source.
Please install the linux-headers-6.1.10-antix.1-amd64-smp package or use the –kernelsourcedir option to tell DKMS where it’s located.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
update-initramfs: Generating /boot/initrd.img-6.1.10-antix.1-amd64-smp
W: No zstd in /usr/bin:/sbin:/bin, using gzip

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

Having difficulty with Alpha 1 adding or changing kernels, including our antiX 6.1.10.

--
Brian Masinick

[Forum Admin anticapitalista]

Helpful

Up

0

::

Brian Masinick wrote:

Having difficulty with Alpha 1 adding or changing kernels, including our antiX 6.1.10.

https://www.antixforum.com/forums/topic/antix-23-alpha1-runit-full-64bit-for-testing/page/14/#post-99421

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

I thought I had taken care of that; apparently I did not.
Works now thanks!

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.10-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-6.1.10-antix.1-amd64-smp
Found linux image: /boot/vmlinuz-4.19.0-256-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-4.19.0-256-antix.1-amd64-smp
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi

--
Brian Masinick

[Author]

Posts