Linux Mint issues challenges with peripherals and sensors.
Linux Mint issues challenges with peripherals and sensors.
Got everything set up smoothly for the Windows 10 end-of-life. Dual boot with Linux works perfectly—apps run fast, Steam games load instantly, and I didn’t need to reinstall anything just by mounting my game drive. No graphics driver problems since I’m using an AMD card; Firefox, Thunderbird, and LibreOffice are all running smoothly without any issues. The fans aren’t responding properly either—Windows FanControl shows fans, but CoolerControl only sees GPU fans. OpenRGB crashes completely at startup, which is frustrating. My board is an Asus model, and I’ve tried troubleshooting for a few years without success. I also have an Asus keyboard and mouse, but can’t manage them. Overall, it’s fine technically, but controlling peripherals and RGB remains a headache.
Have you attempted using "sensors-detect" and adhering to its instructions? If you still can’t view all fans and sensors, it’s likely due to the I/O controller chip on the board, which manages communication with these components. Nuvoton controllers are frequently seen on main boards. The challenge usually lies in the fact that first-party drivers are often exclusive and lack Linux-specific versions. Their integration into the Linux kernel typically follows technical guidelines and involves some level of reverse engineering. Occasionally, slight variations exist between models; using a driver similar to another model can resolve the issue. This applies to the Nuvoton NCT6799D found on X670E boards. If you can identify the exact chip on your board, sharing it would be helpful. This isn’t a Linux issue per se, but rather a reflection of proprietary software constraints. Have you tried using GHub with Wine? It’s a last resort but could work. This situation isn’t exclusive to Linux—it’s more about Asus and Logitech’s approach. If they had released their software for Linux or published the protocol details, developers would have been able to create compatible solutions. Naturally, it remains proprietary. We’re beginning to notice this trend. Despite its annoyance, it might help you better understand why open-source tools are so valuable and why society has accepted these limitations. Running OpenRGB shouldn’t cause system crashes unless executed without root privileges. Have you installed it directly from your distribution’s package manager, or via Snap or Flatpak? It’s unclear how uniform hardware protocols have become. LEDs are generally accessible through "/sys/class/leds". Take a look there to check if more files exist beyond the obvious ones. I assume most are accessed via SMBus, I2C, or USB, though I’m not certain about additional layers manufacturers might add. It’s possible some devices use their own unique communication methods...
You’ve looked into Solaar for handling your Logitech devices. It’s typically available in most package managers, or you can compile it yourself using sources from GitHub.
I've received feedback from ChatGPT about issues with sensors linked to a new Asus chip that doesn't work well with Linux setup. It suggests adjusting fan speeds in the BIOS. Similar problems have been reported for Asus Aura and Armoury models, with discussions on GitHub and Reddit. It seems disabling Aura in the BIOS might help. I also found a Linux app for Logitech mice (logiops) and plan to test it. It appears hardware makers sometimes focus only on Windows, which is frustrating. I'm avoiding Asus moving forward but will keep an eye on it.
For the Logitech Mouse you can try Piper . I know this is probably what you don't want to hear but Linux kind of decides what you get to use and when it comes to things like RGB and Gaming Peripherals you pretty much rely on community support which isn't guaranteed to exist or last long term. In terms of Keyboard and Mice your best overall options are Razer Keyboards and Razer/Logitech Mice. Razer is well supported by OpenRazer and Logitech Mice as mentioned previously by Piper. Fan speeds not being addressable is fairly common, your overall best option is just to set it in BIOS or obtain a usb controller listed at https://github.com/liquidctl/liquidctl?t...ed-devices , which will work with CoolerControl. For your OpenRGB issue, there is a open Device Request so you will probably just have to wait it out. Wine can't interact directly with USB Devices. Not necessarily, it's udev rules grant it full access to the device, send the wrong command and it could cause a hardware error. There have been known events where OpenRGB has bricked boards due to this which is why they actually put a warning on their GitLab Page.
It's worth noting that looking back, I should have recognized this earlier. ChatGPT isn't always a trustworthy reference, even when it seems accurate based on likelihood. It's unlikely ASUS would develop its own chip for fan and sensor control since the issue is already widely available to other makers. If your motherboard model matches the one you have, the Nuvoton NCT6799D-R chip might be present, compatible with the latest Linux kernel (around version 6.5). If the 'sensors' feature doesn't behave as expected, consider updating to a newer kernel or adjusting the driver settings. I encountered the same issue on my X670E board, requiring a temporary fix until the kernel update was finalized and made accessible for your distribution. The most straightforward solution is inspecting the chip directly on the board, as variations between similar boards can exist. This approach won't ensure fan addressability but could prevent needing an extra hub. Still, I concur that configuring the fan curve via BIOS remains the simplest and most dependable method if you don’t need advanced customization, such as GPU temperature-based case fans. Edited July 27, 2025 by NoLeafClover Added more details, sorry.