[swan@xxxxxxxxxxxxxxxx: Ticket #1017]

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

 



Stefan Schwandter wrote:


> > does it actually work though? any chips found on the bus?
> > (try sensors-detect, or i2cdetect 1)

Ok:

sensors-detect suggests:

#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe w83781d
#----cut here----

To make the sensors modules behave correctly, add these lines to either
/etc/modules.conf or /etc/conf.modules:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----


i2cdetect gives:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
	 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
	 10: XX XX XX XX XX XX XX XX XX XX XX 1b XX XX XX XX 
	 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX UU 
	 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
	 40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
	 50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
	 60: XX XX XX XX XX XX XX XX XX 69 6a XX XX XX XX XX 
	 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
	 

I can use sensors to look at the values of the lm80 chip (although
they're nonsense, but that's another problem - the second chip on the
motherboard, w83781d gives sane values).

If you want me to do some more testing, please say so!


regards, Stefan
-- 
----> http://www.shockfrosted.org



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

  Powered by Linux