Skip to contentSkip to conversation

PnP BIOS -- bugfix; update devlist on setpnp

PATCH Thomas Hood 3 participants 6 messages Oct 17, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines

Thomas:
Just to let you know I still have the same problem with a resource conflict between the PnPBIOS code and the i2c/lm_sensors stuff at 1040 with this latest patch.

Yep, I know. I haven't addressed this bug in any of the patches I've submitted to l-k. I'd like to fix it, but I don't know how yet: I have only a partial understanding of how resource allocation works.

Thanks for testing yesterday's PnP BIOS patch.

--
Thomas

#1 lore raw

OK, I tried this with the Intel STL2 motherboard I also have and I got a similar error when trying to load the correct i2c bus module when the PnPBIOS stuff is compiled into the kernel.

modprobe i2c-piix4
/lib/modules/2.4.10-ac12pnp/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.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: insmod /lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o failed /lib/modules/2.4.10-ac12pnp/kernel/drivers/i2c/i2c-piix4.o: insmod i2c-piix4 failed

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

cat /proc/ioports
.
.
.
04d0-04d1 : PnPBIOS PNP0c02
0580-058f : PnPBIOS PNP0c02
0840-084f : ServerWorks OSB4 IDE Controller
0840-0847 : ide0
0848-084f : ide1
0cd6-0cd7 : PnPBIOS PNP0c02
0cf8-0cff : PCI conf1
5000-50ff : ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] 5400-543f : Intel Corporation 82557 [Ethernet Pro 100]
5400-543f : eepro100
5440-547f : Intel Corporation 82557 [Ethernet Pro 100] (#2)
5440-547f : eepro100
5800-58ff : Adaptec 7899P
6000-60ff : Adaptec 7899P (#2)
fe00-fe3f : PnPBIOS PNP0c02

So this is a problem on more than just those old Intel Lancewood L440GX motherboards. The STL2 is a fairly recent dual processor motherboard

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

	http://www.mindspring.com/~sduchene/
#2 lore raw
Quoted 3 lines · Steven A. DuChene

OK, I tried this with the Intel STL2 motherboard I also have and I got a similar error when trying to load the correct i2c bus module when the PnPBIOS stuff is compiled into the kernel.

Understood.

I'd just like to reiterate that my patch isn't the cause of your problem. It's just that my patch doesn't address your problem. IIUC.

I provided a "workaround patch" before. Can you continue to use that for the time being?

I'd like to make a promise that I'll submit a new patch soon that will address your problem; however I don't yet know exactly how to go about addressing it.

--
Thomas

#3 lore raw
In reply to Thomas Hood
Quoted 8 lines · Steven A. DuChene

OK, I tried this with the Intel STL2 motherboard I also have and I got a similar error when trying to load the correct i2c bus module when the PnPBIOS stuff is compiled into the kernel.

modprobe i2c-piix4
/lib/modules/2.4.10-ac12pnp/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

i2c-piix4 has to be taught to ignore PNP0c0x reservations.

PNP0C02 means "mainboard resource" and obviously i2c-piix4 would like to use it, so it should make use of it's knowledge.

As "mainboard resouce" is very generic we must reserve it to protect against mapping other addresses over it.

#4 lore raw
Quoted 7 lines · Gunther Mayer

i2c-piix4 has to be taught to ignore PNP0c0x reservations.

PNP0C02 means "mainboard resource" and obviously i2c-piix4 would like to use it, so it should make use of it's knowledge.

As "mainboard resouce" is very generic we must reserve it to protect against mapping other addresses over it.

Your approach would work. But ...

Alan has said that the thing to do is mark these resources as extant but unused. I presume one does this by calling request_resource with appropriate flags [un]set.

Thomas

#5 lore raw
In reply to Thomas Hood
Quoted 10 lines · Thomas Hood
Quoted 3 lines · Steven A. DuChene

OK, I tried this with the Intel STL2 motherboard I also have and I got a similar error when trying to load the correct i2c bus module when the PnPBIOS stuff is compiled into the kernel.

Understood.

I'd just like to reiterate that my patch isn't the cause of your problem. It's just that my patch doesn't address your problem. IIUC.

Yes, I understood that from the start of all of this but you seemed to be be the only person messing with the PnPBIOS code so I thought you might be interested in this annomoly. I appreciate the info/help you have provided so far.

Quoted 4 lines

I provided a "workaround patch" before. Can you continue to use that for the time being?

Yes, but according to these latest results that work around of skipping a particular ioport would have to be different for each motherboard with this problem. There must be a better way to do this.

Quoted 4 lines

I'd like to make a promise that I'll submit a new patch soon that will address your problem; however I don't yet know exactly how to go about addressing it.

Perhaps someone else can provide us a hint or two as to where to start. :-)

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

	http://www.mindspring.com/~sduchene/