Missing hardware acceleration for rendering on Intel(R) Core(TM) i5-2400 Sandybridge

Help
1

Hi,

A once speedy pc has now become sluggish and I don’t know where to start: boot takes more time than usual, Plasma loads but then makes me wait a lot for panels and the desktop to appear, the UX is at times responsive and at times is not. I’m looking for some advice on what to use or look for to troubleshoot the matter.

Specifics:

  • Operating System: Fedora Linux 43
  • KDE Plasma Version: 6.5.3
  • KDE Frameworks Version: 6.20.0
  • Qt Version: 6.10.1
  • Kernel Version: 6.17.10-300.fc43.x86_64 (64-bit)
  • Graphics Platform: Wayland
  • Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
  • Memory: 16 GiB of RAM (15.4 GiB usable)
  • Graphics Processor: llvmpipe
  • Manufacturer: LENOVO
  • Product Name: 7052A9G
  • System Version: ThinkCentre M91p

Notably, I struggled on installing Linux on this hardware for a long time: after installation distros won’t boot properly. I found that the something may be very old and I needed to use MBR as partition table instead of GPT. But it has always been like this, and before the system was very snappy.

Something I did recently (but I think still before this performance degradation) was reinstalling MariaDB for Akonady, as I tried replacing it with MySQL for some reasons and than reverted back when I saw that Akonadi wasn’t working.

The situation becomes a little better after some time from the boot, but the only startup application is Nextcloud. Even then, System Monitor generally shows this situation, where only background jobs and Firefox consume memory:

immagine
immagine1197×892 96 KB

Something interesting: the userspace now loads in a lot of time!

samuele@192:~$ systemd-analyze
Startup finished in 734ms (kernel) + 2.311s (initrd) + 3min 43.066s (userspace) = 3min 46.112s
graphical.target reached after 25.253s in userspace.
samuele@192:~$ systemd-analyze blame
3min 26.753s plocate-updatedb.service
36.022s fwupd.service
16.326s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397\x2dpart4.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartnum-4.device
16.326s dev-disk-by\x2duuid-44eb3bcb\x2d84e9\x2d4d12\x2d9392\x2d2b2ad927223b.device
16.326s dev-sdb4.device
16.326s dev-disk-by\x2dpartuuid-0bd2edd4\x2df51e\x2d4c46\x2da32c\x2d1c48ad1972e9.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart4.device
16.326s dev-disk-by\x2did-wwn\x2d0x500a0751e4bdf397\x2dpart4.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dlabel-ROOT.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart4.device
16.326s dev-disk-by\x2ddiskseq-2\x2dpart4.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2duuid-44eb3bcb\x2d84e9\x2d4d12\x2d9392\x2d2b2ad927223b.device
16.326s dev-disk-by\x2dlabel-ROOT.device
16.326s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb4.device
16.326s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartuuid-0bd2edd4\x2df51e\x2d4c46\x2da32c\x2d1c48ad1972e9.device
15.981s dev-disk-by\x2dlabel-HOME.device
15.981s dev-disk-by\x2dpartuuid-0fe8ba45\x2daacc\x2d471b\x2db3a3\x2d33074673120b.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartnum-3.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart3.device
15.981s dev-disk-by\x2duuid-1627a1d2\x2db05d\x2d43b8\x2db1d6\x2dd66fbc19f0a7.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dlabel-HOME.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart3.device
15.981s dev-sdb3.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2duuid-1627a1d2\x2db05d\x2d43b8\x2db1d6\x2dd66fbc19f0a7.device
15.981s dev-disk-by\x2ddiskseq-2\x2dpart3.device
15.981s dev-disk-by\x2did-wwn\x2d0x500a0751e4bdf397\x2dpart3.device
15.981s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397\x2dpart3.device
15.981s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb3.device
15.981s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartuuid-0fe8ba45\x2daacc\x2d471b\x2db3a3\x2d33074673120b.device
15.975s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartuuid-f41aa128\x2d675d\x2d41d5\x2d99fa\x2d1ed3e033228a.device
15.975s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartnum-2.device
15.975s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397\x2dpart2.device
15.975s dev-disk-by\x2ddiskseq-2\x2dpart2.device
15.975s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2duuid-9c5530d4\x2d35b0\x2d4920\x2d8a5d\x2d0efa88aabc1b.device
15.975s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dlabel-BOOT.device
15.973s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart2.device
15.973s dev-disk-by\x2duuid-9c5530d4\x2d35b0\x2d4920\x2d8a5d\x2d0efa88aabc1b.device
15.973s dev-disk-by\x2dpartuuid-f41aa128\x2d675d\x2d41d5\x2d99fa\x2d1ed3e033228a.device
15.973s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb2.device
15.973s dev-disk-by\x2did-wwn\x2d0x500a0751e4bdf397\x2dpart2.device
15.973s dev-disk-by\x2dlabel-BOOT.device
15.973s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart2.device
15.973s dev-sdb2.device
15.967s dev-disk-by\x2did-wwn\x2d0x500a0751e4bdf397\x2dpart1.device
15.967s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb-sdb1.device
15.967s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartnum-1.device
15.967s dev-sdb1.device
15.967s dev-disk-by\x2dpartuuid-4b76e47b\x2d82fd\x2d42c1\x2d969d\x2dbd017a86a9e3.device
15.967s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart1.device
15.967s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4\x2dpart1.device
15.967s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397\x2dpart1.device
15.967s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartuuid-4b76e47b\x2d82fd\x2d42c1\x2d969d\x2dbd017a86a9e3.device
15.967s dev-disk-by\x2ddiskseq-2\x2dpart1.device
15.846s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.device
15.846s dev-disk-by\x2ddiskseq-2.device
15.846s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0.device
15.967s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397\x2dpart1.device
15.967s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0\x2dpart-by\x2dpartuuid-4b76e47b\x2d82fd\x2d42c1\x2d969d\x2dbd017a86a9e3.device
15.967s dev-disk-by\x2ddiskseq-2\x2dpart1.device
15.846s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.device
15.846s dev-disk-by\x2ddiskseq-2.device
15.846s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d4.0.device
15.846s sys-devices-pci0000:00-0000:00:1f.2-ata4-host3-target3:0:0-3:0:0:0-block-sdb.device
15.846s dev-sdb.device
15.846s dev-disk-by\x2did-ata\x2dCT480BX500SSD1_2043E4BDF397.device
15.846s dev-disk-by\x2did-wwn\x2d0x500a0751e4bdf397.device
13.696s dev-disk-by\x2did-ata\x2dST500DM002\x2d1BD142_Z2AA3B91.device
13.696s dev-disk-by\x2ddiskseq-1.device
13.696s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda.device
13.696s dev-disk-by\x2did-wwn\x2d0x5000c50035db4a60.device
13.696s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.device
13.696s dev-sda.device
13.696s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0.device
13.692s dev-sda1.device
13.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-e2e1d3e8\x2daa1d\x2d451c\x2dba77\x2de8308cc9e420.device
13.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart1.device
13.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart1.device
13.692s dev-disk-by\x2ddiskseq-1\x2dpart1.device
13.692s dev-disk-by\x2did-ata\x2dST500DM002\x2d1BD142_Z2AA3B91\x2dpart1.device
13.692s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device
13.692s dev-disk-by\x2dpartuuid-e2e1d3e8\x2daa1d\x2d451c\x2dba77\x2de8308cc9e420.device
13.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
13.692s dev-disk-by\x2did-wwn\x2d0x5000c50035db4a60\x2dpart1.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dlabel-STORAGE.device
13.683s dev-sda2.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart2.device
13.683s dev-disk-by\x2did-ata\x2dST500DM002\x2d1BD142_Z2AA3B91\x2dpart2.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart2.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2duuid-7ff738dd\x2d4ed6\x2d4622\x2d95a5\x2d2a9316703e86.device
13.683s dev-disk-by\x2dpartuuid-c86e4280\x2dc349\x2d469f\x2dad4d\x2d7e303800b485.device
13.683s dev-disk-by\x2did-wwn\x2d0x5000c50035db4a60\x2dpart2.device
13.683s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartnum-2.device
13.683s dev-disk-by\x2duuid-7ff738dd\x2d4ed6\x2d4622\x2d95a5\x2d2a9316703e86.device
13.683s dev-disk-by\x2ddiskseq-1\x2dpart2.device
13.683s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart-by\x2dpartuuid-c86e4280\x2dc349\x2d469f\x2dad4d\x2d7e303800b485.device
13.683s dev-disk-by\x2dlabel-STORAGE.device
13.628s dev-ttyS3.device
13.628s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
13.626s dev-ttyS2.device
13.626s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
13.611s sys-devices-pci0000:00-0000:00:16.3-0000:00:16.3:0-0000:00:16.3:0.0-tty-ttyS4.device
13.611s dev-ttyS4.device
13.608s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
13.608s dev-ttyS1.device
13.557s dev-tpm0.device
13.557s sys-devices-pnp0-00:05-tpm-tpm0.device
12.692s systemd-journal-flush.service
12.385s sys-module-fuse.device
12.149s dev-ttyS0.device
12.149s sys-devices-pnp0-00:02-00:02:0-00:02:0.0-tty-ttyS0.device
12.116s sys-module-configfs.device
8.214s systemd-udevd.service
5.061s systemd-tmpfiles-clean.service
4.236s firewalld.service
4.071s passim.service
3.171s NetworkManager-wait-online.service
1.713s systemd-vconsole-setup.service
1.630s initrd-switch-root.service
1.357s mariadb.service
1.173s abrtd.service
1.118s upower.service
1.046s tuned-ppd.service
967ms geoclue.service
895ms udisks2.service
789ms polkit.service
785ms accounts-daemon.service
783ms home-storage.mount
736ms logrotate.service
687ms systemd-zram-setup@zram0.service
687ms chronyd.service
671ms tuned.service
670ms systemd-tmpfiles-setup-dev-early.service
655ms cups.service
640ms dev-zram0.swap
608ms dnf-makecache.service
504ms systemd-fsck@dev-disk-by\x2duuid-9c5530d4\x2d35b0\x2d4920\x2d8a5d\x2d0efa88aabc1b.service
462ms NetworkManager.service
419ms home.mount
395ms wpa_supplicant.service
369ms gssproxy.service
336ms systemd-tmpfiles-setup.service
325ms rsyslog.service
322ms systemd-random-seed.service
321ms systemd-sysctl.service
318ms user@1000.service
287ms systemd-udev-trigger.service
249ms ModemManager.service
235ms smartd.service
194ms unbound-anchor.service
187ms var-lib-nfs-rpc_pipefs.mount
186ms systemd-logind.service
176ms sssd-kcm.service
164ms rpc-statd-notify.service
144ms avahi-daemon.service
114ms lvm2-monitor.service
102ms dracut-shutdown.service
101ms boot.mount
98ms colord.service
93ms foomaticrip-upgrade.service
88ms systemd-resolved.service
86ms systemd-journald.service
83ms systemd-homed.service
74ms systemd-user-sessions.service
72ms rtkit-daemon.service
66ms dbus-broker.service
66ms switcheroo-control.service
65ms systemd-hostnamed.service
63ms packagekit.service
61ms uresourced.service
59ms systemd-oomd.service
57ms systemd-userdbd.service
56ms systemd-tmpfiles-setup-dev.service
49ms audit-rules.service
46ms plymouth-quit-wait.service
45ms auditd.service
45ms dracut-cmdline.service
45ms plymouth-quit.service
42ms systemd-binfmt.service
37ms dev-hugepages.mount
37ms dev-mqueue.mount
37ms systemd-udev-load-credentials.service
37ms flatpak-system-helper.service
36ms sys-kernel-debug.mount
35ms sys-kernel-tracing.mount
35ms plymouth-switch-root.service
33ms plymouth-read-write.service
33ms plymouth-start.service
32ms kmod-static-nodes.service
32ms systemd-fsck-root.service
28ms dracut-pre-udev.service
27ms user-runtime-dir@1000.service
27ms sys-fs-fuse-connections.mount
24ms modprobe@loop.service
23ms initrd-udevadm-cleanup-db.service
21ms dracut-pre-pivot.service
21ms initrd-cleanup.service
21ms systemd-userdb-load-credentials.service
20ms systemd-sysusers.service
20ms systemd-modules-load.service
20ms proc-sys-fs-binfmt_misc.mount
17ms systemd-update-utmp.service
16ms tmp.mount
16ms systemd-remount-fs.service
7ms initrd-parse-etc.service
5ms sshd-unix-local.socket
3ms systemd-coredump.socket
2ms lvm2-lvmpolld.socket
1ms systemd-bootctl.socket
1ms systemd-sysext.socket
1ms systemd-ask-password.socket
1ms systemd-factory-reset.socket
1ms systemd-udevd-control.socket
997us systemd-creds.socket
987us cups.socket
735us sssd-kcm.socket
643us systemd-userdbd.socket
455us dm-event.socket
420us avahi-daemon.socket
411us dbus.socket
311us pcscd.socket
301us systemd-oomd.socket
284us systemd-resolved-monitor.socket
248us systemd-udevd-varlink.socket
239us systemd-hostnamed.socket
224us systemd-logind-varlink.socket
170us systemd-journald-audit.socket
143us systemd-resolved-varlink.socket
133us iscsid.socket
88us systemd-rfkill.socket
87us iscsiuio.socket
82us systemd-homed-activate.service
79us systemd-journald.socket
79us systemd-journald-dev-log.socket
18us systemd-udevd-kernel.socket

After a reboot, the userspace loaded in 30 seconds, but the slugginesh is always there.

I launched atop during this second boot. The red DSK part appeared sometimes, but I think mainly when I launched Firefox after some time.

immagine
immagine1259×915 184 KB

3

This is one thing to look at, though this is not a KDE problem. You are not using your graphics chip, but using software rendering. Can’t say why, and not sure if a 13 year old hardware setup is a reason here. I’d imagine graphics should Just Work, being Intel, but I can’t say why. Don’t neglect looking at potential hardware issues as well.

I assume that this should only be run once in a while, and notr take such a long time even if it is a slow HDD. If it is happening every boot, it is another (non-KDE) problem. `

For these, you definitely also want to seek guidance from your distro’s community for the best knowledge.

2 Likes
4

Is your disk an SSD or a spinning HDD?

What does the SMART Status (in the Info Center app) report for the drive?

1 Like
5

My main disk (where everything is installed) is an SSD and the SMART Status seems passed:

smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.17.10-300.fc43.x86_64] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron Client SSDs
Device Model:     CT480BX500SSD1
Serial Number:    2043E4BDF397
LU WWN Device Id: 5 00a075 1e4bdf397
Firmware Version: M6CR041
User Capacity:    480.103.981.056 bytes [480 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        In smartctl database 7.5/5852
ATA Version is:   ACS-3 T13/2161-D revision 4
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Dec 10 09:57:20 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x11) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
					entering power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  10) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocate_NAND_Blk_Cnt 0x0032   100   100   010    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2653
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2115
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Ave_Block-Erase_Count   0x0032   065   065   000    Old_age   Always       -       246
174 Unexpect_Power_Loss_Ct  0x0032   100   100   000    Old_age   Always       -       76
180 Unused_Reserve_NAND_Blk 0x0033   100   100   000    Pre-fail  Always       -       45
183 SATA_Interfac_Downshift 0x0032   100   100   000    Old_age   Always       -       0
184 Error_Correction_Count  0x0032   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   065   051   000    Old_age   Always       -       35 (Min/Max 15/49)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_ECC_Cnt 0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
202 Percent_Lifetime_Remain 0x0030   065   065   001    Old_age   Offline      -       35
206 Write_Error_Rate        0x000e   100   100   000    Old_age   Always       -       0
210 Success_RAIN_Recov_Cnt  0x0032   100   100   000    Old_age   Always       -       0
246 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       18312964956
247 Host_Program_Page_Count 0x0032   100   100   000    Old_age   Always       -       572280154
248 FTL_Program_Page_Count  0x0032   100   100   000    Old_age   Always       -       3973739168
249 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       0
250 Read_Error_Retry_Rate   0x0032   100   100   000    Old_age   Always       -       0
251 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       2728349428
252 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       32
253 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       0
254 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       859
223 Unkn_CrucialMicron_Attr 0x0032   100   100   000    Old_age   Always       -       55

SMART Error Log not supported

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

The above only provides legacy SMART information - try 'smartctl -x' for more

Therefore the plocate-updatedb.service is even more strange.

But at the next boot it didn’t launch, so I agree that the only problem is the amount of time it took. I remember the startup time being very fast at first, when I installed everything.

These are the information on the CPU:

Architecture:                            x86_64
CPU op-mode(s):                          32-bit, 64-bit
Address sizes:                           36 bits physical, 48 bits virtual
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               GenuineIntel
Model name:                              Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
CPU family:                              6
Model:                                   42
Thread(s) per core:                      1
Core(s) per socket:                      4
Socket(s):                               1
Stepping:                                7
CPU(s) scaling MHz:                      91%
CPU max MHz:                             3400,0000
CPU min MHz:                             1600,0000
BogoMIPS:                                6186,02
Flags:                                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid xsaveopt dtherm ida arat pln pts vnmi md_clear flush_l1d
Virtualization:                          VT-x
L1d cache:                               128 KiB (4 instances)
L1i cache:                               128 KiB (4 instances)
L2 cache:                                1 MiB (4 instances)
L3 cache:                                6 MiB (1 instance)
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             KVM: Mitigation: Split huge pages
Vulnerability L1tf:                      Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled
Vulnerability Mds:                       Mitigation; Clear CPU buffers; SMT disabled
Vulnerability Meltdown:                  Mitigation; PTI
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:                Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:                Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected
Vulnerability Vmscape:                   Mitigation; IBPB before exit to userspace

It seems like the module for hardware acceleration is there and is working, and the rendering is describer as “accelerated” even if I’m on llvmpipe:

samuele@192:~$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 2000 (SNB GT1) (0x102)
    Version: 25.2.7
    Accelerated: yes
    Video memory: 1536MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.3
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 2000 (SNB GT1)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 25.2.7
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.3 (Compatibility Profile) Mesa 25.2.7
OpenGL shading language version string: 3.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 25.2.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

samuele@192:~$ lsmod | grep i915
i915                 5373952  74
i2c_algo_bit           20480  1 i915
drm_buddy              32768  1 i915
video                  81920  1 i915
ttm                   135168  1 i915
drm_display_helper    331776  1 i915
cec                   106496  2 drm_display_helper,i915
samuele@192:~$ sudo modprobe i915
[sudo] password di samuele: 
samuele@192:~$
samuele@192:~$ cat /etc/modprobe.d/i915.conf 
options i915 force_probe=*

ChatGPT suggests that my CPU is blacklisted from hardware acceleration in Wayland due to a recent decision from Fedora, but none of the sources it provides are precise:

Fedora KDE is not coming with x11 at all, so it’s not like I can test it, unless I can try with a USB stick with some distro that still support x11.

6

It’s not there by default, but it can be installed: sudo dnf install plasma-workspace-x11

7

Is it that simple? Thank you. Maybe another (more costly) option is getting a dedicated GPU?

Anyway, I’d like to see if the issue can be fixed on Wayland. I’ll try following that guide instructions.

8

You could also check on the Fedora forum.

If it was their choice to blacklist your iGPU they might know how to undo that.

1 Like
9

Now I’m on X11, but no luck:

  • Operating System: Fedora Linux 43
  • KDE Plasma Version: 6.5.3
  • KDE Frameworks Version: 6.20.0
  • Qt Version: 6.10.1
  • Kernel Version: 6.17.10-300.fc43.x86_64 (64-bit)
  • Graphics Platform: X11
  • Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
  • Memory: 16 GiB of RAM (15.4 GiB usable)
  • Graphics Processor: llvmpipe
  • Manufacturer: LENOVO
  • Product Name: 7052A9G
  • System Version: ThinkCentre M91p

It seems the module cannot be loaded at all?

samuele@192:~$ MESA_LOADER_DRIVER_OVERRIDE=i965 glxinfo | grep "OpenGL renderer"
glx: failed to create dri3 screen
failed to load driver: i965
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
OpenGL renderer string: llvmpipe (LLVM 21.1.5, 256 bits)

Therefore I’ll definitely ask them:

KDE NEON uses llvmpipe (X11 and Wayland) Intel I915 GPU
10

Thank you, I opened a thread with Fedora: Intel Core i5-2400 (SandyBridge) not supported anymore? - #2 by augenauf - Fedora Discussion

1 Like
11

Turns out Vulkan is not supporting the iGPU anymore and the string in System Settings is not that reliable.

1 Like