I have used linux mint for a while but I decided to try manjaro on my pc for about 6 months, when I swapped back I got it on and stable for just long enough to move some of my files over and install csgo but when I tried to launch it the computer froze and after like 5-10 minutes I shut it down then it threw this error code that I had not seen before even when running the same system on the same os
It was fully up to date because I fixed that before I installed anything
As of now it puts up that code looks to me like(ucsi_ccg 0-0008: Failed to get FW build) to me but the only place I can find reference to that is a nixos forum post from 2 years ago saying it is a driver used in laptops for usb-c
But it throws that code then black screens and goes unresponsive either when I try and boot to the main HDD or when I try and boot to an external USB stick so I can’t gain any access to the software to disable the package
I tried checking my BIOS settings and pulling the bios battery already and neither made any change
Usually if you tap you phone’s screen it will force it to autofocus. 🫢
The problem is that the text dosent stay up for more than about half a second before the screen goes black and I get no more display output until I reboot it
If you boot into the installer again you may be able to reinstall without wiping your personal data.
At the very least it’ll give you the chance to copy off anything you don’t want to lose. Then you can install fresh and see if that helps.
It will not boot into a live usb environment either, even with a freshly made live USB from an iso I know is good that will boot on another computer
Maybe try a more commonplace distro just to rule out a hardware issue. Try Ubuntu or Fedora’s live USBs.
If you’re still getting that error, it might be that somehow you’re not actually booting into the live USB environment, or something more fundamental to your system is broken.
I did also find this: https://discourse.nixos.org/t/boot-error-ucsi-ccg-0-0008-failed-to-get-fw-build/27842
Which suggests you could work around the issue by editing your kernel cmdline to blacklist the module ucsi_ccg.
On systemd-boot you can do that temporarily to test it by spamming the e key as the system starts up. You’ll eventually be able to edit the boot params.
Grub should have something similar but I don’t really use that these days.
In theory adding this to your cmdline should block the module from loading: modprobe.blacklist=usci_ccg
I am trying that now but I can’t boot into anything I have tried
Edit, when I put in it did nothing and I got the same error
No idea tbh, but I’d boot from the Live USB and debug the ‘proper’ installation from there.

