Jean, No. Sorry, I missed your previous response about the potential conflict with acpi. I'll give that a try over the weekend. If I remember correctly, i2cscan would not show any devices on 2 of the 3 buses. I doubt that's related to acpi. it looks more like something broke in i2c-nforce. I'll try to do some more debugging over the weekend (if I can find the time). ...juerg On Fri, Jan 15, 2010 at 5:29 AM, Jean Delvare <khali@xxxxxxxxxxxx> wrote: > On Wed, 6 Jan 2010 18:09:05 +0100, Jean Delvare wrote: >> On Wed, 6 Jan 2010 08:50:30 -0800, Juerg Haefliger wrote: >> > Yes and no. I have a patch but it doesn't work on 2.6.33-rc2. In fact, >> > even the vanilla dme1737 driver doesn't seem to work on 2.6.33-rc2 and >> > sensors-detect is unable to find the I2C part of the chip. Haven't >> > looked too closely yet but I must be missing something obvious. 2.6.28 >> > works just fine. >> >> Could be that your machine is affected by the ACPI vs. native driver >> resource conflict check that was added in kernel 2.6.32? >> >> Try booting with acpi_enforce_resources=lax and see if it helps. > > Juerg, anything new? I'd like to solve this issue quickly. > > Thanks, > -- > Jean Delvare > _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
