[SOLVED] Udev not triggered rule

nheolinkin · 2017-10-31 01:52:00

Today, I add a rule to set cpu governor to "performance" in /etc/udev/rule.d/50-scaling-governor.rules like this

SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor ' "
SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy1/scaling_governor ' "
SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy2/scaling_governor ' "
SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy3/scaling_governor ' "

Following to #udev page, it's said that udev automatically detected changes to rules files, so changes took effect immediately without requiring udev to be restarted. But I still did a "system reboot"
After that, nothing changed

So I run this on terminal then reboot again:
sudo udevadm control --reload

But result is still the same.
Do I miss something here? I'm new to Arch btw.

Last edited by nheolinkin (2017-10-31 06:09:11)

cfr · 2017-10-31 02:52:15

nheolinkin wrote:

After that, nothing changed

What did you expect to change exactly?

Are you sure you are not using intel_pstate?

Last edited by cfr (2017-10-31 02:52:52)

nheolinkin · 2017-10-31 03:20:20

cfr wrote:

nheolinkin wrote:
After that, nothing changed
What did you expect to change exactly?
Are you sure you are not using intel_pstate?

No, it was my mistake. I'm using Intel processor so I changed the "KERNEL" option to "intel_pstate".
But it's still "powersave" governor both in /sys/device/system/cpu/cpufreq/policy*/scaling_governor and /sys/device/system/cpu/cpu*/cpufreq/scaling_governor

nheolinkin · 2017-10-31 04:00:47

Ok, so I decided to use "cpupower" instead to switch cpu governor. But if it's possible, allow me to keep this thread "NOT SOLVED" until there is a solution for #udev problem that I mentioned above.
Thank you!

Last edited by nheolinkin (2017-10-31 04:01:48)

cfr · 2017-10-31 04:02:56

nheolinkin wrote:

But it's still "powersave" governor both in /sys/device/system/cpu/cpufreq/policy*/scaling_governor and /sys/device/system/cpu/cpu*/cpufreq/scaling_governor

https://wiki.archlinux.org/index.php/CP … ncy_driver

nheolinkin wrote:

Ok, so I decided to use "cpupower" instead to switch cpu governor.

The issue isn't udev or cpupower. You cannot control intel_pstate. You could disable it, if you insisted, but that is not at all recommended. cpupower will tell you what the governor is doing, but you cannot control it. The most you can do is nudge it a little using 'bias' settings.

Last edited by cfr (2017-10-31 04:05:58)

nheolinkin · 2017-10-31 06:08:20

cfr wrote:

The issue isn't udev or cpupower. You cannot control intel_pstate. You could disable it, if you insisted, but that is not at all recommended. cpupower will tell you what the governor is doing, but you cannot control it. The most you can do is nudge it a little using 'bias' settings.

That makes sense
Thank you for that info. QUESTION ANSWERED.

Arch Linux

#1 2017-10-31 01:52:00

[SOLVED] Udev not triggered rule

#2 2017-10-31 02:52:15

Re: [SOLVED] Udev not triggered rule

#3 2017-10-31 03:20:20

Re: [SOLVED] Udev not triggered rule

#4 2017-10-31 04:00:47

Re: [SOLVED] Udev not triggered rule

#5 2017-10-31 04:02:56

Re: [SOLVED] Udev not triggered rule

#6 2017-10-31 06:08:20

Re: [SOLVED] Udev not triggered rule

Board footer