Samstag, 5. Mai 2007Das leidige Thema lm-sensors
Ich habe mich ja wirklich über meinen neuen Computer gefreut. Leider kam die Ernüchterung, als ich versucht habe Linux darauf zu installieren. Jetzt habe ich einen Haufen Hardware und kann nicht drauf zugreifen, weil sie noch nicht unterstützt wird. Da ich ein Anhänger des Paketsystems bin, habe ich mich bisher gescheut Programme aus den Sourcen zu installieren. Durch meinen Versuch, ob Feisty sich installieren lässt, habe ich noch eine Testversion auf dem Rechner. Auf dieser habe ich nun einen neuen Kernel mit den Patches für die Sensors compiliert.
Bei hobbesBlog habe ich einen Beitrag gefunden, in dem die Patches für mein MB vorhanden sind. Nur der Patch für die Doku für coretemp kam direkt aus einem Beitrag im Gentoo Forum. Ich habe also die folgenden 3 Patches verwendet: add-coretemp-driver.patch coretemp-add-documentation.patch hwmon-w83627ehf-add-w83627dhg-support.patch Als erstes habe ich die Sourcen für meinen bestehenden Kernel mit synaptic runtergeladen und wie weiter unten beschrieben konfiguriert. Durch Ausführen von sensors-detect wurden die entsprechenden Module (i2c-i801, eeprom, lm83, w83627ehf) dann zwar gefunden, die Ausgabe von sensors brachte aber keinen einzigen Wert. Ich habe mich dann doch entschlossen die sourcen von lm-sensors.org runterzuladen und zu installieren. Mir fehlten zum compilieren zwar einige Pakete (z. B. bison und flex), nach deren Installation funktionierte dann aber das compilieren und installieren mit: CODE: make clean #zum beseitigen des voherigen Versuchs make user make user_install (um die Installation wieder los zu werden: make user_uninstall) so wie in der Dokumentation angegeben. Im Anschluss musste ich nur noch wie angegeben die neue sensors.conf.eg nach /etc/sensors.conf kopieren und es gab die erste Ausgabe meiner Sensoren. Nachdem ich dann noch das Modul coretemp manuell in die /etc/modules eingefügt habe erhalte ich folgende Ausgabe der Sensoren. CODE: root@toelvatux:/usr/src/lm_sensors-2.10.3# sensors w83627dhg-isa-0290 Adapter: ISA adapter VCore: +1.12 V (min = +0.00 V, max = +1.74 V) in1: +12.20 V (min = +11.83 V, max = +2.69 V) ALARM AVCC: +3.30 V (min = +3.87 V, max = +2.51 V) ALARM 3VCC: +3.30 V (min = +0.22 V, max = +1.22 V) ALARM in4: +0.03 V (min = +0.09 V, max = +1.02 V) ALARM in5: +1.58 V (min = +1.84 V, max = +0.81 V) ALARM in6: +0.13 V (min = +3.69 V, max = +4.07 V) ALARM VSB: +3.30 V (min = +2.99 V, max = +0.00 V) ALARM VBAT: +3.02 V (min = +0.11 V, max = +0.90 V) ALARM Case Fan: 0 RPM (min = 21093 RPM, div = 64) ALARM CPU Fan: 562 RPM (min = 42187 RPM, div = 16) ALARM Aux Fan: 0 RPM (min = 21093 RPM, div = 64) ALARM fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM Sys Temp: +36°C (high = +18°C, hyst = +62°C) CPU Temp: +44.5°C (high = +80.0°C, hyst = +75.0°C) AUX Temp: +124.5°C (high = +80.0°C, hyst = +75.0°C) ALARM coretemp-isa-0000 Adapter: ISA adapter temp1: +41°C (high = +85°C) coretemp-isa-0001 Adapter: ISA adapter temp1: +41°C (high = +85°C) Die vielen Alarme weisen zwar noch auf falsche Wete in der sensors.conf hin, aber die Ausgabe der Sensoren stimmt zumindest mit dem win-Programm von Asus überein. Der Versuch die .ko Dateien einfach in meine produktiv-Partition zu kopieren ist natürlich gescheitert. In der Testumgebung ist aber mit dem neuen Kernel auch die Nvidia-Paketunterstützung "verschwunden". Bei der Suche nach einer Lösung bin im im ubuntuforum auf einen Hinweis auf das Programm envy gestoßen. Damit lässt sich per GUI der Treiber für die Grafikkarte von der Nvidia-Seite installieren. Wie angegeben habe ich zuerst alle nvidia-Pakete deinstalliert. Das wäre wahrscheinlich nicht nötig gewesen, weil der Installer von envy auf deren Existenz prüft und sie ggf. deinstalliert (kann im log - /var/log/envy-installer.log bewundert weden). Besagter Installer erzeugt praktischerweise auch gleich ein Kernel-Paket mit integrierter Nvidia-Unterstützung. Leider gibt es auch mit dem Nvidia-Treiber in der .xsession-errors haufenweise Fehlermeldungen (X Error: BadWindow (invalid Window parameter) 3). Leider ist es mir bisher nicht gelungen diesen auf den Grund zu gehen. Das einzige was ich weiß ist, dass diese mit dem Grafiktreiber zusammenhängen. Es gibt sie aber sowohl unter Debian (etch), als auch unter Ubuntu (Edgy, Feisty mit Paket-nvidia und Original-Treiber). Falls es einer weis bitte posten . Ausgabe von sensors-detect:
CODE: root@toelvatux:/home/lirio# sensors-detect # sensors-detect revision 4348 (2007-03-18 02:45:21 -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): y Probing for PCI bus adapters... Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801H ICH8 We will now try to load each adapter module in turn. Module `i2c-i801' 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): y 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 (i2c-4) Do you want to scan it? (YES/no/selectively): y Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Dallas Semiconductor DS1621'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... 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'... No Probing for `EDID EEPROM'... Success! (confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0 x56 0x57 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'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x54 Probing for `SPD EEPROM'... No Client found at address 0x55 Probing for `SPD EEPROM'... No Client found at address 0x56 Probing for `SPD EEPROM'... No Client found at address 0x57 Probing for `SPD EEPROM'... No Probing for `Sony Vaio EEPROM'... No Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-3) Do you want to scan it? (YES/no/selectively): y Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Dallas Semiconductor DS1621'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... 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'... No Probing for `EDID EEPROM'... Success! (confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0 x56 0x57 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'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x54 Probing for `SPD EEPROM'... No Client found at address 0x55 Probing for `SPD EEPROM'... No Client found at address 0x56 Probing for `SPD EEPROM'... No Client found at address 0x57 Probing for `SPD EEPROM'... No Probing for `Sony Vaio EEPROM'... No Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-2) Do you want to scan it? (YES/no/selectively): y Next adapter: SMBus I801 adapter at 0400 (i2c-1) Do you want to scan it? (YES/no/selectively): y Client found at address 0x50 Handled by driver `eeprom' (already loaded), chip type `eeprom' Client found at address 0x52 Handled by driver `eeprom' (already loaded), chip type `eeprom' Next adapter: bt878 #0 [sw] (i2c-0) Do you want to scan it? (YES/no/selectively): y Client found at address 0x18 Handled by driver `i2c ir driver' (already loaded), chip type `Hauppauge IR' (note: this is probably NOT a sensor chip!) Client found at address 0x40 Handled by driver `msp3400' (already loaded), chip type `MSP3415G-B8' (note: this is probably NOT a sensor chip!) Client found at address 0x50 Handled by driver `tveeprom' (already loaded), chip type `tveeprom' (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): y 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): y Probing for Super-I/O at 0x2e/0x2f Trying family `ITE'... No Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... Yes Found `Winbond W83627DHG Super IO Sensors' Success! (address 0x290, driver `w83627ehf') 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 Some CPUs or memory controllers may also contain embedded sensors. Do you want to scan for them? (YES/no): y AMD K8 thermal sensors... No Intel Core family thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `eeprom' (should be inserted): Detects correctly: <strong> Bus `NVIDIA i2c adapter 2 at 1:00.0' Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x5 7) Chip `EDID EEPROM' (confidence: <img src="/templates/default/img/emoticons/cool.png" alt="8-)" class="emoticon" /> </strong> Bus `NVIDIA i2c adapter 1 at 1:00.0' Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x5 7) Chip `EDID EEPROM' (confidence: <img src="/templates/default/img/emoticons/cool.png" alt="8-)" class="emoticon" /> <strong> Bus `SMBus I801 adapter at 0400' Busdriver `i2c-i801', I2C address 0x50 Chip `eeprom' (confidence: 6) </strong> Bus `SMBus I801 adapter at 0400' Busdriver `i2c-i801', I2C address 0x52 Chip `eeprom' (confidence: 6) EEPROMs are <strong>NOT</strong> sensors! They are data storage chips commonly found on memory modules (SPD), in monitors (EDID), or in some laptops, for example. Driver `w83627ehf' (should be inserted): Detects correctly: <strong> ISA bus, address 0x290 Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9) Driver `coretemp' (should be inserted): Detects correctly: </strong> Chip `Intel Core family thermal sensor' (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.conf: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers # modprobe unknown adapter bt878 #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 modprobe i2c-i801 # Chip drivers modprobe eeprom modprobe w83627ehf modprobe coretemp # sleep 2 # optional /usr/local/bin/sensors -s # recommended #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): y Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. komischerweise funktionierte lm-sensors in der einen Installation und in der anderen nicht. Jetzt habe ich einfach die sensor-Dateien aus /usr/local/bin, /usr/local/lib kopiert und jetzt funzt es. Trackbacks
Trackback-URL für diesen Eintrag
Keine Trackbacks
Kommentare
Ansicht der Kommentare:
(Linear | Verschachtelt)
Noch keine Kommentare
Die Kommentarfunktion wurde vom Besitzer dieses Blogs in diesem Eintrag deaktiviert.
|
SuchedeliciousError on line 132 of /var/www/vhosts/web53.server2.configcenter.info/httpdocs/hlr/bundled-libs/Onyx/RSS.php: The specified file could not be opened. (#301) A del.icio.us error occured! Verwaltung des Blogs |