* sensors
2005-05-19 6:23 sensors Gyimesi Attila
@ 2005-05-19 6:23 ` Mark D. Studebaker
2005-05-19 6:23 ` Sensors mdlinfa
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Mark D. Studebaker @ 2005-05-19 6:23 UTC (permalink / raw)
To: lm-sensors
see FAQ #4.12
Gyimesi Attila wrote:
>
> Hi!
>
> I have a problem with sensors. There is 6 celsius degree difference
> between in the BIOS menu and what the sensors says.
>
> I have asus a7a266 and amd XP 1600+ .
>
> sensors says: CPU: +45.0?C (limit = +60?C, hysteresis = +50?C) sensor = thermistor
> BIOS says: 51.0?C
>
> why?
>
> bye
> JiM
> My E-MAIL address :
> jim@ond.vein.hu
^ permalink raw reply [flat|nested] 10+ messages in thread* Sensors
2005-05-19 6:23 sensors Gyimesi Attila
2005-05-19 6:23 ` sensors Mark D. Studebaker
@ 2005-05-19 6:23 ` mdlinfa
2014-01-22 23:27 ` [lm-sensors] sensors Ryan
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: mdlinfa @ 2005-05-19 6:23 UTC (permalink / raw)
To: lm-sensors
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20030325/c3877b1c/attachment.html
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
2005-05-19 6:23 ` sensors Mark D. Studebaker
2005-05-19 6:23 ` Sensors mdlinfa
@ 2014-01-22 23:27 ` Ryan
2014-01-23 0:37 ` Ryan
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Ryan @ 2014-01-22 23:27 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
hello,
I'm having an issue getting the correct output from sensors on my asus
laptop. I'm running xubuntu on it and I've attached the following files
hoping it gives you all the information you may need.
grub - my /etc/default/grub
modules_file.txt - my /etc/modules
sensors_output.txt - output from running 'sudo sensors'
lshw_short.txt - hardware information from lshw command
Please let me know if you need more information and thank you for your
time. I greatly appreciate any advise.
Ryan
[-- Attachment #2: grub --]
[-- Type: text/plain, Size: 1241 bytes --]
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
# GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=" radeon.dpm=1 "
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
[-- Attachment #3: modules_file.txt --]
[-- Type: text/plain, Size: 308 bytes --]
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
rtc
i2c-dev
i2c-i801
cpuid
# Generated by sensors-detect on Wed Jan 22 17:12:33 2014
# Chip drivers
coretemp
[-- Attachment #4: sensors_output.txt --]
[-- Type: text/plain, Size: 356 bytes --]
acpitz-virtual-0
Adapter: Virtual device
temp1: +101.0°C (crit = +108.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +33.0°C (high = +95.0°C, crit = +105.0°C)
Core 2: +27.0°C (high = +95.0°C, crit = +105.0°C)
radeon-pci-0100
Adapter: PCI adapter
temp1: -128.0°C (crit = +120.0°C, hyst = +90.0°C)
[-- Attachment #5: lshw_short.txt --]
[-- Type: text/plain, Size: 3531 bytes --]
H/W path Device Class Description
======================================================
system B43J (0)
/0 bus B43J
/0/0 memory 64KiB BIOS
/0/4 processor Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
/0/4/5 memory 32KiB L1 cache
/0/4/6 memory 256KiB L2 cache
/0/4/7 memory 3MiB L3 cache
/0/25 memory 8GiB System Memory
/0/25/0 memory 4GiB SODIMM DDR3 Synchronous 1067 MHz (0.9 ns)
/0/25/1 memory 4GiB SODIMM DDR3 Synchronous 1067 MHz (0.9 ns)
/0/100 bridge Core Processor DRAM Controller
/0/100/1 bridge Core Processor PCI Express x16 Root Port
/0/100/1/0 generic Illegal Vendor ID
/0/100/1/0.1 multimedia Cedar HDMI Audio [Radeon HD 5400/6300 Series]
/0/100/2 display Core Processor Integrated Graphics Controller
/0/100/16 communication 5 Series/3400 Series Chipset HECI Controller
/0/100/16.3 communication 5 Series/3400 Series Chipset KT Controller
/0/100/19 eth0 network 82577LM Gigabit Network Connection
/0/100/1a bus 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
/0/100/1b multimedia 5 Series/3400 Series Chipset High Definition Audio
/0/100/1c bridge 5 Series/3400 Series Chipset PCI Express Root Port 1
/0/100/1c.1 bridge 5 Series/3400 Series Chipset PCI Express Root Port 2
/0/100/1c.1/0 wlan0 network Centrino Advanced-N 6200
/0/100/1c.2 bridge 5 Series/3400 Series Chipset PCI Express Root Port 3
/0/100/1d bus 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
/0/100/1e bridge 82801 Mobile PCI Bridge
/0/100/1f bridge Mobile 5 Series Chipset LPC Interface Controller
/0/100/1f.2 storage 5 Series/3400 Series Chipset 6 port SATA AHCI Controller
/0/100/1f.3 bus 5 Series/3400 Series Chipset SMBus Controller
/0/100/1f.6 generic 5 Series/3400 Series Chipset Thermal Subsystem
/0/101 bridge Core Processor QuickPath Architecture Generic Non-core Registers
/0/102 bridge Core Processor QuickPath Architecture System Address Decoder
/0/103 bridge Core Processor QPI Link 0
/0/104 bridge Core Processor QPI Physical 0
/0/105 bridge Core Processor Reserved
/0/106 bridge Core Processor Reserved
/0/1 scsi0 storage
/0/1/0.0.0 /dev/sda disk 320GB ST9320423AS
/0/1/0.0.0/1 /dev/sda1 volume 184GiB EXT4 volume
/0/1/0.0.0/2 /dev/sda2 volume 7987MiB Extended partition
/0/1/0.0.0/2/5 /dev/sda5 volume 7987MiB Linux swap / Solaris partition
/0/1/0.0.0/3 /dev/sda3 volume 105GiB EXT4 volume
/0/2 scsi1 storage
/0/2/0.0.0 /dev/cdrom disk DVDRAM GT32N
/1 power B43-44
[-- Attachment #6: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (2 preceding siblings ...)
2014-01-22 23:27 ` [lm-sensors] sensors Ryan
@ 2014-01-23 0:37 ` Ryan
2014-01-23 4:59 ` Guenter Roeck
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Ryan @ 2014-01-23 0:37 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1: Type: text/plain, Size: 65 bytes --]
Sorry, I should have added this file to my previous email.
Ryan
[-- Attachment #2: sensors3.conf --]
[-- Type: text/plain, Size: 10344 bytes --]
# libsensors configuration file
# -----------------------------
#
# This default configuration file only includes statements which do not
# differ from one mainboard to the next. Only label, compute and set
# statements for internal voltage and temperature sensors are included.
#
# In general, local changes should not be added to this file, but rather
# placed in custom configuration files located in /etc/sensors.d. This
# approach makes further updates much easier.
#
# Such custom configuration files for specific mainboards can be found at
# http://www.lm-sensors.org/wiki/Configurations
#
# It is recommended not to modify this file, but to drop your local
# changes in /etc/sensors.d/. File with names that start with a dot
# are ignored.
chip "lm78-*" "lm79-*" "lm80-*" "lm96080-*"
label temp1 "M/B Temp"
chip "w83792d-*"
label in0 "VcoreA"
label in1 "VcoreB"
label in6 "+5V"
label in7 "5VSB"
label in8 "Vbat"
set in6_min 5.0 * 0.90
set in6_max 5.0 * 1.10
set in7_min 5.0 * 0.90
set in7_max 5.0 * 1.10
set in8_min 3.0 * 0.90
set in8_max 3.0 * 1.10
chip "w83793-*"
label in0 "VcoreA"
label in1 "VcoreB"
label in7 "+5V"
label in8 "5VSB"
label in9 "Vbat"
set in7_min 5.0 * 0.90
set in7_max 5.0 * 1.10
set in8_min 5.0 * 0.90
set in8_max 5.0 * 1.10
set in9_min 3.0 * 0.90
set in9_max 3.0 * 1.10
chip "w83795g-*" "w83795adg-*"
label in12 "+3.3V"
label in13 "3VSB"
label in14 "Vbat"
set in12_min 3.3 * 0.90
set in12_max 3.3 * 1.10
set in13_min 3.3 * 0.90
set in13_max 3.3 * 1.10
set in14_min 3.0 * 0.90
set in14_max 3.3 * 1.10
chip "via686a-*"
label in0 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in4_min 12.0 * 0.90
set in4_max 12.0 * 1.10
chip "adm1025-*" "ne1619-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "VCC"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
# Depending on how your chip is hardwired, you may or may not have
# +12V readings.
# set in4_min 12.0 * 0.90
# set in4_max 12.0 * 1.10
label temp1 "CPU Temp"
label temp2 "M/B Temp"
chip "lm87-*" "adm1024-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in4_min 12.0 * 0.90
set in4_max 12.0 * 1.10
label temp1 "M/B Temp"
label temp2 "CPU Temp"
chip "it87-*" "it8712-*" "it8716-*" "it8718-*" "it8720-*"
label in8 "Vbat"
chip "fscpos-*" "fscher-*"
#FSC "Hermes"
label in0 "+12V"
label in1 "+5V"
label in2 "Vbat"
label temp1 "CPU Temp"
label temp2 "M/B Temp"
label temp3 "Aux Temp"
chip "fscscy-*"
#FSC "Scylla"
label in0 "+12V"
label in1 "+5V"
label in2 "+3.3V"
label temp1 "CPU0 Temp"
label temp2 "CPU1 Temp"
label temp3 "M/B Temp"
label temp4 "Aux Temp"
chip "fschds-*"
# Fujitsu Technology Solutions, "Hades"-Chip
# Temperatures
label temp1 "CPU Temp"
label temp2 "Super I/O Temp"
label temp3 "System Temp"
# Fans
label fan1 "PSU Fan"
label fan2 "CPU Fan"
label fan3 "System FAN2"
label fan4 "System FAN3"
label fan5 "System FAN4"
# Voltages
label in0 "+12V"
label in1 "+5V"
label in2 "Vbat"
chip "fscsyl-*"
# Fujitsu Technology Solutions, "Syleus"-Chip
# Temperatures
label temp1 "CPU Temp"
label temp4 "Super I/O Temp"
label temp5 "Northbridge Temp"
# Fans
label fan1 "CPU Fan"
label fan2 "System FAN2"
label fan3 "System FAN3"
label fan4 "System FAN4"
label fan7 "PSU Fan"
# Voltages
label in0 "+12V"
label in1 "+5V"
label in2 "Vbat"
label in3 "+3.3V"
label in5 "+3.3V-Aux"
chip "vt1211-*"
label in5 "+3.3V"
label temp2 "SIO Temp"
chip "vt8231-*"
label in5 "+3.3V"
chip "smsc47m192-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "VCC"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in4_min 12.0 * 0.90
set in4_max 12.0 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
label temp1 "SIO Temp"
chip "lm85-*" "lm85b-*" "lm85c-*" "adm1027-*" "adt7463-*" "adt7468-*" \
"emc6d100-*" "emc6d102-*" "emc6d103-*" "emc6d103s-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
# Depending on how your chip is hardwired, you may or may not have
# +12V readings.
# set in4_min 12.0 * 0.90
# set in4_max 12.0 * 1.10
label temp2 "M/B Temp"
chip "emc6w201-*"
label in2 "+3.3V"
label in3 "+5V"
label temp6 "M/B Temp"
chip "pc87365-*" "pc87366-*"
# Voltage inputs
label in7 "3VSB"
label in8 "VDD"
label in9 "Vbat"
label in10 "AVDD"
compute in7 @*2, @/2
compute in8 @*2, @/2
compute in10 @*2, @/2
# These are the operating conditions as recommended by National
# Semiconductor
set in7_min 3.0
set in7_max 3.6
set in8_min 3.0
set in8_max 3.6
set in10_min 3.0
set in10_max 3.6
# Depending on the hardware setup, the battery voltage may or may not
# be monitored.
# set in9_min 2.4
# set in9_max 3.6
label temp3 "SIO Temp"
set temp3_min 0
set temp3_max 70
set temp3_crit 85
chip "adm1030-*" "adm1031-*"
label temp1 "M/B Temp"
chip "w83627thf-*"
label in3 "+5V"
label in7 "5VSB"
label in8 "Vbat"
# Internal resistors
compute in3 @ * (1 + 34/51), @ / (1 + 34/51)
compute in7 @ * (1 + 34/51), @ / (1 + 34/51)
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in7_min 5.0 * 0.90
set in7_max 5.0 * 1.10
# The battery voltage may or may not be monitored.
# set in8_min 3.0 * 0.90
# set in8_max 3.0 * 1.10
chip "w83627ehf-*" "w83627dhg-*" "w83667hg-*" "nct6775-*" "nct6776-*"
label in0 "Vcore"
label in2 "AVCC"
label in3 "+3.3V"
label in7 "3VSB"
label in8 "Vbat"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 3.3 * 0.90
set in3_max 3.3 * 1.10
set in7_min 3.3 * 0.90
set in7_max 3.3 * 1.10
set in8_min 3.0 * 0.90
set in8_max 3.3 * 1.10
chip "w83627uhg-*"
label in2 "AVCC"
label in3 "+5V"
label in7 "5VSB"
label in8 "Vbat"
set in2_min 5.0 * 0.90
set in2_max 5.0 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in7_min 5.0 * 0.90
set in7_max 5.0 * 1.10
set in8_min 3.0 * 0.90
set in8_max 3.3 * 1.10
chip "f71805f-*"
label in0 "+3.3V"
set in0_min 3.3 * 0.90
set in0_max 3.3 * 1.10
chip "f71872f-*"
label in0 "+3.3V"
label in9 "Vbat"
label in10 "3VSB"
set in0_min 3.3 * 0.90
set in0_max 3.3 * 1.10
set in9_min 3.0 * 0.90
set in9_max 3.0 * 1.10
set in10_min 3.3 * 0.90
set in10_max 3.3 * 1.10
chip "k8temp-*"
label temp1 "Core0 Temp"
label temp2 "Core0 Temp"
label temp3 "Core1 Temp"
label temp4 "Core1 Temp"
chip "dme1737-*"
label in0 "5VSB"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "3VSB"
label in6 "Vbat"
label temp2 "SIO Temp"
set in0_min 5.0 * 0.90
set in0_max 5.0 * 1.10
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in4_min 12.0 * 0.90
set in4_max 12.0 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
set in6_min 3.0 * 0.90
set in6_max 3.0 * 1.10
chip "sch311x-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "3VSB"
label in6 "Vbat"
label temp2 "SIO Temp"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
set in4_min 12.0 * 0.90
set in4_max 12.0 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
set in6_min 3.0 * 0.90
set in6_max 3.0 * 1.10
chip "sch5027-*"
label in0 "5VSB"
label in1 "Vcore"
label in2 "+3.3V"
label in5 "3VSB"
label in6 "Vbat"
label temp2 "SIO Temp"
set in0_min 5.0 * 0.90
set in0_max 5.0 * 1.10
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
set in6_min 3.0 * 0.90
set in6_max 3.0 * 1.10
chip "sch5127-*"
label in2 "+3.3V"
label in5 "3VSB"
label in6 "Vbat"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in5_min 3.3 * 0.90
set in5_max 3.3 * 1.10
set in6_min 3.0 * 0.90
set in6_max 3.0 * 1.10
chip "f71808e-*" "f71808a-*" "f71862fg-*" "f71869-*" "f71869a-*" "f71882fg-*" \
"f71889fg-*" "f71889ed-*" "f71889a-*"
label in0 "+3.3V"
label in7 "3VSB"
label in8 "Vbat"
compute in0 @*2, @/2
compute in7 @*2, @/2
compute in8 @*2, @/2
chip "f71858fg-*" "f8000-*"
label in0 "+3.3V"
label in1 "3VSB"
label in2 "Vbat"
compute in0 @*2, @/2
compute in1 @*2, @/2
compute in2 @*2, @/2
chip "f81865f-*"
label in0 "+3.3V"
label in5 "3VSB"
label in6 "Vbat"
compute in0 @*2, @/2
compute in5 @*2, @/2
compute in6 @*2, @/2
chip "adt7473-*" "adt7475-*"
label in2 "+3.3V"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
label temp2 "Board Temp"
chip "adt7476-*" "adt7490-*"
label in1 "Vcore"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
set in2_min 3.3 * 0.90
set in2_max 3.3 * 1.10
set in3_min 5.0 * 0.90
set in3_max 5.0 * 1.10
# Depending on how your ADT7476 is hardwired, you may or may not have
# +12V readings.
# set in4_min 12.0 * 0.90
# set in4_max 12.0 * 1.10
label temp2 "M/B Temp"
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (3 preceding siblings ...)
2014-01-23 0:37 ` Ryan
@ 2014-01-23 4:59 ` Guenter Roeck
2014-01-23 7:41 ` Jean Delvare
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Guenter Roeck @ 2014-01-23 4:59 UTC (permalink / raw)
To: lm-sensors
On 01/22/2014 03:27 PM, Ryan wrote:
> hello,
>
> I'm having an issue getting the correct output from sensors on my asus
> laptop. I'm running xubuntu on it and I've attached the following files
> hoping it gives you all the information you may need.
>
> grub - my /etc/default/grub
> modules_file.txt - my /etc/modules
> sensors_output.txt - output from running 'sudo sensors'
> lshw_short.txt - hardware information from lshw command
>
> Please let me know if you need more information and thank you for your
> time. I greatly appreciate any advise.
>
Hi Ryan,
please don't use attachments when posting. It makes it difficult to reply.
> acpitz-virtual-0
> Adapter: Virtual device
> temp1: +101.0°C (crit = +108.0°C)
This temperature is reported by ACPI, or in other words by the BIOS, and
suggests that the system is running really hot (unlikely) or that the BIOS
has a bug. Do you have the latest BIOS installed ?
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0: +33.0°C (high = +95.0°C, crit = +105.0°C)
> Core 2: +27.0°C (high = +95.0°C, crit = +105.0°C)
This looks ok.
> radeon-pci-0100
> Adapter: PCI adapter
> temp1: -128.0°C (crit = +120.0°C, hyst = +90.0°C)
This suggests that there is either no temperature sensor attached to
the graphics adapter (that is most likely), or that it is broken.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (4 preceding siblings ...)
2014-01-23 4:59 ` Guenter Roeck
@ 2014-01-23 7:41 ` Jean Delvare
2014-01-23 7:57 ` Ryan
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Jean Delvare @ 2014-01-23 7:41 UTC (permalink / raw)
To: lm-sensors
On Wed, 22 Jan 2014 20:59:30 -0800, Guenter Roeck wrote:
> On 01/22/2014 03:27 PM, Ryan wrote:
> > radeon-pci-0100
> > Adapter: PCI adapter
> > temp1: -128.0°C (crit = +120.0°C, hyst = +90.0°C)
>
> This suggests that there is either no temperature sensor attached to
> the graphics adapter (that is most likely), or that it is broken.
First time I see this. I'd suggest that Ryan reports this to the radeon
driver folks. I think all recent Radeon chips are supposed to have at
least an internal thermal sensor. If I'm wrong then the ones which do
not shouldn't instantiate a hwmon class device at all.
There's another odd thing about this graphics chipset. From
lshw_short.txt:
/0/100/1/0 generic Illegal Vendor ID
/0/100/1/0.1 multimedia Cedar HDMI Audio [Radeon HD 5400/6300 Series]
So the main PCI device has a wrong device ID. I'm curious how the
radeon driver even manages to bind to it then. Does lspci look wrong
too?
Could be defective hardware...
You may also try removing radeon.dpm=1 from your boot command line and
see if it makes any difference. Which reminds me I should really add it
back on mine, I forgot to do so last time I reinstalled my system.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (5 preceding siblings ...)
2014-01-23 7:41 ` Jean Delvare
@ 2014-01-23 7:57 ` Ryan
2014-01-23 8:21 ` Jean Delvare
2014-01-23 17:42 ` Jean Delvare
8 siblings, 0 replies; 10+ messages in thread
From: Ryan @ 2014-01-23 7:57 UTC (permalink / raw)
To: lm-sensors
hello jean,
I don't see anything unusable when I run lspci.
$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller
(rev 18)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16
Root Port (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series
Chipset HECI Controller (rev 06)
00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series
Chipset KT Controller (rev 06)
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network
Connection (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI
Express Root Port 3 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC
Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset
6 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400
Series Chipset Thermal Subsystem (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI
Audio [Radeon HD 5400/6300 Series]
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200
(rev 35)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath
Architecture Generic Non-core Registers (rev 05)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath
Architecture System Address Decoder (rev 05)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0
(rev 05)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
On 01/23/2014 02:41 AM, Jean Delvare wrote:
> On Wed, 22 Jan 2014 20:59:30 -0800, Guenter Roeck wrote:
>> On 01/22/2014 03:27 PM, Ryan wrote:
>> > radeon-pci-0100
>> > Adapter: PCI adapter
>> > temp1: -128.0°C (crit = +120.0°C, hyst = +90.0°C)
>>
>> This suggests that there is either no temperature sensor attached to
>> the graphics adapter (that is most likely), or that it is broken.
> First time I see this. I'd suggest that Ryan reports this to the radeon
> driver folks. I think all recent Radeon chips are supposed to have at
> least an internal thermal sensor. If I'm wrong then the ones which do
> not shouldn't instantiate a hwmon class device at all.
>
> There's another odd thing about this graphics chipset. From
> lshw_short.txt:
>
> /0/100/1/0 generic Illegal Vendor ID
> /0/100/1/0.1 multimedia Cedar HDMI Audio [Radeon HD 5400/6300 Series]
>
> So the main PCI device has a wrong device ID. I'm curious how the
> radeon driver even manages to bind to it then. Does lspci look wrong
> too?
>
> Could be defective hardware...
>
> You may also try removing radeon.dpm=1 from your boot command line and
> see if it makes any difference. Which reminds me I should really add it
> back on mine, I forgot to do so last time I reinstalled my system.
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (6 preceding siblings ...)
2014-01-23 7:57 ` Ryan
@ 2014-01-23 8:21 ` Jean Delvare
2014-01-23 17:42 ` Jean Delvare
8 siblings, 0 replies; 10+ messages in thread
From: Jean Delvare @ 2014-01-23 8:21 UTC (permalink / raw)
To: lm-sensors
On Thu, 23 Jan 2014 02:57:37 -0500, Ryan wrote:
> hello jean,
>
> I don't see anything unusable when I run lspci.
>
> $ lspci
> (...)
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]
> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI
> Audio [Radeon HD 5400/6300 Series]
Looks good indeed. Maybe a bug in lshw then - if this is reproducible.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [lm-sensors] sensors
2005-05-19 6:23 sensors Gyimesi Attila
` (7 preceding siblings ...)
2014-01-23 8:21 ` Jean Delvare
@ 2014-01-23 17:42 ` Jean Delvare
8 siblings, 0 replies; 10+ messages in thread
From: Jean Delvare @ 2014-01-23 17:42 UTC (permalink / raw)
To: lm-sensors
On Thu, 23 Jan 2014 08:41:01 +0100, Jean Delvare wrote:
> On Wed, 22 Jan 2014 20:59:30 -0800, Guenter Roeck wrote:
> > On 01/22/2014 03:27 PM, Ryan wrote:
> > > radeon-pci-0100
> > > Adapter: PCI adapter
> > > temp1: -128.0°C (crit = +120.0°C, hyst = +90.0°C)
> >
> > This suggests that there is either no temperature sensor attached to
> > the graphics adapter (that is most likely), or that it is broken.
>
> First time I see this. I'd suggest that Ryan reports this to the radeon
> driver folks. I think all recent Radeon chips are supposed to have at
> least an internal thermal sensor. If I'm wrong then the ones which do
> not shouldn't instantiate a hwmon class device at all.
I have been explained that this is the expected result when the
graphics card is currently disabled. That would happen if the machine
has hybrid graphics and the other graphics chip was enabled at the time
the "sensors" command was run.
Returning something more sensible would be good, but I'm not too sure
what that would be... -EBUSY comes to mind but it's a bit misleading as
precisely the graphics chip isn't busy at all.
Anyway libsensors will translate all errors other than -EIO to
-SENSORS_ERR_ACCESS_R, so the exact error code doesn't really matter,
unless we also decide to extend libsensors to deal with it more
gracefully. Suggestions welcome.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 10+ messages in thread