From: Stefan Sassenberg <stefan.sassenberg@gmx.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] No sensors found >2.6.21, w83627hf, ICH6
Date: Wed, 05 Mar 2008 10:31:30 +0000 [thread overview]
Message-ID: <47CE7682.9090106@gmx.de> (raw)
In-Reply-To: <47CD5B89.1070302@gmx.de>
Jean Delvare wrote:
> Hi Stefan,
>
> On Tue, 04 Mar 2008 15:24:09 +0100, Stefan Sassenberg wrote:
>> I have a problem making lm-sensors work on my system. It's a slightly
>> old debian where I updated some packages and now use sensors and
>> libsensors of version 2.9.1. I used to run a 2.6.21 kernel where sensors
>> finds some chip and also shows fan speed and temperature values.
>
> "some chip" doesn't tell us much... Can you please provide the complete
> output of "sensors"?
w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.24 V (min = +0.70 V, max = +1.87 V)
+12V: +11.98 V (min = +6.51 V, max = +9.18 V) ALARM
+3.3V: +3.38 V (min = +0.26 V, max = +0.19 V) ALARM
+5V: +5.04 V (min = +2.72 V, max = +3.28 V) ALARM
-12V: -12.20 V (min = +3.27 V, max = -14.75 V) ALARM
V5SB: +5.05 V (min = +4.27 V, max = +1.61 V) ALARM
VBat: +3.22 V (min = +3.04 V, max = +3.92 V)
fan1: 0 RPM (min = 1035 RPM, div = 8) ALARM
CPU Fan: 0 RPM (min = 1171 RPM, div = 8) ALARM
fan3: 0 RPM (min = 3183 RPM, div = 8) ALARM
M/B Temp: -48°C (high = +29°C, hyst = +14°C) sensor =
thermistor
CPU Temp: +108.5°C (high = +120°C, hyst = +115°C) sensor = diode
temp3: -48.0°C (high = +120°C, hyst = +115°C) sensor =
thermistor
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm enabled
The values are nonsens, of course, but I wanted to do first things first.
>
>> Then I upgraded the kernel to a 2.6.23 and always get the error message
>> "No sensors found". The board is an MSI board and it has an 82801 ICH6
>> chipset.
>
> What is the exact motherboard model?
"Hetis 915 A7137IMS V1.3 02/10/06"
>
>> sensors-detect advises me to modprobe w83627hf, which I do, but the
>> result is the above.
>
> Any message in the kernel logs when you modprobe w83627hf? Does the
> modprobe itself fail or succeed? If it fails, what's the error message?
When I modprobe, a line is added to /var/log/dmesg:
w83627hf: Found W83627THF chip at 0x290
There's no message on stdout or stderr.
>
>> I installed a gentoo on the same machine, where it worked, and made an
>> lsmod, which showed w83627hf, hwmod and hwmon_vid. I took the kernel
>> config file and applied it to the kernel from kernel.org to build the
>> same kernel for my debian. I modprobed the very same modules but failed.
>
> What kernel is your gentoo system running?
2.6.23-r9 (the latest "not-masked" 2.6.23)
>
>> What can I do to find the solution?
>
> Please compare /proc/ioports between a system where the w83627hf driver
> works for you and a system where it doesn't. I'd suspect a resource
> conflict.
Using the 2.6.21.5 kernel:
0295-0296 : pnp 00:09
0295-0296 : w83627hf
Using the 2.6.23.14 kernel:
Before modprobing:
...
0295-0296 : pnp 00:09
...
After modprobing:
...
0295-0296 : w83627hf
0295-0296 : pnp 00:09
0295-0296 : w83627hf
...
Stefan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-03-05 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 14:24 [lm-sensors] No sensors found >2.6.21, w83627hf, ICH6 Stefan Sassenberg
2008-03-04 15:00 ` Jean Delvare
2008-03-05 10:31 ` Stefan Sassenberg [this message]
2008-03-05 14:28 ` Jean Delvare
2008-03-05 14:57 ` Stefan Sassenberg
2008-03-05 15:04 ` Jean Delvare
2008-03-05 16:09 ` Stefan Sassenberg
2008-03-05 16:26 ` Jean Delvare
2008-03-05 17:25 ` Stefan Sassenberg
2008-03-06 8:31 ` Jean Delvare
2008-03-07 15:30 ` Stefan Sassenberg
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=47CE7682.9090106@gmx.de \
--to=stefan.sassenberg@gmx.de \
--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.