[lm-sensors] New Asus board and multiple sensors chips

[lm-sensors] New Asus board and multiple sensors chips

[Marco Chiappero]

Hi everyone,
I recently bought an Asus Maximus II Formula mainboard which provides 
lots of temperature and voltage readings (and a total of 8 fan header), 
as you can see here using the Asus utility under Windows:
http://i38.tinypic.com/2gt109c.jpg
It's quite similar to the previous Maximus Formula board that, 
accordingly with this site
http://linux-eyecandy.org/misc/howtos/asus-maximus-formula/amf_sensors.shtml, 
comes with these sensors chips:

- Winbond W83627DHG
- Winbond W83791D
- Analog Devices ADT7475

Now, in this board the first one has been replaced by the new Winbond
W83667HG and it works thank to the trick of loading the w83627ehf driver
with the force_id=0x8860 option (but a its own driver is on the way,
right?). Starting from kernel 2.6.26 the coretemp driver works fine, but
my cpu isn't recognized by sensors-detect ("Sorry, no sensors were
detected", with lm-sensors 3.0.0) probably because I own a brand new
E8600 Intel CPU which is a E0 revision. I haven't tried lm-sensors 3.0.2
though.
For what concerns the other two sensors chips I can modprobe the
w83781, w83791d, w83792d, w83793 and adt7473 modules but running sensors
or sensors-detect shows no new sensors at all. Unfortunately adt7475
driver is not the upstream kernels yet.

Thank you for paying attention, here I am if you need some testing.


Marco Chiappero



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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Marco Chiappero]

Marco Chiappero ha scritto:
> Now, in this board the first one has been replaced by the new Winbond
> W83667HG and it works thank to the trick of loading the w83627ehf driver
> with the force_id=0x8860 option (but a its own driver is on the way,
> right?). Starting from kernel 2.6.26 the coretemp driver works fine, but
> my cpu isn't recognized by sensors-detect ("Sorry, no sensors were
> detected", with lm-sensors 3.0.0) probably because I own a brand new
> E8600 Intel CPU which is a E0 revision. I haven't tried lm-sensors 3.0.2
> though.
> For what concerns the other two sensors chips I can modprobe the
> w83781, w83791d, w83792d, w83793 and adt7473 modules but running sensors
> or sensors-detect shows no new sensors at all. Unfortunately adt7475
> driver is not the upstream kernels yet.

Having some spare time I gave a try to the lastest sensors-detect 
patched for the w83667hg and both the coretemp and the new winbond chip 
are now detected. I also compiled the adt7475 driver, it loads fine but 
no sensors are show/discovered. Maybe is a specific address needed?


Marco Chiappero

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Jean Delvare]

Hi Marco,

Le samedi 13 septembre 2008, Marco Chiappero a écrit :
> Marco Chiappero ha scritto:
> > Now, in this board the first one has been replaced by the new Winbond
> > W83667HG and it works thank to the trick of loading the w83627ehf driver
> > with the force_id=0x8860 option (but a its own driver is on the way,
> > right?). Starting from kernel 2.6.26 the coretemp driver works fine, but
> > my cpu isn't recognized by sensors-detect ("Sorry, no sensors were
> > detected", with lm-sensors 3.0.0) probably because I own a brand new
> > E8600 Intel CPU which is a E0 revision. I haven't tried lm-sensors 3.0.2
> > though.
> > For what concerns the other two sensors chips I can modprobe the
> > w83781, w83791d, w83792d, w83793 and adt7473 modules but running sensors
> > or sensors-detect shows no new sensors at all. Unfortunately adt7475
> > driver is not the upstream kernels yet.
> 
> Having some spare time I gave a try to the lastest sensors-detect 
> patched for the w83667hg and both the coretemp and the new winbond chip 
> are now detected. I also compiled the adt7475 driver, it loads fine but 
> no sensors are show/discovered. Maybe is a specific address needed?

Loading random drivers isn't going to help. The two interesting
things are:

* What does sensors-detect see? Unidentified chips on the SMBus at
  addresses typically used by monitoring chips (0x2c-0x2f or
  0x48-0x4f)? Or nothing at all? If unidentified chips are seen then
  we need the output of i2cdump for these chips to find out what
  they are.

* What makes you think there are "two other sensor chips" on the
  board? Can you see them physically on the board?

-- 
Jean Delvare

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Marco Chiappero]

[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

Jean Delvare ha scritto:
> Loading random drivers isn't going to help. The two interesting
> things are:
> 
> * What does sensors-detect see? Unidentified chips on the SMBus at
>   addresses typically used by monitoring chips (0x2c-0x2f or
>   0x48-0x4f)? Or nothing at all? If unidentified chips are seen then
>   we need the output of i2cdump for these chips to find out what
>   they are.

I attached the sensors-detect output, but I have never used i2cdump 
before, so I don't know exactly which parameters I should pass to it. 
Any help appreciated.

> * What makes you think there are "two other sensor chips" on the
>   board? Can you see them physically on the board?

A little search through the web. Let me explain. This board I own (Asus
Maximus II Formula) it's essentially a refreshment of the previous
Maximus Formula / Rampage Formula motherboard (which are exactly the
same board with different northbridge chip) and both share the same
temperature & voltage readings, fan and optional sensors headers. So I
think we can assume the hwmon section it's almost the same.
Unfortunately the only chip clearly visible is the Winbond W83667HG also
because the board comes with a wide heatsink that may cover some chips
(as it is for the ICS clock generator, half visible). As soon as I can
I'll try to get a closer look. However I've found these informations
about those "older" models:

- Sensor Type W83627DHG + W83791D + ADT7475 + ADP3228 (ISA 290h, SMB
2Ch/2Eh/20h)

It's all I know, but I think it's a good starting point. So let me know
how to investigate and do some tests.

Thank you,
Marco


[-- Attachment #2: detect_output --]
[-- Type: text/plain, Size: 4961 bytes --]

# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): 
Module loaded successfully.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no): 
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 0400 (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'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
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

Some chips are also 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 LM78-J' 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
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain 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/Fintek'...                       Yes
Found `Nuvoton W83667HG Super IO Sensors'                   Success!
    (address 0x290, driver `w83627ehf')
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 south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (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...                         Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `Nuvoton W83667HG Super IO Sensors' (confidence: 9)

Driver `coretemp' (should be inserted):
  Detects correctly:
  * Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): 
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe w83627ehf
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Jean Delvare]

Hi Rudolf, Marco,

Le mardi 16 septembre 2008, Rudolf Marek a écrit :
> Hello,
> 
> Here is mine research:
> 
> DHG chip is wired as follows:
> 
> in0 is Vcore
> in1 is 12V
> in2 not used
> in3 is 3.3V
> in4 is 5V
> 
> temp1 is MB temp
> fans are
> fan2 is cpu,
> fan5 is not, fan4 is not
> 
> There is some unknown i2c chip at 0x38 which measures voltages, and fans
> 
> It measures:
> Cpu voltage, DDR voltage, SB 1.1V voltage SB 1.5V, CPU PLL voltage, NB 1.1V Dram 
> VTT volrage, VTT CPU voltage,
> 
> And also fans:
> Chasis fan1
> Chasis fan2
> Power Fan
> And some Opt fans, I know what registers are there (mostly up 0xa0 for fans)
> 
> So we need to find out what chip it is, because it measures a lot too.
> 
> The NB temperature etc etc is measured by some chip at 0x40 it seems it also 
> controls some fan temperature???
> 
> Definitely what is the output of
> 
> i2cdetect 0
> i2cdump 0 0x40
> i2cdump 0 0x38

Excellent work, thanks Rudolf. We don't currently know of any
hardware monitoring chip at either 0x40 or 0x38, which is why
sensors-detect didn't reveal anything. The output of i2cdetect would
definitely be a good thing to have, sorry for not thinking of this
earlier.

-- 
Jean Delvare

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Marc Hulsman]

Hi Jean,

From the earlier communication on list I got the impression you were planning 
to include the w83791d patches I send last month (which were acked by Hans) 
in your tree for submission. 
Are you still planning to do this (as you later made it clear you dont want to 
be _the_ maintainer)? No pressure, I can also send them directly to Andrew if 
you like. I just want to try to get them in for 2.6.28.

Regards,
Marc

On Wednesday 17 September 2008 00:35:41 Jean Delvare wrote:
> Hi Rudolf, Marco,
>
> Le mardi 16 septembre 2008, Rudolf Marek a écrit :
> > Hello,
> >
> > Here is mine research:
> >
> > DHG chip is wired as follows:
> >
> > in0 is Vcore
> > in1 is 12V
> > in2 not used
> > in3 is 3.3V
> > in4 is 5V
> >
> > temp1 is MB temp
> > fans are
> > fan2 is cpu,
> > fan5 is not, fan4 is not
> >
> > There is some unknown i2c chip at 0x38 which measures voltages, and fans
> >
> > It measures:
> > Cpu voltage, DDR voltage, SB 1.1V voltage SB 1.5V, CPU PLL voltage, NB
> > 1.1V Dram VTT volrage, VTT CPU voltage,
> >
> > And also fans:
> > Chasis fan1
> > Chasis fan2
> > Power Fan
> > And some Opt fans, I know what registers are there (mostly up 0xa0 for
> > fans)
> >
> > So we need to find out what chip it is, because it measures a lot too.
> >
> > The NB temperature etc etc is measured by some chip at 0x40 it seems it
> > also controls some fan temperature???
> >
> > Definitely what is the output of
> >
> > i2cdetect 0
> > i2cdump 0 0x40
> > i2cdump 0 0x38
>
> Excellent work, thanks Rudolf. We don't currently know of any
> hardware monitoring chip at either 0x40 or 0x38, which is why
> sensors-detect didn't reveal anything. The output of i2cdetect would
> definitely be a good thing to have, sorry for not thinking of this
> earlier.



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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Thierry Bothorel]

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

As I did not saw an answer, here is my dsdt.dsl file.

>From: Rudolf Marek <r.marek <at> assembler.cz>
>Subject: Re: New Asus board and multiple sensors chips (W83667HG/W83791D/ADT7475)
>Newsgroups: gmane.linux.drivers.sensors
>Date: 2008-09-15 12:17:17 GMT (9 weeks, 3 days, 8 hours and 10 minutes ago)
>
>Hi,
>
>Can you display a tree of sensors? To sort them by connection to right
>chips. Maybe it would help me the
>DSDT of the ACPI.
>
>Please can you post the text file obtained by iasl util.
>
>cd /tmp
>cat /proc/acpi/dsdt.bin >dsdt.bin
>iasl -d dsdt.bin
>
>It will be called dsdt.asl or dsdt.dsl
>
>Thanks,
>Rudolf

[-- Attachment #2: dsdt.dsl.tar.gz --]
[-- Type: application/x-gzip, Size: 30209 bytes --]

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Luca Tettamanti]

On Thu, Nov 20, 2008 at 9:32 PM, Thierry Bothorel
<thierry.bothorel@gmail.com> wrote:
>>From: Rudolf Marek <r.marek <at> assembler.cz>
>>Subject: Re: New Asus board and multiple sensors chips (W83667HG/W83791D/ADT7475)
>>Newsgroups: gmane.linux.drivers.sensors
>>Date: 2008-09-15 12:17:17 GMT (9 weeks, 3 days, 8 hours and 10 minutes ago)
>>
>>Can you display a tree of sensors? To sort them by connection to right
>>chips. Maybe it would help me the
>>DSDT of the ACPI.
>
> As I did not saw an answer, here is my dsdt.dsl file.

I totally missed the original thread, but this gives me a good excuse
to jump on this issue again :)
Asus boards have two different ACPI interfaces for hwmon:
- an old one (based on RVLT/RFAN/RTMP)
- a new one (GGRP/GITM)
Both may be present but there a few cases (my board, sigh) where the
new interface is just an empty stub.
I've rewritten my old ATK driver for the third time so that it works
with both interfaces (and this time I _really_ intend to push it
upstream); currently I'm not 100% sure of the output of the new
interface (the user that originally contacted me is not responsive...)
but the code is almost complete.
Thierry are you willing to test this _experimental_ driver?

Luca

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Thierry Bothorel]

2008/11/20 Luca Tettamanti <kronos.it@gmail.com>:

> I totally missed the original thread, but this gives me a good excuse
> to jump on this issue again :)
> Asus boards have two different ACPI interfaces for hwmon:
> - an old one (based on RVLT/RFAN/RTMP)
> - a new one (GGRP/GITM)
> Both may be present but there a few cases (my board, sigh) where the
> new interface is just an empty stub.
> I've rewritten my old ATK driver for the third time so that it works
> with both interfaces (and this time I _really_ intend to push it
> upstream); currently I'm not 100% sure of the output of the new
> interface (the user that originally contacted me is not responsive...)
> but the code is almost complete.
> Thierry are you willing to test this _experimental_ driver?
>
> Luca
>
Yes but you will have to tell me how, i'm not an "expert".

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Luca Tettamanti]

On Fri, Nov 21, 2008 at 12:39 AM, Thierry Bothorel
<thierry.bothorel@gmail.com> wrote:
> 2008/11/20 Luca Tettamanti <kronos.it@gmail.com>:
[cut]
>> I've rewritten my old ATK driver for the third time so that it works
>> with both interfaces (and this time I _really_ intend to push it
>> upstream); currently I'm not 100% sure of the output of the new
>> interface (the user that originally contacted me is not responsive...)
>> but the code is almost complete.
>> Thierry are you willing to test this _experimental_ driver?
>
> Yes but you will have to tell me how, i'm not an "expert".

Ok, I see that you motherboard uses the old interface (and has
non-working stub of the new one - just like mine); the driver should
work fine, but testing will involve a recompilation of the kernel
(what version are you using?), are you comfortable with this?

Luca

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Jean Delvare]

Hi Marco,

On Sun, 23 Nov 2008 16:23:52 +0100, Marco Chiappero wrote:
> [1] By the way, I patched the lm-sensors package too, the compilation
> runs fine but "sensors" is still unable to show the atk readings.

If you use lm-sensors 3.0.2 or later and if the atk0110 driver
implements the standard sysfs interface (it really should), then you
shouldn't have to patch anything, it should work out of the box.

-- 
Jean Delvare

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Thierry Bothorel]

To be honest, no :-). Can I do that from a live-cd  or from a
virtualized machine and just copy and install the final deb file on my
real system and install it ?

2008/11/21 Luca Tettamanti <kronos.it@gmail.com>:
> On Fri, Nov 21, 2008 at 12:39 AM, Thierry Bothorel
> <thierry.bothorel@gmail.com> wrote:
>> 2008/11/20 Luca Tettamanti <kronos.it@gmail.com>:

>
> Ok, I see that you motherboard uses the old interface (and has
> non-working stub of the new one - just like mine); the driver should
> work fine, but testing will involve a recompilation of the kernel
> (what version are you using?), are you comfortable with this?
>
> Luca
>

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Luca Tettamanti]

(top posting is bad)

On Sun, Nov 23, 2008 at 8:25 PM, Thierry Bothorel
<thierry.bothorel@gmail.com> wrote:
> 2008/11/21 Luca Tettamanti <kronos.it@gmail.com>:
>> On Fri, Nov 21, 2008 at 12:39 AM, Thierry Bothorel
>> <thierry.bothorel@gmail.com> wrote:
>>> 2008/11/20 Luca Tettamanti <kronos.it@gmail.com>:
>> Ok, I see that you motherboard uses the old interface (and has
>> non-working stub of the new one - just like mine); the driver should
>> work fine, but testing will involve a recompilation of the kernel
>> (what version are you using?), are you comfortable with this?
>
> To be honest, no :-). Can I do that from a live-cd  or from a
> virtualized machine and just copy and install the final deb file on my
> real system and install it ?

Hum, not really. If you're on Debian the recompilation is mostly automatic:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building
YMMV with other distros.

Luca

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Luca Tettamanti]

On Thu, Nov 27, 2008 at 3:41 PM, Marco Chiappero <marco@absence.it> wrote:
>> Hum, anything in dmesg?
>> Anyway I'm attacching the new version (plus patch for ACPI - diffed
>> against git-current, but it's easily adapted to older kernels).
[...]
> I compiled and loaded the new atk driver and compiled again lm-sensors with
> the old patch (that was laying around in my /usr/src) and this time I
> managed to see the atk driver readings from the "sensors" output (don't know
> why it didn't work the first time, sorry). However I noticed that the code
> you posted recently it's a little bit different, isn't? Should I try that
> one too?

The patch for lm-sensors? I've just rebased to SVN-current.

> About the atk, it seems to work fine, but I haven't got the time to verify
> the presence of strange issues, regarding for example suspend and/or
> hibernate, stuff like that (does it matter?).

The driver is stateless, so it shouldn't matter (testing won't harm though :P)

> The only thing to say is that in the new code now shows all the readings in
> the /sys/class/hwmon/hwmonX/ dir instead of the
> /sys/class/hwmon/hwmonX/device/ I used to see with many other sensors chips.

Both are supported, I'm not sure which one is "better" - I used the
class directory since the ATK device also controls stuff other than
hwmon.

> I know that no fan control is possible with this driver, however I was
> asking to myself whether it is possible to select on the fly one of the
> three "silent, normal, turbo" profiles available in the BIOS settings. Even
> if it is not a fine fan tuning, such regulation should be enough for me.

It's doable using the Q-FAN interface. You use the interface calling
GITM/SITM with class 0x4 (see the documentation embedded in my
driver). There are at least 3 different types of control in this
class, you'll have to reverse engineer the exact calling interface
(start with the getters).

> One, last thing: I use to collect and plot system data with collectd and
> rrdtool, but collectd seems to ignore the atk driver. I know, I should read
> the code, however any idea for addressing this issue?

I suppose that collectd is using the unpatched libsensor which ignores
the ATK device (it's attached to the unknown ACPI bus).

Luca

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Marco Chiappero]

Luca Tettamanti ha scritto:
>> About the atk, it seems to work fine, but I haven't got the time to verify
>> the presence of strange issues, regarding for example suspend and/or
>> hibernate, stuff like that (does it matter?).
> The driver is stateless, so it shouldn't matter (testing won't harm though :P)

Good :)

>> I know that no fan control is possible with this driver, 
 >> [...]
> It's doable using the Q-FAN interface. You use the interface calling
> GITM/SITM with class 0x4 (see the documentation embedded in my
> driver). There are at least 3 different types of control in this
> class, you'll have to reverse engineer the exact calling interface
> (start with the getters).

Ok, I'll have a look as soon as I have some spare time.

>> One, last thing: I use to collect and plot system data with collectd and
>> rrdtool, but collectd seems to ignore the atk driver. I know, I should read
>> the code, however any idea for addressing this issue?
> I suppose that collectd is using the unpatched libsensor which ignores
> the ATK device (it's attached to the unknown ACPI bus).

Ok, many thanks for the driver and your help!

Waiting for it to be merged in the upstream kernel.

Regards,
Marco

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

Re: [lm-sensors] New Asus board and multiple sensors chips

[Luca Tettamanti]

On Sun, Dec 7, 2008 at 12:50 PM, Marco Chiappero <marco@absence.it> wrote:
> Luca Tettamanti ha scritto:
>>> I know that no fan control is possible with this driver,
>
>>> [...]
>>
>> It's doable using the Q-FAN interface. You use the interface calling
>> GITM/SITM with class 0x4 (see the documentation embedded in my
>> driver). There are at least 3 different types of control in this
>> class, you'll have to reverse engineer the exact calling interface
>> (start with the getters).
>
> Ok, I'll have a look as soon as I have some spare time.

I might be able to assist, I do have the hardware and vague idea of
the interface :)

>>> One, last thing: I use to collect and plot system data with collectd and
>>> rrdtool, but collectd seems to ignore the atk driver. I know, I should
>>> read
>>> the code, however any idea for addressing this issue?
>>
>> I suppose that collectd is using the unpatched libsensor which ignores
>> the ATK device (it's attached to the unknown ACPI bus).
>
> Ok, many thanks for the driver and your help!
>
> Waiting for it to be merged in the upstream kernel.

Hum, unfortunately my tester for the GITM interface has disappeared,
so I'm not 100% sure that the code is correct. I'll probably send a
CFT on the list and see what happens. I'd like to see it upstream
anyway instead of letting it rot on my HD though.
Jean, how does the process work now? Are you still picking up stray
patches on the list?

Luca

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