It is told that the legacy partitioning schemes were designed around disc storage and we have not yet adjusted to SSDs. I am worried about the TEAR
I would even go further and request you to create MX installers geared towards this. To begin with can you provide howto for people who have already installed the OS.
Partition schemes that reduce TEAR on SSDs [Solved]
Partition schemes that reduce TEAR on SSDs
mx linux 19 (KDE) - using mx linux since 17.1
x86_64 / 32-bit, 64-bit / CPUs 4 / GenuineIntel / Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz
x86_64 / 32-bit, 64-bit / CPUs 4 / GenuineIntel / Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz
Re: Partition schemes that reduce TEAR on SSDs
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Re: Partition schemes that reduce TEAR on SSDs [Solved]
All the FS tools used in MX-Linux have done the proper alignment for SSD drives for some years now.
MX-Linux already installs a weekly cron job to run fstrim. It logs in /var/log/trim.log
That's really all you need for almost all use cases. If you have a particular issue of concern, please give use the details.
MX-Linux already installs a weekly cron job to run fstrim. It logs in /var/log/trim.log
That's really all you need for almost all use cases. If you have a particular issue of concern, please give use the details.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
- uncle mark
- Posts: 859
- Joined: Sat Nov 11, 2006 9:42 pm
Re: Partition schemes that reduce TEAR on SSDs
I'll be damned. I didn't know that. You guys think of everything.timkb4cq wrote: Thu Nov 25, 2021 11:26 am All the FS tools used in MX-Linux have done the proper alignment for SSD drives for some years now.
MX-Linux already installs a weekly cron job to run fstrim. It logs in /var/log/trim.log
Custom build Asus/AMD/nVidia circa 2011 -- MX 19.2 KDE
Acer Aspire 5250 -- MX 21 KDE
Toshiba Satellite C55 -- MX 18.3 Xfce
Assorted Junk -- assorted Linuxes
Acer Aspire 5250 -- MX 21 KDE
Toshiba Satellite C55 -- MX 18.3 Xfce
Assorted Junk -- assorted Linuxes
Re: Partition schemes that reduce TEAR on SSDs
The dev team added the fstrim cronjob back in MX-15. I didn't have an SSD then so I don't think I participated in the thread but I do remember it.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
- chrispop99
- Global Moderator
- Posts: 3365
- Joined: Tue Jan 27, 2009 2:07 pm
Re: Partition schemes that reduce TEAR on SSDs
Note also that swappiness on MX Linux is set to 15, rather than the normal Linux amount of 60. This helps a bit by potentially reducing writes.uncle mark wrote: Thu Nov 25, 2021 12:48 pmI'll be damned. I didn't know that. You guys think of everything.timkb4cq wrote: Thu Nov 25, 2021 11:26 am All the FS tools used in MX-Linux have done the proper alignment for SSD drives for some years now.
MX-Linux already installs a weekly cron job to run fstrim. It logs in /var/log/trim.log
Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines
Re: Partition schemes that reduce TEAR on SSDs
Bravo, no wonder MX Linux is number one distro.timkb4cq wrote: Thu Nov 25, 2021 11:26 am All the FS tools used in MX-Linux have done the proper alignment for SSD drives for some years now.
MX-Linux already installs a weekly cron job to run fstrim. It logs in /var/log/trim.log
That's really all you need for almost all use cases. If you have a particular issue of concern, please give use the details.
mx linux 19 (KDE) - using mx linux since 17.1
x86_64 / 32-bit, 64-bit / CPUs 4 / GenuineIntel / Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz
x86_64 / 32-bit, 64-bit / CPUs 4 / GenuineIntel / Intel(R) Core(TM) i3-4010U CPU @ 1.70GHz