[Feature Request] Improve RAM detection
<!-- Have something you would like to see added to OpenRGB? Let us know here To help us keep track of the requests please start the title with [Feature Request] --> ### Feature Request <!-- Please explain the new feature you would like to see added in detail. Explain how you think it should work and provide any mock-ups, code snippets, etc. that you think will help explain the feature. --> This is just a thought but it is based on data provided by one user on Discord that when the did multiple i2cdetect scans they did not always see the RAM controller addresses show up. This may explain why some systems have issues detecting sticks randomly (the probe of the address returned empty). [Source](https://discord.com/channels/699861463375937578/722900386028978186/745233668783734836) ![image](/uploads/1751eeae8c4c33832d7657660b0a1052/image.png) ![image](/uploads/d41bdeb9c2e2eb74a0667cba7e556694/image.png) Does it make sense to attempt to probe each location a few times and enable the controller if any of them return valid? I do see the SPD info (0x50-0x53) so maybe we use these and then search for a controller as another option.
issue