All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm_sensors and nvidia graphic card temperature
Date: Tue, 13 Dec 2005 20:16:30 +0000	[thread overview]
Message-ID: <20051213211630.13006ce2.khali@linux-fr.org> (raw)
In-Reply-To: <4399BE92.9020705@mathematica.scientia.net>

Hi Volker,

> > Alternatively, you should be able to gain control of the nVidia I2C
> > busses using the in-kernel-tree rivafb or nvidiafb framebuffer drivers.
> 
> I have a rivafb module, which loads fine and produces no output on
> stderr or syslog. What does "gain control of the nvidia i2c busses"
> mean? That sensors-detect should find them? It doesn't for me:

"Gain control" means that i2c/smbus chip drivers can "see" the bus and
try attaching to devices thereon. You can use i2cdetect to list and
probe these busses.

> modprobe -v rivafb
> sensors-detect
> ...
> Driver `eeprom' (should be inserted):
>   Detects correctly:
>   * Bus `SMBus nForce2 adapter at 1c00'
>     Busdriver `i2c-nforce2', I2C address 0x50
>     Chip `SPD EEPROM' (confidence: 8)
>   * Bus `SMBus nForce2 adapter at 1c00'
>     Busdriver `i2c-nforce2', I2C address 0x51
>     Chip `SPD EEPROM' (confidence: 8)
> Driver `it87' (should be inserted):
>   Detects correctly:
>   * ISA bus address 0x0290 (Busdriver `i2c-isa')
>     Chip `ITE 8712F Super IO Sensors' (confidence: 9)
> ...
> 
> Same output as always.
> 
> Are we talking about the same thing?

If you have a recent graphics adapter, you most likely need the
nvidiafb driver. Just because rivafb loads silently doesn't mean it did
anything useful. Actually, the fact that it was silent suggests very
strongly that it does NOT support your graphics adapter.

> Linux .. 2.6.13-15.7-default #1 Tue Nov 29 14:32:29 UTC 2005 x86_64
> sensors-2.9.1-4
> Gigabyte PCI-express graphics card with nvidia geforce 6600 chip
> 
> > Make sure to enable "DDC support" in either case.
> 
> Where? The kernel config doesn't seem to know about it:
> zgrep -i ddc /proc/config.gz
> gives no output. Grepping through the kernel source doesn't tell me
> anything more, and none of the 5 rivafb module paramters have to do with
> DDC.

For some reason the symbols have "I2C" rather than "DDC" in their names:

CONFIG_FB_RIVA_I2C:
CONFIG_FB_NVIDIA_I2C

-- 
Jean Delvare


  parent reply	other threads:[~2005-12-13 20:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 17:27 [lm-sensors] lm_sensors and nvidia graphic card temperature Christoph Anton Mitterer
2005-12-11 20:07 ` Christoph Anton Mitterer
2005-12-12 18:09 ` Jean Delvare
2005-12-12 22:11 ` Volker Kuhlmann
2005-12-13 20:16 ` Jean Delvare [this message]
2005-12-15 19:25 ` Volker Kuhlmann
2005-12-18 17:39 ` Jean Delvare
2005-12-19 16:07 ` Volker Kuhlmann
2005-12-12 18:16 Jean Delvare
2005-12-12 23:37 ` Volker Kuhlmann

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=20051213211630.13006ce2.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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.