Intel 82801DA ICH4

Intel 82801DA ICH4

[Alexander Pohl]

Hello,

I am seeking support for the Intel 82801DA ICH4 Southbridge (Reference to
ticket # 1345)

Here comes lspci -v and lspci -n output:


00:00.0 Host bridge: Intel Corp.: Unknown device 2560 (rev 02)
        Subsystem: Asustek Computer, Inc.: Unknown device 80b2
        Flags: bus master, fast devsel, latency 0
        Memory at f8000000 (32-bit, prefetchable) [sizedM]
        Capabilities: [e4] #09 [6105]
        Capabilities: [a0] AGP version 2.0

00:01.0 PCI bridge: Intel Corp.: Unknown device 2561 (rev 02) (prog-if 00
[Normal decode])
        Flags: bus master, 66Mhz, fast devsel, latency 64
        Bus: primary\0, secondary\x01, subordinate\x01, sec-latency=0
        Memory behind bridge: f2000000-f36fffff
        Prefetchable memory behind bridge: f3700000-f7ffffff

00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 02) (prog-if
00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8089
        Flags: bus master, medium devsel, latency 0, IRQ 5
        I/O ports at d800 [size2]

00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 02) (prog-if
00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8089
        Flags: bus master, medium devsel, latency 0, IRQ 9
        I/O ports at d400 [size2]

00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 02) (prog-if
00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8089
        Flags: bus master, medium devsel, latency 0, IRQ 9
        I/O ports at d000 [size2]

00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 02) (prog-if
20)
        Subsystem: Asustek Computer, Inc.: Unknown device 8089
        Flags: bus master, medium devsel, latency 0, IRQ 11
        Memory at f1800000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] #0a [2080]

00:1e.0 PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (rev 82)
(prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary\0, secondary\x02, subordinate\x02, sec-latency2
        I/O behind bridge: 0000b000-0000bfff
        Memory behind bridge: f0800000-f17fffff

00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 02)
        Flags: bus master, medium devsel, latency 0

00:1f.1 IDE interface: Intel Corp.: Unknown device 24cb (rev 02) (prog-if
8a [Master SecP PriP])
        Subsystem: Asustek Computer, Inc.: Unknown device 8089
        Flags: bus master, medium devsel, latency 0, IRQ 9
        I/O ports at <unassigned> [size=8]
        I/O ports at <unassigned> [size=4]
        I/O ports at <unassigned> [size=8]
        I/O ports at <unassigned> [size=4]
        I/O ports at f000 [size\x16]
        Memory at 20000000 (32-bit, non-prefetchable) [size=1K]

00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev
02)
        Subsystem: Asustek Computer, Inc.: Unknown device 80b0
        Flags: bus master, medium devsel, latency 0, IRQ 9
        I/O ports at a800 [size%6]
        I/O ports at a400 [sized]
        Memory at f0000000 (32-bit, non-prefetchable) [sizeQ2]
        Memory at ef800000 (32-bit, non-prefetchable) [size%6]
        Capabilities: [50] Power Management version 2

01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0253
(rev a3) (prog-if 00 [VGA])
        Subsystem: Asustek Computer, Inc.: Unknown device 803f
        Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 5
        Memory at f2000000 (32-bit, non-prefetchable) [size\x16M]
        Memory at f4000000 (32-bit, prefetchable) [sizedM]
        Memory at f3800000 (32-bit, prefetchable) [sizeQ2K]
        Expansion ROM at f37e0000 [disabled] [size\x128K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0

02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. OHCI Compliant IEEE
1394 Host Controller (rev 80) (prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 808a
        Flags: bus master, stepping, medium devsel, latency 32, IRQ 9
        Memory at f1000000 (32-bit, non-prefetchable) [size=2K]
        I/O ports at b800 [size\x128]
        Capabilities: [50] Power Management version 2

02:05.0 Ethernet controller: BROADCOM Corporation: Unknown device 4401
(rev 01)
        Subsystem: Asustek Computer, Inc.: Unknown device 80a8
        Flags: bus master, fast devsel, latency 32, IRQ 10
        Memory at f0800000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

00:00.0 Class 0600: 8086:2560 (rev 02)
00:01.0 Class 0604: 8086:2561 (rev 02)
00:1d.0 Class 0c03: 8086:24c2 (rev 02)
00:1d.1 Class 0c03: 8086:24c4 (rev 02)
00:1d.2 Class 0c03: 8086:24c7 (rev 02)
00:1d.7 Class 0c03: 8086:24cd (rev 02)
00:1e.0 Class 0604: 8086:244e (rev 82)
00:1f.0 Class 0601: 8086:24c0 (rev 02)
00:1f.1 Class 0101: 8086:24cb (rev 02)
00:1f.5 Class 0401: 8086:24c5 (rev 02)
01:00.0 Class 0300: 10de:0253 (rev a3)
02:03.0 Class 0c00: 1106:3044 (rev 80)
02:05.0 Class 0200: 14e4:4401 (rev 01)

Best regards,
Alexander Pohl

Intel 82801DA ICH4

[Jean Delvare]

> Hello,
> 
> I am seeking support for the Intel 82801DA ICH4 Southbridge (Reference
> to ticket # 1345)
> 
> Here comes lspci -v and lspci -n output:
> (...)

I don't see any I2C bus here. Asus is known to hide them. Please follow
the instructions in prog/hotplug/README.p4b. Note that you need hotplug
support on your kernel. I think we don't officialy support the 82801DA,
but if it's close enough to the 82801DB, I suppose it should work (maybe
we'll have to add a device ID, but I doubt even this will be necessary).

Tell us how it goes, so that we can add support for your bus or simply
claim we already support it.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Intel 82801DA ICH4

[Alexander Pohl]

Hello,

I have some trouble compiling the module p4b_smbus.o and adding support
for the i2c-bus. Adding support for pci-hotplug to my kernel was
successful.
(reference to ticket # 1345)


Here the compiler output:

cc  -D__SMP__ -DMODVERSIONS -include
/lib/modules/2.4.20-hotplug/build/include/linux/modversions.h -D__KERNEL__
-DMODULE -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -I/lib/modules/2.4.20-hotplug/build/include   -c -o
p4b_smbus.o p4b_smbus.c
p4b_smbus.c: In function `cleanup_module':
p4b_smbus.c:263: incompatible type for argument 1 of `write_lock'
p4b_smbus.c:268: invalid type argument of `->'
make: *** [p4b_smbus.o] Error 1


Here what setpci said:

setpci -d 24C0:24C3 f2.w
setpci: Warning: No devices selected for `f2.w'.


Thanks for your fast respond,
Alexander Pohl

Intel 82801DA ICH4

[Jean Delvare]

> I have some trouble compiling the module p4b_smbus.o and adding
> support for the i2c-bus. Adding support for pci-hotplug to my kernel
> was successful.
> (reference to ticket # 1345)
> 
> Here the compiler output:
> 
> cc  -D__SMP__ -DMODVERSIONS -include
> /lib/modules/2.4.20-hotplug/build/include/linux/modversions.h
> -D__KERNEL__-DMODULE -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer-fno-strict-aliasing
> -I/lib/modules/2.4.20-hotplug/build/include   -c -o p4b_smbus.o
> p4b_smbus.c p4b_smbus.c: In function `cleanup_module':
> p4b_smbus.c:263: incompatible type for argument 1 of `write_lock'
> p4b_smbus.c:268: invalid type argument of `->'
> make: *** [p4b_smbus.o] Error 1

Strange. I can compile it. I suspect the code isn't SMP-compliant. Try
forcing SMP=0 in Makefile.p4b, just to make sure this is the cause of
the failure. Once confirmed, Mark D. Studebaker will take a look at it.

> Here what setpci said:
> 
> setpci -d 24C0:24C3 f2.w
> setpci: Warning: No devices selected for `f2.w'.

That's normal. The README.p4b file may not be really clear about this,
but the -d parameter for ICH4 is 8086:24C0. 8086 is Intel's vendor ID,
24C0 is the PCI bus main ID, and 24C3 is the I2C bus (which we are
trying to activate) ID.

> Thanks for your fast respond,

You're welcome.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Intel 82801DA ICH4

[Alexander Pohl]

Hi Jean,

I finally got it running, but your p4b_smbus.o code is not SMP compliant.
I compiled it successfully under a single processor kernel. Here comes
what the module said, when inserting it under the SMP kernel again:

# insmod p4b_smbus.o
p4b_smbus.o: unresolved symbol pci_insert_device_R3341a12e
p4b_smbus.o: unresolved symbol pci_read_config_word_R923654cb
p4b_smbus.o: unresolved symbol pci_remove_device_R2d6c74a6
p4b_smbus.o: unresolved symbol kmalloc_R93d4cfe6
p4b_smbus.o: unresolved symbol pcibios_present_R520a75b9
p4b_smbus.o: unresolved symbol pci_find_device_Rc584f4e3
p4b_smbus.o: unresolved symbol pci_enable_device_R1bc741d2
p4b_smbus.o: unresolved symbol pci_write_config_word_Rf23d8795
p4b_smbus.o: unresolved symbol kfree_R037a0cba
p4b_smbus.o: unresolved symbol printk_R1b7d4074
p4b_smbus.o: unresolved symbol pci_setup_device_R863ed348


When activating the SMBus I really didn't know what I was doing. I got the
hex value 0049 and then changed it to 0040, like described in the
README.p4b. The output of pcitweak was as followed:

# setpci -d 8086:24c0 f2.w@
# pcitweak -l
PCI: Probing config type using method 1
PCI: Config type is 1
PCI: PCI scan (all values are in hex)
PCI: 00:00:0: chip 8086,2560 card 1043,80b2 rev 02 class 06,00,00 hdr 00
PCI: 00:01:0: chip 8086,2561 card 0000,0000 rev 02 class 06,04,00 hdr 01
PCI: 00:1d:0: chip 8086,24c2 card 1043,8089 rev 02 class 0c,03,00 hdr 80
PCI: 00:1d:1: chip 8086,24c4 card 1043,8089 rev 02 class 0c,03,00 hdr 00
PCI: 00:1d:2: chip 8086,24c7 card 1043,8089 rev 02 class 0c,03,00 hdr 00
PCI: 00:1d:7: chip 8086,24cd card 1043,8089 rev 02 class 0c,03,20 hdr 00
PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 82 class 06,04,00 hdr 01
PCI: 00:1f:0: chip 8086,24c0 card 0000,0000 rev 02 class 06,01,00 hdr 80
PCI: 00:1f:1: chip 8086,24cb card 1043,8089 rev 02 class 01,01,8a hdr 00
PCI: 00:1f:3: chip 8086,24c3 card 1043,8089 rev 02 class 0c,05,00 hdr 00
PCI: 00:1f:5: chip 8086,24c5 card 1043,80b0 rev 02 class 04,01,00 hdr 00
PCI: 01:00:0: chip 10de,0253 card 1043,803f rev a3 class 03,00,00 hdr 00
PCI: 02:03:0: chip 1106,3044 card 1043,808a rev 80 class 0c,00,10 hdr 00
PCI: 02:05:0: chip 14e4,4401 card 1043,80a8 rev 01 class 02,00,00 hdr 00
PCI: End of PCI scan

I hope you have all information to change the module code. Anyway, sensors
works now under the single processor kernel.

Best regards,
Alexander Pohl

Intel 82801DA ICH4

[Jean Delvare]

> I finally got it running, but your p4b_smbus.o code is not SMP
> compliant.

Bad news. MDS, can you take a look?

> I compiled it successfully under a single processor kernel.
> Here comes what the module said, when inserting it under the SMP
> kernel again:
> 
> # insmod p4b_smbus.o
> p4b_smbus.o: unresolved symbol pci_insert_device_R3341a12e
> p4b_smbus.o: unresolved symbol pci_read_config_word_R923654cb
> p4b_smbus.o: unresolved symbol pci_remove_device_R2d6c74a6
> p4b_smbus.o: unresolved symbol kmalloc_R93d4cfe6
> p4b_smbus.o: unresolved symbol pcibios_present_R520a75b9
> p4b_smbus.o: unresolved symbol pci_find_device_Rc584f4e3
> p4b_smbus.o: unresolved symbol pci_enable_device_R1bc741d2
> p4b_smbus.o: unresolved symbol pci_write_config_word_Rf23d8795
> p4b_smbus.o: unresolved symbol kfree_R037a0cba
> p4b_smbus.o: unresolved symbol printk_R1b7d4074
> p4b_smbus.o: unresolved symbol pci_setup_device_R863ed348

That's no surprise. Modules compiled for one kernel are not supposed to
be used by another one AFAIK.

> When activating the SMBus I really didn't know what I was doing. I got
> the hex value 0049 and then changed it to 0040, like described in the
> README.p4b.

No! README.p4b says you have to erase the bits 8 and 3 from the original
value, not to use 0040, which is just given as an example starting from
0148. So, 0049 becomes 0041.

> The output of pcitweak was as followed:
> (...)
> PCI: 00:1f:3: chip 8086,24c3 card 1043,8089 rev 02 class 0c,05,00 hdr
> 00

OK, the device now shows.

> I hope you have all information to change the module code. Anyway,
> sensors works now under the single processor kernel.

Well, all we need is to make it SMP compliant. I hope MDS will have some
time to fix this.

Thank you for reporting.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Intel 82801DA ICH4

[Mark D. Studebaker]

I've hopefully fixed the SMP compile problem in CVS if you would like to try it.

Jean Delvare wrote:
>>I finally got it running, but your p4b_smbus.o code is not SMP
>>compliant.
> 
> 
> Bad news. MDS, can you take a look?
> 
> 
>>I compiled it successfully under a single processor kernel.
>>Here comes what the module said, when inserting it under the SMP
>>kernel again:
>>
>># insmod p4b_smbus.o
>>p4b_smbus.o: unresolved symbol pci_insert_device_R3341a12e
>>p4b_smbus.o: unresolved symbol pci_read_config_word_R923654cb
>>p4b_smbus.o: unresolved symbol pci_remove_device_R2d6c74a6
>>p4b_smbus.o: unresolved symbol kmalloc_R93d4cfe6
>>p4b_smbus.o: unresolved symbol pcibios_present_R520a75b9
>>p4b_smbus.o: unresolved symbol pci_find_device_Rc584f4e3
>>p4b_smbus.o: unresolved symbol pci_enable_device_R1bc741d2
>>p4b_smbus.o: unresolved symbol pci_write_config_word_Rf23d8795
>>p4b_smbus.o: unresolved symbol kfree_R037a0cba
>>p4b_smbus.o: unresolved symbol printk_R1b7d4074
>>p4b_smbus.o: unresolved symbol pci_setup_device_R863ed348
> 
> 
> That's no surprise. Modules compiled for one kernel are not supposed to
> be used by another one AFAIK.
> 
> 
>>When activating the SMBus I really didn't know what I was doing. I got
>>the hex value 0049 and then changed it to 0040, like described in the
>>README.p4b.
> 
> 
> No! README.p4b says you have to erase the bits 8 and 3 from the original
> value, not to use 0040, which is just given as an example starting from
> 0148. So, 0049 becomes 0041.
> 
> 
>>The output of pcitweak was as followed:
>>(...)
>>PCI: 00:1f:3: chip 8086,24c3 card 1043,8089 rev 02 class 0c,05,00 hdr
>>00
> 
> 
> OK, the device now shows.
> 
> 
>>I hope you have all information to change the module code. Anyway,
>>sensors works now under the single processor kernel.
> 
> 
> Well, all we need is to make it SMP compliant. I hope MDS will have some
> time to fix this.
> 
> Thank you for reporting.
> 

Intel 82801DA ICH4

[Alexander Pohl]

Hello,

yes, the module p4b_smbus.o compiles now. But the lm-sensors package
itself won't compile anymore.

Best reguards
Alexander Pohl

gcc  -D__SMP__ -DMODVERSIONS -include
/lib/modules/2.4.20-smp/build/include/linux/modversions.h -D__KERNEL__
-DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include
-I/usr/local/include  -I/lib/modules/2.4.20-smp/build/include -nostdinc -I
/usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2   -c
kernel/chips/xeontemp.c -o kernel/chips/xeontemp.o
kernel/chips/xeontemp.c:112: `I2C_DRIVERID_XEONTEMP' undeclared here (not
in a function)
kernel/chips/xeontemp.c:112: initializer element is not constant
kernel/chips/xeontemp.c:112: (near initialization for `xeontemp_driver.id')
make: *** [kernel/chips/xeontemp.o] Error 1

<Zitiere wer="Mark D. Studebaker ">
> I've hopefully fixed the SMP compile problem in CVS if you would like to
> try it.

Intel 82801DA ICH4

[Mark D. Studebaker]

my bad, forgot to check in the new id on the i2c side.
It's in there now - but best bet if you don't want to download i2c CVS
is just use 'make -k' to skip the new drivers.
Thanks for testing.
mds

Alexander Pohl wrote:
> Hello,
> 
> yes, the module p4b_smbus.o compiles now. But the lm-sensors package
> itself won't compile anymore.
> 
> Best reguards
> Alexander Pohl
> 
> gcc  -D__SMP__ -DMODVERSIONS -include
> /lib/modules/2.4.20-smp/build/include/linux/modversions.h -D__KERNEL__
> -DMODULE -DEXPORT_SYMTAB -fomit-frame-pointer -I. -Ikernel/include
> -I/usr/local/include  -I/lib/modules/2.4.20-smp/build/include -nostdinc -I
> /usr/lib/gcc-lib/i386-linux/2.95.4/include  -Wall -O2   -c
> kernel/chips/xeontemp.c -o kernel/chips/xeontemp.o
> kernel/chips/xeontemp.c:112: `I2C_DRIVERID_XEONTEMP' undeclared here (not
> in a function)
> kernel/chips/xeontemp.c:112: initializer element is not constant
> kernel/chips/xeontemp.c:112: (near initialization for `xeontemp_driver.id')
> make: *** [kernel/chips/xeontemp.o] Error 1
> 
> <Zitiere wer="Mark D. Studebaker ">
> 
>>I've hopefully fixed the SMP compile problem in CVS if you would like to
>>try it.
> 
> 
> 
> 
> 
>