- This topic has 436 replies, 24 voices, and was last updated Mar 21-8:50 pm by Brian Masinick.
-
Posts
-
calciumsodium
Some more tests with sound:
I am running alpha1 test system with alsa only using the 6.1 kernel.
Sounds from browsers like firefox-esr and google-chrome sound great.
Sounds from mpv not as good, using the same ytdlautoformat.lua configuration file that I had used in my antiX21 systems.
After some experimentation, I added the line
volume_max=200to my ~/.config/mpv/scripts/ytdlautoformat.lua configuration file.
Now sounds from mpv sound great, similar to that of using the browsers.
Note that this sound increase is sharp and crisp! This is unlike when you have 150% sound amplification using pulseaudio where there are lots of sound distortions.
Hope this is useful to those that use mpv in antiX.
Brian Masinick
Just tested a YouTube video with Firefox Nightly and apulse. Sound came through very nicely.
--
Brian MasinickBrian Masinick
sudo ps_mem.py
Private + Shared = RAM used Program112.0 KiB + 12.5 KiB = 124.5 KiB runit
128.0 KiB + 16.5 KiB = 144.5 KiB runsvdir
148.0 KiB + 21.5 KiB = 169.5 KiB seatd
292.0 KiB + 72.5 KiB = 364.5 KiB cron
364.0 KiB + 118.5 KiB = 482.5 KiB icewm-session
352.0 KiB + 156.5 KiB = 508.5 KiB udevil
420.0 KiB + 118.0 KiB = 538.0 KiB svlogd (4)
492.0 KiB + 408.0 KiB = 900.0 KiB avahi-daemon (2)
736.0 KiB + 190.0 KiB = 926.0 KiB dbus-launch (2)
760.0 KiB + 211.5 KiB = 971.5 KiB gconfd-2
648.0 KiB + 392.5 KiB = 1.0 MiB devmon
816.0 KiB + 378.5 KiB = 1.2 MiB desktop-session
968.0 KiB + 470.5 KiB = 1.4 MiB getty (7)
864.0 KiB + 759.0 KiB = 1.6 MiB sudo (2)
1.3 MiB + 491.0 KiB = 1.8 MiB dbus-daemon (4)
1.7 MiB + 353.5 KiB = 2.0 MiB runsv (19)
1.8 MiB + 295.5 KiB = 2.1 MiB udevd
1.9 MiB + 272.5 KiB = 2.2 MiB bluetoothd
1.8 MiB + 437.5 KiB = 2.2 MiB bash
2.6 MiB + 389.5 KiB = 3.0 MiB dconf-service
2.9 MiB + 609.5 KiB = 3.5 MiB cupsd
2.2 MiB + 1.3 MiB = 3.5 MiB sshd
3.0 MiB + 585.5 KiB = 3.6 MiB at-spi-bus-launcher
3.6 MiB + 131.5 KiB = 3.7 MiB connmand
4.2 MiB + 452.5 KiB = 4.6 MiB conky
4.7 MiB + 1.2 MiB = 5.9 MiB wpa_supplicant
6.4 MiB + 1.6 MiB = 7.9 MiB icewm
7.3 MiB + 2.3 MiB = 9.6 MiB volumeicon
8.9 MiB + 955.5 KiB = 9.8 MiB slimski
11.7 MiB + 1.5 MiB = 13.1 MiB ntpd
12.4 MiB + 3.9 MiB = 16.3 MiB roxterm
14.1 MiB + 3.8 MiB = 17.9 MiB zzzfm
48.1 MiB + 24.3 MiB = 72.4 MiB Xorg
469.3 MiB + 114.6 MiB = 583.9 MiB firefox-bin (9)
———————————
779.2 MiB
=================================This is Firefox Nightly 112.0a1 (2023-02-24) (64-bit) on antiX 23 Alpha 1 with a single tab open.
--
Brian MasinickBrian Masinick
Fresh login with the Kernel: 4.19.0-256-antix.1-amd64-smp x86_64 sudo ps_mem.py Private + Shared = RAM used Program 112.0 KiB + 17.5 KiB = 129.5 KiB runit 128.0 KiB + 21.5 KiB = 149.5 KiB runsvdir 148.0 KiB + 30.5 KiB = 178.5 KiB seatd 296.0 KiB + 115.5 KiB = 411.5 KiB cron 388.0 KiB + 121.5 KiB = 509.5 KiB dbus-launch 408.0 KiB + 140.0 KiB = 548.0 KiB svlogd (4) 368.0 KiB + 272.5 KiB = 640.5 KiB icewm-session 388.0 KiB + 288.5 KiB = 676.5 KiB udevil 464.0 KiB + 467.0 KiB = 931.0 KiB avahi-daemon (2) 648.0 KiB + 437.5 KiB = 1.1 MiB devmon 760.0 KiB + 378.0 KiB = 1.1 MiB dbus-daemon (2) 700.0 KiB + 467.5 KiB = 1.1 MiB getty (5) 816.0 KiB + 435.5 KiB = 1.2 MiB desktop-session 932.0 KiB + 756.0 KiB = 1.6 MiB sudo (2) 1.5 MiB + 418.5 KiB = 1.9 MiB runsv (17) 1.6 MiB + 464.5 KiB = 2.1 MiB bash 1.9 MiB + 535.5 KiB = 2.4 MiB bluetoothd 964.0 KiB + 1.5 MiB = 2.5 MiB udevd (2) 2.2 MiB + 662.5 KiB = 2.9 MiB conky 2.9 MiB + 664.5 KiB = 3.6 MiB cupsd 2.2 MiB + 1.3 MiB = 3.6 MiB sshd 3.5 MiB + 270.5 KiB = 3.8 MiB connmand 4.6 MiB + 1.3 MiB = 5.9 MiB wpa_supplicant 3.3 MiB + 3.4 MiB = 6.7 MiB volumeicon 5.4 MiB + 2.4 MiB = 7.8 MiB icewm 8.9 MiB + 1.4 MiB = 10.3 MiB slimski 9.5 MiB + 3.7 MiB = 13.1 MiB zzzfm 11.8 MiB + 1.5 MiB = 13.3 MiB ntpd 12.1 MiB + 5.1 MiB = 17.1 MiB roxterm 100.7 MiB + 1.6 MiB = 102.2 MiB Xorg --------------------------------- 209.5 MiB =================================--
Brian MasinickXunzi_23
With many users now having SSD or NVME on family computers trim is a theme.
Would suggest to have trim setup to be performed monthly or after a number of boots,
was thinking of 35 as a starting point.Reasoning is many computers, especialy those used by children and students are only
in use for a few hours daily, setting discard for continous trim is a bad option as is
issuing trim command too often.There are plenty of posts for system D setups in the net, I have found little information
of use with nosystemd and runit and, sorry, not enough knowledge/brains to provide a working
solution.A simple setup solution would be useful both in antiX 23 and previous versions.
- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
Robin
With many users now having SSD or NVME on family computers trim is a theme.
Would suggest to have trim setup to be performed monthly or after a number of boots,
was thinking of 35 as a starting point.What will be the consequence for non-SSD or NVME systems on antiX if such a setup is preset?
Windows is like a submarine. Open a window and serious problems will start.
Brian Masinick
With many users now having SSD or NVME on family computers trim is a theme.
Would suggest to have trim setup to be performed monthly or after a number of boots,
was thinking of 35 as a starting point.What will be the consequence for non-SSD or NVME systems on antiX if such a setup is preset?
While these ideas may be useful, it would be best to perform these steps ONLY on systems containing hardware for which a trim is performed, therefore if and only if trimming is useful and needed, then perform the test on a monthly basis, else ignore.
--
Brian MasinickNormal HDD does not have trim command implimented, same goes for some early SSD,
only HDD affected are SMR shingled magnetic drives which support and need trim.Above According to Seagate and WD support docs.
Here several systems are running mixed drive setups, even NVME SSD and HDD Terabyte HDD, as
expected no untoward effects noted, the HDD have discard set which is equivalent to continous
trim. Other setups are either left to themselves or at present manualy trimmed. Most SSD and NVME
become slower if never trimmed.Recent Buntu, Mint some others trim every boot, IMHO too much for best drive health and longevity
unless long run times are the norm.- This reply was modified 2 months, 2 weeks ago by Xunzi_23.
stevesr0
Anyone with SSDs that do trim should be especially careful to have backup, as the deletions are generally NOT recoverable.
stevesr0
techore
Is someone proposing to enable trim by default?
If true, I would recommend to let the operator to decide. Ignoring the fact not all devices support it, there are pros and cons and best to leave it to the operator to decide if it fits their scenario.
I am a big proponent of smart, I still wouldn’t enable it by default. Not my place to tell others they should use it.
Addendum, sister distro info.
MX Linux uses by default an automatic clearing procedure by running the command “ trim ” on a weekly schedule.
So likely not that hard to transfer a setup to antix.Please posters inform yourselves, what trim is and why it is of importance. Good place to get sensible
info Arch Wiki and Forum plus manufacturer documents. This is getting out of hand and OT..
https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Discards
SSD is as the name implies a solid state drive.antiX is used for and openly says supports old and new computers. Means supporting components is important.
Why am I so involved, SSD or NVME brings after a memory upgrade the best possible performance boost to older
devices. Fitted routinely in devices I work on. See samsung controller defect. Not mine but a person close
by is affected.RE: Let the operator decide,
since windoze 7, Trim is enabled by default, Ubuntu, Mint, RHEL, explains how the admin, on the Enterprise
system they sell can trim on RAID arrays. Intel recommends periodic Trim, same approach as Arch. SuSE points
to Arch Wiki and recommends periodic trim.Using discard or continous trim is not recommended.
Re techore comment:
The operator, is in most cases unlikely to be an expert, more likely came from windoze where users need to do nothing,
the system takes care of trim. As it does in pretty much all the more popular consumer distros. Does the owner even know
what trim is…Call pure arch gentoo and a few others less age 60 plus granny Smith or families struggling to educate kids orientated.
There I assume the owner is capable of deciding after consulting the excellent forum, of arch.Please do not confuse or mixup tools.
SMART, is a drive self test and readout tool, generaly not intended to be routinely run in short periods, never has been.@steves, the drive will still eventuaaly overwrite data, just in huge blocks not pages which is not the best way to preserve
the integrity of memory cells. It is initiated by the drive controller and much slower.Yes Important data always needs a backup. That is important no matter what drive is used.
Data loss on SSD and NVME is, should it occur usualy catastrophic and non recoverable outside of a lab costing thousands of USD
for one recovery attempt. No Warranty as impossible to give.- This reply was modified 2 months, 1 week ago by Xunzi_23.
- This reply was modified 2 months, 1 week ago by Xunzi_23.
- This reply was modified 2 months, 1 week ago by Xunzi_23.
MX Linux uses by default an automatic clearing procedure by running the command “ trim ” on a weekly schedule.
So likely not that hard to transfer a setup to antix.Probably true, but then you need to teach people without SSDs how to deactivate this. Does it make any difference whether you teach SSD owners how to activate it, or non SSD owners how to deactivate?
Please posters inform yourselves, what trim is and why it is of importance.
All the available information I can find, reads about what advantages it has when applied on SSDs. But I can’t find any information what happens to a system without SSDs when the commands are applied per OS default. My simple question is still: Can applying these commands as a default do any harm to classical HDDs?
since windoze 7, Trim is enabled by default
Windows is wellknown to enable many things which cause older hardware to fail on their OS.
Intel recommends periodic Trim, same approach as Arch. SuSE points
to Arch Wiki and recommends periodic trim.I can’t see they recommend it for rotational devices. It’s all about SSDs only.
So, before requesting the setting of this constantly repeated cleaning procedure as a default on antiX I’d plead for investigating the side effects on old (non SSD) hardware.
Windows is like a submarine. Open a window and serious problems will start.
Hi Robin,
The reason little or no information is found relating to effects of trim on HDD is that if received
the unsupported thus meaningless Trim command is ignored by the controller of rotating devices i.e HDD with
exception of those having SMR shingled magnetic recording. They need trim.The trim function has been a standard since windows 7, if it damaged HDD the internet would be full of posts
warning about the fact.On a personal note:
My terabyte Rotating drive has been in use together with an SSD for years, it started with
win 7, now has win 10 is in best of health. I did an extended self test recently.
I have manualy issued trim command countless times. Also run a cron job.Difference between me and joe or jane new user is I know how to do so.
A lot of effort is going in to making antiX more attractive and more easily usable for those with little or no
knowledge beyond windoze..You are knowledgable and can easily turn off anything that even mildly irritates or worries you.
anticapitalista
Just some other points to consider.
1, fstrim-antix already exists in /usr/local/bin
2. By default on live medium, cron is turned off
3. During installation user can enable/disable cron (I always disable it).
4. users may be using anacron instead of cronPerhaps the best way to tackle this is to have a simple tool that sets it up for user just by making a couple of choices and pressing a button
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
I have tried this fstrim on the alpha1 test system.
It is easy to use. I used the command:
sudo fstrim --fstab --verbose --quiet
- You must be logged in to reply to this topic.
