search

nagisa / msi-rgb

Linux utility for controlling RGB header on select MSI motherboards
ISC License
418 stars 40 forks source link

Not working for MSI X370 Gaming pro Carbon #5

Open Souks opened 7 years ago

Souks commented 7 years ago

After many tests, this dont work for MSI X370 Gaming pro Carbon (with Debian). Did you plan to make it work for X370 chipsets ? You'll be my savior x)

nagisa commented 7 years ago

Hi,

How does the tool fail? Does it print any errors? Does it fail without doing anything?

RGB header is not controlled by the chipset, but I don't really have the resources to get a board myself to figure out why it doesn't work for you.

On Jun 5, 2017 12:05 PM, "Souks" notifications@github.com wrote:

After many tests, this dont work for MSI X370 Gaming pro Carbon (with Debian). Did you plan to make it work for X370 chipsets ? You'll be my savior x)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nagisa/msi-rgb/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AApc0nyxvP6F1j9dhHrsDJAoG3kgTuzZks5sA8TJgaJpZM4NvziQ .

tenten8401 commented 7 years ago

It works on my X370 SLI Plus, so I don't think it's an issue with the chipset specifically.

Ben64 commented 6 years ago

It fails without doing anything. Would very much appreciate this working. I can test anything you'd want.

nagisa commented 6 years ago

It is fairly hard to do anything without having some hardware, and cheap pre-owned (maybe not entirely functional) boards are impossible to come-by yet.

dcerisano commented 6 years ago

For about $10 you can connect WS2812B addressable RGB strips to any USB header on any motherboard runnning any OS.

You just need an ATTiny chip and the opensource RGB firmware. You can get a prefab one here.

Proprietary SIO chip controlled RGB headers are locked to manufacturer bloatware that sucks, which is why you have come here.

Ben64 commented 6 years ago

That's great, but still doesn't let me control the LEDs on the motherboard.

@nagisa if there's anything I can do to help you get this to work (besides sending you my motherboard) let me know.

dcerisano commented 6 years ago

That's the point - the proprietary motherboard LEDs are not addressable, and the proprietary software is locked to a single platform and is terrible. It is far easier and better to replace them with standard USB addressable RGB hardware and opensource cross-platform software.

Ultimately msi-rgb should serve just one very valuable purpose - to turn off the proprietary LEDs. Face it, you came to this thread because you want to design your own case lighting.

nagisa commented 6 years ago

Since the LEDs are on by default I see the use case of turning them off a good enough reason to want this tool to work (as you can't just unplug the motherboard LEDs without desoldering them.)

On Nov 8, 2017 8:34 AM, "Dominic Cerisano" notifications@github.com wrote:

That's the point - the leds on the motherboard are not addressable, and the control software is proprietary corporate bloatware. It is easier to replace them with an WS2812 addressable lighting system.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nagisa/msi-rgb/issues/5#issuecomment-342724196, or mute the thread https://github.com/notifications/unsubscribe-auth/AApc0uVz7vhuRUu7yFsBzW8R1ETd9xH4ks5s0UuKgaJpZM4NvziQ .

Ben64 commented 6 years ago

@dcerisano nobody is saying proprietary LEDs are awesome, the fact remains that the ones on the board are unchangeable without the MSI software, which is lame.

Therefore, I'd like this tool to work for more boards.

dcerisano commented 6 years ago

The only solution is to buy a much cheaper mobo without any leds and just buy standard USB addressable RGB hardware and opensource cross-platform software (which will always be far superior).

The amount of work involved to reverse engineer seriously weird proprietary SIO RGB controllers is simply not worth it - the mobo manufactures are obviously deliberately making this difficult. @nagisa and I have the exact same board (MSI B350 Mortar), except his is the white "Arctic" version and I had to hack the bejayzoos out of his code to make it work on mine!

In fact, when manufacturers include RGBs on their mobos and devices that are on by default and require their crapware to turn them off, they are effectively making it difficult to design your own case lighting. They are claiming your PC as their lighting brand territory!

I will never buy another mobo or device with proprietary RGB. I would like to thank @nagisa for this project, without which I would not have come to this conclusion, and never found that I can easily fab way better lighting on my own.

tenten8401 commented 6 years ago

Gigabyte does RGB control in the BIOS, which is what I've been using.

sybohy commented 6 years ago

X399 here. also happy to help.

mmenanno commented 6 years ago

I've also got this installed with a MSI X370 Gaming Pro Carbon. If anyone finds a solution or needs help for testing. Lemme know.

mmenanno commented 6 years ago

Alright so I tested with every single one of the commands listed. None of the colours would change BUT if I use the Happy Easter command sudo ./target/release/msi-rgb 58e01c0d 504fdcb9 e4aa75eb --blink 2 -d 32 it does make the light under my ram, and under my graphics card blink. I don't know if this helps, but it shows that at least some information is passing on. If I use any of the other commands it goes back to default. I shot a quick video of it below:

https://monosnap.com/file/rdplK3OZU0J2r9OwaoEIrT2BZDeGp1

EDIT: Pulse also works

nagisa commented 6 years ago

it does make the light under my ram, and under my graphics card blink. I don't know if this helps, but it shows that at least some information is passing on. If I use any of the other commands it goes back to default. I shot a quick video of it below:

and from #24:

I can disable it and make it pulse but that's it.

Amusing, this makes me suspect that there may be multiple register blocks for controlling RGB and I’m only aware of one of them (which happens to blink that led under RAM/GPU for this mobo). That would explain why so many different motherboards do not work.

2e gives me this error and using --ignore-check doesn't change any LED:

Unsurprisingly, as there’s no chip on the other end of that port. (the 0xffff self-identification is a dead giveaway)

staeffn commented 5 years ago

Hello, x370 gaming pro carbon board here - as stated before, I thought it to not work at all and eventually tried the pulse command. I tested with red, as it would be easier to notice. Paniced for a moment then, bc some little LEDs looking like error LEDs are on in a bright red. After a cpl of seconds I noticed them pulsing. Tried to change them to green, no success. Adding 2 pics, maybe that makes it better to understand. Not sure if that's a result from my efforts to change the RGB colors, but I think they haven't been showing before.

https://imgur.com/a/suuVXaN

Board: Micro-Star International Co., Ltd. X370 GAMING PRO CARBON (MS-7A32) Found `Nuvoton NCT6795D Super IO Sensors' Success!

staeffn commented 5 years ago

Add: with msi-rgb -x ff ff ff (couldn't run -x without color arguments) it deactivates the red LEDs. So i guess the adressing is wrong. The MSI gaming app won't launch for me and I'm also worried about the LEDs turned off. Simply clearing cmos and resetting my BIOS didn't turn the red pulsing off, so I guess at least some of my onboard LEDs are turned off for good at the moment and won't turn on again on alerts or whatever.

nagisa commented 5 years ago

Simply clearing cmos and resetting my BIOS didn't turn the red pulsing off, so I guess at least some of my onboard LEDs are turned off for good at the moment and won't turn on again on alerts or whatever.

The SI/O chip has no inherent memory and it does not share memory with the CMOS-powered firmware storage, but it will remember its register values as long as there is enough charge present for it to not reset. In order to reset the SI/O chip follow these steps:

  1. After shutting down your computer, flip the switch on your PSU to off (or pull the power cable out of the power outlet);
  2. Hold the power on button for a little while (you’ll notice fans spinning up briefly even though PSU is powered off);
  3. Turn on the PSU back and power on your computer as usual.

After these steps most changes made to the SuperI/O should be cleared.

staeffn commented 5 years ago

I'm oldschool i guess, did all that while resetting cmos. I did not remove the battery though. Also I honestly have little to no clue about the lighting stuff, hence taking a look at it 1 year after buying the stuff. The leds were still pulsing in red. And after msi-rgb -x they are out. Both in my OS and before booting it and while in bios if I'm not mistaken. Will investigate further after dinner. :) The rest was just a wild guess, the adressing thing, msi-rgb does change lights, just different ones on the x370 gpc

staeffn commented 5 years ago

Just double checked, turned my PSU off and unplugged the cable again, after turning everything back on the LEDs are still on until I deactivate them with msi-rgb -x. Both before booting an OS and in a booted OS. So I guess it has to be saved somewhere/-how.

Also tried flashing the bios, the lights are still lit.

staeffn commented 5 years ago

Finally got MSI Gaming App up and running. seems like what i mistakenly took for error leds are actually part of the lighting. Already forgot their name though. I was able to turn them off under windows when they were still turned on. Now they're off but all colors I set under windows (even for my trident-z rgb which I set seperately with the trident program under windows but I have never once touched them under linux) are still in place. Maybe they put smth in place to store settings with one of the firmware updates?

dcerisano commented 5 years ago

You can reset SIO by turning off the PSU and then holding down the power button for a few seconds. Like others, you found that the proprietary bloatware is really the only way to fully control proprietary RGB.

Not surprisingly, the very same RGB bloatware is now being used as a new attack vector for malware. RGB viruses!

So that is a new reason to pursue the msi-rgb approach to eliminating the dependency on bloatware. But better yet is to simply design and build your own aRGB lighting controller firmware and applications.