Hey everyone! I'm a new Linux user who just switched my work and gaming rig from Windows 10 to a distribution called Bazzite about a week ago. It's been a generally smooth experience until I ran into a really annoying issue with gaming. After about half an hour of playing, my system completely freezes - the game stays on screen, and I can't do anything. Alt+Tab doesn't work, I can't access the terminal, nothing at all. The only option is to hard reboot my machine.
I checked the logs using journalctl to investigate the crashes, and I found these error messages popping up right when it freezes:
`Nov 02 14:37:24 bazzite kernel: nvidia-gpu 0000:08:00.3: i2c timeout error e0000000`
`Nov 02 14:37:24 bazzite kernel: ucsi_ccg 6-0008: i2c_transfer failed -110`
`Nov 02 14:37:24 bazzite kernel: ucsi_ccg 6-0008: ucsi_ccg_init failed - -110`
I'm still figuring out what all this means and I'm wondering if this i2c timeout error can really cause a full system lockup like I'm experiencing? Here's a bit about my setup:
CPU: 5600x
GPU: RTX 2060
The OS is running the latest Bazzite update on Fedora 43. Also, I'm using kernel version 6.17.5-ba07.fc43.x86_64 and NVIDIA version 580.95.05.
2 Answers
It sounds frustrating! The i2c timeout error could definitely be the culprit. It generally suggests an issue with communication between the system's GPU and other components. In my case, I found that updating my drivers and the kernel often helped solve similar freezes. Have you tried checking for updates or even rolling back to a previous driver version to see if it stabilizes your system?
I had a similar issue while experimenting with different Linux distros. It turned out that my NVIDIA drivers weren't properly installed. Bazzite is usually stable, but maybe you can try reinstalling the drivers or switching to a slightly different version. It's weird how hardware compatibility can mess things up, but it's worth trying!
Reinstalling the drivers sounds like a solid plan. I’ll give that a shot and see if it makes a difference!
Thanks for the tip! I haven't tried rolling back yet, but I’ll definitely look into updating my drivers to see if that resolves the issue.