Did you update the last version of BIOS firmware ?
If no CPPC, you can use acpi-cpufreq only.
Remove displaylink
from AUR.
Try to install v4l2loopback-dkms
and acpi_call-dkms
Did you update the last version of BIOS firmware ?
If no CPPC, you can use acpi-cpufreq only.
Remove displaylink
from AUR.
Try to install v4l2loopback-dkms
and acpi_call-dkms
yes
OK
done
v4l2loopback-dkms was already installed and acpi_call-dkms is no installed. error message is gone
Here the current output.
Okt 18 14:30:21 T14 systemd-modules-load[376]: Failed to find module 'v4l2loopback-dc'
Okt 18 14:30:21 T14 systemd-modules-load[376]: Failed to find module 'v4l2loopback'
Okt 18 14:30:21 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found
Okt 18 14:30:21 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at ind
ex 1
Okt 18 14:30:22 T14 systemd[1]: displaylink.timer: Refusing to start, unit displaylink.service to trigger not loaded.
Okt 18 14:30:22 T14 systemd[1]: Failed to start Start Displaylink with 5 Sec delay..
Okt 18 14:30:22 T14 bluetoothd[781]: src/plugin.c:add_plugin() Version mismatch for sixaxis
Okt 18 14:30:25 T14 systemd[1086]: /run/user/1000/systemd/generator.late/app-org.kde.yakuake@autostart.service:18: WorkingDirectory
= path is not absolute, ignoring:
Okt 18 14:30:27 T14 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Okt 18 14:30:32 T14 bluetoothd[781]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object
upon power down
Thanks a lot already! I think, it goes now off-topic, didn’t it? You helped already a lot.
Now I will have to make to open an issue in gitlab I think…Or somebody other has still an idea…
Disable “displaylink.timer” that does not need to trigger displaylink service:
sudo systemctl disable --now displaylink.timer
I think, I found a bug-report related to this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17d819e2828cacca2e4c909044eb9798ed379cd2
With kernel 6.0.3 I get nearly the same glmark score like with 5.18:
Score: 3263
Now I’m using linux-manjaro-xanmod (6.0.3-1)
So, it’s fine.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.