-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set fan mode/Dell XPS 7390/dell_smm
/pwm1_enable
#229
Comments
fan2go tries to set |
You are right. I think simply using |
I'm re-opening this issue because maybe some other people may help. I'm unsure if this is simply a permission issue or something else. I found that writing So I think the permission error message originated from line 163 when trying to read the value: Lines 160 to 169 in 0a6ea59
|
@markusressel Just to give an update. If my understanding is correct, for Dell fans that rely on the See: https://docs.kernel.org/hwmon/dell-smm-hwmon.html. In the table of available |
Hmm interesting 🤔 I am not sure if we can test for this somehow in code and ignore the validation logic in case the As I am not able to test this with real hardware myself, we would need to test it on yours. I will let you know when I have something ready. |
Describe the bug
fan2go fan init -i <fan>
andfan2go
gave errors complaining being unable to set fan mode throughpwm*_enable
.To Reproduce
$ fan2go detect
(I'm only posting relevant sections here):Click me to expand
$ cat /etc/fan2go/fan2go.yaml
:Click me to expand
# fan2go fan init -i fan-1
, I gotClick me to expand
Expected behavior
No error messages.
Desktop (please complete the following information):
uname -a
: 6.3.2-arch1-1sensors -v
: sensors version 3.6.0+git with libsensors version 3.6.0+gitfan2go version
: commit c20619eAdditional context
According to
hwmon
's documentation, fordell_smm
, the filepwm1_enable
does not accept0
. A value of1
topwm1_enable
means disabling the automatic BIOS fan control, while2
means enabling such automatic control. See here.The text was updated successfully, but these errors were encountered: