* [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset
@ 2010-08-28 16:09 support RG
2010-08-31 23:50 ` support RG
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: support RG @ 2010-08-28 16:09 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2177 bytes --]
hi
under ubuntu 10.04LTS
on dell vostro 3500
Intel Corporation 5 Series/3400 Series Chipset SMBus Controller
[8086:3b30] (rev 06)
By default i2c-i801 is in blacklist.conf
if i remove from blacklist here it is dmesg
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 14.801179] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
with ACPI region SMBI [0xf000-0xf00f]
[ 14.801182] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
where SMBI is in DSDT_DELL_WN09.dsl
OperationRegion (SMBI, SystemIO, ShiftLeft (SBAR,
0x05), 0x10)
Field (SMBI, ByteAcc, NoLock, Preserve)
{
HSTS, 8,
Offset (0x02),
HCON, 8,
HCOM, 8,
TXSA, 8,
DAT0, 8,
DAT1, 8,
HBDR, 8,
PECR, 8,
RXSA, 8,
SDAT, 16
}
lspci -vvnnxxxx
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset
SMBus Controller [8086:3b30] (rev 06)
Subsystem: Dell Device [1028:0441]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 18
Region 0: Memory at fbc05000 (64-bit, non-prefetchable) [size=256]
Region 4: I/O ports at f000 [size=32]
Kernel modules:* i2c-i801*
00: 86 80 30 3b 03 00 80 02 06 00 05 0c 00 00 00 00
10: 04 50 c0 fb 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 f0 00 00 00 00 00 00 00 00 00 00 28 10 41 04
30: 00 00 00 00 00 00 00 00 00 00 00 00 03 03 00 00
finaly, _with or without i2c-i801_ and//or k8temp load at startup
sensors return only
fidit@de100816A:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +39.5°C (crit = +100.0°C)
under everest on seven, 6 temp are detect.
[-- Attachment #1.2: Type: text/html, Size: 4268 bytes --]
[-- Attachment #2: 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] 4+ messages in thread* [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset
2010-08-28 16:09 [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset support RG
@ 2010-08-31 23:50 ` support RG
2010-09-01 13:07 ` support RG
2010-09-01 13:54 ` Jean Delvare
2 siblings, 0 replies; 4+ messages in thread
From: support RG @ 2010-08-31 23:50 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 6860 bytes --]
Hi
is there a good place for this request ?
i2c-801 module seem to be not working or conflict with 3400 Series
Chipset SMBus Controller [8086:3b30]
dmesg | grep conflict
[ 17.552437] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
with ACPI region SMBI [0xf000-0xf00f]
so sensors command return only one temp ?
follow step by step manual from ubuntu with mkdev.sh script and launch
sensors-detect
what have i made wrong ?
sudo sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +39.5°C (crit = +100.0°C)
sudo sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Dell Inc. Vostro 3500
# Board: Dell Inc. 0G2R51
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
_Trying family `National Semiconductor'... Yes
Found unknown chip with ID 0xfc11_
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
_Do you want to probe the I2C/SMBus adapters now? (YES/no):
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3._
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Next adapter: intel drm CRTDDC_A (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Next adapter: intel drm LVDSDDC_C (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: intel drm HDMIB (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: DPDDC-B (i2c-3)
Do you want to scan it? (YES/no/selectively):
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
sudo pwmconfig
# pwmconfig revision 5770 (2009-09-16)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
lsmod | egrep -i "temp|core|i2c|dell"
i2c_dev 4970 0
dell_wmi 1793 0
i2c_algo_bit 5028 1 i915
dell_laptop 6856 0
dcdbas 5422 1 dell_laptop
soundcore 6620 1 snd
i2c_i801 7722 0
k8temp 3024 0
[-- Attachment #1.2: Type: text/html, Size: 13223 bytes --]
[-- Attachment #2: 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] 4+ messages in thread* Re: [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset
2010-08-28 16:09 [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset support RG
2010-08-31 23:50 ` support RG
@ 2010-09-01 13:07 ` support RG
2010-09-01 13:54 ` Jean Delvare
2 siblings, 0 replies; 4+ messages in thread
From: support RG @ 2010-09-01 13:07 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 14138 bytes --]
as i read in Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
i launch latest release from svn
pass one step more than ever
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
as before
_>Do you want to probe the I2C/SMBus adapters now? (YES/no):
>Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3._
>Sorry, no supported PCI bus adapters found.
but sensors view no more and dmesg already says conflict
fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ dmesg | grep conflict
[ 17.201490] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
with ACPI region SMBI [0xf000-0xf00f]
could you help me ?
fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ ls /dev/i2c-*
/dev/i2c-0 /dev/i2c-11 /dev/i2c-14 /dev/i2c-17 /dev/i2c-2
/dev/i2c-22 /dev/i2c-25 /dev/i2c-28 /dev/i2c-30 /dev/i2c-5 /dev/i2c-8
/dev/i2c-1 /dev/i2c-12 /dev/i2c-15 /dev/i2c-18 /dev/i2c-20
/dev/i2c-23 /dev/i2c-26 /dev/i2c-29 /dev/i2c-31 /dev/i2c-6 /dev/i2c-9
/dev/i2c-10 /dev/i2c-13 /dev/i2c-16 /dev/i2c-19 /dev/i2c-21
/dev/i2c-24 /dev/i2c-27 /dev/i2c-3 /dev/i2c-4 /dev/i2c-7
fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ sudo sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +36.5°C (crit = +100.0°C)
fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ sudo
detect/sensors-detect
# sensors-detect revision 5853 (2010-08-12 23:30:13 +0200)
# System: Dell Inc. Vostro 3500
# Board: Dell Inc. 0G2R51
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... Yes
Found unknown chip with ID 0xfc11
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
Next adapter: intel drm CRTDDC_A (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Next adapter: intel drm LVDSDDC_C (i2c-1)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: intel drm HDMIB (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: DPDDC-B (i2c-3)
Do you want to scan it? (YES/no/selectively):
Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.
fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ sudo sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +35.5°C (crit = +100.0°C)
Le 01/09/2010 01:50, support RG a écrit :
> Hi
> is there a good place for this request ?
>
> i2c-801 module seem to be not working or conflict with 3400 Series
> Chipset SMBus Controller [8086:3b30]
>
> dmesg | grep conflict
> [ 17.552437] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
> with ACPI region SMBI [0xf000-0xf00f]
>
> so sensors command return only one temp ?
>
> follow step by step manual from ubuntu with mkdev.sh script and launch
> sensors-detect
> what have i made wrong ?
>
> sudo sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1: +39.5°C (crit = +100.0°C)
>
> sudo sensors-detect
> # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
> # System: Dell Inc. Vostro 3500
> # Board: Dell Inc. 0G2R51
>
> This program will help you determine which kernel modules you need
> to load to use lm_sensors most effectively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what you're doing.
>
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no):
> Silicon Integrated Systems SIS5595... No
> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated Sensors... No
> AMD K8 thermal sensors... No
> AMD Family 10h thermal sensors... No
> AMD Family 11h thermal sensors... No
> Intel Core family thermal sensor... No
> Intel Atom thermal sensor... No
> Intel AMB FB-DIMM thermal sensor... No
> VIA C7 thermal sensor... No
> VIA Nano thermal sensor... No
>
> Some Super I/O chips contain embedded sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
> Probing for Super-I/O at 0x4e/0x4f
> _Trying family `National Semiconductor'... Yes
> Found unknown chip with ID 0xfc11_
>
> Some systems (mainly servers) implement IPMI, a set of common interfaces
> through which system health data may be retrieved, amongst other things.
> We first try to get the information from SMBIOS. If we don't find it
> there, we have to read from arbitrary I/O ports to probe for such
> interfaces. This is normally safe. Do you want to scan for IPMI
> interfaces? (YES/no):
> Probing for `IPMI BMC KCS' at 0xca0... No
> Probing for `IPMI BMC SMIC' at 0xca8... No
>
> Some hardware monitoring chips are accessible through the ISA I/O ports.
> We have to write to arbitrary I/O ports to probe them. This is usually
> safe though. Yes, you do have ISA I/O ports even if you do not have any
> ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
> Probing for `National Semiconductor LM78' at 0x290... No
> Probing for `National Semiconductor LM79' at 0x290... No
> Probing for `Winbond W83781D' at 0x290... No
> Probing for `Winbond W83782D' at 0x290... No
>
> Lastly, we can probe the I2C/SMBus adapters for connected hardware
> monitoring devices. This is the most risky part, and while it works
> reasonably well on most systems, it has been reported to cause trouble
> on some systems.
> _Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3._
> Sorry, no supported PCI bus adapters found.
> Module i2c-dev loaded successfully.
>
> Next adapter: intel drm CRTDDC_A (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Probing for `EDID EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Client found at address 0x51
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Client found at address 0x52
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Client found at address 0x53
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
>
> Next adapter: intel drm LVDSDDC_C (i2c-1)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Probing for `EDID EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
>
> Next adapter: intel drm HDMIB (i2c-2)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: DPDDC-B (i2c-3)
> Do you want to scan it? (YES/no/selectively):
>
> Sorry, no sensors were detected.
> Either your system has no sensors, or they are not supported, or
> they are connected to an I2C or SMBus adapter that is not
> supported. If you find out what chips are on your board, check
> http://www.lm-sensors.org/wiki/Devices for driver status.
>
> sudo pwmconfig
> # pwmconfig revision 5770 (2009-09-16)
> This program will search your sensors for pulse width modulation (pwm)
> controls, and test each one to see if it controls a fan on
> your motherboard. Note that many motherboards do not have pwm
> circuitry installed, even if your sensor chip supports pwm.
>
> We will attempt to briefly stop each fan using the pwm controls.
> The program will attempt to restore each fan to full speed
> after testing. However, it is ** very important ** that you
> physically verify that the fans have been to full speed
> after the program has completed.
>
> /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
>
> lsmod | egrep -i "temp|core|i2c|dell"
> i2c_dev 4970 0
> dell_wmi 1793 0
> i2c_algo_bit 5028 1 i915
> dell_laptop 6856 0
> dcdbas 5422 1 dell_laptop
> soundcore 6620 1 snd
> i2c_i801 7722 0
> k8temp 3024 0
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
[-- Attachment #1.2: Type: text/html, Size: 26342 bytes --]
[-- Attachment #2: 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] 4+ messages in thread* Re: [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset
2010-08-28 16:09 [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset support RG
2010-08-31 23:50 ` support RG
2010-09-01 13:07 ` support RG
@ 2010-09-01 13:54 ` Jean Delvare
2 siblings, 0 replies; 4+ messages in thread
From: Jean Delvare @ 2010-09-01 13:54 UTC (permalink / raw)
To: lm-sensors
On Wed, 01 Sep 2010 15:07:50 +0200, support RG wrote:
> as i read in Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> i launch latest release from svn
> pass one step more than ever
>
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
>
> as before
> _>Do you want to probe the I2C/SMBus adapters now? (YES/no):
> >Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3._
> >Sorry, no supported PCI bus adapters found.
>
> but sensors view no more and dmesg already says conflict
>
> fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ dmesg | grep conflict
> [ 17.201490] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
> with ACPI region SMBI [0xf000-0xf00f]
>
> could you help me ?
Poster avec un nom bidon, ça n'aide pas à avoir des réponses. La
prochaine fois, postez avec un vrai nom...
Your problem is that the ACPI BIOS requested the I/O ports of the SMBus
control, so they are no longer available for native Linux drivers. What
the BIOS uses the ports for, I can't tell without disassembling the
DSDT table of the machine.
> finaly, _with or without i2c-i801_ and//or k8temp load at startup
> sensors return only
Why the hell would you load the k8temp driver on an Intel system?
If anything, you would load the coretemp driver, which is meant for
Intel CPUs.
> fidit@de100816A:~$ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1: +39.5°C (crit = +100.0°C)
This is quite possibly why the ACPI BIOS needed access the SMBus.
> under everest on seven, 6 temp are detect.
This is awfully vague. Which temperatures? From what devices?
It is entirely possible that Everest decided to bypass the ACPI
resource conflict. Something you definitely don't want to do on a
production machine, at least not before a complete analysis of the DSDT.
If you aren't happy with the situation, I suggest that you contact the
hardware vendor and ask they how you are supposed to do hardware
monitoring on that model.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-09-01 13:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-28 16:09 [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset support RG
2010-08-31 23:50 ` support RG
2010-09-01 13:07 ` support RG
2010-09-01 13:54 ` Jean Delvare
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.