Question

Question

[phil]

Basicly, you insmod the driver, and you should see some files in
/proc/sys/dev/sensors/bt869*/ .  Then, you put your X-server in a NTSC
resolution, and then set the appropriate values in the files in the
directory noted above (e.g. "echo 0 > colorbars", and set ntsc/pal,
resolution, etc.).  Check the output.  If nessesary, you may need to
select the appropriate output port if you don't get anything.  Some
modifications to the driver were recently submitted to CVS (see our
download page for instruction on CVS), so you might try that.

Good luck!


Phil


On Thu, Feb 14, 2002 at 02:26:32PM -0500, Hoopez wrote:
> 
> Hi,                                                                                                                                                       
> I have a question about voodoo 3 cards and s-video tv-out in
> linux that i hope you can answer. I ran through the howto (i'm in america,
> ntsc) and i'm at the point just before you restart the X server. I'm out of sync (or whatever                                                                                  
> you call it), and then when i hit ctrl-alt-number_pad_+, i can see the                                                                                    
> colorbars for one second, until the x server restarts, then it goes back                                                                                  
> to the out-of-sync display. I was wondering if you had any advice on what                                                                                 
> to do or where I should look? I'm running Redhat 7.2 on an Athlon K7,                                                                                     
> Voodoo 3 3000, kernel 2.4.7-10 (i also tried it on 2.4.17)                                                                                                
>                                                                                                                                                           
> If you can help me, thanks, if not, thanks again!                                                                                                         
> Matt Hoopes         

-- 
Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR
   phil@netroedge.com -- http://www.netroedge.com/~phil
 PGP F16: 01 D2 FD 01 B5 46 F4 F0  3A 8B 9D 7E 14 7F FB 7A

question

[Paul Aviles]

Hello all,

Thanks to all for your answers and support. I was finally able to figure out 
my problems with the .spec file and I am now creating the rpms.

One question I have is that I have two indentical systems from the same 
manufacturer, Tyan. One has a Celeron CPU and the other has a P4 with HT, 
but the motherboards are the same. On one unit I must use a lm85-* in 
sensors.conf and the the other with a adt7463-* for the chips section or the 
values don't make sense.

Could the different CPU's be causing lmsensors to get confused? I even ran 
the detect routines and came with the same results. What else could I do to 
check this?

Thanks so much!!

Paul

Sample report.

lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 1480
+2.6V:      +2.62 V  (min =  +2.47 V, max =  +2.73 V)
CPU Volt: +1.31 V  (min =  +1.25 V, max =  +1.40 V)
+3.3V:      +3.35 V  (min =  +3.13 V, max =  +3.47 V)
+5V:       +5.05 V  (min =  +4.74 V, max =  +5.26 V)
Fan2:      8424 RPM  (min = 4800 RPM)
Fan1:      6136 RPM  (min = 4800 RPM)
Fan3:      9294 RPM  (min = 2200 RPM)
CPU Temp:    +47?C  (low  =    +5?C, high =   +68?C)
Loc Temp:     +36?C  (low  =    +5?C, high =   +40?C)
Sys Temp:      +38?C  (low  =    +5?C, high =   +50?C)
vid:      +1.325 V  (VRM Version 9.1)

eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 1480
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-53
Adapter: SMBus I801 adapter at 1480
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512




-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

question

[Jean Delvare]

Hi Paul,

> One question I have is that I have two indentical systems from the
> same  manufacturer, Tyan. One has a Celeron CPU and the other has a P4
> with HT,  but the motherboards are the same. On one unit I must use a
> lm85-* in  sensors.conf and the the other with a adt7463-* for the
> chips section or the  values don't make sense.
> 
> Could the different CPU's be causing lmsensors to get confused? I even
> ran  the detect routines and came with the same results. What else
> could I do to  check this?

There's nothing wrong with that. Both chips are mostly compatible, so
Tyan may simply have switched at some point in time for some reason
(price or availabilty for example). You can notice that both chips are
supported by the same driver (lm85).

You can share a section of sensors.conf among several chips by simply
giving it more than just one chip name. If you take a look at the
default configuration file, that's exactly what we do for the lm85
driver:

chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"

   set temp1_max 50

(...)

Just do that for your own file and you will have a single file to
maintain for both boards.

-- 
Jean Delvare
http://khali.linux-fr.org/

question

[Philip Pokorny]

I think the chips are even pin compatible which means that Tyan could 
concievably switch from vendor to vendor for each lot of boards.

Reading the lm85 docs, I see that there are a couple of documented 
"enchancements" in the ADT7463 over the LM85, so it's probably a better 
chip anyway.

:v)

Jean Delvare wrote:

>Hi Paul,
>
>  
>
>>One question I have is that I have two indentical systems from the
>>same  manufacturer, Tyan. One has a Celeron CPU and the other has a P4
>>with HT,  but the motherboards are the same. On one unit I must use a
>>lm85-* in  sensors.conf and the the other with a adt7463-* for the
>>chips section or the  values don't make sense.
>>
>>Could the different CPU's be causing lmsensors to get confused? I even
>>ran  the detect routines and came with the same results. What else
>>could I do to  check this?
>>    
>>
>
>There's nothing wrong with that. Both chips are mostly compatible, so
>Tyan may simply have switched at some point in time for some reason
>(price or availabilty for example). You can notice that both chips are
>supported by the same driver (lm85).
>
>You can share a section of sensors.conf among several chips by simply
>giving it more than just one chip name. If you take a look at the
>default configuration file, that's exactly what we do for the lm85
>driver:
>
>chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"
>
>   set temp1_max 50
>
>(...)
>
>Just do that for your own file and you will have a single file to
>maintain for both boards.
>
>  
>

[lm-sensors] Question

[sc2]

hello
i need the mtp008 module, how i can compile it into the kernel, to use 
sensors?
normal compile does not work .
thanks
ps: its a 2.6 kernel
bye
richard 

[lm-sensors] Question

[Rudolf Marek]

Hello

> i need the mtp008 module, how i can compile it into the kernel, to use 
> sensors?
> normal compile does not work .
> thanks
> ps: its a 2.6 kernel

This driver has not been ported to 2.6 kernel. You can do it yourself, offer 
some reward for it or pay it. Currently we do not have any free time to do that 
on "free" basis. But of course if you want to do it yourself we will help you.

If you need just quick and dirty solution, you can use i2cdump util to read a 
raw register value and convert it to a temperature with a shell script.

Regards
Rudolf

[lm-sensors] question

[Ari Illikainen]

Could someone explain which sensor is for what and if you might think
something is wrong.
For me it seems strange that something at 22°C has a critical limit
+112.0°C, while something at 70.0°C has a limit 90.0°C.
In my logic the two 112°C limits should be for CPU0 and CPU1, but the other
two is a bit of a mystery for me.
Anyways something feels wrong about this, please help

Adapter: Virtual device
temp1:        +22.0°C  (crit = +112.0°C)
temp2:        +79.0°C  (crit = +112.0°C)
temp3:        +70.0°C  (crit = +90.0°C)
temp4:        +71.0°C  (crit = +107.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +72.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:       +72.0°C  (high = +105.0°C, crit = +105.0°C)

/ Ari
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] question

[Ari Illikainen]

Further information:
I am running crunchbang x64 on a HP Elitebook 6930p with Ati Mobility
Radeon HD 3450


2013/11/19 Ari Illikainen <illikainenak@gmail.com>

> Could someone explain which sensor is for what and if you might think
> something is wrong.
> For me it seems strange that something at 22°C has a critical limit
> +112.0°C, while something at 70.0°C has a limit 90.0°C.
> In my logic the two 112°C limits should be for CPU0 and CPU1, but the
> other two is a bit of a mystery for me.
> Anyways something feels wrong about this, please help
>
> Adapter: Virtual device
> temp1:        +22.0°C  (crit = +112.0°C)
> temp2:        +79.0°C  (crit = +112.0°C)
> temp3:        +70.0°C  (crit = +90.0°C)
> temp4:        +71.0°C  (crit = +107.0°C)
>
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:       +72.0°C  (high = +105.0°C, crit = +105.0°C)
> Core 1:       +72.0°C  (high = +105.0°C, crit = +105.0°C)
>
> / Ari
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] question

[Guenter Roeck]

On Tue, Nov 19, 2013 at 04:38:25PM +0100, Ari Illikainen wrote:
> Could someone explain which sensor is for what and if you might think
> something is wrong.
> For me it seems strange that something at 22°C has a critical limit
> +112.0°C, while something at 70.0°C has a limit 90.0°C.
> In my logic the two 112°C limits should be for CPU0 and CPU1, but the other
> two is a bit of a mystery for me.
> Anyways something feels wrong about this, please help
> 
> Adapter: Virtual device
> temp1:        +22.0°C  (crit = +112.0°C)
> temp2:        +79.0°C  (crit = +112.0°C)
> temp3:        +70.0°C  (crit = +90.0°C)
> temp4:        +71.0°C  (crit = +107.0°C)
> 
Unfortunately, ACPI doesn't have the habit of actually explaining such readings.
Best you can do is to extract and disassemble the DSDT, and hope that enough
information is in there to determine the sensors associated with those values.

What is the system ? Is this a laptop or a PC ? Also, what is the CPU ?

Guenter

> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:       +72.0°C  (high = +105.0°C, crit = +105.0°C)
> Core 1:       +72.0°C  (high = +105.0°C, crit = +105.0°C)
> 
> / Ari
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors