On Tuesday 17 July 2007 17:01, Bob S wrote:
> On Sunday 15 July 2007 10:21:32 Rajko M. wrote:
> > On Sunday 15 July 2007 00:26, Bob S wrote:
> > > Hello SuSE people,
> > >
> > > Been trying to get my sensors.conf file to report accurately on my
> > > system.
.....
> > It would be good to read
> > http://www.lm-sensors.org/wiki/FAQ
> > section 3. Problems.
> > http://www.lm-sensors.org/wiki/FAQ/Chapter3
....
> Nothing in the above URL's about these problems.
>
> .... Maybe we should take this off list.
If you want to. We can post result in this thread.
> > Short: Sensors will show what you set in sensors.conf, and that can be
> >correct or out of way.
>
> Welllll. not exactly,
What I meant is that you can do whatever math you want on raw values. You get
those values if /etc/sensors.conf has only one line:
chip "w83627thf-*"
and than run
sensors -s
and than
sensors
Make backup copy of original. Make one copy that has only your chip section,
it will be easier to edit.
To create one line sensors.conf run:
echo chip \"w83627thf-*\" > /etc/sensors.conf
> I made some changes today in sensors.conf and one of
> the changes is not being honored. To bring you up to date. Today, I just
> commented out the -12V parameter because the bios doesn't report it and
> that worked OK.
BIOS might not use all values even if they are present. The previous oneliner
sensors.conf will give you all values that are reported by chip.
> But,,,,,I created a new problem when I removed the comment
> lines for in0, the Vcore. See that in my latest sensors printout just
> below: Still have the alarm problem for the 3.3V parameter.
>
> EasyStreet:/ # sensors
> w83627thf-isa-0290
> Adapter: ISA adapter
> VCore: +1.54 V (min = +1.94 V, max = +1.94 V) ALARM
This is Vcore, but min and max values are wrong.
See
/usr/share/doc/packages/sensors/vid
to understand what is going on with this, and your chip driver should be able
to recognize command
set vrm 2.4
according to above file put that right below section title:
chip "w83627thf-*" "w83637hf-*"
set vrm 2.4
> +12V: +12.28 V (min = +10.82 V, max = +13.19 V)
> +3.3V: +0.45 V (min = +3.14 V, max = +3.47 V) ALARM
Simply wrong input is taken as 3.3 V. From raw values listing and more reading
it should be possible to find input line.
> +5V: +5.09 V (min = +4.75 V, max = +5.25 V)
> V5SB: +5.16 V (min = +4.76 V, max = +5.24 V)
> VBat: +3.62 V (min = +2.40 V, max = +4.08 V)
> Sys Fan: 3183 RPM (min = 2800 RPM, div = 2)
> CPU Fan: 5672 RPM (min = 5487 RPM, div = 2)
> M/B Temp: +46°C (high = +86°C, hyst = +2°C) sensor = thermistor
> CPU Temp: +33.5°C (high = +80°C, hyst = +75°C) sensor = diode
For CPU temperature you should try other options for sensor
until you get what BIOS reports. I doubt it is diode, as above report tells.
*****************************************************************************
# set up sensor types (thermistor is default)
# 1 = PII/Celeron Diode; 2 = 3904 transistor;
# 3435 = thermistor with Beta = 3435
# If temperature changes very little, try 1 or 2.
# set sensor1 1
# set sensor2 2
# set sensor3 3435
******************************************************************************
...
> OK,,Here is what is reported in the bios"
>
> CPU 55 degrees C
> Sys Tmp 45 degrees C
> CPU Fan 5720 rpm
> Sys Fan 3185 rpm
> Vcore =1.54V
> +5 =5.25V
> +12 =11.8V
> +3.3 =3.4V
>
> > Also the section of /etc/sensors.conf that is used with your sensor:
> > chip w83627thf-*
>
> OK, Here is sensors.conf: (Mind you I have made changes to this conf file)
> I uncommented and commented in0 several times and still come up with the
> crazy min/max levels for Vcore as shown above.
This has to wait until you see raw values.
> > What is your motherboard and chipset?
> # lspci -v
....
> K8T800Pro
> Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
> Micro-Star International Co., Ltd. K8T NEO 2 motherboard
...
MSI is not very verbose about hardware. Maybe if one asks, and explain details
why they are needed, we can get some information.
--
Regards,
Rajko.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
