Skip to contentSkip to conversation

PNPBios & lm_sensors don't mix on 440GX w/2.4.9-ac18

DISCUSSION [email protected] 2 participants 2 messages Sep 30, 2001 – Oct 1, 2001

lore
Share & tools
lore
#0 lore raw

Today I updated a system with a Intel 440GX (Lancewood) motherboard to 2.4.9-ac18 and normally I have PNP support turned on. Later I updated to the current i2c and lm_sensors code and discovered that the PNPBios support allocates IO port 0x1040. Since the i2c-piix4 wants to use the same port range, this module would not load on the system. A modprobe of i2c-piix4 resulted in:

test:/usr/local/src/lm_sensors2 # modprobe i2c-piix4 /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o: insmod /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o failed /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o: insmod i2c-piix4 failed

Using insmod and force=1 gave:

test:/usr/local/src/lm_sensors2 # insmod /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o force=1 /lib/modules/2.4.9-ac18/kernel/drivers/i2c/i2c-piix4.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters

The entry in dmesg for these operations was:

i2c-piix4.o version 2.6.1 (20010830) i2c-piix4.o: Found PIIX4 device
i2c-piix4.o: SMB region 0x1040 already in use! i2c-piix4.o: Device not detected, module not inserted.

So I then looked at the /proc/ioports entries:

04d0-04d1 : PNP0401
0c00-0c3f : Intel Corporation 82371AB PIIX4 ACPI
0c00-0c3f : PNP0401
0ca0-0ca3 : PNP0401
0cb8-0cbf : PNP0401
0cf8-0cff : PCI conf1
1000-103f : PNP0401
1040-105f : Intel Corporation 82371AB PIIX4 ACPI
1040-104f : PNP0401

When I recompiled the kernel without PNP support altogether the module loaded just fine and then the ioports entries looked like:

0c00-0c3f : Intel Corporation 82371AB PIIX4 ACPI
0cf8-0cff : PCI conf1
1040-105f : Intel Corporation 82371AB PIIX4 ACPI
1040-1047 : piix4-smbus

and the dmesg output for the i2c stuff was:

i2c-core.o: i2c core module version 2.6.1 (20010830)
i2c-piix4.o version 2.6.1 (20010830)
i2c-piix4.o: Found PIIX4 device
i2c-core.o: adapter SMBus PIIX4 adapter at 1040 registered as adapter 0. i2c-piix4.o: SMBus detected and initialized
i2c-proc.o version 2.6.1 (20010830)
lm75.o version 2.6.1 (20010830)
i2c-core.o: driver LM75 sensor chip driver registered.
i2c-core.o: client [LM75 chip] registered to adapter [SMBus PIIX4 adapter at 1040](pos. 0).

Not sure if this is expected behavior but thought I would report it here.

Signature · 5 lines
Steven A. DuChene	[email protected]
			[email protected]
			[email protected]

	http://www.mindspring.com/~sduchene/
#1 lore raw
Quoted 5 lines

Today I updated a system with a Intel 440GX (Lancewood) motherboard to 2.4.9-ac18 and normally I have PNP support turned on. Later I updated to the current i2c and lm_sensors code and discovered that the PNPBios support allocates IO port 0x1040. Since the i2c-piix4 wants to use the same port range, this module would not load on the system. A modprobe of i2c-piix4 resulted in:

Yep. I know. The Pnpbios code needs fixing to allocate the regions as present but unused - so we dont map pci crap over them but at the same time we dont stop drivers allocating it.

Its a bug.

Alan