i2c i temp - jak to zainstalowa

[bigl]

Debian lenny, kernel 2.6.22.6

repo standardowe - z podwieszonego tematu
lm-sensors-sources nie mam, więc nie mogłem wydać apt-get install lm-sensors-sources

Zainstalowałem lm-sensors, odpowiedziałem na te wszystkie pytania tak jak jest to opisane w temacie o conky.
Mam w jądrze I2C support i I2C device interfaces

komenda sensors (jako user) wywala mi, że nie znalał żadnych czujników.

Próbowałem ściągać lm-sensors-sources i kompilować, ale wywalił mi:

Kod: Zaznacz cały

make: *** No rule to make target `linux/i2c-proc.h', needed by `prog/sensord/chips.rd'.  Stop.

EDIT
Nie mam nigdzie tego pliku i2c-proc.h - nawet w źródłach jądra (kompilowałem je ręcznie)

Kto pomoże ?

[stoper]

Witam. Nie chce mi się wierzyć, że się nie da. A czy wykonałeś po instalacji pakietu lm_sensors

Kod: Zaznacz cały

 #sensors-detect

Na wszystkie pytania odpowiadasz twierdząco. Szczególnie zwróć uwagę na komunikaty i jeden z ostatnich, bo być może trzeba będzie zgodnie z sugestią wkleić fragment kodu do właściwego katalogu. Poza tym na ten temat było już tak wiele razy i wyczerpująco, że chyba nie przeszukałeś Forum. Nie dziwne więc, że jakoś się ludziom nie chce zabierać głosu w tej sprawie.
Po drugie - po co kompilować, czy masz jakiś specjalnie dziwny i unikalny sprzęt? To nie Gentoo i masz gotową paczkę która załatwia sprawę.
Pozdrawiam i powodzenia.

[bigl]

Przeszukalem forum i nie znalazlem nic, co by mi pomoglo.
Na koncu jest wykrywany k8 cos tam i jest napisane, zebym dopisal go do /etc/modules - zrobilem to

Jadro z paczki nie chcialo dzialac tak jak powinno - mialem problemy z urzadzeniami USB itp - po samodzielnym skompilowaniu wszystko zaczelo dzialac poprawnie

[ Dodano: 2007-10-17, 17:40 ]
Tak wygląda mój proces sensors-detect

Kod: Zaznacz cały

Script started on Wed 17 Oct 2007 05:37:49 PM CEST
debian:/home/me# sensors-detect 
# sensors-detect revision 4609 (2007-07-14 09:28:39 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no): 
Probing for PCI bus adapters...
Use driver `i2c-sis96x' for device 0000:00:02.1: Silicon Integrated Systems SMBus Controller

We will now try to load each adapter module in turn.
Load `i2c-sis96x' (say NO if built into your kernel)? (YES/no): 
FATAL: Module i2c_sis96x not found.
Loading failed... skipping.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: PCA9564 ISA Adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): 

Next adapter: SiS96x SMBus adapter at 0x8100 (i2c-1)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   Yes
Found `Nat. Semi. PC87591 Super IO'                         
    (but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): 
AMD K8 thermal sensors...                                   Success!
    (driver `k8temp')
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k8temp' (should be inserted):
  Detects correctly:
  * Chip `AMD K8 thermal sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue: 

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# Chip drivers
# Warning: the required module k8temp is not currently installed
# on your system. For status of 2.6 kernel ports check
# [url]http://www.lm-sensors.org/wiki/Devices[/url]. If driver is built
# into the kernel, or unavailable, comment out the following line.
k8temp
#----cut here----


Do you want to add these lines to /etc/modules automatically? (yes/NO)yes
debian:/home/me# c[Kexit

Script done on Wed 17 Oct 2007 05:40:42 PM CEST

[stoper]

Nie używam monitora temperatury akurat w tej wersji debiana (dreamlinux) ale przy tej okazji zainstalowałem lm_sensors z takim wynikiem. Działa prawidłowo i "od ręki"

Kod: Zaznacz cały

# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge

We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
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.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: NVIDIA i2c adapter 2 at 1:00.0
Do you want to scan it? (YES/no/selectively):


Next adapter: NVIDIA i2c adapter 1 at 1:00.0
Do you want to scan it? (YES/no/selectively): Client found at address 0x75

Next adapter: NVIDIA i2c adapter 0 at 1:00.0
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x07
Client found at address 0x08
Client found at address 0x09
Probing for `Smart Battery Charger'...                      Success!
    (confidence 5, driver `to-be-written')
Client found at address 0x1a
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Philips Semiconductors PCA9556'...             No
Client found at address 0x4f
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS1621'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Success!
    (confidence 1, driver `eeprom')
Probing for `EDID EEPROM'...                                No
Probing for `Maxim MAX6900'...                              No
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'...               Success!
    (confidence 1, driver `not-a-sensor')
Client found at address 0x62
Client found at address 0x63
Client found at address 0x64
Client found at address 0x65
Client found at address 0x66
Client found at address 0x67
Client found at address 0x68
Client found at address 0x69
Client found at address 0x6a
Client found at address 0x6b
Client found at address 0x6c
Client found at address 0x6d
Client found at address 0x6e

Next adapter: bt848 #0 [sw]
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x60
Handled by driver `tuner' (already loaded), chip type `Temic PAL (4002 FH5)'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x61
Handled by driver `tuner' (already loaded), chip type `(tuner unset)'
    (note: this is probably NOT a sensor chip!)

Next adapter: SMBus Via Pro adapter at e800
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x37
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Success!
    (confidence 8, driver `eeprom')
Probing for `EDID EEPROM'...                                No
Probing for `Maxim MAX6900'...                              No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Success!
    (confidence 8, driver `eeprom')
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `Winbond W83627HF' at 0x290...                  No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `AMD K8 thermal sensors'...                     No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found `ITE IT8712F Super IO Sensors'                        Success!
    (address 0x290, driver `it87')
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * Bus `NVIDIA i2c adapter 0 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x09
    Chip `Smart Battery Charger' (confidence: 5)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `NVIDIA i2c adapter 0 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 1)
  * Bus `SMBus Via Pro adapter at e800'
    Busdriver `i2c-viapro', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus Via Pro adapter at e800'
    Busdriver `i2c-viapro', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus Via Pro adapter at e800'
    Busdriver `i2c-viapro', I2C address 0x52
    Chip `SPD EEPROM' (confidence: 8)

  EEPROMs are *NOT* sensors! They are data storage chips commonly
  found on memory modules (SPD), in monitors (EDID), or in some
  laptops, for example.

Driver `it87' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE IT8712F Super IO Sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter bt848 #0 [sw]
# modprobe unknown adapter NVIDIA i2c adapter 0 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 1:00.0
i2c-viapro
# Chip drivers
# no driver for Smart Battery Charger yet
eeprom
it87
#----cut here----


Do you want to add these lines to /etc/modules automatically? (yes/NO)

Może przyda ci się dla porównania. Cała operacja zajęła mi dosłownie 120 sek wraz ze sprawdzeniem poprawności wpisów w /etc/modules.

Kod: Zaznacz cały

stoper@DL:~$ sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1:   +1.68 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
VCore 2:   +0.00 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
+3.3V:      +3.18 V  (min =  +4.08 V, max =  +4.08 V)   ALARM
+5V:         +4.95 V  (min =  +6.85 V, max =  +6.85 V)   ALARM
+12V:       +12.42 V  (min = +16.32 V, max = +16.32 V)   ALARM
-12V:        -27.36 V  (min =  +3.93 V, max =  +3.93 V)   ALARM
-5V:          -13.64 V  (min =  +4.03 V, max =  +4.03 V)   ALARM
Stdby:       +4.95 V  (min =  +6.85 V, max =  +6.85 V)   ALARM
VBat:         +3.23 V
fan1:          5152 RPM  (min =    0 RPM, div = 2)
fan2:          5113 RPM  (min =    0 RPM, div = 2)
fan3:               0 RPM  (min =    0 RPM, div = 2)
CPU Temp:      +36°C  (low  =    -1°C, high =    -1°C)   sensor = thermistor
M/B  Temp:      +28°C  (low  =    -1°C, high =    -1°C)   sensor = thermistor
Temp3:              -1°C  (low  =    -1°C, high =    -1°C)   sensor = disabled   ALARM

Oczywiście trochę trzeba jeszcze dostroić wskazania w lm_sensors.conf.
Może nie doinstalowałeś libsensors, jeżeli instalowałeś za pomocą synaptic'a. Jeżeli apt-get'em to powinno się dociągnąć w zależnościach. Warto sprawdzić.
Pozdrawiam.

[bigl]

No ja niestety mam ciągle te same błędy, a przy jądrze instalowanym w sposób:
apt-get install linux-image-2.6.22 nawet system nie wstaje.

EDIT
instalowałem tez jądro tym sposobem
http://www.debianusers.pl/article.php?aid=10

i to samo przy komendzie sensors

[stoper]

bigl widzę, że się nie rozumiemy. Ciągle mówisz o kompilacji jądra, ale nic o sprzęcie.
Wklej wyniki komend:

Kod: Zaznacz cały

#lspci

oraz

Kod: Zaznacz cały

#lsmod

bo może masz jakiś nietypowy sprzęt.

[bigl]

Ok:

Kod: Zaznacz cały

lsmod:
Module                  Size  Used by
button                  5776  0 
thermal                10504  0 
processor              19372  1 thermal
fan                     3588  0 

Kod: Zaznacz cały

lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760/761 PCI/AGP VGA Display Adapter

Myślę, żę to dość typowy sprzęt

[stoper]

No to jesteśmy w domu. Sprzęt owszem, normalny. Ale 64-bitowy (tak to wygląda) a o czym nie napisałeś. Niestety nie mam doświadczeń z tym sprzętem, więc nie umiem ci pomóc. Z tego co się pobieżnie orientuję są jeszcze pewne problemy z obsługą maszyn 64-bitowych. Rozumiem że wybrałeś dystrybucję pod 64 bity do instalacji. Może wypowie się ktoś kto już na takim sprzęcie walczył. Na przyszłość, jeżeli przedstawiasz temat zawsze trzeba podać w pierwszej kolejności jak najwięcej informacji na temat posiadanej konfiguracji, bo inaczej nie znajdą się chętni do udzielenia pomocy.
Jeszcze jedno. Tylko tyle wyrzuca ci lsmod??? Jeżeli tak, to masz totalnie skoszoną kompilację jaja i dziwne że to w ogóle wstaje.
Pozdrawiam.

[bigl]

To tak:
To jest laptop (3 letni), Acer Aspire 3003NLC i on ma na 100% procesor 32 bitowy:
Mobile AMD Sempron 3000+, więc nie wiem jakim cudem on widzi tam 64 bitową architekturę :|

Napisałbym, gdyby był 64 bitowy bo wiem jakie problemy potrafią sprawiać te procki we współpracy z oprogramowaniem, ale dam sobie rękę uciąc, że jest 32 bitowy

Kurde, jak instaluje jądro z paczki, wywala mi błąd przy starcie, że nie może rootfs zamontować, albo coś z /bin/bash i przełącza mnie do powłoki csh

[stoper]

Może jest to i AMD Sempron 3000+, może 32 bit ale linux go widzi inaczej. Przykład: wynik lspci.
Jednak upierałbym się że nie jest to sprzęt należący do typowych i stąd reakcja jądra, które nie rozpoznaje go poprawnie. A poza tym to laptop (Po cichu tak podejrzewałem) czyli konstrukcja zamknięta sprzętowo i można sądzić, że "Windows'owe" oprogramowanie też ma na nim swoje kłopoty. Możliwe że tylko pod Gentoo da się sprzęt poprawnie dostroić. Oczywiście nie jestem ekspertem w tej sprawie.

Ciekawe jak sobie radzą wersje CD_live, np Knoppix. Czy prawidłowo rozpoznają ten sprzęt?
Może wypróbuj wersję live Debiana.

Pozdrawiam.