All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Hrvoje T <hrvooje@jankovci.net>, linux-i2c@vger.kernel.org
Subject: Re: SMBus not found
Date: Fri, 03 Feb 2017 11:53:28 +0100	[thread overview]
Message-ID: <1486119208.4299.11.camel@suse.de> (raw)
In-Reply-To: <CANE=DpU===GBGNY0+QJCKuw295kkYSEPN-oeaT7cG6DRcNdjiA@mail.gmail.com>

Hi Hrvoje,

Please use plain text (no HTML) when writing to development lists.

On jeu., 2017-02-02 at 14:50 +0100, Hrvoje T wrote:
> When I run sensors-detect I get an answer:
> Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
> Sorry, no supported PCI bus adapters found.
> Is tehere anything else I can try?

You did not tell which version of sensors-detect you tried, nor what
kernel you are running, nor what your hardware is. What kind of help
are you expecting?

You should probably not be using sensors-detect in the first place
anyway. i2cdetect (from the i2c-tools package) is a much better tool
for what you are trying to do.

> Is it possible to dump addresses 0x50-0x57 on this bus with i2cdump
> and run decode-dimms -x on them? How could I do this when I don't
> know which bus is SMBus?

This question makes no sense as "this bus" is clearly undefined at this
point. First check what I2C/SMBus busses are available on your system:

# modprobe i2c-dev
# i2cdetect -l

Then either run i2cdetect / i2cdump on the relevant bus if it was
listed, or try to figure out why it is not listed (looking for it with
lspci maybe, if your SMBus controller is a PCI device.)

-- 
Jean Delvare
SUSE L3 Support

       reply	other threads:[~2017-02-03 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANE=DpU===GBGNY0+QJCKuw295kkYSEPN-oeaT7cG6DRcNdjiA@mail.gmail.com>
2017-02-03 10:53 ` Jean Delvare [this message]
     [not found]   ` <CANE=DpWovf4BO31Dqzj72hN=8etRLwFbyrDMZMzqzFNFtRe2cg@mail.gmail.com>
2017-02-04  1:55     ` SMBus not found Hrvoje T
2017-02-09  8:49       ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1486119208.4299.11.camel@suse.de \
    --to=jdelvare@suse.de \
    --cc=hrvooje@jankovci.net \
    --cc=linux-i2c@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.