Manjaro KDE much slower after reinstallation since 2023

I’ve bought the laptop (“Acer Swift Go 16”) I’m currently using as my “daily driver” end of August 2023, so 9-10 months ago. When I got it, I’ve installed Manjaro KDE on it and was quite happy with it (was already using Manjaro on other Laptops before)

About a month ago, as it sometimes happens with Arch-based distros, my Manjaro refused to boot after installing some updates the day before. I’ve had heard of NixOS and had been wanting to try it for about 2 months already (after seeing the no-boilerplate youtube video about it) and figured this was my sign to do so. Sadly (or luckily for Manjaro) this adventure didn’t go well, and a week later, I was back on Manjaro.

Now the strange thing is, that the same aweful performance I’ve seen on NixOS now also often shows itself with Manjaro. With my previous installation, I never had such performance problems, but know they seem to be everywhere. Kate still works fine almost always (typing this in Kate), but Firefox, Chromium, VS-Code, … all are really horrible to use, especially when I have an external monitor connected. Rebooting after the monitor is connected sometimes helps a bit, but doesn’t make it really okey. Also restarting kwin or plasmashell (with --replace parameter) sometimes makes it better. But also not consistent.

I wonder if this is some regression in the software stack, or some configuration that had a different default a year ago that better suited my hardware - or maybe even some hardware defect?

I have no idea how to find or even search for the cause of this performance problem, and am hoping someone here on the forum can give me some pointers.

$ inxi -F
System:
  Host: acer-swiftgo16manjaro Kernel: 6.6.32-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.0.5 Distro: Manjaro Linux
Machine:
  Type: Laptop System: Acer product: Swift SFG16-71 v: V1.04
    serial: <superuser required>
  Mobo: RPL model: Lionfish_RTH v: V1.04 serial: <superuser required>
    UEFI: Insyde v: 1.04 date: 04/27/2023
Battery:
  ID-1: BAT1 charge: 54.7 Wh (100.0%) condition: 54.7/65.2 Wh (84.0%)
CPU:
  Info: 14-core (6-mt/8-st) model: 13th Gen Intel Core i7-13700H bits: 64
    type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 400 min/max: 400/4800:5000:3700 cores: 1: 400 2: 400
    3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Chicony ACER QHD User Facing driver: hid-generic,usbhid,uvcvideo
    type: USB
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: vesa gpu: i915 resolution:
    1: 3440x1440 2: 1488x930
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.0.9-manjaro1.1
    renderer: Mesa Intel Graphics (RPL-P)
  API: Vulkan v: 1.3.279 drivers: intel surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS driver: sof-audio-pci-intel-tgl
  Device-2: Realtek USB Audio driver: snd-usb-audio type: USB
  API: ALSA v: k6.6.32-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi
  IF: wlp0s20f3 state: up mac: 74:04:f1:dd:3b:fa
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
  IF: enp0s13f0u3u4 state: up speed: 1000 Mbps duplex: full
    mac: c0:3e:ba:2e:5c:95
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb type: USB
  Report: rfkill ID: hci0 state: up address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
    driver: vmd
Drives:
  Local Storage: total: 953.87 GiB used: 271.41 GiB (28.5%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD PC SN740
    SDDQNQD-1T00-1014 size: 953.87 GiB
Partition:
  ID-1: / size: 835.41 GiB used: 271.29 GiB (32.5%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot/efi size: 256 MiB used: 120.5 MiB (47.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 835.41 GiB used: 271.29 GiB (32.5%) fs: btrfs
    dev: /dev/dm-0
  ID-4: /var/log size: 835.41 GiB used: 271.29 GiB (32.5%) fs: btrfs
    dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: file size: 39.06 GiB used: 75.3 MiB (0.2%)
    file: /swap/swapfile
Sensors:
  Src: /sys System Temperatures: cpu: 42.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.04 GiB
    used: 10.07 GiB (32.4%)
  Processes: 452 Uptime: 1d 9h 3m Shell: Zsh inxi: 3.3.34

Thank you for reading,
kind regards,
Thomas

Give output of mhwd -l and mhwd -li

Maybe just try to logout, and log back into a X11 session instead of Wayland, for a test.

Also maybe your CPU stays low frequency all the time, I see all cores at 400. Give output of cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

1 Like

Thank you for the response @omano! I’ve tried X11 which is worse in some things and better in others. Overall it feels worse to me.

$ mhwd -l
> 0000:00:02.0 (0300:8086:a7a0) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI
$ mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


Warning: No installed USB configs!
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave

That powersave seems really strange, I’ve selected “performance” in the KDE power widget!

UPDATE: I found CPU frequency scaling - ArchWiki and installed and started i7z and can observe, all my cpu cores stick to a frequency between 398 & 400 MHz… No wonder everything feels so slugish…
I ran sudo cpupower frequency-set -g performance and now cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor gives 20 lines of “performance” instead of “powersave” but the cpu frequency is still fixed at 400MHz…

UPDATE2: I’ve tried around and so far was unable to force my cpu to do more than 400MHz. I’ve found this which sounds like a similar problem: CPU frequency always at 200Mhz [Solved] / Kernel & Hardware / Arch Linux Forums

So luckily I still have the MS Windows my laptop came with on a shrunk partition in front, I’ll try booting that and will check if there’s some way to install a bios / firmware update as suggested on that arch forum.

UPDATE3: those seem to talk about similar issues:

You have all three installed? that’s an issue on its own I guess.
You probably only want video-linux

No, video-modesetting is also recommended. video-vesa should be removed. :wink:

Does it have a purpose for his system if he only has one video chip and also video-linux is installed?

Yes, it makes sure that the Intel or AMD driver in the kernel uses KMS. It actually replaces the older (and deprecated) xf86-video-intel and xf86-video-amdgpu drivers.

2 Likes

Thanks for all the replies!

Sadly my plan to look for firmware / bios updates with windows is out - I only thought my windows still was working, it’s not. It just bootloops with some recovery crap which apparently doesn’t succeed…

How do I remove video-vesa from my system? It doesn’t seem to be a package?

$ sudo pacman -R video-vesa
error: target not found: video-vesa

UPDATE: never mind, found how to remove it in the “Manjaro Settings Manager”.

Probably you can boot some Windows LIVE ISO like Hiren BootCD, to proceed to the BIOS update if it requires to do it from Windows.

//EDIT: May require a Windows 11 based LIVE ISO as it seems your computer is officially supported only by Windows 11. The BIOS update executable may be compatible with Windows 10 though but I can’t guarantee.

2 Likes

I downloaded that Hiren BootCD iso and put it on my Ventoy USB-Stick, and tried to boot it in both “normal” and “wimboot” or mode, both time it ended up rebooting my laptop in just a few minutes without ever displaying anything that looked like windows…

Very similar to the behavior the windows my laptop came with currently displays actually - main difference beeing that my locally installed windows seems to store this boot error somewhere and on every second boot displays some kind of recovery menu. I’ve tried a few of the recovery options, none worked so far.

How can I determine if this is a hardware error I need to contact the vendor / maker for or just some software / firmware problem I could fix myself?

I’ve now let the windows recovery tool delete my windows user profile while reinstalling windows (but not yet let him delete the whole disk which I strongly suspect would also reformat it and deleting this Manjaro installation). But sadly it still wasn’t able to boot into Windows afterwards.

But before letting Windows deleting my Windows user profile, I found “manjaro-kde-22.1.3-230529-linux61.iso” which I promptly copied to my Ventoy USB disk and tried booting it. Funny enough, this version was able to get the CPU to run with more reasonable speeds after switching to the “performance” profiler:

$ sudo cpupower frequency-set -g performance
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
400091
400109
2900000
2900000
400229
2900000
399997
2900000
2900000
400046
400037
2900000
2900000
400004
2900000
2900000
2900000
2900000
2900000
2900000

Doing the same with my current Manjaro installation gives this sad result:

$ sudo cpupower frequency-set -g performance
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
400115
400000
400000
400000
400000
400054
400000
400000
400000
400299
400028
400000
400010
400000
400000
400002
400000
399997
400000
400000

I’m gonna try the same thing inside this live system next: “manjaro-kde-24.0.1-240529-linux69.iso”

I’d suggest installing Linux61 on the current system, to see if it actually is the kernel which is the issue. :slight_smile: (Assuming you haven’t already tried that).

My current manjaro installation is running:

$ uname -a
Linux acer-swiftgo16manjaro 6.6.32-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:41:25 UTC 2024 x86_64 GNU/Linux

I remember I also tried 6.1 when I stepped back from 6.9 to 6.6, but back then I didn’t know about having this CPU scaling issue and since both the 6.6 and 6.1 LTS kernels performed about the same I’ve stuck to the latest LTS kernel. (I also tried 5.15 but something was wrong with it, I can’t remember if it was missing network drivers or didn’t boot or something)

I’ll try 6.1 right away.

1 Like

I should mention that I’ve had issues with recent 66 kernels: specifically 6.6.26-1 and anything else that may have come since (before 6.6.32 which switched to this morning, seems to work at this end now, though),

I’ve now tried both the “manjaro-kde-24.0.1-240529-linux69.iso” live system, and my installed Manjaro with 6.1 kernel. Both fail to scale the CPU to anything above the lowest possible frequency = 400MHz.

Only success so far was with the “manjaro-kde-22.1.3-230529-linux61.iso” live system. Though something fishy is going on with none of the Microsoft Windows media suceeding to boot / install.

The kernel log (dmesg) may yield some insights.

If think you mean the xf86-video-modesetting driver included with the xorg-server package. Intel graphics - ArchWiki

1 Like

That’s the one referenced as video-modesetting in the Manjaro Settings Manager.

How come it’s included with xorg-server but we can still install it in the Manjaro Settings Manager?

Your machine doesn’t seem to be set up as a RAID configuration, and yet you have a RAID contoller active in BIOS. You might check your BIOS configuration and ensure that AHCI mode is selected, and not RAID.

The Hiren’s BootCD PE isn’t meant to look like Windows – it’s a bootable ISO based on Windows – it has all the commandline tools usually found in a Windows Preinstallation (PE) environment; the same as those in Windows itself.

Did you check downloaded ISO’s for consistency? Is it possible some of these issues might have resulted from a damaged ISO? You can download a fresh ISO and verify the hashes, to be sure.


Do you have XMP settings in your BIOS?

I don’t know. When I installed this system now over five years ago, the default was xf86-video-intel, which blocks the use of video-modesetting, and was only ever needed for very old Intel graphics. All modern Intel graphics use the X.Org default video-modesetting.

There is no separate xf86-video-modesetting package in the repos, by the way.