<br><br><div class="gmail_quote">2010/1/7 Alan Jenkins <span dir="ltr"><<a href="mailto:sourcejedi.lkml@googlemail.com">sourcejedi.lkml@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On 1/6/10, giggzounet <<a href="mailto:giggzounet@gmail.com">giggzounet@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> With the kernel of lenny bakcport 2.6.30 the module i2c_nforce2 loads<br>
> without problem : in dmesg I see :<br>
><br>
> [ 6.569759] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x4d00<br>
> [ 6.569905] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x4e00<br>
><br>
><br>
> With the 2.6.32.2 I see :<br>
> [ 3.842775] i2c i2c-0: nForce2 SMBus adapter at 0x4d00<br>
> [ 3.842861] ACPI: I/O resource nForce2_smbus [0x4e00-0x4e3f]<br>
> conflicts with ACPI region SM00 [0x4e00-0x4e3f]<br>
> [ 3.842949] ACPI: If an ACPI driver is available for this device, you<br>
> should use it instead of the native driver<br>
> [ 3.843036] nForce2_smbus 0000:00:03.2: Error probing SMB2.<br>
><br>
><br>
> What can I do in order to solve this problem ?<br>
<br>
</div></div>It's only a problem if you have hardware monitoring sensors you want<br>
to use on that bus, for whatever reason.<br>
<br>
If you know the kernel is being over-cautious because you've inspected<br>
the DSDT etc. and found that the ACPI BIOS doesn't actually use the<br>
SM00 region, then you want "acpi_enforce_resources=lax". (<br>
<br>
If you want to see an example of a ACPI hwmon driver, look at the Asus ATK0110.<br>
<br>
The third possibility is that the ACPI BIOS uses the sensors for<br>
internal purposes but exposes no interface. Or more realistically, it<br>
exposes it as an ACPI thermal zone, but omits information like<br>
voltages that you're interested in.<br>
<br>
The kernel has to respect these ACPI resource reservations.<br>
Conflicts between the BIOS and kernel driving the same hardware can<br>
cause mysterious slowdowns and worse (and have done so on other EeePC<br>
models).<br>
</blockquote></div><br>Ok thx for your explanation.<br><br>What I found strange is : I don't have any error messages with the 2.6.30 and I get this error message with 2.6.32. Also perhaps a driver does something wrong...<br>
<br>Cheers,<br>Guillaume<br>