I have tried this setting and the backlight error is gone but the problem still persists:
Dez 08 17:23:38 cptLegendary kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Dez 08 17:23:39 cptLegendary bluetoothd[610]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dez 08 17:23:39 cptLegendary bluetoothd[610]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dez 08 17:23:39 cptLegendary bluetoothd[610]: src/plugin.c:plugin_init() Failed to init bap plugin
Dez 08 17:23:39 cptLegendary gdm-autologin][753]: gkr-pam: couldn't unlock the login keyring.
Dez 08 17:23:47 cptLegendary smbd[803]: [2022/12/08 17:23:47.269531, 0] ../../source3/smbd/server.c:1741(main)
Dez 08 17:23:47 cptLegendary smbd[803]: smbd version 4.17.3 started.
Dez 08 17:23:47 cptLegendary smbd[803]: Copyright Andrew Tridgell and the Samba Team 1992-2022
Dez 08 17:24:00 cptLegendary systemd-backlight[1022]: nvidia_0: Failed to write system 'brightness' attribute: Invalid argument
Dez 08 17:24:00 cptLegendary systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:nvidia_0.
Dez 08 17:24:06 cptLegendary kernel: nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000947d:0:0:407
Dez 08 17:25:53 cptLegendary gdm[693]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Dez 08 17:25:53 cptLegendary systemd-coredump[1098]: Failed to connect to coredump service: Connection refused
I think the backlight issue is a symptom and not the disease.
I think the kernel (5.18) was a typo and thus far I have tried those kernels:
- 5.10.157-1-MANJARO
- 5.15.81-1-MANJARO
- 6.0.11-1-MANJARO
I have also deactivated Bluetooth, WiFi and the fingerprint reader, just to be on the safe side. Furthermore, I stumbled over a thread with a similar issue:
So, I went ahead and added ibt=off but it did not solve it on my end 