Skip to main content
Topic: Every time I boot up, the system holds for 2 minutes (Read 667 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Every time I boot up, the system holds for 2 minutes

I recently installed Artix, and it all is going quite well. However, whenever I boot up, the kernel logs display this message multiple times:
Code: [Select]
Bluetooth: hci0: Failed to read codec capabilities (-56
And then hangs for 2 minutes (I assume before giving up and just starting).

Here is the relevant dmesg at startup:
Code: [Select]
[    3.600808] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    4.414401] Bluetooth: hci0: Waiting for firmware download to complete
[    4.415957] Bluetooth: hci0: Firmware loaded in 1701259 usecs
[    4.417567] Bluetooth: hci0: Waiting for device to boot
[    4.432221] Bluetooth: hci0: Device booted in 14339 usecs
[    4.436021] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[    4.439115] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.442130] Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
[    4.503113] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.505120] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.507119] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.509144] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.511137] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.513129] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.515172] Bluetooth: hci0: Failed to read codec capabilities (-56)
[    4.625809] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    5.649814] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    6.672652] i2c_hid_acpi i2c-GDIX0000:00: can't add hid device: -121
[    6.681058] i2c_hid_acpi: probe of i2c-GDIX0000:00 failed with error -121
[   66.642963] PDLOG 2022/01/21 21:23:20.571 P0 SNK Charger ??? 19520mV max 5000mV / 500mA
[   66.646176] PDLOG 2022/01/21 21:23:20.570 P1 Disconnected
[   66.649394] PDLOG 2022/01/21 21:23:20.617 P0 SNK Charger ??? 15680mV max 5000mV / 3000mA
[   66.652632] PDLOG 2022/01/21 21:23:21.696 P0 SNK Charger ??? 5120mV max 20000mV / 3000mA
[  126.150973] EXT4-fs (mmcblk1p3): re-mounted. Opts: (null). Quota mode: none.
[  126.191905] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  126.199383] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[  126.224811] Adding 2097148k swap on /dev/mmcblk1p2.  Priority:-2 extents:1 across:2097148k SSFS
[  126.975164] elogind[939]: New seat seat0.
[  126.977277] elogind[939]: Watching system buttons on /dev/input/event1 (Power Button)
[  126.978749] elogind[939]: Watching system buttons on /dev/input/event0 (Lid Switch)
[  126.979290] elogind[939]: Watching system buttons on /dev/input/event4 (Intel Virtual Buttons)
[  126.980330] elogind[939]: Watching system buttons on /dev/input/event2 (AT Translated Set 2 keyboard)
As you can see, it fails to check bluetooth, then, exactly a minute later, it registers the charger (?), and then, exactly a minute after that, continues with the boot. There are some messages from i2c_hid_acpi there, but this problem was present before I installed that. I believe I saw online that a problem related to this one was going to be solved in the 5.17 kernel, but that person was not waiting 2 minutes every boot up.
This is very annoying, and I would appreciate it if anyone could help me with this, and let me know if I need to include anything else.