MX-Linux KDE stuck at boot with psmouse error when using systemd boot option [Solved]

[NetWORKER]

i dont know why but mx linux gets stuck on boot with "psmouse serio1 synaptics unable to query device -5" when i use systemd to boot.

couldnt find a fix on google or this forum. well there was one saying to disable psmouse module but it didnt work. is there any way to fix this issue? i was also getting dell keyboard backlihgt error but i was able to fix that.

i m on Dell Inspiron 15-3567. i have tried reinstalling mx and when i run it with systemd it always gets stuck there

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 
           root=UUID=<filter> ro text splash init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Inspiron 15-3567 v: N/A serial: <filter> Chassis: 
           type: 9 serial: <filter> 
           Mobo: Dell model: 0D53F5 v: A00 serial: <filter> UEFI-[Legacy]: Dell v: 2.19.0 
           date: 03/22/2022 
Battery:   ID-1: BAT0 charge: 22.8 Wh (100.0%) condition: 22.8/41.4 Wh (55.0%) volts: 16.1 
           min: 14.8 model: LGC-LGC2.80 DELL 991XP76 type: Li-poly serial: <filter> status: Full 
CPU:       Info: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake 
           note: check family: 6 model-id: 8E (142) stepping: 9 microcode: F0 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599 
           Speed: 900 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 899 2: 900 3: 900 4: 900 
           Vulnerabilities: 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 mitigation: Clear CPU buffers; SMT vulnerable 
           Type: retbleed mitigation: IBRS 
           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: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:5916 class-ID: 0300 
           Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] 
           vendor: Dell driver: radeon v: kernel alternate: amdgpu bus-ID: 01:00.0 
           chip-ID: 1002:6660 class-ID: 0380 
           Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-5:3 
           chip-ID: 0c45:6a05 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: 
           loaded: ati,modesetting,radeon unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 506x285mm (19.9x11.2") 
           s-diag: 581mm (22.9") 
           Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell 
           driver: ath10k_pci v: kernel modules: wl port: e000 bus-ID: 02:00.0 chip-ID: 168c:0042 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8136 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: Lite-On Dell Wireless Device type: USB driver: hid-generic,usbhid 
           bus-ID: 1-3:2 chip-ID: 04ca:00ac class-ID: 0301 
Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-8:5 
           chip-ID: 0cf3:e009 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 25a hci-v: 4.2 
           Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 1.13 TiB used: 7.84 GiB (0.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: B1D1 scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 
           serial: <filter> rev: SDM2 scheme: MBR 
Partition: ID-1: / raw-size: 58.6 GiB size: 57.38 GiB (97.92%) used: 7.46 GiB (13.0%) fs: ext4 
           dev: /dev/sda2 maj-min: 8:2 
           ID-2: /home raw-size: 30.27 GiB size: 29.63 GiB (97.87%) used: 394.8 MiB (1.3%) 
           fs: ext4 dev: /dev/sda5 maj-min: 8:5 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb3 
           maj-min: 8:19 
Sensors:   System Temperatures: cpu: 55.0 C mobo: 55.0 C gpu: radeon temp: 49.0 C 
           Fan Speeds (RPM): cpu: 2542 
Repos:     Packages: note: see --pkg apt: 2347 lib: 1312 flatpak: 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 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/mx.list 
           1: deb http://mirrors.piconets.webwerks.in/mx-mirror/packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.piconets.webwerks.in/mx-mirror/packages/mx/repo/ bullseye ahs
Info:      Processes: 212 Uptime: 25m wakeups: 1 Memory: 3.61 GiB used: 2.3 GiB (63.7%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A alt: 10 
           Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

[j2mcgreg]

Why are you running with SystemD? Do you have specific software packages that require it? I'd like to know if the same error appears with the default SysVinit? It might indicate a hardware problem instead.

[NetWORKER]

Why are you running with SystemD? Do you have specific software packages that require it? I'd like to know if the same error appears with the default SysVinit? It might indicate a hardware problem instead.

it does appear with sysvinit but it doesnt get stuck with it. only in systemd it gets stuck there. is there a way to avoid this issue and boot properly ?

[j2mcgreg]

I did a search for that error and it appears that it is a touchpad problem:

https://www.google.com/search?q=psmouse ... e&ie=UTF-8

You should probably turn off the touchpad on your laptop (if you can), or disable it in MX, and use a mouse instead. The reports in the above search indicate that a mouse should work fine.

edited to add that going forward with MX, you will likely have to use SysVinit in lieu of SystemD, if disabling the touch pad doesn't eliminate the error.

[Huckleberry Finn]

Menu => "MX Boot Options" : Add into "Kernel Parameters" area (with a space before it)

Code: Select all

pcie_aspm=off

Apply, reboot.

[NetWORKER]

I did a search for that error and it appears that it is a touchpad problem:

https://www.google.com/search?q=psmouse ... e&ie=UTF-8

You should probably turn off the touchpad on your laptop (if you can), or disable it in MX, and use a mouse instead. The reports in the above search indicate that a mouse should work fine.

edited to add that going forward with MX, you will likely have to use SysVinit in lieu of SystemD, if disabling the touch pad doesn't eliminate the error.

i disabled the touch pad with "xinput set-prop 15 "Device Enabled" 0" where 15 was my touch pad id. but still same.

can u please give me a guide to learn sysVinit commands like how to check a service is running, enable service to run at startup etc? online i get systemctl commands to do this, so i don't know how to use there equivalent commands in sysVinit

[NetWORKER]

Menu => "MX Boot Options" : Add into "Kernel Parameters" area (with a space before it)

Code: Select all

pcie_aspm=off

Apply, reboot.

didn't work. still same issue.

[j2mcgreg]

@NetWORKER wrote

can u please give me a guide to learn sysVinit commands like how to check a service is running, enable service to run at startup etc? online i get systemctl commands to do this, so i don't know how to use there equivalent commands in sysVinit

https://www.2daygeek.com/sysvinit-vs-sy ... and-usage/

[Huckleberry Finn]

Code: Select all

idle=nomwait nvme_core.default_ps_max_latency_us=5500

[NetWORKER]

Code: Select all

idle=nomwait nvme_core.default_ps_max_latency_us=5500

thanks a lot. it seems to be working. i restarted laptop 10 times and did shutdown + start 4 times. it boots up just fine. although its a bit slow at booting now. but that's ok.

will u please explain to me what this & previous kernal parameters exactly do? just to increase my knowledge. thank you.