diff --git a/ResourceManager.cpp b/ResourceManager.cpp index bbe2bfe0..5c041698 100644 --- a/ResourceManager.cpp +++ b/ResourceManager.cpp @@ -1441,19 +1441,22 @@ void ResourceManager::DetectDevicesThreadFunction() \*-------------------------------------------------*/ if(i2c_interface_fail) { - const char* message = "

WARNING:

" - "

One or more I2C/SMBus interfaces failed to initialize.

" - "

RGB DRAM modules and some motherboards' onboard RGB lighting will not be available without I2C/SMBus.

" + const char* message = "

Some internal devices may not be detected:

" + "

One or more I2C or SMBus interfaces failed to initialize.

" + "

RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB Graphics Cards, will not be available in OpenRGB without I2C or SMBus.

" + + "

How to fix this:

" #ifdef _WIN32 - "

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.

" + "

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.

" #endif #ifdef __linux__ - "

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. " + "

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. " "This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.

" #endif - "

See help.openrgb.org for additional troubleshooting steps if you keep seeing this message.

"; + "

See help.openrgb.org for additional troubleshooting steps if you keep seeing this message.

" + "

If you are not using internal RGB on a desktop this message is not important to you.

"; LOG_DIALOG("%s", message); }