On 09/25/2013 11:09 PM, Jean Delvare wrote:
On Wed, 25 Sep 2013 15:05:11 -0700, Guenter Roeck wrote:
On Wed, Sep 25, 2013 at 05:45:38PM -0400, Benjo Dans wrote:
Jean/Guenter,
I am not sure where I got the version from but it is working a little bit better after getting the one from your link. Thank you for noticing that difference. I now get the following using i2cdetect -l after loading i2c-dev and the newer i2c-i801.
Doesn't look better, though.
I2c-0 i2c i915 gmbus ssc I2C adapter
I2c-1 i2c i915 gmbus vga I2C adapter
I2c-2 i2c i915 gmbus panel I2C adapter
I2c-3 i2c i915 gmbus dpc I2C adapter
I2c-4 i2c i915 gmbus dpb I2C adapter
I2c-5 i2c i915 gmbus dpd I2C adapter
I2c-6 i2c i915 gmbus DPDDC-D I2C adapter
Although I do see devices on i2c-1, I still do not see the smbus anywhere. This aligns with my not seeing any activity on the smbus with an oscilloscope during the i2cdetect process. What am I missing on why it is not communicating and/or finding my Lynx Point PCH as well as the devices connected to that smbus?
As always, thank you, everyone.
Next step might be to run lspci -nn and compare the output with the PCI IDs
supported by your version of the i2c-i801 driver.
And again, check the kernel log after loading the i2c-i801 driver. If
probing the device fails for any reason, there should be an error
message in that log.
Yes. I have a system with LynxPoint. I tested it last night;
it fails to load on that system because of an ACPI conflict.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
