Root size needed for MX 23 - or just old hardware?  [Solved]

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Root size needed for MX 23 - or just old hardware?

#1 Post by Solon »

Hi guys!

I run two different laptops, both are dual boot with Win. Both have big HD's so space (overall) is not a problem. Also, I am not a 'power' user.

This computer is a much older one, which was running MX 19, which I stepped up through MX 21 and then went on to MX 23 almost immediately, just to try things out. My other, much newer laptop is running MX 21.

However, on this (older) computer, I noticed a much longer load time for processes and programs. Everything works, and runs, but the time for loading or switching is longer, maybe as long as 5+ seconds, compared to the almost instantaneous loading of the past.

When I abandoned Win 7, and first did a dual boot, and moved this older computer to MX, I followed good advice from the Internet, to actually have a Root partition since it made movement from one version to another safer and easier, since your Home files would be separated and unaffected if something went wrong with the Root. This has worked fine up to now, and I sized the Root partition above what was suggested back then.

This recent move from MX 19 to MX 23 is the first time I have had a 'slow down' in speed, although functionality is still fine.

So.... before I move my new machine over to MX 23 -- here are my questions:
  1. Is the slow down due to Root being too small for MX 23
  2. Or is it just that my older processor is the source of the problem?
I will put my Quick Info below, and then sign on immediately with my new computer, and put its Quick Info below in Post #2.

Thanks!

Code: Select all

System:
  Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: hpet
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=<filter> ro quiet
    splash
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: N/A info: frameworks v: 5.103.0 wm: kwin_x11 vt: 7
    dm: SDDM Distro: MX-23.3_KDE_x64 Libretto January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: TOSHIBA product: Satellite P770 v: PSBY1U-009005
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: TOSHIBA model: PHRAA v: 1.00 serial: <superuser required> part-nu: PSBY1U-009005
    uuid: <superuser required> BIOS: TOSHIBA v: 2.20 date: 10/30/2012
Battery:
  ID-1: BAT1 charge: 0% condition: 7.1/48.6 Wh (14.6%) volts: 6.7 min: 10.8
    model: COMPAL PABAS0241231 type: Li-ion serial: <filter> status: not charging
CPU:
  Info: model: Intel Core i5-2410M bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 level: v2
    built: 2010-12 process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1038 high: 1563 min/max: 800/2900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 917 2: 828 3: 1563 4: 844 bogomips: 18357
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Toshiba
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300
  Device-2: Alcor Micro USB 2.0 Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-1.4:3 chip-ID: 058f:b003 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
  Monitor-1: LVDS-1 model: Seiko Epson 0x544b built: 2008 res: 1600x900 hz: 60 dpi: 106
    gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 1600x900
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast
    gbm: drv: crocus surfaceless: drv: crocus x11: drv: crocus inactive: wayland
  API: OpenGL v: 3.3 vendor: intel mesa v: 23.1.2-1~mx23ahs glx-v: 1.4 es-v: 3.0
    direct-render: yes renderer: Mesa Intel HD Graphics 3000 (SNB GT2) device-ID: 8086:0116
    memory: 1.46 GiB unified: yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Toshiba 6
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Toshiba driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter vendor: Lite-On driver: ath9k
    v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:002b
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Info: services: mld, NetworkManager, nfsd, wpa_supplicant
Drives:
  Local Storage: total: 596.17 GiB used: 83.61 GiB (14.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS547564A9E384 size: 596.17 GiB block-size:
    physical: 4096 B logical: 512 B speed: 3.0 Gb/s tech: HDD rpm: 5400 serial: <filter> fw-rev: A60B
    scheme: MBR
Partition:
  ID-1: / raw-size: 19.92 GiB size: 19.44 GiB (97.59%) used: 12.97 GiB (66.7%) fs: ext4
    dev: /dev/sda6 maj-min: 8:6
  ID-2: /home raw-size: 194.15 GiB size: 190.04 GiB (97.88%) used: 70.64 GiB (37.2%) fs: ext4
    dev: /dev/sda7 maj-min: 8:7
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 12.21 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda5
    maj-min: 8:5
Sensors:
  System Temperatures: cpu: 58.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: 2587 pm: dpkg pkgs: 2581 libs: 1398 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bookworm main non-free
    2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bookworm ahs
Info:
  Memory: total: 6 GiB available: 5.7 GiB used: 1.46 GiB (25.6%)
  Processes: 175 Power: uptime: 30m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 2.25 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 252 target: graphical (5)
    default: graphical tool: systemctl
  Compilers: gcc: 12.2.0 Client: shell wrapper v: 5.2.15-release inxi: 3.3.34
Boot Mode: BIOS (legacy, CSM, MBR)

User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Re: Root size needed for MX 23 - or just old hardware?

#2 Post by Solon »

Hi again!

Here is my Quick Info for my new Computer, currently running MX 21 which I want to migrate to MX 23:

Code: Select all

Snapshot created on: 20240504_0043
System:    Kernel: 6.1.0-2mx-amd64 [6.1.7-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-2mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A715-42G v: V1.08 serial: <filter> 
           Mobo: LN model: Azalea_CAS v: V1.08 serial: <filter> UEFI: Insyde v: 1.08 
           date: 09/15/2021 
Battery:   ID-1: BAT1 charge: 44.1 Wh (90.4%) condition: 48.8/47.8 Wh (102.2%) volts: 12.1 
           min: 11.2 model: LGC AP18C8K type: Li-ion serial: <filter> status: Discharging 
CPU:       Info: 6-Core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP 
           arch: Zen 2 family: 17 (23) model-id: 68 (104) stepping: 1 microcode: 8608103 cache: 
           L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 50305 
           Speed: 1400 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 1: 1400 
           2: 1400 3: 1397 4: 1397 5: 1700 6: 1696 7: 1409 8: 1400 9: 1400 10: 1400 11: 1400 
           12: 1400 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Acer Incorporated ALI 
           driver: nvidia v: 535.183.06 bus-ID: 01:00.0 chip-ID: 10de:1f9d class-ID: 0302 
           Device-2: AMD Lucienne vendor: Acer Incorporated ALI driver: amdgpu v: kernel 
           bus-ID: 05:00.0 chip-ID: 1002:164c class-ID: 0300 
           Device-3: Chicony HD User Facing type: USB driver: uvcvideo bus-ID: 3-3:3 
           chip-ID: 04f2:b72b class-ID: fe01 serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: ati,modesetting,nvidia unloaded: fbdev,nouveau,radeon,vesa alternate: nv 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 144 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: AMD RENOIR (LLVM 14.0.5 DRM 3.49 6.1.0-2mx-amd64) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: AMD Renoir Radeon High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403 
           Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor 
           vendor: Acer Incorporated ALI Raven/Raven2/FireFlight/Renoir Processor driver: N/A 
           alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x 
           bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 
           Device-3: AMD Family 17h/19h HD Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-2mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 2000 bus-ID: 03:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: Lite-On 
           driver: mt7921e v: kernel modules: wl port: 2000 bus-ID: 04:00.0 chip-ID: 14c3:7961 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Lite-On Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 
           chip-ID: 04ca:3802 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 2402 hci-v: 5.2 rev: 1911 
           Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio, telephony 
Drives:    Local Storage: total: 931.51 GiB used: 102.02 GiB (11.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD Blue SN570 1TB 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 234110WD temp: 35.9 C scheme: GPT 
Partition: ID-1: / raw-size: 34.18 GiB size: 33.35 GiB (97.56%) used: 29.64 GiB (88.9%) fs: ext4 
           dev: /dev/nvme0n1p5 maj-min: 259:5 
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 55 MiB (21.5%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-3: /home raw-size: 195.31 GiB size: 191.19 GiB (97.89%) used: 36.96 GiB (19.3%) 
           fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p7 maj-min: 259:7 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: 2572 note: see --pkg apt: 2565 lib: 1405 flatpak: 7 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye main non-free
           2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 264 Uptime: 21m wakeups: 2 Memory: 7.11 GiB used: 1.61 GiB (22.6%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
I assume that the processor will not be a problem (although all of the Nvidia stuff might be?), but will Root be big enough, or do I need to enlarge Root partition before migrating to MX 23?

Thanks!

User avatar
MadMax
Posts: 483
Joined: Wed Aug 04, 2021 3:25 pm

Re: Root size needed for MX 23 - or just old hardware?

#3 Post by MadMax »

System 1: / size ~20 GiB, used ~13 GiB

This is fine tbh. 20 GiB is on the lower end for /, but if you're not using more than let's say 15 GiB there's no reason for concern. This system uses an old HDD, though, which could be replaced with a SATA SSD for much better performance. Especially on laptops SSDs are great, because they are shock-resistant and you don't have to be as careful with the laptop anymore.

System 2: / size ~34 GiB, used ~30 GiB

This one is actually close to full. It shouldn't be the reason for the system running slowly, though, since ext4 is very good at managing highly filled disks and fragmentation shouldn't matter on an nvme SSD. If you plan on migrating to MX 23 I recommend a fresh install and to repartition the disks so / is at least 40 GiB in size, make it 50 if you have the space and you will be fine for a while.
If you want to try the in-place upgrade you will need to make space. 4 GiB is likely not enough to download and unpack all update data. I wouldn't start a full upgrade with less than 10 GiB of free space.

On both systems you can use MX Cleanup to reduce used space. A quick "sudo apt clean" will remove downloaded deb files from updates and reclaim quite a bit of space from my experience. That's the top right option "APT cache" in MX Cleanup.
If it ain't broke, don't fix it.
Main: MX 23 | Second: Mint 22 | HTPC: Linux Lite 7 | VM Machine: Debian 12 | Testrig: Arch/FreeBSD 14 | Work: RHEL 8

User avatar
j2mcgreg
Global Moderator
Posts: 7055
Joined: Tue Oct 23, 2007 12:04 pm

Re: Root size needed for MX 23 - or just old hardware?

#4 Post by j2mcgreg »

@Solon wrote:
So.... before I move my new machine over to MX 23 -- here are my questions:
Is the slow down due to Root being too small for MX 23
Or is it just that my older processor is the source of the problem?
Your second gen i5 might be a factor, but your eleven year old HDD (long past its replacement date] is certainly the main cause of the computers lethargy. If you were to replace that drive with an SSD similar to this:
https://www.canadacomputers.com/en/desk ... g3b0a.html
it would make a world of difference. For instance when i replaced the HDD in my Aspire V5 two years ago the boot to desktop time went from minutes to seconds.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Re: Root size needed for MX 23 - or just old hardware?

#5 Post by Solon »

MadMax wrote: Sat Sep 07, 2024 7:35 am System 1: / size ~20 GiB, used ~13 GiB

This is fine tbh. 20 GiB is on the lower end for /, but if you're not using more than let's say 15 GiB there's no reason for concern. This system uses an old HDD, though, which could be replaced with a SATA SSD for much better performance. Especially on laptops SSDs are great, because they are shock-resistant and you don't have to be as careful with the laptop anymore.

System 2: / size ~34 GiB, used ~30 GiB

This one is actually close to full. It shouldn't be the reason for the system running slowly, though, since ext4 is very good at managing highly filled disks and fragmentation shouldn't matter on an nvme SSD. If you plan on migrating to MX 23 I recommend a fresh install and to repartition the disks so / is at least 40 GiB in size, make it 50 if you have the space and you will be fine for a while.
If you want to try the in-place upgrade you will need to make space. 4 GiB is likely not enough to download and unpack all update data. I wouldn't start a full upgrade with less than 10 GiB of free space.

On both systems you can use MX Cleanup to reduce used space. A quick "sudo apt clean" will remove downloaded deb files from updates and reclaim quite a bit of space from my experience. That's the top right option "APT cache" in MX Cleanup.
Great suggestion! I ran MX Cleanup, and it knocked it down to 20GB. I wonder if it is all of the constant Nvidia stuff that updates regularly? You can see the results below:

Code: Select all

Snapshot created on: 20240504_0043
System:    Kernel: 6.1.0-2mx-amd64 [6.1.7-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-2mx-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A715-42G v: V1.08 serial: <filter> 
           Mobo: LN model: Azalea_CAS v: V1.08 serial: <filter> UEFI: Insyde v: 1.08 
           date: 09/15/2021 
Battery:   ID-1: BAT1 charge: 48.8 Wh (100.0%) condition: 48.8/47.8 Wh (102.2%) volts: 12.7 
           min: 11.2 model: LGC AP18C8K type: Li-ion serial: <filter> status: Full 
CPU:       Info: 6-Core model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP 
           arch: Zen 2 family: 17 (23) model-id: 68 (104) stepping: 1 microcode: 8608103 cache: 
           L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 50307 
           Speed: 1400 MHz min/max: 1400/2100 MHz boost: enabled Core speeds (MHz): 1: 1400 
           2: 1700 3: 1700 4: 1400 5: 1393 6: 1400 7: 1378 8: 1400 9: 1400 10: 1400 11: 2111 
           12: 1400 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Acer Incorporated ALI 
           driver: nvidia v: 535.183.06 bus-ID: 01:00.0 chip-ID: 10de:1f9d class-ID: 0302 
           Device-2: AMD Lucienne vendor: Acer Incorporated ALI driver: amdgpu v: kernel 
           bus-ID: 05:00.0 chip-ID: 1002:164c class-ID: 0300 
           Device-3: Chicony HD User Facing type: USB driver: uvcvideo bus-ID: 3-3:3 
           chip-ID: 04f2:b72b class-ID: fe01 serial: <filter> 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: ati,modesetting,nvidia unloaded: fbdev,nouveau,radeon,vesa alternate: nv 
           display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 144 dpi: 142 size: 344x194mm (13.5x7.6") 
           diag: 395mm (15.5") 
           OpenGL: renderer: AMD RENOIR (LLVM 14.0.5 DRM 3.49 6.1.0-2mx-amd64) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: AMD Renoir Radeon High Definition Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403 
           Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor 
           vendor: Acer Incorporated ALI Raven/Raven2/FireFlight/Renoir Processor driver: N/A 
           alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x 
           bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480 
           Device-3: AMD Family 17h/19h HD Audio vendor: Acer Incorporated ALI 
           driver: snd_hda_intel v: kernel bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-2mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 2000 bus-ID: 03:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: Lite-On 
           driver: mt7921e v: kernel modules: wl port: 2000 bus-ID: 04:00.0 chip-ID: 14c3:7961 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Lite-On Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 
           chip-ID: 04ca:3802 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 2402 hci-v: 5.2 rev: 1911 
           Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio, telephony 
Drives:    Local Storage: total: 931.51 GiB used: 90.35 GiB (9.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD Blue SN570 1TB 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 234110WD temp: 38.9 C scheme: GPT 
Partition: ID-1: / raw-size: 34.18 GiB size: 33.35 GiB (97.56%) used: 19.96 GiB (59.8%) fs: ext4 
           dev: /dev/nvme0n1p5 maj-min: 259:5 
           ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 55 MiB (21.5%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-3: /home raw-size: 195.31 GiB size: 191.19 GiB (97.89%) used: 34.97 GiB (18.3%) 
           fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p7 maj-min: 259:7 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: 2572 note: see --pkg apt: 2565 lib: 1405 flatpak: 7 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye main non-free
           2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 294 Uptime: 1m wakeups: 2 Memory: 7.11 GiB used: 1.28 GiB (18.0%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Both of you suggested me upgrading to an SSD. However, I am blocked from opening this website due to my location (don't have a VPN). Years ago I considered 'cleaning the fan', and the video on getting to that was a horror story. So I just went out on YouTube, and it seems that changing the HDD out, and even adding RAM is right there in the back, not in the guts. So possible!
j2mcgreg wrote: Sat Sep 07, 2024 7:51 am @Solon wrote:
So.... before I move my new machine over to MX 23 -- here are my questions:
Is the slow down due to Root being too small for MX 23
Or is it just that my older processor is the source of the problem?
Your second gen i5 might be a factor, but your eleven year old HDD (long past its replacement date] is certainly the main cause of the computers lethargy. If you were to replace that drive with an SSD similar to this:
https://www.canadacomputers.com/en/desk ... g3b0a.html
it would make a world of difference. For instance when i replaced the HDD in my Aspire V5 two years ago the boot to desktop time went from minutes to seconds.
So, there is a process for "Cloning" a HD, and the Win with its license, tied to the laptop can be moved to a SSD! However, what about the dual boot? I suppose I may just have to go through the dual boot process later, maybe with a live USB and my stored files there?

There are a lot of quite capable computer shops around here.

Thanks guys!
Last edited by Solon on Sat Sep 07, 2024 9:28 am, edited 1 time in total.

User avatar
j2mcgreg
Global Moderator
Posts: 7055
Joined: Tue Oct 23, 2007 12:04 pm

Re: Root size needed for MX 23 - or just old hardware?

#6 Post by j2mcgreg »

@Solon wrote:
I wouldn't mind putting in an SSD, but not being able to watch the video, there are two things that I wonder about.
It's not a video, rather it's a link to show you what an SSD suitable for your Satellite looks like.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Solon
Posts: 70
Joined: Thu Mar 25, 2021 3:33 pm

Re: Root size needed for MX 23 - or just old hardware?  [Solved]

#7 Post by Solon »

j2mcgreg wrote: Sat Sep 07, 2024 9:02 am @Solon wrote:
I wouldn't mind putting in an SSD, but not being able to watch the video, there are two things that I wonder about.
It's not a video, rather it's a link to show you what an SSD suitable for your Satellite looks like.
Thanks!
I was just out on the Internet, and I edited my prior post a bit. Seems it's possible, at least for Win 11, now I need to look into Win 7 cloning, then the Dual Boot issue, since I doubt a Win program can 'clone' a Linux partition?

Well, we're into a different topic now.

Thanks for all your input, and I'll mark this Root Partition issue as solved!

Post Reply

Return to “MX KDE Official Release”