Intel i840 support (Examined/Solved - lm_sensors 2.5.0 RedHat Linux 2.2.14-6.1.1 SMP)

[contact]

First off I had a previous ticket #325 that I figured out. I had tried to build

lm_senors before I built i2c. That caused problems when I tried to rebuild the

lm_senors after I had built i2c. Removing the source and untarring fresh source

fixed it.

Now I have a different problem. I have a SuperMicro? PIIIDME mb that has a i840

chipset on it. It reports back a i810 for the SMBus controller. lspci follows

00:00.0 Host bridge: Intel Corporation: Unknown device 1a21 (rev 01)

00:01.0 PCI bridge: Intel Corporation: Unknown device 1a23 (rev 01)

00:02.0 PCI bridge: Intel Corporation: Unknown device 1a24 (rev 01)

00:1e.0 PCI bridge: Intel Corporation 82801AA 82810 PCI Bridge (rev 02)

00:1f.0 ISA bridge: Intel Corporation 82801AA 82810 Chipset ISA Bridge (LPC)

(rev 02)

00:1f.1 IDE interface: Intel Corporation 82801AA 82810 Chipset IDE (rev 02)

00:1f.3 SMBus: Intel Corporation 82801AA 82810 Chipset SMBus (rev 02)

00:1f.5 Multimedia audio controller: Intel Corporation 82801AA 82810 AC'97 Audio

(rev 02)

01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev

5c)

01:01.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875 (rev

04)

01:08.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)

02:1f.0 PCI bridge: Intel Corporation: Unknown device 1360 (rev 02)

03:00.0 PIC: Intel Corporation: Unknown device 1161 (rev 01)

03:02.0 SCSI storage controller: Adaptec 7892A (rev 02)

I can modprobe all the required modules execpt for i810.o, which results in the

following.

/lib/modules/2.2.14-6.1.1/misc/i2c-i810.o: init_module: Device or resource busy

/lib/modules/2.2.14-6.1.1/misc/i2c-i810.o: insmod

/lib/modules/2.2.14-6.1.1/misc/i2c-i810.o failed

/lib/modules/2.2.14-6.1.1/misc/i2c-i810.o: insmod i2c-i810 failed

I am not sure what could be using the SMBus already as I don't have any other

i2c devices in the machine that I am aware of. Any suggestions would be greatly

appreciated. PS. The sensors-detect script failed to detect the i810 controller.

Chris --- Your "840" chipset contains, presumably, an 840 and an 801.

The 801 chip is erroneously labeled by 'lspci' as part of the

'810' chipset. The 801 originally came out with the 810

but it lives on in newer chipsets.

So you don't have an 810, you have an 801.

So you want to use the i2c-i801 module.

Now if sensors-detect doesn't recognize the 801 and/or

the i2c-i801 module doesn't load then we have a problem.

If so, send us the output of 'lspci -n' and 'sensors-detect',

as well as any relevant output from the syslog when the modules

try and load.

Let us know.

Follow up by sending mail to sensors@… and

referencing ticket #326.

mds 5/8/00

---

closed 6/15/00 MDS without identifying chip.

email history:

I have not been able to locate the chip nor have I gotten any response

back from SuperMicro?.... At this point and time, unless the chip jumps out

of the case and announces itself to me, I am just going to let it slide.

Thank you for your help though.

Chris

Corporate Communications Technical Support Group

 http://www.corpcomm.net

 http://www.roadfeldt.com

701.281.5741 - 888.926.7726

On Fri, 2 Jun 2000, Mark D. Studebaker wrote:

Did you ever get over to your ISP and figure out what chip this is?

mds

Chris Roadfeldt wrote:

replies below

Two questions:

* What is the output of 'sensors' and of 'ls -al /proc/sys/dev/sensors'

after inserting the w83781d module?

[root@piii2 dev]# sensors

eeprom-i2c-0-50

Adapter: SMBus I801 adapter at efa0

Algorithm: Non-I2C SMBus adapter

Memory type: SDRAM DIMM SPD

SDRAM Size (MB): 256

eeprom-i2c-0-52

Adapter: SMBus I801 adapter at efa0

Algorithm: Non-I2C SMBus adapter

Memory type: SDRAM DIMM SPD

SDRAM Size (MB): 256

[root@piii2 /root]# ls -al /proc/sys/dev/sensors

total 0

dr-xr-xr-x 4 root root 0 May 9 23:49 .

dr-xr-xr-x 5 root root 0 May 9 23:49 ..

-rw-r--r-- 1 root root 0 May 9 23:49 chips

dr-xr-xr-x 2 root root 0 May 9 23:49 eeprom-i2c-0-50

dr-xr-xr-x 2 root root 0 May 9 23:49 eeprom-i2c-0-52

* Can you please make a register dump:

lm_sensors/prog/dump/i2cdump 0 0x2d b

[root@piii2 lm_sensors2]# ./prog/dump/i2cdump 0 0x2d b

WARNING! This program can confuse your I2C bus, cause data loss and worse!

I will probe file /dev/i2c-0, address 0x2d, mode byte

You have five seconds to reconsider and press CTRL-C!

0 1 2 3 4 5 6 7 8 9 a b c d e f

00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

10: 00 00 00 46 55 00 00 46 55 ff 00 00 00 00 00 00

20: c0 77 bc bd c3 eb 21 26 ff ff 00 ab d1 ab d1 ab

30: d1 ab d1 ab d1 ab d1 ab 06 05 06 05 e1 00 02 04

40: 01 ff 03 00 00 00 00 a8 00 80 00 00 cd 03 00 00

50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

80: 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

c0: 30 2e 0f 00 48 05 00 00 00 00 00 00 00 00 00 00

d0: 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00 00

e0: 00 00 00 00 7f ca b3 00 00 00 00 00 00 00 00 00

f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Can't see the motherboard from home. It's a co-locate at my ISP. If it

becomes an issue, I can look at it on Wed. May 10th.

Chris

---

Update 7/24/00 MDS:

User reports that he inspected the motherboard

and that it contains a LM87, which we do not currently support.