Are boot time journalctl entries for "ucsi_ccg 0-0008: failed to get FW build information" something to fix or informational?

Support
3

Thank you for sharing your investigation and feedback @megavolt !

I appreciate knowing ucsi_ccg is nVidia GPU specific, so not relevant since I use an AMD GPU.

I’ll likely make a note to ignore this entry going forward… but I’m also not shy about learning how I would blacklist this kernel module to prevent this “unnecessary” error (in my case).

Following Kernel module - ArchWiki, I think my steps would be…

  • I executed $ mkinitcpio -M just to confirm the module name was listed as expected
$ mkinitcpio -M | grep -i ucsi_ccg
ucsi_ccg
  1. Since I have no files under /etc/modprobe.d/ I would begin by creating one via $ sudo nano /etc/modprobe.d/no_nvidia_gpu_usb.conf
  2. Within nano I would add the following contents…
# Do not load the 'ucsi_ccg' module on boot... I don't have an nVidia GPU, so loading a module for its USB port is pointless.
blacklist ucsi_ccg
  1. I confirmed I have the modconf hook in my HOOKS array… so I can safely ignore the part of editing the FILES array
$ cat /etc/mkinitcpio.conf | grep -i modconf
HOOKS="base udev autodetect modconf block keyboard keymap filesystems fsck"
  1. Now that the blacklisting is in place, I’d run $ mkinitcpio -P to regenerate all initramfs files for my installed kernels
  2. Reboot
  3. Validate blacklisting worked via…
    • I feel $ mkinitcpio -M should no longer list ucsi_ccg :x:… but, more importantly…
    • Running $ journalctl -k --priority err should confirm no more ucsi_ccg error messages :white_check_mark:
2 Likes
Are boot time journalctl entries for "sp5100-tco: Watchdog hardware is disabled" something to fix or informational?