From: David Kremer <david.kremer.dk@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ERROR: could not insert 'w83627ehf': Device or resource busy
Date: Wed, 14 Mar 2012 15:32:21 +0000 [thread overview]
Message-ID: <4F60BA05.1060601@gmail.com> (raw)
In-Reply-To: <4F60A0AA.2050107@gmail.com>
On 14/03/2012 16:23, Guenter Roeck wrote:
> On Wed, 2012-03-14 at 10:23 -0400, David Kremer wrote:
>> On 14/03/2012 14:55, Guenter Roeck wrote:
>>> Most likely
>>>
>>> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
>>>
>> Thank you guenter.
>>
>> However, there is no clear explanation of how to fix this.
>>
>> Indeed, I load the linux module asus_atk0110 and ran again sensors-detect.
>>
> Hi David,
>
> Question is not what happens if you ran sensors-detect again; that is
> not the point and has nothing to do with the ability to load the module
> or not.
>
> Question is what you get when running the "sensors" command after
> loading the asus_atk0110 module.
>
>> The script ended up saying that the following modules was needed :
>>
>> Driver `w83627ehf':
>> * ISA bus, address 0x290
>> Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
>>
>> Driver `coretemp':
>> * Chip `Intel digital thermal sensor' (confidence: 9)
>>
>> However, there is still no way to load w83627ehf as I read your link.
>>
> Did you get the acpi error message as described ?
>
> If so, the link does provide the answer:
>
> "If you want to restore the old behaviour (which might be dangerous)
> add: "acpi_enforce_resources=lax" to the kernel cmdline when booting (or
> add it in grub.conf to make this permanent)."
>
> Just remember the "which might be dangerous". You might be better off
> with asus_atk0100 if it works for you.
>
> Guenter
>
>
>
I loaded the asus_atk0110 module into the kernel :
$ lsmod |grep atk
asus_atk0110 10131 0
However the interface is still using the coretemp linux module, so the
pwm config says me :
/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
I guess the only way to have my fancontrol working properly is to
enforce the old way with the kernel command line.
How do you plan to fix the situation in future releases ?
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-03-14 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 13:44 [lm-sensors] ERROR: could not insert 'w83627ehf': Device or resource busy David Kremer
2012-03-14 13:55 ` Guenter Roeck
2012-03-14 14:23 ` David Kremer
2012-03-14 15:23 ` Guenter Roeck
2012-03-14 15:32 ` David Kremer [this message]
2012-03-14 15:36 ` David Kremer
2012-03-14 15:46 ` Guenter Roeck
2012-03-14 15:57 ` Guenter Roeck
2012-03-14 16:19 ` David Kremer
2012-03-14 16:40 ` Guenter Roeck
2012-03-14 18:53 ` David Kremer
2012-03-14 19:01 ` David Kremer
2012-03-14 19:11 ` Guenter Roeck
2012-03-14 20:57 ` David Kremer
2012-03-14 23:06 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F60BA05.1060601@gmail.com \
--to=david.kremer.dk@gmail.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.