improved I2C/SMBus warning message

This commit is contained in:
Cooper Hall
2024-05-03 04:08:11 +00:00
committed by Adam Honse
parent 6c4d901cb9
commit 1ca946f3eb

View File

@@ -1441,19 +1441,22 @@ void ResourceManager::DetectDevicesThreadFunction()
\*-------------------------------------------------*/
if(i2c_interface_fail)
{
const char* message = "<h2>WARNING:</h2>"
"<p>One or more I2C/SMBus interfaces failed to initialize.</p>"
"<p>RGB DRAM modules and some motherboards' onboard RGB lighting will not be available without I2C/SMBus.</p>"
const char* message = "<h2>Some internal devices may not be detected:</h2>"
"<p>One or more I2C or SMBus interfaces failed to initialize.</p>"
"<p><b>RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB Graphics Cards, will not be available in OpenRGB</b> without I2C or SMBus.</p>"
"<h4>How to fix this:</h4>"
#ifdef _WIN32
"<p>On Windows, this is usually caused by a failure to load the WinRing0 driver. "
"You must run OpenRGB as administrator at least once to allow WinRing0 to set up.</p>"
"<p>On Windows, this is usually caused by a failure to load the WinRing0 driver.</p>"
"<p>You must run OpenRGB as administrator at least once to allow WinRing0 to set up.</p>"
#endif
#ifdef __linux__
"<p>On Linux, this is usually because the i2c-dev module is not loaded. "
"You must load the i2c-dev module along with the correct i2c driver for your motherboard. "
"<p>On Linux, this is usually because the i2c-dev module is not loaded.</p>"
"<p>You must load the i2c-dev module along with the correct i2c driver for your motherboard. "
"This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.</p>"
#endif
"<p>See <a href='https://help.openrgb.org/'>help.openrgb.org</a> for additional troubleshooting steps if you keep seeing this message.<br></p>";
"<p>See <a href='https://help.openrgb.org/'>help.openrgb.org</a> for additional troubleshooting steps if you keep seeing this message.<br></p>"
"<h3>If you are not using internal RGB on a desktop this message is not important to you.</h3>";
LOG_DIALOG("%s", message);
}