MX Linux Forum

Posted: **Sun Apr 20, 2025 8:37 am**

OK.. it is in the forum rules, if you don't post them we can't help you.

Posted: **Sun Apr 20, 2025 8:54 am**

Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.

i dont think you could either way, so dont bother. maybe someone else will :-)

Posted: **Sun Apr 20, 2025 9:19 am**

samegold wrote: Sun Apr 20, 2025 8:54 am
Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.
i dont think you could either way, so dont bother. maybe someone else will :-)

@samegold No-ones going to help until you cooperate with the request. We aren't going to play 20 questions, when we can quickly look at the output of your QSI.

Boot up the live ISO , like you were told to do, and post the QSI from there. It will give us a starting point.

Posted: **Sun Apr 20, 2025 1:39 pm**

siamhie wrote: Sun Apr 20, 2025 9:19 am
samegold wrote: Sun Apr 20, 2025 8:54 am
Eadwine Rose wrote: Sun Apr 20, 2025 8:37 am OK.. it is in the forum rules, if you don't post them we can't help you.
i dont think you could either way, so dont bother. maybe someone else will :-)
@samegold No-ones going to help until you cooperate with the request. We aren't going to play 20 questions, when we can quickly look at the output of your QSI.

soo, are you going to delete all potential answers on the topic or is that just a figure of speech and/or your personal opinion?
please let me know, just in case, so i dont have to waste our time here.
because - no offense - my opinion is, if someone is going to ask 20 questions about my HARDWARE with a problem clearly related to SOFTWARE, then he has no idea what hes talking about and cant help anyone anyway.
i also asked 3 times already if the QSI can read software infos from external SSD/system or just from its own partition - still no answer - instead orders.
communication could be better on this forum IMO. heres a screenshot in case somebody is interested in the actual problem:

https://ibb.co/wN1x1hXX

INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...done.
Starting Init script for Simple Desktop Display Manager: sddmerror: unexpectedly disconnected

Starting Common Unix Printing System: cupsd.
Starting S.M.A.R.T. daemon: smartd.
Starting virtual private network daemon:
Stopping VMware services:
VMware Authentication Daemon done
Virtual machine monitor done
Starting VMware services:
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet failed
VMware Authentication Daemon done
startpar: service(s) returned failure: tlp system start ... **failed!**

Welcome to MX Linux! Powered by Debian.
mx login: root
Password:
Last login: Sun Apr 20 20:08:23 CEST 2025 on tty1
root@mx:~#

Posted: **Sun Apr 20, 2025 3:33 pm**

samegold wrote: Sun Apr 20, 2025 1:39 pm please let me know, just in case, so i dont have to waste our time here.
because - no offense - my opinion is, if someone is going to ask 20 questions about my HARDWARE with a problem clearly related to SOFTWARE, then he has no idea what hes talking about

For someone who's been lurking on the forum for a few weeks, it sure seems like you haven't been paying attention.

Posted: **Sun Apr 20, 2025 4:02 pm**

samegold wrote: Sun Apr 20, 2025 1:39 pm i also asked 3 times already if the QSI can read software infos from external SSD/system or just from its own partition - still no answer - instead orders.
communication could be better on this forum IMO.

Communication has been quite clear up to this point.

if the QSI can read software infos from external SSD/system

Yes. Here is my QSI showing my USB attached NVMe drive that I store data on. It is listed as SDC under Drives:

Code: Select all

Snapshot created on: 20250411_1148
System:
  Kernel: 6.12.23-x64v3-xanmod1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.23-x64v3-xanmod1 root=UUID=<filter> ro
    init=/lib/systemd/systemd
  Desktop: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.6_fluxbox_x64 Libretto
    September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: A.F0 date: 10/11/2023
CPU:
  Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
    microcode: 0xA20120E
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
    KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 906 high: 3400 min/max: 550/5084 boost: disabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 550 2: 550 3: 550 4: 550 5: 550 6: 550
    7: 550 8: 550 9: 550 10: 550 11: 550 12: 3400 13: 550 14: 3397 15: 550 16: 550 17: 550 18: 550
    19: 550 20: 550 21: 550 22: 550 23: 550 24: 550 25: 550 26: 3397 27: 550 28: 550 29: 3398
    30: 550 31: 550 32: 550 bogomips: 217598
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3 empty: DP-1, DP-2, HDMI-A-1, Writeback-1
    bus-ID: 0b:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: amdgpu unloaded: fbdev dri: radeonsi
    gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
  Monitor-1: DP-3 mapped: DisplayPort-2 model: HP X27q serial: <filter> built: 2021
    res: 2560x1440 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.61
    6.12.23-x64v3-xanmod1) direct-render: Yes
Audio:
  Device-1: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series BlasterX AE-5 Plus]
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 1102:0012 class-ID: 0403
  Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28 class-ID: 0403
  API: ALSA v: k6.12.23-x64v3-xanmod1 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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:
  Message: No PCI device data found.
  Device-1: NetGear Wireless_Device type: USB driver: mt7921u bus-ID: 4-1:2 chip-ID: 0846:9060
    class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 8.41 TiB used: 1.31 TiB (15.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital model: WDS500G1X0E-00AFY0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 613000WD temp: 36.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
    rev: 0001 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Samsung model: SSD 970 EVO size: 232.89 GiB
    block-size: physical: 4096 B logical: 512 B type: SSD serial: <filter> rev: 5102 scheme: MBR
Partition:
  ID-1: / raw-size: 465 GiB size: 456.63 GiB (98.20%) used: 11.89 GiB (2.6%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 779 MiB size: 777.5 MiB (99.80%) used: 28 MiB (3.6%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: partition size: 64 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
    maj-min: 8:18
Sensors:
  System Temperatures: cpu: 30.9 C mobo: N/A gpu: amdgpu temp: 32.0 C mem: 30.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 710
Repos:
  Packages: pm: dpkg pkgs: 2338 libs: 1254 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  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 http://la.mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/xanmod-release.list
    1: deb [signed-by=/etc/apt/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 506 Uptime: 22h 55m wakeups: 0 Memory: 31.26 GiB used: 2.76 GiB (8.8%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Mon Apr 21, 2025 3:52 am**

if i access the home folder of the said installation from another linux PC i get this. its the locked home folder of the described system with the new root user that doesnt start KDE. it doesnt show the size of the folder.
i have the root passwort ofcourse, how can i unlock the home folder permanently, so i can access the files and maybe fix the bootup in the process? i would need to give back permissions to the first user, which is/was configured in KDE autologin and that would fix the KDE starting problem maybe? so basically disable the root account and go back how it was before.
i am using dolphin file manager.

https://i.postimg.cc/9FfgbtBJ/screen-HOMEfolder.png

Posted: **Mon Apr 21, 2025 4:42 am**

Image changed to link, you would have known this if you had read the forum rules.

Posted: **Mon Apr 21, 2025 10:55 am**

samegold wrote: Mon Apr 21, 2025 3:52 am if i access the home folder of the said installation from another linux PC i get this.

Post your QSI from the live ISO please. Like I said in post #13, We aren't going to play 20 questions.

Posted: **Mon Apr 21, 2025 7:03 pm**

if the QSI can read software infos from external SSD/system

"Yes. Here is my QSI showing my USB attached NVMe drive that I store data on. It is listed as SDC under Drives:"

that is not what i asked. it shows HARDWARE infos like vendor name, size, etc. which you can get probably in any OS by right-clicking on the hardware "properties".
SOFTWARE infos are for example: which OS version is installed on the SSD,which kernel, if any? and that is what matters.

thats why i asked:
"if the live session is running from an usb stick, how should i read out the software that is installed on the SSD that doesnt boot? wouldnt the live-usb show the software versions of the live-system?"

so im trying to explain this for the fifth time now and i dont know how to be any clearer, thanks for your reply though.

MX Linux Forum

startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account

Re: startpar services returned failure: tlp sysstat failed. KDE doesnt start after enabling root account