[lm-sensors] unhide_ICH_SMBus: line 33:

[lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Hi,
  I am trying to figure out how to setup lm-sensors on my ASUS L3C/S
laptop (ICH3-M chipset) with P4-M processor. It all started with these
lines in dmesg(1) output:

i2c /dev entries driver
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe81f] conflicts with ACPI region SMB0 [0xe800-0xe80f]
ACPI: Device needs an ACPI driver
i801_smbus: probe of 0000:00:1f.3 failed with error -16
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
input: AT Translated Set 2 keyboard as /class/input/input5
iTCO_wdt: Found a ICH3-M TCO device (Version=1, TCOBASE=0xe460)
iTCO_wdt: initialized. heartbeat0 sec (nowayout=0)
iTCO_vendor_support: vendor-support=0




  Apparently I do not have something enabled in my kernel (currently 2.6.31-rc6-git6).
;)

  Here is the output from
http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/hotplug/unhide_ICH_SMBus?revB83&format=raw

# ~/bin/unhide_ICH_SMBus 
Enabling SMBus PCI device ...
Rescanning the bus ...
/root/bin/unhide_ICH_SMBus: line 33: /sys/bus/pci/slots//0000:00:1f.0/power: No such file or directory
Failed to enable the SMBUS
# ls -la /sys/bus/pci/slots/
total 0
drwxr-xr-x 2 root root 0 Aug 23 12:29 .
drwxr-xr-x 5 root root 0 Aug 23  2009 ..
#

What kernel option should I enable?




Further, some more info:

# ~/bin/sensors-detect 
# sensors-detect revision $Revision$
# Board: ASUSTeK Computer INC. P4_L3C

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 K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       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'...                   Yes
Found `Nat. Semi. PC8739x Super IO'                         
    (no hardware monitoring capabilities)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

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 82801CA/CAM ICH3
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/ath_pci, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/slmodem, it will be ignored in a future release.
FATAL: Module i2c_i801 not found.
Failed to load module i2c-i801.

Next adapter: radeonfb monid (i2c-0)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb dvi (i2c-1)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb vga (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb crt2 (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.
#


And snippets from lspci(1) output:

# lspci -vvv
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
        Subsystem: ASUSTeK Computer Inc. Device 1626
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSELúst >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at e0000000 (32-bit, prefetchable) [size%6M]
        Capabilities: [e4] Vendor Specific Information <?>
        Capabilities: [a0] AGP version 2.0
                Status: RQ2 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
                Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
        Kernel driver in use: agpgart-intel
        Kernel modules: intel-agp


00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device 1628
        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 B routed to IRQ 11
        Region 4: I/O ports at e800 [size2]




Thank you for any comments,
Martin

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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

Hi Martin,

On Sun, 23 Aug 2009 13:07:13 +0200, Martin MOKREJ¦ wrote:
> Hi,
>   I am trying to figure out how to setup lm-sensors on my ASUS L3C/S
> laptop (ICH3-M chipset) with P4-M processor. It all started with these
> lines in dmesg(1) output:
> 
> i2c /dev entries driver
> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
> ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe81f] conflicts with ACPI region SMB0 [0xe800-0xe80f]
> ACPI: Device needs an ACPI driver
> i801_smbus: probe of 0000:00:1f.3 failed with error -16
> iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
> input: AT Translated Set 2 keyboard as /class/input/input5
> iTCO_wdt: Found a ICH3-M TCO device (Version=1, TCOBASE=0xe460)
> iTCO_wdt: initialized. heartbeat0 sec (nowayout=0)
> iTCO_vendor_support: vendor-support=0
> 
> 
> 
> 
>   Apparently I do not have something enabled in my kernel (currently 2.6.31-rc6-git6).
> ;)
> 
>   Here is the output from
> http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/hotplug/unhide_ICH_SMBus?revB83&format=raw
> 
> # ~/bin/unhide_ICH_SMBus 
> Enabling SMBus PCI device ...
> Rescanning the bus ...
> /root/bin/unhide_ICH_SMBus: line 33: /sys/bus/pci/slots//0000:00:1f.0/power: No such file or directory
> Failed to enable the SMBUS
> # ls -la /sys/bus/pci/slots/
> total 0
> drwxr-xr-x 2 root root 0 Aug 23 12:29 .
> drwxr-xr-x 5 root root 0 Aug 23  2009 ..
> #
> 
> What kernel option should I enable?

CONFIG_HOTPLUG and/or CONFIG_HOTPLUG_PCI presumably. But you don't
actually need to use the unhide_ICH_SMBus script in the first place, as
the SMBus device is _not_ hidden (you do see it in the output of lspci).

Better see this post from Hans:
http://hansdegoede.livejournal.com/7932.html

-- 
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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

Hi Martin,

Please keep the list in Cc or I am no longer replying.

On Tue, 15 Sep 2009 00:53:41 +0200, Martin MOKREJ¦ wrote:
> Hi Jean,
>   yes, on 2.6.30.4 it "works" (probably in the broken way):

This is exactly the symptom described in the blog post I sent you to.
http://hansdegoede.livejournal.com/7932.html
Did you read it?

> $ dmesg
> [cut]
> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
> [cut]
> 
> $ sensors
> ds1621-i2c-4-4c
> Adapter: SMBus I801 adapter at e800
> temp:     +51.00°C  (low  = +51.0°C, high = +51.0°C)  ALARM (LOW)

You don't really have a DS162x chip on your system, do you? The output
above is rather suspicious. Does the temperature value ever changes?

This chip is very difficult to detect and misdetections are very
frequent. We should probably even disable it altogether. So if that's
all you had with kernel 2.6.30.4, it hardly qualifies as "worked".

> Maybe I got bitten due to the broken driver implementation with IRQ issues?
> http://bugzilla.kernel.org/show_bug.cgi?id\x14149
> What do you think?

I don't know anything about this specific issue, sorry.

-- 
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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Hi Jean,

Jean Delvare wrote:
> Hi Martin,
> 
> Please keep the list in Cc or I am no longer replying.

sorry for that.

> 
> On Tue, 15 Sep 2009 00:53:41 +0200, Martin MOKREJŠ wrote:
>> Hi Jean,
>>   yes, on 2.6.30.4 it "works" (probably in the broken way):
> 
> This is exactly the symptom described in the blog post I sent you to.
> http://hansdegoede.livejournal.com/7932.html
> Did you read it?

I did and therefore it seemed to me the problem is with the driver.
I haven't figured out I am using a wrong one. :( So I should probably
go and read the FAQ again. ;-)

> 
>> $ dmesg
>> [cut]
>> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
>> [cut]
>>
>> $ sensors
>> ds1621-i2c-4-4c
>> Adapter: SMBus I801 adapter at e800
>> temp:     +51.00°C  (low  = +51.0°C, high = +51.0°C)  ALARM (LOW)
> 
> You don't really have a DS162x chip on your system, do you? The output
> above is rather suspicious. Does the temperature value ever changes?

At the moment I have under 2.6.30.6:

# sensors
ds1621-i2c-4-4c
Adapter: SMBus I801 adapter at e800
temp:     +64.00°C  (low  = +64.0°C, high = +64.0°C)  ALARM (HIGH)

# lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB Controller #2 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:07.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a8)
02:07.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev a8)
02:07.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller
#
> 
> This chip is very difficult to detect and misdetections are very
> frequent. We should probably even disable it altogether. So if that's
> all you had with kernel 2.6.30.4, it hardly qualifies as "worked".

The below is probably useless to you as long as the driver is statically included in the kernel,
right?

# sensors-detect 
# sensors-detect revision $Revision$
# Board: ASUSTeK Computer INC. P4_L3C

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 K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       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'...                   Yes
Found `Nat. Semi. PC8739x Super IO'                         
    (no hardware monitoring capabilities)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

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 82801CA/CAM ICH3
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/ath_pci, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/slmodem, it will be ignored in a future release.
FATAL: Module i2c_i801 not found.
Failed to load module i2c-i801.

Next adapter: radeonfb monid (i2c-0)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb dvi (i2c-1)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb vga (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: radeonfb crt2 (i2c-3)
Do you want to scan it? (YES/no/selectively): 

Next adapter: SMBus I801 adapter at e800 (i2c-4)
Do you want to scan it? (YES/no/selectively): 
Client at address 0x4c can not be probed - unload all client drivers first!
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

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.
#

Hmm, but when I had compiled all the available drivers as a module the driver
I use now was the one proposed.


Once again, it is ASUS L3C/S laptop.

Thanks,
M.


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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

On Tue, 15 Sep 2009 15:11:39 +0200, Martin MOKREJ¦ wrote:
> Jean Delvare wrote:
> > This is exactly the symptom described in the blog post I sent you to.
> > http://hansdegoede.livejournal.com/7932.html
> > Did you read it?
> 
> I did and therefore it seemed to me the problem is with the driver.
> I haven't figured out I am using a wrong one. :( So I should probably
> go and read the FAQ again. ;-)
> 
> > 
> >> $ dmesg
> >> [cut]
> >> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
> >> [cut]
> >>
> >> $ sensors
> >> ds1621-i2c-4-4c
> >> Adapter: SMBus I801 adapter at e800
> >> temp:     +51.00°C  (low  = +51.0°C, high = +51.0°C)  ALARM (LOW)
> > 
> > You don't really have a DS162x chip on your system, do you? The output
> > above is rather suspicious. Does the temperature value ever changes?
> 
> At the moment I have under 2.6.30.6:
> 
> # sensors
> ds1621-i2c-4-4c
> Adapter: SMBus I801 adapter at e800
> temp:     +64.00°C  (low  = +64.0°C, high = +64.0°C)  ALARM (HIGH)

Once again, input = low = high, this doesn't make any sense. This has
to be a misdetection. So I suggest that you stop loading the ds1621
driver.

As this was the only chip seen by sensors-detect on your system, this
simply means that lm-sensors' native drivers are of no use on your
system. The good news is that this means the ACPI conflicts policy
change in recent kernels doesn't affect you much.

> (...)
> Once again, it is ASUS L3C/S laptop.

On laptops, thermal management is almost always handled by ACPI. So
your best chances are the acpi "thermal" driver and its bridge driver
to lm-sensors (thermal_sys, CONFIG_THERMAL=m or y and
CONFIG_THERMAL_HWMON=y).

And there are also a number of drivers dedicated to Asus systems, such
as asus_atk0110, asus-laptop and asus_acpi. You should try them if you
haven't already.

-- 
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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Luca Tettamanti]

On Tue, Sep 15, 2009 at 3:27 PM, Jean Delvare <khali@linux-fr.org> wrote:
> And there are also a number of drivers dedicated to Asus systems, such
> as asus_atk0110, asus-laptop and asus_acpi. You should try them if you
> haven't already.

I never saw a laptop with the ATK0110 hwmon interface; the other two
are for back light, leds, special keys.
As Jean suggested you should try the thermal driver which should work
(I have a L3D and it works).

Luca

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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Jean Delvare wrote:
> On Tue, 15 Sep 2009 15:11:39 +0200, Martin MOKREJŠ wrote:
>> Jean Delvare wrote:
>>> This is exactly the symptom described in the blog post I sent you to.
>>> http://hansdegoede.livejournal.com/7932.html
>>> Did you read it?
>> I did and therefore it seemed to me the problem is with the driver.
>> I haven't figured out I am using a wrong one. :( So I should probably
>> go and read the FAQ again. ;-)
>>
>>>> $ dmesg
>>>> [cut]
>>>> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
>>>> [cut]
>>>>
>>>> $ sensors
>>>> ds1621-i2c-4-4c
>>>> Adapter: SMBus I801 adapter at e800
>>>> temp:     +51.00°C  (low  = +51.0°C, high = +51.0°C)  ALARM (LOW)
>>> You don't really have a DS162x chip on your system, do you? The output
>>> above is rather suspicious. Does the temperature value ever changes?
>> At the moment I have under 2.6.30.6:
>>
>> # sensors
>> ds1621-i2c-4-4c
>> Adapter: SMBus I801 adapter at e800
>> temp:     +64.00°C  (low  = +64.0°C, high = +64.0°C)  ALARM (HIGH)
> 
> Once again, input = low = high, this doesn't make any sense. This has
> to be a misdetection. So I suggest that you stop loading the ds1621
> driver.
> 
> As this was the only chip seen by sensors-detect on your system, this
> simply means that lm-sensors' native drivers are of no use on your
> system. The good news is that this means the ACPI conflicts policy
> change in recent kernels doesn't affect you much.
> 
>> (...)
>> Once again, it is ASUS L3C/S laptop.
> 
> On laptops, thermal management is almost always handled by ACPI. So
> your best chances are the acpi "thermal" driver and its bridge driver
> to lm-sensors (thermal_sys, CONFIG_THERMAL=m or y and
> CONFIG_THERMAL_HWMON=y).
> 
> And there are also a number of drivers dedicated to Asus systems, such
> as asus_atk0110, asus-laptop and asus_acpi. You should try them if you
> haven't already.

$ gzip -dc /proc/config.gz | grep THERMAL
CONFIG_ACPI_THERMAL=y
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
$ gzip -dc /proc/config.gz | grep ATK
CONFIG_KEYBOARD_ATKBD=y
CONFIG_SENSORS_ATK0110=y
$

These I have already in the kernel, so I can drop the whole SMbus thing?
Could sensors-detect give me an advice like this? Are these hidden in the dmesg
output I have provided recently?

I am sorry for the silly questions.
M.


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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJ¦ wrote:
> $ gzip -dc /proc/config.gz | grep THERMAL
> CONFIG_ACPI_THERMAL=y
> CONFIG_THERMAL=y
> CONFIG_THERMAL_HWMON=y
> $ gzip -dc /proc/config.gz | grep ATK
> CONFIG_KEYBOARD_ATKBD=y
> CONFIG_SENSORS_ATK0110=y
> $
> 
> These I have already in the kernel, so I can drop the whole SMbus thing?

Yes.

> Could sensors-detect give me an advice like this? Are these hidden in the dmesg
> output I have provided recently?

I know that sensors-detect doesn't cope properly with non-native
hardware monitoring mechanism. This is something we must improve in the
future. I have some ideas but I need time and, if possible, affected
hardware to implement them.

-- 
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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Hi,

Jean Delvare wrote:
> On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJÅ  wrote:
>> $ gzip -dc /proc/config.gz | grep THERMAL
>> CONFIG_ACPI_THERMAL=y
>> CONFIG_THERMAL=y
>> CONFIG_THERMAL_HWMON=y
>> $ gzip -dc /proc/config.gz | grep ATK
>> CONFIG_KEYBOARD_ATKBD=y
>> CONFIG_SENSORS_ATK0110=y
>> $
>>
>> These I have already in the kernel, so I can drop the whole SMbus thing?
> 
> Yes.
> 
>> Could sensors-detect give me an advice like this? Are these hidden in the dmesg
>> output I have provided recently?
> 
> I know that sensors-detect doesn't cope properly with non-native
> hardware monitoring mechanism. This is something we must improve in the
> future. I have some ideas but I need time and, if possible, affected
> hardware to implement them.

Feel free to email me directly once it happens, I can do some testing.
Thanks for your time,
Martin


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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Jean Delvare wrote:
> On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJÅ  wrote:
>> $ gzip -dc /proc/config.gz | grep THERMAL
>> CONFIG_ACPI_THERMAL=y
>> CONFIG_THERMAL=y
>> CONFIG_THERMAL_HWMON=y
>> $ gzip -dc /proc/config.gz | grep ATK
>> CONFIG_KEYBOARD_ATKBD=y
>> CONFIG_SENSORS_ATK0110=y
>> $
>>
>> These I have already in the kernel, so I can drop the whole SMbus thing?
> 
> Yes.

Ooops, are we talking about I2C_I801=N, I2C=N or SENSORS_DS1621=N? ;-)
Actually I had SENSORS_LM90=Y as it was also proposed by sensors-detect.
That one was also mis-detected?
M.


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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

On Tue, 15 Sep 2009 18:41:41 +0200, Martin MOKREJ¦ wrote:
> Jean Delvare wrote:
> > On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJ¦ wrote:
> >> $ gzip -dc /proc/config.gz | grep THERMAL
> >> CONFIG_ACPI_THERMAL=y
> >> CONFIG_THERMAL=y
> >> CONFIG_THERMAL_HWMON=y
> >> $ gzip -dc /proc/config.gz | grep ATK
> >> CONFIG_KEYBOARD_ATKBD=y
> >> CONFIG_SENSORS_ATK0110=y
> >> $
> >>
> >> These I have already in the kernel, so I can drop the whole SMbus thing?
> > 
> > Yes.
> 
> Ooops, are we talking about I2C_I801=N, I2C=N or SENSORS_DS1621=N? ;-)

ENSORS_DS1621=N and I2C_I801=N, yes. I2C=N, bad idea, you might need
I2C support for something else.

> Actually I had SENSORS_LM90=Y as it was also proposed by sensors-detect.
> That one was also mis-detected?

I can't tell as your sensors-detect report was incomplete (with ds1621
loaded, sensors-detect can't probe the chip). I'm not sure why you are
hard-building all the drivers that way, BTW, it makes investigating
problems much harder. Probably the LM90 detection was correct, as these
chips are much more reliably detected than the DS1621.

Anyway, as further kernels say that ACPI is conflicting with the native
SMBus controller driver, the only safe bet is to drop i2c-i801 and go
with the ACPI thermal driver instead.

-- 
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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

Jean Delvare wrote:
> On Tue, 15 Sep 2009 18:41:41 +0200, Martin MOKREJŠ wrote:
>> Jean Delvare wrote:
>>> On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJŠ wrote:
>>>> $ gzip -dc /proc/config.gz | grep THERMAL
>>>> CONFIG_ACPI_THERMAL=y
>>>> CONFIG_THERMAL=y
>>>> CONFIG_THERMAL_HWMON=y
>>>> $ gzip -dc /proc/config.gz | grep ATK
>>>> CONFIG_KEYBOARD_ATKBD=y
>>>> CONFIG_SENSORS_ATK0110=y
>>>> $
>>>>
>>>> These I have already in the kernel, so I can drop the whole SMbus thing?
>>> Yes.
>> Ooops, are we talking about I2C_I801=N, I2C=N or SENSORS_DS1621=N? ;-)
> 
> ENSORS_DS1621=N and I2C_I801=N, yes. I2C=N, bad idea, you might need
> I2C support for something else.

$ sensors 
max6657-i2c-4-4c
Adapter: SMBus I801 adapter at e800
M/B Temp:  +39.1°C  (low  =   -55°C, high =  +127°C)   
CPU Temp:  +49.2°C  (low  = +48.0°C, high = +62.0°C)   
M/B Crit:    +85°C  (hyst =   +75°C)                  
CPU Crit:    +75°C  (hyst =   +65°C)                  

$
> 
>> Actually I had SENSORS_LM90=Y as it was also proposed by sensors-detect.
>> That one was also mis-detected?
> 
> I can't tell as your sensors-detect report was incomplete (with ds1621
> loaded, sensors-detect can't probe the chip). I'm not sure why you are
> hard-building all the drivers that way, BTW, it makes investigating
> problems much harder. Probably the LM90 detection was correct, as these
> chips are much more reliably detected than the DS1621.
> 
> Anyway, as further kernels say that ACPI is conflicting with the native
> SMBus controller driver, the only safe bet is to drop i2c-i801 and go
> with the ACPI thermal driver instead.

So doing that lm90 driver does not find any hardware chip and sensors
do not see therefore anything either. modprob-ing ATK0110 driver surprisingly
doesn't give anything either (lsmod reports it is unused and nothing new in
dmesg). 

Dropping i2c-i801 seems like a bad idea. ;-)

What do you propose now? Some debug flags for insmod when inserting the atk*
driver?

M.


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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Martin MOKREJŠ]

>>>>> These I have already in the kernel, so I can drop the whole SMbus thing?
>>>> Yes.
>>> Ooops, are we talking about I2C_I801=N, I2C=N or SENSORS_DS1621=N? ;-)
>> ENSORS_DS1621=N and I2C_I801=N, yes. I2C=N, bad idea, you might need
>> I2C support for something else.
> 
> $ sensors 
> max6657-i2c-4-4c
> Adapter: SMBus I801 adapter at e800
> M/B Temp:  +39.1°C  (low  =   -55°C, high =  +127°C)   
> CPU Temp:  +49.2°C  (low  = +48.0°C, high = +62.0°C)   
> M/B Crit:    +85°C  (hyst =   +75°C)                  
> CPU Crit:    +75°C  (hyst =   +65°C)                  

I forgot that once I opened the laptop and put on the web its contents.
See http://ribosome.natur.cuni.cz/~mmokrejs/ASUS_L3800/p1010020-1-0.html
I see MAX1715 (or 1745?) chip.



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

Re: [lm-sensors] unhide_ICH_SMBus: line 33:

[Jean Delvare]

On Wed, 16 Sep 2009 18:48:43 +0200, Martin MOKREJ¦ wrote:
> Jean Delvare wrote:
> > On Tue, 15 Sep 2009 18:41:41 +0200, Martin MOKREJ¦ wrote:
> >> Jean Delvare wrote:
> >>> On Tue, 15 Sep 2009 17:43:19 +0200, Martin MOKREJ¦ wrote:
> >>>> $ gzip -dc /proc/config.gz | grep THERMAL
> >>>> CONFIG_ACPI_THERMAL=y
> >>>> CONFIG_THERMAL=y
> >>>> CONFIG_THERMAL_HWMON=y
> >>>> $ gzip -dc /proc/config.gz | grep ATK
> >>>> CONFIG_KEYBOARD_ATKBD=y
> >>>> CONFIG_SENSORS_ATK0110=y
> >>>> $
> >>>>
> >>>> These I have already in the kernel, so I can drop the whole SMbus thing?
> >>> Yes.
> >> Ooops, are we talking about I2C_I801=N, I2C=N or SENSORS_DS1621=N? ;-)
> > 
> > ENSORS_DS1621=N and I2C_I801=N, yes. I2C=N, bad idea, you might need
> > I2C support for something else.
> 
> $ sensors 
> max6657-i2c-4-4c
> Adapter: SMBus I801 adapter at e800
> M/B Temp:  +39.1°C  (low  =   -55°C, high =  +127°C)   
> CPU Temp:  +49.2°C  (low  = +48.0°C, high = +62.0°C)   
> M/B Crit:    +85°C  (hyst =   +75°C)                  
> CPU Crit:    +75°C  (hyst =   +65°C)                  
> 
> $
> > 
> >> Actually I had SENSORS_LM90=Y as it was also proposed by sensors-detect.
> >> That one was also mis-detected?
> > 
> > I can't tell as your sensors-detect report was incomplete (with ds1621
> > loaded, sensors-detect can't probe the chip). I'm not sure why you are
> > hard-building all the drivers that way, BTW, it makes investigating
> > problems much harder. Probably the LM90 detection was correct, as these
> > chips are much more reliably detected than the DS1621.
> > 
> > Anyway, as further kernels say that ACPI is conflicting with the native
> > SMBus controller driver, the only safe bet is to drop i2c-i801 and go
> > with the ACPI thermal driver instead.
> 
> So doing that lm90 driver does not find any hardware chip and sensors
> do not see therefore anything either. modprob-ing ATK0110 driver surprisingly
> doesn't give anything either (lsmod reports it is unused and nothing new in
> dmesg). 
> 
> Dropping i2c-i801 seems like a bad idea. ;-)
> 
> What do you propose now? Some debug flags for insmod when inserting the atk*
> driver?

I propose that you read again what I already wrote before, because
apparently you didn't pay attention.

-- 
Jean Delvare

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