question (IBM i2c-piix4)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tomas,

> Here is my "vpddecode" output:
> 
> # vpddecode 2.6
> BIOS Build ID: NVKT39AGR
> Product Name: PC 300PL
> Box Serial Number: 5575C0D
> Motherboard Serial Number: D7G5UCE0BDE
> Machine Type/Model: 6862270

This one DOES have the faulty EEPROM IIRC, and an LM80 hardware
monitoring driver.

> Thanks for your advice how to hack the i2c-piix4 driver.

First of all, you MUST NOT load the eeprom driver on your system. NEVER.
Make sure you don't even compile it.

Now if you really want to bypass the security check, edit
drivers/i2c/busses/i2c-piix4.c. In function piix4_setup, you'lle find:

	/* Don't access SMBus on IBM systems which get corrupted eeproms */
	if (dmi_check_system(piix4_dmi_table) &&
			PIIX4_dev->vendor == PCI_VENDOR_ID_INTEL) {
		dev_err(&PIIX4_dev->dev, "IBM Laptop detected; this module "
			"may corrupt your serial eeprom! Refusing to load "
			"module!\n");
		return -EPERM;
	}

Rip the whole block, recompile and you're done.

(And if you break your system we are not reponsible, of course.)

-- 
Jean Delvare



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux