My problem is it is so laggy I have not installed any software that it is very consuming. I am using vscodium and librewolf and terminator and everything is lagging.
I was on fedora 43 before xfce everything is perfect.
So now on my 44 KDE I have switched from i915 to xe driver as explained here . I still have laggy issues and sometime the time is not correct so I reboot and the time is correct again but still laggy.
I have installed XFCE on top of KDE using dnf as shown here but still in xfce sometimes laggy.
I suspect some KDE packages or Wayland or both that keeps lagging my system.
Post the output from inxi -ezxx, which you’ll need to install first.
Post the output as pre-formatted text, rather than a screenshot of text as you have done above. No-one can quote, copy or search screenshots and screeenreaders can’t announce the content.
Why did you install the KDE edition if you’re intending to use xfce? Why not just install the xfce spin from Fedora Xfce | The Fedora Project?
I am new and I do make mistakes by putting screenshot.
I am not english native speaker and maybe I was not clear. My intention is to use KDE I did not said I installed XFCE on top of KDE because I want XFCE I will be dump to do such a thing. I installed XFCE on top of KDE becasue KDE is unsusable I cannot use it normally too much lagging, the mouse is not smooth, switching virtual desktop is freezing, the screen is freezing, the clock is not working sometimes and my time zone is correct after a reboot it will work. and then after sometime it will repeat.
When you’re experiencing the jerky mouse, slow desktop, frozen clock, if you can open up a terminal and take a look at top to ensure that nothing is hammering the CPU that would be useful.
I suspect you’ll find that it’s barely doing anything at all, and I’m guessing that the freezing likely down to Xe driver issues. I assume you switched to Xe because you already had issues with i915?
Can you post the output from sudo dmesg | grep -Ei "xe|gpu|hang|drm|reset"? Some of it will be useless output like finding “hang” inside “change” but I’m looking specifically for Xe driver crashes/lockups/resets/ etc.
I suspect you’ll find that it’s barely doing anything at all, and I’m guessing that the freezing likely down to Xe driver issues. I assume you switched to Xe because you already had issues with i915?
Yes exactly, I had issues with i915 so I switched to Xe.
I had the application system monitoring of KDE and it looked not super charged. I find out that when switching between virtual desktops I have a little CPU utilisation but not very high.
here below is the output of the command:
[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-7.1.5-200.fc44.x86_64 root=UUID=9f162a0e-0edd-4c9b-92ec-6acb8e74ec41 ro rootflags=subvol=root rd.luks.uuid=luks-cfe2e6c2-9171-4c37-9f6c-61dd1ddbd98f rhgb quiet i915.force_probe=!7d41 xe.force_probe=7d41
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000015] MTRR map: 8 entries (3 fixed + 5 variable; max 23), built from 10 variable MTRRs
[ 0.030299] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-7.1.5-200.fc44.x86_64 root=UUID=9f162a0e-0edd-4c9b-92ec-6acb8e74ec41 ro rootflags=subvol=root rd.luks.uuid=luks-cfe2e6c2-9171-4c37-9f6c-61dd1ddbd98f rhgb quiet i915.force_probe=!7d41 xe.force_probe=7d41
[ 0.083328] ... fixed-purpose counters: 4
[ 0.083328] ... fixed-purpose bitmap: 000000000000000f
[ 0.007180] ... fixed-purpose counters: 3
[ 0.007180] ... fixed-purpose bitmap: 0000000000000007
[ 0.464977] pci 0000:00:1f.4: BAR 4 [io 0xefa0-0xefbf]
[ 0.494707] acpi PNP0C02:05: Reserved [mem 0xe0000000-0xe0d0ffff]
[ 0.494709] acpi PNP0C02:05: Reserved [mem 0xe0d60000-0xefffffff]
[ 0.739926] ACPI: bus type drm_connector registered
[ 0.773299] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[ 0.773317] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[ 0.775801] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 0.869588] evm: security.SMACK64EXEC (disabled)
[ 1.642525] intel_vpu 0000:00:0b.0: [drm] Firmware: intel/vpu/vpu_37xx_v1.bin, version: 20260505*MTL_CLIENT_SILICON-NVR+NN-deployment*3b1e1e826d34b0aeea5cc6d75b017eb4cbf5b735*3b1e1e826d34b0aeea5cc6d75b017eb4cbf5b735*3b1e1e826d3
[ 1.642534] intel_vpu 0000:00:0b.0: [drm] Scheduler mode: HW
[ 1.799061] [drm] Initialized intel_vpu 1.0.0 for 0000:00:0b.0 on minor 0
[ 2.932855] xe 0000:00:02.0: vgaarb: deactivate vga console
[ 2.933122] xe 0000:00:02.0: [drm] Support for SR-IOV is not available
[ 2.933318] xe 0000:00:02.0: [drm] Found meteorlake/u (device ID 7d41) integrated display version 14.00 stepping D0
[ 2.957924] xe 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.23)
[ 2.968847] xe 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io:owns=io+mem
[ 3.026522] xe 0000:00:02.0: [drm] Tile0: GT0: Using GuC firmware from i915/mtl_guc_70.bin version 70.53.0
[ 3.545323] xe 0000:00:02.0: [drm] Tile0: GT1: Using GuC firmware from i915/mtl_guc_70.bin version 70.53.0
[ 3.559666] xe 0000:00:02.0: [drm] Tile0: GT1: Using HuC firmware from i915/mtl_huc_gsc.bin version 8.5.4
[ 3.588528] xe 0000:00:02.0: [drm] Tile0: GT1: Using GSC firmware from i915/mtl_gsc_1.bin version 102.1.15.1926
[ 3.717217] xe 0000:00:02.0: [drm] Tile0: GT1: vcs1 fused off
[ 3.717228] xe 0000:00:02.0: [drm] Tile0: GT1: vcs3 fused off
[ 3.717231] xe 0000:00:02.0: [drm] Tile0: GT1: vcs4 fused off
[ 3.717232] xe 0000:00:02.0: [drm] Tile0: GT1: vcs5 fused off
[ 3.717234] xe 0000:00:02.0: [drm] Tile0: GT1: vcs6 fused off
[ 3.717235] xe 0000:00:02.0: [drm] Tile0: GT1: vcs7 fused off
[ 3.717237] xe 0000:00:02.0: [drm] Tile0: GT1: vecs1 fused off
[ 3.717239] xe 0000:00:02.0: [drm] Tile0: GT1: vecs2 fused off
[ 3.717241] xe 0000:00:02.0: [drm] Tile0: GT1: vecs3 fused off
[ 4.027531] xe 0000:00:02.0: [drm] Registered 4 planes with drm panic
[ 4.027544] [drm] Initialized xe 1.1.0 for 0000:00:02.0 on minor 0
[ 4.065892] xe 0000:00:02.0: [drm] Allocated fbdev into stolen
[ 4.067264] xe 0000:00:02.0: [drm] fb0: xedrmfb frame buffer device
[ 4.072986] xe 0000:00:02.0: [drm] Tile0: GT1: found GSC cv102.1.0
[ 14.597909] SELinux: Permission kexec_image_load in class system not defined in policy.
[ 14.597909] SELinux: Permission kexec_initramfs_load in class system not defined in policy.
[ 14.600430] SELinux: policy capability ioctl_skip_cloexec=0
[ 15.457702] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[ 15.462005] systemd[1]: Listening on systemd-factory-reset.socket - Factory Reset Management.
[ 15.489330] systemd[1]: modprobe@drm.service - Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm
[ 15.526871] audit: type=1130 audit(1785330036.260:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-udev-load-credentials comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 15.536813] audit: type=1130 audit(1785330036.270:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 15.557563] audit: type=1130 audit(1785330036.291:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 15.558221] audit: type=1130 audit(1785330036.292:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 15.559618] audit: type=1130 audit(1785330036.293:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 15.921395] zram0: detected capacity change from 0 to 16777216
[ 16.414308] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[ 16.414314] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 16.459278] Bluetooth: hci0: DSM reset method type: 0x00
[ 16.460172] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
[ 16.483740] cs35l56-hda spi0-CSC3554:00-cs35l54-hda.1: Reset GPIO busy, assume shared reset
[ 16.487606] r8152-cfgselector 2-2.1: reset SuperSpeed USB device number 3 using xhci_hcd
[ 16.560995] Bluetooth: hci0: Fseq executed: 00.00.04.202
[ 16.912393] sof-audio-pci-intel-mtl 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [xe])
[ 548.575568] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=32236 recv=32235
[ 589.599572] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=32655 recv=32654
[ 589.599603] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=32656 recv=32654
[ 607.583636] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=32814 recv=32813
[ 1819.876423] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=51439 recv=51438
[ 7637.630688] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=81347 recv=81346
[ 9192.645836] xe 0000:00:02.0: [drm] *ERROR* TLB invalidation fence timeout, seqno=104386 recv=104385
You’re running a KDE installation which is designed to work with wayland, with XFCE which is specifically intended to operate with X11, and both of which are being used with a somewhat new graphice driver.
The issue is the TLB fence timeouts almost certainly - the Xe driver is still relatively new and still in development and I guess you’re seeing the effects of that with this relatively new laptop.
You could try a few things:
See if the issue is just as bad when only using the laptop screen - disconnect display port 6.
remove the xe.force_probe=7d41 from the boot parameters - do you actually need that for the meteorlake stuff to be found these with recent kernels?
try booting with the parameter xe.enable_psr=0 to turn off panel self refresh. It’ll cost you more power, and battery life will be lower but you may not care about it.
Switch back to i915 which is far more stable and has millions of users.
Remove XFCE and all the detritus is brought in with it and just run a straight KDE installation, assuming KDE is the intended long term goal.
To remove XFCE you’d sudo dnf remove followed by whatever package you installed to get XFCE in the first place.
I’ve no idea what those packages would be as it’s been about 25 years since I used XFCE but dnf history list should get you a full historical list of everything you installed, in order. It won’t remove any XFCE configuration files, but it should remove everything it can, dependencies permitting.
I still have little laggin issues. I will try to work and charge the machine I will open a IDE, terminals and some docker applications and see if I still have the same issues I will keep you updated. now I am full KDE no more XFCE I disinstalle it.
from top I can see kwin_wayland pic at 30% CPU ressources I do not know if this is normal when specially when switching virtual desktop.
Seems far too high to be honest. For comparison, here’s my machine with a few minutes of history on screen. As you can see, kwin_wayland is 0.1% on my machine - I took the screenshot rather than just clipping some text so you can see the history inthe top left, the per CPU% in the top right and the memeory usage and relative process consumption bottom right. This had Zen open with about 35 tabs open, a video with sound active) actively playing in Youtube on one of them. As you can see, nowhere near 30%.
I use Zen (spotify + outlook), librewolf (surfing internet), vscodium and terminator also. I have the mouse always lagging not smooth as it was in the past. I have fedora 42 on another machine works perfectly with nvidia 5070 inside. no issues.
But on this machine maybe wayland or something in the background is running. When I move the mouse pointer it is really not smooth.
When I switch also virtual desktops it is not smooth.
Do you have multiple virtual desktop ? I have 4.
What do you suggest me to do ? maybe wait for a new update will be fixed, what do you think ?
Thank you again Steve for you time and for your help.
Only usually one, but I’ve just started up 8 and saw no difference in the CPU usage.
I’ve also just started up VS Code, RustRover, Pycharm, Jetbrains toolbox, applied updates to all the jetbrains products (as you can see from the screenshot below, quite a bit of CPU usage during that period and network traffic). No sluggishness, no pausing, no stuttering… so you should be seeing the same kind of responsiveness.
It would be handy to see precisely what the CPU% load is on your machine for the top handful of processes - I’m using btop for these screenshots, but the same output should come from htop or even just top. I’d not expect to see more than a few % of CPU at most from a machine that you were just waving the mouse around an on - anything in double figures would look suspicious to me.
Hmm - quite a lot of CPU cores are relatively busy - close to an average of 20% across nearly all of them, apart from 12 and 13. That looks way too high for a relatively idle machine.
If you run journalctl -f --no-hostname in a window, it’ll follow what’s currently happening in the log. Is there any sort of pattern of errors or warning being popped out?
(are you still using the Xe driver or have you tried switching back to the i915 driver to compare?)
I would suggest to look more at the memory usate, especially the swap space usage. Also important is how busy the disk is. All that can be chown using top -i.
As long as the CPU usage is less than 100 % the interactive program can always get cpu time, unless it is waition for some IO to finish first.
More interesing is the i915_flip in status “D” meaning waiting for IO (usually disk IO). If the status stays at “D” that would be strange. If it is just a coincidence it may not mean anything.
