Thank you.j2mcgreg wrote: Mon Mar 06, 2023 6:58 am @NetWORKER wrote
https://www.2daygeek.com/sysvinit-vs-sy ... and-usage/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
MX-Linux KDE stuck at boot with psmouse error when using systemd boot option [Solved]
Re: MX-Linux KDE stuck at boot with psmouse error when using systemd boot option
Re: MX-Linux KDE stuck at boot with psmouse error when using systemd boot option

Thank you, too for the feedback.
I know, this is not the answer you expected but at least from original sources (and for now)
Code: Select all
pcie_aspm= [PCIE] Forcibly enable or disable PCIe Active State Power Management.
off Disable ASPM.
Code: Select all
idle= [X86]
Format: idle=poll, idle=halt, idle=nomwait
Poll forces a polling idle loop that can slightly
improve the performance of waking up a idle CPU, but
will use a lot of power and make the system run hot.
Not recommended.
idle=halt: Halt is forced to be used for CPU idle.
In such case C2/C3 won't be used again.
idle=nomwait: Disable mwait for CPU C-states
default_ps_max_latency_us: default power state max latency (μs)
https://lore.kernel.org/lkml/d9c55ed1b9b950fe314257b2ec6f4339617d075c.1474049701.git.luto@kernel.org/ wrote:
APST (Autonomous Power State Transition) lets us program a table of power state transitions that the controller will perform automatically. We configure it with a simple heuristic: we are willing to spend at most 2% of the time transitioning between power states. Therefore, when running in any given state, we will enter the next lower-power non-operational state after waiting 100 * (enlat + exlat) microseconds, as long as that state's total latency is under the requested maximum latency.
We will not autonomously enter any non-operational state for which the total latency exceeds ps_max_latency_us. Users can set ps_max_latency_us to zero to turn off APST.
Re: MX-Linux KDE stuck at boot with psmouse error when using systemd boot option
Actually it may also be ok without the idle=nomwait
If you like you can try these temporarily in 2-3 boots:
Press E on grub, just delete that part ( idle=nomwait ) press F10 to go on boot.
Next time (press E again...) you can try smaller numbers instead of 5500 , change it to 1000 press F10 , ... next time try 200 (... can try even 0 to completely disable APST )
If anything's better you can change them permanently in "MX Boot Options".
If you like you can try these temporarily in 2-3 boots:
Press E on grub, just delete that part ( idle=nomwait ) press F10 to go on boot.
Next time (press E again...) you can try smaller numbers instead of 5500 , change it to 1000 press F10 , ... next time try 200 (... can try even 0 to completely disable APST )
If anything's better you can change them permanently in "MX Boot Options".
Re: MX-Linux KDE stuck at boot with psmouse error when using systemd boot option
In the meantime:
You do not have the required permissions to view the files attached to this post.
Re: MX-Linux KDE stuck at boot with psmouse error when using systemd boot option
thanks for the explanations. i will try this method and see which one works best.Huckleberry Finn wrote: Fri Mar 10, 2023 5:01 pm Actually it may also be ok without the idle=nomwait
If you like you can try these temporarily in 2-3 boots:
Press E on grub, just delete that part ( idle=nomwait ) press F10 to go on boot.
Next time (press E again...) you can try smaller numbers instead of 5500 , change it to 1000 press F10 , ... next time try 200 (... can try even 0 to completely disable APST )
If anything's better you can change them permanently in "MX Boot Options".