Hi Karl, On Sat, 05 Sep 2009 14:07:49 -0500, Karl Schmidt wrote: > Jean Delvare wrote: > > Now, one thing I would like to understand is how the lm85 driver was > > loaded in the first place. In the dump you sent, the chip is clearly > > identified as an SMSC chip, with the device ID of the DME1737. So, if > > the lm85 driver identifies this chip as a different device, it must > > have been told to, by the means of a module parameter. > > > > Please provide the output of: > > > > modprobe -c | grep lm85 > > # modprobe -c|grep lm85 > > [returns nothing ] > > #lsmod |grep lm85 > lm85 35492 0 > hwmon_vid 7296 2 lm85,dme1737 > i2c_core 27936 4 i2c_nforce2,lm85,dme1737,i2c_dev > > > - ah but looking at /et/modules I have: > --------------------------------- > # Generated by sensors-detect on Tue Mar 13 22:13:10 2007 > # I2C adapter drivers > i2c-nforce2 > # Chip drivers > > #make it look like lm85b > lm85 force_lm85b=0,0x2e > #lm85 > eeprom > k8temp > # Warning: the required module k8temp is not currently installed > # on your system. For status of 2.6 kernel ports check > # http://www.lm-sensors.org/wiki/Devices. If driver is built > # into the kernel, or unavailable, comment out the following line. > #k8temp > > # Generated by sensors-detect on Fri Aug 28 12:15:00 2009 > # I2C adapter drivers > i2c-nforce2 > ------------------ > > > > > I bet you have a force_lm85b module parameter there. If so, please > > remove it. > You are correct! Removed it - /etc/modules (modules to load at boot time) now reads: > > > options dme1737 ignore=1,0x2e > # Generated by sensors-detect on Sat Sep 5 12:51:21 2009 > # I2C adapter drivers > i2c-nforce2 > # Chip drivers > dme1737 > k8temp > > ?? It is still seeing that chip both times. > > dme1737-i2c-0-2e > Adapter: SMBus nForce2 adapter at 1c00 > <sinp> > dme1737-i2c-0-2e > Adapter: SMBus nForce2 adapter at 1c00 Please double-check. I don't even see how this is technically possible. The second entry would have a different address (1-2e), and live on an adapter with a different address too. Not that it really matters... > > I rmmod dme1737 - and then > modprobe dme1737 option ignore=1,0x2e > > failed to work - As expected, this isn't a valid modprobe command. > > but > modprobe dme1737 ignore=1,0x2e > > OK - it now sees just one chip - but alarms still won't work - I think the keyword 'option' > shouldn't be used in /etc/modules - confirmed with a reboot. > > > #sensors > > k8temp-pci-00c3 > > Adapter: PCI adapter > > temp1: +20.0°C > > > > dme1737-i2c-0-2e > > Adapter: SMBus nForce2 adapter at 1c00 > > in0: +2.61 V (min = +0.00 V, max = +2.00 V) > > in1: +1.43 V (min = +0.00 V, max = +2.99 V) > > in2: +3.35 V (min = +0.00 V, max = +4.38 V) > > in3: +5.10 V (min = +0.00 V, max = +6.64 V) > > in4: +12.09 V (min = +0.00 V, max = +15.94 V) > > in5: +3.30 V (min = +0.00 V, max = +4.38 V) > > in6: +3.00 V (min = +0.00 V, max = +4.38 V) > > fan1: 7826 RPM (min = 8000 RPM) > > fan2: 8157 RPM (min = 9000 RPM) > > fan3: 7917 RPM (min = 0 RPM) > > fan4: 7929 RPM (min = 0 RPM) > > temp1: +37.1°C (low = -127.0°C, high = +127.0°C) > > temp2: +26.8°C (low = -127.0°C, high = +127.0°C) > > temp3: +23.4°C (low = -127.0°C, high = +127.0°C) > > cpu0_vid: +1.550 V > > Is it ignoring the wrong one?? I doubt there is a "right one" and a "wrong one". Tomorrow I'll look at the DME1737 datasheet and compare with the i2c dump. I'm not too familiar with this chip, maybe the alarms can be disabled somehow. Juerg, does it ring a bell? > > I would also be curious to see the full output sensors-detect after > > unloading both the lm85 and the dme1737 drivers. > > See attached You forgot to rmmod dme1737 beforehand, which makes the output uninteresting. -- Jean Delvare http://khali.linux-fr.org/wishlist.html _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
