Easier said than done. :-/ The only other hardware I have laying around here is a RasPi and a Cubitruck… I might just wait until fp publishes a build if nobody has an idea how to find out the cause for my problems.
I guess this will keep the module busy. Just stop it for unloading (I think…)
service acpid stop (is ubuntu using service? I more in the fedora/rhel region )
Not sure if I get you right. Purely rebooting probably won’t help as acpid will get started again… First I would need to make sure that the module is loaded with the correct parameter. But I’m not sure which program/process starts it and where and how to pass the parameter “fan_control=1” to it. I would guess placing a file in /etc/modprobe.d/ might be the right way to do it, but I don’t understand the syntax the existing files use.
stupid me, the module is called thinkpad_acpi, isn’t it:
simon@laptop:/sys/module$ cat thinkpad_acpi/parameters/fan_control
N
so that doesn’t look exactly like a 1…
Should the file in /etc/modprobe.d/acpid.conf and it’s content then be changed to thinkpad_acpi as well? On the other hand ps does show an acpid (which simply could be a daemon to control something):
Well, there’s a difference between the process name and the module name. They don’t need to be in sync, actually, they won’t be in sync. Acpid is the (generic) process for handling acpi events, and the module thinkpad_acpi understands your hardware and translates its events to the generic acpi implementation (might be simplified, but this should be it…)
So, the filename acpid.conf is irrelevant (except for it’s location and the suffix .conf), BUT, inside, the options will have to be
N, I would expect, means “no”, so, no fan control (what ever this means… Might be that the bios is in charge, and no operating system based program, might be it means no fan control at all… I really don’t know… Just give it a try with 1, or even Y
I did two reboots, trying 1 and Y. Both led to Y in thinkpad_acpi/parameters/fan_control and now I can again echo any level value without any error message, but still also without any effect. cat-ing always shows level 1 and 250rpm…
So fan control doesn’t seem to work.
yes, sounds like it’s broken. Only one thing. When you started compiling, did the fan actually get faster (acustically), or did the fan sound like always turning at the same speed?
It always stays at level 1, which is not even noticeable. Thus later on the throttling kicks in. I’ll try to see if I can do the uefi update tomorrow to see if it changes anything.