ilya-zlobintsev
Allow selecting alternate fan/PWM controller per GPU (custom hwmon/pwm index)
Please add an option to pick which fan a GPU controls, not just the default one. On cards with multiple fans or an AUX header, LACT can grab the wrong one; letting us choose fixes that.
Keep auto as default—manual selection would be optional and remembered per GPU.
No, it's not a bug. The card-side fan is read and displayed correctly. For example, on my RX 9070 XT, it's always 0 RPM. The point is that you can assign a different fan in the GUI, because some tuners (including me) use external fans. For example, I have three ‘NOCTUA NF-P12 redux 1700 PWM’ fans. If you could select these in the GUI (so that the standard is always automatic and there is an advanced function to select individual fans), this would certainly be a nice addition to LACT.
I understand that this is a feature request. I'm asking for a debug snapshot because it would contain the information about how the extra fans are exposed by the GPU, as I don't have such a setup that I could test on.
Understandable, but certainly not like that! WHY? Privacy risk in LACT debug snapshots! Current snapshots include host-identifying data (e.g. root=UUID=… from proc/cmdline), hostname, and IP/IPv6 traces, plus detailed PCI/VBIOS topology.
Public posting enables cross-project deanonymization and targeted social engineering.
Request: make privacy-mode default (mask hostname/IP/MAC/UUID/LUKS), exclude proc/cmdline and storage/network configs, switch to a allow-list of GPU-relevant files, and add a redaction step with a short manifest. Provide an explicit opt-in “verbose” mode with a warning.
Most of what you said is incorrect... the only identifiable information in LACT snapshots is the hostname (and it's only there because journalctl includes it when fetching service logs, which are vital for bug reports). There is no network info, user info or anything else of the sort. PCI topology of GPUs is included because that's required for looking at what's going on with the system, and kernel params have to be included because amdgpu overclocking options are configured through them. The GPU serial number is also explicitly excluded.
If you are really paranoid about this, you can go through the files in the snapshot and redact what you consider "private", but there really isn't a security risk here...
Thanks for the quick reply. Two concrete issues remain: • proc/cmdline exposes root=UUID=… (stable storage identifier). • journalctl adds the hostname (and sometimes IPv6 traces).
This isn’t theoretical: user-posted snapshots in public issues already contain these fields, so anyone can correlate hosts across repos and time.
Minimal changes fix it without losing diagnostics: use journalctl --no-hostname -o short, redact or drop proc/cmdline (or whitelist only amdgpu parameters via /sys/module/amdgpu/parameters/*), and exclude machine-id and any network/storage details by default. Suggest a default privacy mode with an explicit opt-in “verbose” mode and a warning.
Can't you do a retraction your self, manually...@MTrage ? I agree debug info shouldn't include identifying data, it's irrelevant. But you should also open a separate issue of this so everybody can benefit, and take apart.
