Your message dated Tue, 11 Jan 2005 06:47:35 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289798: fixed in lm-sensors 1:2.9.0-5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Jan 2005 03:34:39 +0000
>From [EMAIL PROTECTED] Mon Jan 10 19:34:38 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mxc.rambler.ru [81.19.66.31]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CoCnl-0001wI-00; Mon, 10 Jan 2005 19:34:38 -0800
Received: from mailc.rambler.ru (mailc.rambler.ru [81.19.66.27])
by mxc.rambler.ru (Postfix) with ESMTP id 4AE20CD985;
Tue, 11 Jan 2005 06:34:36 +0300 (MSK)
Received: from balto (bioline.dialup.wplus.net [195.131.75.85])
(authenticated bits=0)
by mailc.rambler.ru (8.12.10/8.12.10) with ESMTP id j0B3YWYl046208;
Tue, 11 Jan 2005 06:34:34 +0300 (MSK)
Received: from balto by balto with local (Exim 4.34)
id 1CoCau-0001V3-7j; Tue, 11 Jan 2005 06:21:20 +0300
Content-Type: multipart/mixed; boundary="===============1129079301=="
MIME-Version: 1.0
From: Dmitry Rutsky <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: lm-sensors: sensors-detect doesn't work perfectly for my VT82C686A
chipset
X-Mailer: reportbug 2.99.5
Date: Tue, 11 Jan 2005 06:21:20 +0300
Message-Id: <[EMAIL PROTECTED]>
Sender: Dmitry Rutsky <[EMAIL PROTECTED]>
X-Auth-User: gnuser, whoson: (null)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============1129079301==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: lm-sensors
Version: 1:2.9.0-4
Severity: wishlist
Output of sensors-detect attached. Proposed configuration didn't work --- "No
sensors found!" After a bit of expirementation I found that following modules
sequence:
====
i2c-isa
i2c-core
i2c-dev
via686a
====
works. But if I try to modprobe that after i2c-viapro is loaded, it doesn't
work and there seems to be silence in /var/log/syslog (no messages at all on
insertion). Does i2c-viapro somehow interfere with other drivers? If it does,
it would be nice to have a line about that in
/usr/share/doc/lm-sensors/doc/FAQ.gz, section 4.21, until whatever causes this
malfunction will be fixed.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R
Versions of packages lm-sensors depends on:
ii debconf [debconf-2.0] 1.4.38 Debian configuration management sy
ii libc6 2.3.2.ds1-17 GNU C Library: Shared libraries an
ii libsensors3 1:2.9.0-4 Library to read temperature/voltag
ii makedev 2.3.1-75 Creates device files in /dev
ii perl 5.8.4-2.3 Larry Wall's Practical Extraction
ii sed 4.1.2-1 The GNU sed stream editor
ii sysvinit 2.86-5 System-V like init
ii ucf 1.09 Update Configuration File: preserv
-- debconf information:
lm-sensors/negatives:
--===============1129079301==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="o"
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:07.4: VIA Technologies VT82C686 Apollo
ACPI
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-viapro' (say NO if built into your kernel)? (YES/no): Module loaded
succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): Module loaded
succesfully.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Next adapter: SMBus Via Pro adapter at 5000
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x69
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): Probing for `National Semiconductor
LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Success!
(confidence 9, driver `via686a')
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): Probing for `ITE 8702F
Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Do you want to scan for secondary Super I/O sensors? (YES/no): Probing for `ITE
8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus Via Pro adapter at 5000' (Algorithm unavailable)
Busdriver `i2c-viapro', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
Driver `via686a' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Hint: Try forcing the chip address. Consult the documentation
of particular chip for details and address value.
Chip `VIA Technologies VT82C686 Integrated Sensors' (confidence: 9)
I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)?
To make the sensors modules behave correctly, add these lines to
/etc/modules:
#----cut here----
# I2C adapter drivers
i2c-viapro
i2c-isa
# I2C chip drivers
eeprom
via686a
#----cut here----
Do you wan't to add these lines to /etc/modules automatically? (yes/NO)
--===============1129079301==--
---------------------------------------
Received: (at 289798-close) by bugs.debian.org; 11 Jan 2005 11:52:15 +0000
>From [EMAIL PROTECTED] Tue Jan 11 03:52:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CoKZK-0001CN-00; Tue, 11 Jan 2005 03:52:14 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CoKUp-0006yk-00; Tue, 11 Jan 2005 06:47:35 -0500
From: Aurelien Jarno <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.54 $
Subject: Bug#289798: fixed in lm-sensors 1:2.9.0-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 11 Jan 2005 06:47:35 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-4.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: lm-sensors
Source-Version: 1:2.9.0-5
We believe that the bug you reported is fixed in the latest version of
lm-sensors, which is due to be installed in the Debian FTP archive:
kernel-patch-2.4-lm-sensors_2.9.0-5_all.deb
to pool/main/l/lm-sensors/kernel-patch-2.4-lm-sensors_2.9.0-5_all.deb
libsensors-dev_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/libsensors-dev_2.9.0-5_i386.deb
libsensors3_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/libsensors3_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-386_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-386_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-586tsc_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-586tsc_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-686-smp_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-686-smp_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-686_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-686_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-k6_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-k6_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-k7-smp_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-k7-smp_2.9.0-5_i386.deb
lm-sensors-2.4.27-1-k7_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors-2.4.27-1-k7_2.9.0-5_i386.deb
lm-sensors-source_2.9.0-5_all.deb
to pool/main/l/lm-sensors/lm-sensors-source_2.9.0-5_all.deb
lm-sensors_2.9.0-5.diff.gz
to pool/main/l/lm-sensors/lm-sensors_2.9.0-5.diff.gz
lm-sensors_2.9.0-5.dsc
to pool/main/l/lm-sensors/lm-sensors_2.9.0-5.dsc
lm-sensors_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/lm-sensors_2.9.0-5_i386.deb
sensord_2.9.0-5_i386.deb
to pool/main/l/lm-sensors/sensord_2.9.0-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurelien Jarno <[EMAIL PROTECTED]> (supplier of updated lm-sensors package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 11 Jan 2005 12:12:34 +0100
Source: lm-sensors
Binary: lm-sensors-2.4.27-1-k6 lm-sensors-2.4.27-1-586tsc lm-sensors-source
libsensors-dev lm-sensors-2.4.27-1-k7 lm-sensors sensord
kernel-patch-2.4-lm-sensors lm-sensors-2.4.27-1-686 lm-sensors-2.4.27-1-k7-smp
libsensors3 lm-sensors-2.4.27-1-386 lm-sensors-2.4.27-1-686-smp
Architecture: source i386 all
Version: 1:2.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Aurelien Jarno <[EMAIL PROTECTED]>
Changed-By: Aurelien Jarno <[EMAIL PROTECTED]>
Description:
kernel-patch-2.4-lm-sensors - Drivers to read temperature/voltage/fan sensors
libsensors-dev - Lm-sensors development kit
libsensors3 - Library to read temperature/voltage/fan sensors
lm-sensors - Utilities to read temperature/voltage/fan sensors
lm-sensors-2.4.27-1-386 - Kernel drivers to read temperature/voltage/fan
sensors
lm-sensors-2.4.27-1-586tsc - Kernel drivers to read temperature/voltage/fan
sensors
lm-sensors-2.4.27-1-686 - Kernel drivers to read temperature/voltage/fan
sensors
lm-sensors-2.4.27-1-686-smp - Kernel drivers to read temperature/voltage/fan
sensors
lm-sensors-2.4.27-1-k6 - Kernel drivers to read temperature/voltage/fan sensors
lm-sensors-2.4.27-1-k7 - Kernel drivers to read temperature/voltage/fan sensors
lm-sensors-2.4.27-1-k7-smp - Kernel drivers to read temperature/voltage/fan
sensors
lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors
(source)
sensord - Hardware sensor information logging daemon
Closes: 289798
Changes:
lm-sensors (1:2.9.0-5) unstable; urgency=medium
.
* Added a note to the FAQ and to sensors-detect about via686a and
i2c-viapro conflict.
* Prevent this module to be automatically loaded by hotplug.
* Closes: bug#289798.
Files:
61f059a441d91304d52c1184d8dce518 1067 utils extra lm-sensors_2.9.0-5.dsc
05baba963bb7d6cca0d9fd67ec8a85c3 37013 utils extra lm-sensors_2.9.0-5.diff.gz
a15995b16f54fe3a89327fce4ab90790 453558 utils extra lm-sensors_2.9.0-5_i386.deb
2119f7b69f60af737259158c65370615 74320 libs optional
libsensors3_2.9.0-5_i386.deb
4be289d6dbc67e0ff915febd0e468160 89354 libdevel extra
libsensors-dev_2.9.0-5_i386.deb
56e77f8fa52039f2a1c8f69eb5e8caea 53524 utils extra sensord_2.9.0-5_i386.deb
43f2f623b39a7d50382210fe8a17bbda 247608 utils extra
lm-sensors-2.4.27-1-386_2.9.0-5_i386.deb
59f8e6516efac2aaf8ed6df328e135c6 247326 utils extra
lm-sensors-2.4.27-1-586tsc_2.9.0-5_i386.deb
f1cdfd2ff37c973ccd3be61bf6157ab5 247606 utils extra
lm-sensors-2.4.27-1-686_2.9.0-5_i386.deb
d023a0461de672424da73a920aeffec0 247826 utils extra
lm-sensors-2.4.27-1-686-smp_2.9.0-5_i386.deb
482c4309125790e62df0bea72279262b 247618 utils extra
lm-sensors-2.4.27-1-k6_2.9.0-5_i386.deb
46ca47e4d94a2118939471ce8e406e75 247908 utils extra
lm-sensors-2.4.27-1-k7_2.9.0-5_i386.deb
e9659ec9a3b190d133f994b69bf56a62 248104 utils extra
lm-sensors-2.4.27-1-k7-smp_2.9.0-5_i386.deb
b1f5671a395966b5428f10ecdddfdf74 274250 devel extra
kernel-patch-2.4-lm-sensors_2.9.0-5_all.deb
6a0a4ba6c1e4e2b8b403e5c7968b3cef 897006 misc extra
lm-sensors-source_2.9.0-5_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFB47mNw3ao2vG823MRAqQ2AJ9O0z3eM9f5/Rfuw8efjUB6oBAYvQCeNzb1
4w1KyxOP/3zMjpq5ZCzyIew=
=NnuB
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
