On EeePC 1015 PED (in Live mode), cpupower.service seemed to start too
early, before /sys/devices/.../scaling_available_governors was there,
and failed as a result. There were no such problems on faster machines,
but still.
Now cpupower.service will start only when 'scaling_available_governors'
file is available. cpupower.path unit handles this. If CPU frequency
scaling is not supported the file will never appear and cpupower.service
will not start at all, which is natural.
Should fix bug #4810.
cpupower will now select the governor automatically during the start of
the service, based on what is available. This can be overridden with
the variables in /etc/sysconfig/cpupower (see the comments there).
Apart from the update to version 3.14.31 itself, the following changes
were made:
* BFQ was updated to version 7r7.
* arch-x86-kernel-tsc-hide-warning.patch was removed as the issue had
been addressed in the mainline.
* A patch was added to increase inotify max_user_watch limit to 32768
(bug 4791).
* A patch was added that might help fix bug 4613 (no output to an
external monitor on HP EliteBook 820 G1).
