You are not logged in.
Hello,
I've read many posts about how booting with this kernel parameter is unsafe, or to be more precise damaging to the hardware. Several times it was mentioned that this was only a maybe (hardware specific) and I never really found a concrete explanation on what it can do to your hardware.
I'm using a Gigabyte Aorus B550m Elite motherboard with 16 GB of HyperX Fury RAM (2 sticks), and the only way (as far as I know) that I can get to control of their RGB on Linux is through OpenRGB, which requires this kernel parameter to detect them. This is why I would want to have this parameter active.
Additionally, I already booted my system with this parameter once, and there wasn't anything that seemed off. So if it's something plain to see I must've missed it or there aren't any issues at all.
Last edited by Zeash (2021-06-27 17:00:19)
Offline
Trying to figure this out myself.
Offline
Anyone got some info on the matter?
Offline
I doubt there's a generally correct answer here and will depend on your MB and how it reacts.
It's unlikely to be relevant if you just do read access but since your explicit intention is to write values that are otherwise blocked then there will be that risk, whatever that may entail. Have you asked this in the relevant OpenRGB channels? I'd assume they'd be able to answer this best.
Offline
This question comes up every now and then.
The best explanation/summary I've found is in a related bug report, comment 37 here: https://bugzilla.kernel.org/show_bug.cgi?id=204807#c37 .
That being said, there are motherboards which allow accessing their HW sensors chips without using this parameter (such as MSI B550 Tomahawk). Personally, I wouldn't risk using the parameter for RGB (H/W sensors and fan control is a bit more serious issue), but YMMV.
Online
I'm waiting for a response in the OpenRGB subreddit, in the meantime here's the post which got me to consider this parameter in the first place. The motherboard in use is also pretty much the same as mine except it's ATX and v.2. The RAM is not the exact same model though, the one in the post has a speed of 3200MHz while mine has 3000Mhz. I doubt this matters though.
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/978
Last edited by Zeash (2021-05-27 08:42:39)
Offline
I've been running it for a while now, no real issues on my own linux box. I guess people can use this as insurance for this particular combination.
Offline