This problem still exists in gutsy.  There are some additional tools
such as i2cdetect.  The message should be something like:

"Try sudo modprobe i2c-dev

Then try running sensors-detect again:

sudo sensors-detect"

The error description in i2cdetect is a little more descriptive:

[EMAIL PROTECTED]:/usr/sbin$ i2cdetect -a
Error: No i2c-bus specified!
Syntax: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
        i2cdetect -l
        i2cdetect -V
  I2CBUS is an integer
  With -a, probe all addresses (NOT RECOMMENDED)
  With -q, uses only quick write commands for probing (NOT RECOMMENDED)
  With -r, uses only read byte commands for probing (NOT RECOMMENDED)
  If provided, FIRST and LAST limit the probing range.
  With -l, lists installed busses only
Error: No I2C busses found!
Be sure you have done 'modprobe i2c-dev'
and also modprobed your i2c bus drivers

Adding the i2c-dev module is the same as running the mkdev.sh, it's just
that mkdev.sh is not included in the normal debian package.

This does trip up first-time lm-sensor users.

-- 
does not include mkdev.sh
https://bugs.launchpad.net/bugs/45482
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to