Page 14 of 15
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Sun Aug 28, 2022 7:03 pm
by Huckleberry Finn
Ok. These ones are just for those slow boot and slow working issues.
So, if you don't feel lazy, (rather than trying to find what causes that, cause you tried many things)
You can install for the last time, your favorite one and use only these parameters and do nothing else. (Just boot with these and install)... Then let us know if everything's fine.
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 1:44 am
by sisqonrw
what do you mean? i do not understand.
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 5:00 am
by itsme
I installed MX-21.1 and it installed just fine.
Confused.
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 7:43 am
by Huckleberry Finn
sisqonrw wrote: Mon Aug 29, 2022 1:44 am
what do you mean? i do not understand.
I mean: Since the resolution (hence the drivers) is ok on live session and since we know that these parameters solve the slow boot & slow working issues:
Just boot with live usb using these parameters (only these other than
quiet splash splasht and nothing else: no
failsafe and particularly no
nomodeset ) , then install.
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 7:44 am
by Huckleberry Finn
@itsme this one is just a specific problem with this brand and model(s), hence such parameters ...
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 8:15 am
by Huckleberry Finn
@sisqonrw look: With your MX AHS (with 5.16 kernel)
it was ok:
Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: ASUSTeK
driver: i915 v: kernel
bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
Device-2: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:3
chip-ID: 13d3:5a01 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.13 compositor: xfwm4 v: 4.16.1 driver:
loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0")
s-diag: 414mm (16.3")
Monitor-1: eDP-1 res:
1366x768 hz: 60 dpi: 101 size: 344x193mm (13.5x7.6")
diag: 394mm (15.5")
OpenGL: renderer: Mesa
Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.2.5
direct render: Yes
So, you can boot with AHS with these if you like, then install:
Code: Select all
quiet nosplash lang=de_DE pci=nommconf,nomsi,noaer pcie_aspm=off
Or simply try:
Code: Select all
quiet nosplash lang=de_DE pcie_aspm=off
Re: installed MX 2.1 MX-21.1_x64 so slow [Solved]
Posted: Mon Aug 29, 2022 1:15 pm
by sisqonrw
its working with ahs 64 bit. it is fast with the parameters. see attatchment.
open, using and installing apps ist fast. and it is a high resolution.
only when i am using the installed firefox the system froze. i have deinstall firefox and install chrome. no frozing!
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 1:53 pm
by Huckleberry Finn
So glad to hear that. Also special thanks to
@j2mcgreg for reminding those specific (problematic) models :)
... You can also try other browsers (maybe Slimjet) if you like.. and also on Firefox you can try what happens if you disable "hardware acceleration" in its settings.
If you feel it's solved, you can (and please) mark the thread like this:
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 1:56 pm
by sisqonrw
Huckleberry Finn wrote: Mon Aug 29, 2022 1:53 pm
So glad to hear that. Also special thanks to @j2mcgreg for reminding those specific (problematic) models :)
... You can also try other browsers (maybe Slimjet) if you like.. and also on Firefox you can try what happens if you disable "hardware acceleration" in its settings.
If you feel it's solved, you can (and please) mark the thread like this:
can you send me an screenshot where can i do this with the hardware acceleration
Re: installed MX 2.1 MX-21.1_x64 so slow
Posted: Mon Aug 29, 2022 1:58 pm
by Huckleberry Finn
Just in the settings (preferences) of the browser itself (Firefox in this case).. just open its settings and type that to search, you'll see.
(It may also be an issue just due to this version of Firefox, nothing to worry about)
In the meantime, it's really so nice to see this as "solved" :D