ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: community@lists.altlinux.org
Subject: Re: [Comm] lm sensors
Date: Sun, 27 Apr 2008 23:31:42 +0400
Message-ID: <20080427193142.GA5004@atlas.home> (raw)
In-Reply-To: <4814C5C8.80409@mail.ru>

[-- Attachment #1: Type: text/plain, Size: 3359 bytes --]

On Sun, Apr 27, 2008 at 10:28:24PM +0400, Vladimir Karpinsky wrote:
> Пытаюсь настроить lm_sensors: sensors-detect 
> отрабатывает и выдаёт:
> 
> Driver `to-be-written' (should be inserted):
>   Detects correctly:
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x09
>     Chip `Smart Battery Charger' (confidence: 5)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x0a
>     Chip `Smart Battery Manager/Selector' (confidence: 5)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x18
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x19
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1a
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1b
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1c
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1d
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1e
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x1f
>     Chip `Philips Semiconductors PCA9556' (confidence: 1)

Это явно что-то неверно определилось...

> Driver `smartbatt' (should be inserted):
>   Detects correctly:
>   * Bus `NVIDIA i2c adapter 2 at 5:00.0'
>     Busdriver `UNKNOWN', I2C address 0x0b
>     Chip `Smart Battery' (confidence: 5)

И это тоже (ну откуда на видеокарте батарея?).

> Driver `w83627ehf' (should be inserted):
>   Detects correctly:
>   * ISA bus, address 0x290
>     Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Хотя модуль w83627ehf и есть в ядре 2.6.18, поддержка чипа W83627DHG в
нём появилась только начиная с 2.6.21.

> Driver `coretemp' (should be inserted):
>   Detects correctly:
>   * Chip `Intel Core family thermal sensor' (confidence: 9)

Модуль coretemp в общем случае присутствует только в ядрах >= 2.6.22,
однако добавлен в kernel-image-std-smp >= 2.6.18-alt11.

> Можно всё-таки заставить работать 
> сенсоры?
> 
> # sensors -v
> sensors version 2.10.2 with libsensors version 2.10.2
> 
> # uname -a
> Linux newseismix 2.6.18-std-smp-alt7 #1 SMP Sat Aug 4 00:07:54 MSD 2007 
> i686 GNU/Linux

Модуль coretemp есть в свежих сборках ядер 2.6.18-std-smp (правда,
поддержки новых процессоров Penryn там нет - её добавили только в
2.6.25); для поддержки остальных сенсоров потребуется более
существенное обновление ядра.

Кстати, что это за материнка?  На некоторых платах сенсоры на самом
деле не подключены к чипу Super-IO (например, у ABIT в топовых моделях
используется собственный чип uGuru, который не определяется
автоматически через sensors-detect; модуль abituguru3 также добавлен в
2.6.18-std-smp-alt11, а вообще входит в ядро начиная с 2.6.23).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-27 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 18:28 Vladimir Karpinsky
2008-04-27 19:31 ` Sergey Vlasov [this message]
2008-04-28  7:48   ` Vladimir Karpinsky

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=20080427193142.GA5004@atlas.home \
    --to=vsu@altlinux.ru \
    --cc=community@lists.altlinux.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

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git