Ewout van Mansom

> Oh, looking at the code a bit further, currently that board doesn't automatically ignore ACPI issues. Can you check `dmesg` and see if you have a line like >...

Output of `lshw`: There are three versions of this exact motherboard. This motherboard is a rev 1.3 model. I'm not entirely sure if the other revisions have different ITE chips...

I think `gigabyte_wmi` might be the cause of the conflict, not sure.

> @emansom the actual conflict is basically a stupid setup by Gigabyte, as they have claimed the address space, but often don't use it. In this case they are almost...

Further digging. This is weird: ```shell 22:46 root@am5ws ~# echo 1 > /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm1_enable 22:47 root@am5ws ~# cat /sys/devices/platform/it87.2624/hwmon/hwmon5/pwm1_enable 0 22:47 root@am5ws ~# ```

Do you by chance know any USB (preferably header based) or PCI-e based PWM controllers, available as consumer products that have good quality mainline kernel drivers?

> Unfortunately no. @frankcrawford Came across this, will buy the Micro version and test it with a Noctua fan hub (NA-FH1) next month. It seems like the most viable solution...

Is the width in the `GtkStringList` [from the ui definition file](https://github.com/wwmm/easyeffects/blob/efcaefeacbe0d3b2f6647172fb219a5a6ec3955b/data/ui/autogain.ui#L107-L117) maybe decided at compile-time instead of run-time?

> and maybe Meetkundig instead of Geometrisch - 1 char shorter > > > Meetkundig gem. (MSI) > > So maybe this is a solution. > Committed these changes to...

> For what it's worth, you could kind of do your own workaround without any code changes by setting d3d9,dxgi,d3d11 to build-in in winecfg for only the launcher.exe, and then...