[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[Andrew]

Hi All,

I'm trying to get sensors working on a motherboard I have (see details 
below)

I have run sensors-detect (see output further below) - and it says that 
I have a i801 chipset, but when I run sensors I get this output:
"No sensors found!"

I am running a 2.6.16.2 kernel on a debian x86 machine.

Kind Regards,

Andrew.



(lspci gives this output)
0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM 
Controller/Host-Hub Interface (rev 01)
        Subsystem: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM 
Controller/Host-Hub Interface
        Flags: bus master, fast devsel, latency 0
        Memory at d0000000 (32-bit, prefetchable) [size\x128M]
        Capabilities: [e4] #09 [0105]


(sensors-detect gives this output):

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

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.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported 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.
 If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will 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. That often
 includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 5000
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x30
Client found at address 0x31
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!

Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): Probing for `National 
Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8712F'
  Trying address 0x0290... Success!
    (confidence 8, driver `it87')
Probing for `ITE IT8705F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
  Success... found at address 0x0290
Probing for `ITE 8705F Super IO Sensors'
  Failed! (0x8702)
Probing for `ITE 8712F Super IO Sensors'
  Failed! (0x8702)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (skipping family)

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

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 5000'
    Busdriver `i2c-i801', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus I801 adapter at 5000'
    Busdriver `i2c-i801', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)

Driver `it87' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE IT8712F' (confidence: 8)

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE 8702F Super IO Sensors' (confidence: 9)


 I will now generate the commands needed to load the I2C modules.
 Sometimes, a chip is available both through the ISA bus and an I2C bus.
 ISA bus access is faster, but you need to load an additional driver module
 for it. If you have the choice, do you want to use the ISA bus or the
 I2C/SMBus (ISA/smbus)?

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-i801
i2c-isa
# I2C chip drivers
eeprom
# no driver for ITE 8702F Super IO Sensors yet
#----cut here----

[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[Jean Delvare]

Hi Andrew,

> I'm trying to get sensors working on a motherboard I have (see details 
> below)
> 
> I have run sensors-detect (see output further below) - and it says that 
> I have a i801 chipset, but when I run sensors I get this output:
> "No sensors found!"
> 
> I am running a 2.6.16.2 kernel on a debian x86 machine.
> (...)
> (lspci gives this output)
> 0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM 
> Controller/Host-Hub Interface (rev 01)
>         Subsystem: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM 
> Controller/Host-Hub Interface
>         Flags: bus master, fast devsel, latency 0
>         Memory at d0000000 (32-bit, prefetchable) [size\x128M]
>         Capabilities: [e4] #09 [0105]

This isn't the device with the SMBus interface. Look for an entry with
type "SMBus", e.g.:

00:1f.3 SMBus: Intel Corporation 82801CA/CAM SMBus Controller (rev 01)
        Subsystem: Sony Corporation VAIO PCG-GR214EP/GR214MP/GR215MP/GR314MP/GR315MP
        Flags: medium devsel, IRQ 255
        I/O ports at 1880 [size2]

> Probing for PCI bus adapters...
> Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4
> Probe succesfully concluded.
> 
> We will now try to load each adapter module in turn.
> Module `i2c-i801' already loaded.
> (...)
> Next adapter: SMBus I801 adapter at 5000
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x08
> Client found at address 0x30
> Client found at address 0x31
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
> Client found at address 0x50
> Probing for `SPD EEPROM'... Success!
>     (confidence 8, driver `eeprom')
> Probing for `DDC monitor'... Failed!
> Probing for `Maxim MAX6900'... Failed!
> Client found at address 0x51
> Probing for `SPD EEPROM'... Success!
>     (confidence 8, driver `eeprom')
> Client found at address 0x69

This means that your SMBus adapter was properly detected by the
i2c-i801 driver, but you only have SPD EEPROMs (memory module
information) available on this bus.

As for the i2c-i810 driver, you need lm_sensors 2.10.0 or later for
sensors-detect to find it. With earlier version, you must load it
manually before running sensors-detect if you want it to be probed.
However, this only makes sense if you are actually using the integrated
graphics chip and not an additional graphics adapter. Even then, the
chances that any hardware monitoring device is found on this bus are
very thin, all you'll see there is most certainly an information EEPROM
about the connected display if it supports DDC.

> Probing for `ITE 8702F Super IO Sensors'
>   Success... found at address 0x0290

This is your hardware monitoring chip. It's not a dedicated chip on the
SMBus, instead the hardware monitoring features are integrated into
your ITE Super-I/O chip.

Unfortunately, we don't have a driver for this chip at the moment. A
datasheet is available, so writing a driver is possible, however, this
takes time and we don't have much. I could find two previous requests
here:
http://lists.lm-sensors.org/pipermail/lm-sensors/2003-August/003765.html
http://secure.netroedge.com/~lm78/readticket.cgi?ticket\x1828
I've updated our "new drivers" page to mention all three requests.

According to my earlier investigation, the IT8702F chip only supports
fan speed monitoring and control (5 channels) and VID input, so it's
not a complete hardware monitoring chip (no voltages, no temperatures.)
The good side is that the driver should be relatively simple to write,
if anyone wants to take a chance.

You may try ACPI for the temperature (modprobe thermal, acpi -V).

-- 
Jean Delvare

[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[Andrew]

An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060409/10bcc98c/attachment.html

[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[Jean Delvare]

Andrew,

No HTML mail to the list please...

> Thank you for the speedy reply (and detailed explanation).  Considering
> that the chipset doesn't have temp or voltage sensors, I wouldn't
> consider a module for this chip as very useful to me (so please feel
> free to remove the request you have put in - I don't want anyone
> wasting their time on my behalf).

It's still useful for us to have pointers to potential testers if a
driver is ever written, so I think I'll leave the reference to your
post. The number of requests is also a good hint of how popular a chip
is, even if you are not particularly interested in a driver.

> If I can get my C skills up in the future, I might have a crack at
> writing it myself.

Sure, why not. If you do, please let us know so that we avoid
duplicating the effort.

-- 
Jean Delvare

[lm-sensors] i2c-i801 and i2c-i810 can't see 82845G

[Andrew]

Hi Jean,

Sorry for the HTML - normally Mozilla prompts me (and I use text), if 
this comes through as HTML - let me know and i'll double check my settings.


I am happy to test any modules if they get written before I can look at 
it.  I have about 40 more servers to install lm-sensors on with most of 
them varying in hardware spec, so i'll let you know if I have any other 
hardware that could be used in testing.

Ironically, the next server I installed sensors on had a IT8712F 
chipset... (which has fan and temp, and works well with the it87 module).


Cheers,
Andrew.



Jean Delvare wrote:

>Andrew,
>
>No HTML mail to the list please...
>
>  
>
>>Thank you for the speedy reply (and detailed explanation).  Considering
>>that the chipset doesn't have temp or voltage sensors, I wouldn't
>>consider a module for this chip as very useful to me (so please feel
>>free to remove the request you have put in - I don't want anyone
>>wasting their time on my behalf).
>>    
>>
>
>It's still useful for us to have pointers to potential testers if a
>driver is ever written, so I think I'll leave the reference to your
>post. The number of requests is also a good hint of how popular a chip
>is, even if you are not particularly interested in a driver.
>
>  
>
>>If I can get my C skills up in the future, I might have a crack at
>>writing it myself.
>>    
>>
>
>Sure, why not. If you do, please let us know so that we avoid
>duplicating the effort.
>
>  
>