Von KDE 3 zu Xfce unter openSuse 13.1

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

Hinweis: In dem Thema Von KDE 3 zu Xfce unter openSuse 13.1 gibt es 43 Antworten auf 5 Seiten. Der letzte Beitrag () befindet sich auf der letzten Seite.
  • Ich hatte beim ersten Laufenlassen von sensors-detect gedacht, dass die Detektionen kein Ende mehr nehmen würden, außerdem wurde zunehmend auf Risiken dabei hingewiesen, so dass ich irgendwann nicht mehr "yes" eingetippt hatte- jetzt sehe ich auch, dass es für den Gesamtprozess wichtig ist, bis zum Ende zu gehen und dass nur noch eine Abfrage mehr vorhanden war...


    Also jetzt:

    Quellcode

    1. linux-w648:~ # sensors-detect
    2. # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
    3. # System: Hewlett-Packard HP 625 (laptop)
    4. # Board: Hewlett-Packard 1475
    5. This program will help you determine which kernel modules you need
    6. to load to use lm_sensors most effectively. It is generally safe
    7. and recommended to accept the default answers to all questions,
    8. unless you know what you're doing.
    9. Some south bridges, CPUs or memory controllers contain embedded sensors.
    10. Do you want to scan for them? This is totally safe. (YES/no): YES
    11. Module cpuid loaded successfully.
    12. Silicon Integrated Systems SIS5595... No
    13. VIA VT82C686 Integrated Sensors... No
    14. VIA VT8231 Integrated Sensors... No
    15. AMD K8 thermal sensors... No
    16. AMD Family 10h thermal sensors... Success!
    17. (driver `k10temp')
    18. AMD Family 11h thermal sensors... No
    19. AMD Family 12h and 14h thermal sensors... No
    20. AMD Family 15h thermal sensors... No
    21. AMD Family 15h power sensors... No
    22. AMD Family 16h power sensors... No
    23. Intel digital thermal sensor... No
    24. Intel AMB FB-DIMM thermal sensor... No
    25. VIA C7 thermal sensor... No
    26. VIA Nano thermal sensor... No
    27. Some Super I/O chips contain embedded sensors. We have to write to
    28. standard I/O ports to probe them. This is usually safe.
    29. Do you want to scan for Super I/O sensors? (YES/no): YES
    30. Probing for Super-I/O at 0x2e/0x2f
    31. Trying family `National Semiconductor/ITE'... No
    32. Trying family `SMSC'... Yes
    33. Found `SMSC FDC37B72x Super IO'
    34. (no hardware monitoring capabilities)
    35. Probing for Super-I/O at 0x4e/0x4f
    36. Trying family `National Semiconductor/ITE'... No
    37. Trying family `SMSC'... No
    38. Trying family `VIA/Winbond/Nuvoton/Fintek'... No
    39. Trying family `ITE'... No
    40. Some hardware monitoring chips are accessible through the ISA I/O ports.
    41. We have to write to arbitrary I/O ports to probe them. This is usually
    42. safe though. Yes, you do have ISA I/O ports even if you do not have any
    43. ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES
    44. Probing for `National Semiconductor LM78' at 0x290... No
    45. Probing for `National Semiconductor LM79' at 0x290... No
    46. Probing for `Winbond W83781D' at 0x290... No
    47. Probing for `Winbond W83782D' at 0x290... No
    48. Lastly, we can probe the I2C/SMBus adapters for connected hardware
    49. monitoring devices. This is the most risky part, and while it works
    50. reasonably well on most systems, it has been reported to cause trouble
    51. on some systems.
    52. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES
    53. Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus
    54. Module i2c-dev loaded successfully.
    55. Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
    56. Do you want to scan it? (yes/NO/selectively): yes
    57. Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
    58. Do you want to scan it? (yes/NO/selectively): yes
    59. Client found at address 0x28
    60. Probing for `National Semiconductor LM78'... No
    61. Probing for `National Semiconductor LM79'... No
    62. Probing for `National Semiconductor LM80'... No
    63. Probing for `National Semiconductor LM96080'... No
    64. Probing for `Winbond W83781D'... No
    65. Probing for `Winbond W83782D'... No
    66. Probing for `Winbond W83627HF'... No
    67. Probing for `Winbond W83627EHF'... No
    68. Probing for `Winbond W83627DHG/W83667HG/W83677HG'... No
    69. Probing for `Asus AS99127F (rev.1)'... No
    70. Probing for `Asus AS99127F (rev.2)'... No
    71. Probing for `Asus ASB100 Bach'... No
    72. Probing for `Analog Devices ADM1029'... No
    73. Probing for `ITE IT8712F'... No
    74. Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
    75. Do you want to scan it? (yes/NO/selectively): yes
    76. Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
    77. Do you want to scan it? (yes/NO/selectively): yes
    78. Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
    79. Do you want to scan it? (yes/NO/selectively): yes
    80. Now follows a summary of the probes I have just done.
    81. Just press ENTER to continue:
    82. Driver `k10temp' (autoloaded):
    83. * Chip `AMD Family 10h thermal sensors' (confidence: 9)
    84. No modules to load, skipping modules configuration.
    85. Unloading i2c-dev... OK
    86. Unloading cpuid... OK
    Alles anzeigen

    Also zum Schluss steht da u.a.:
    "Driver `k10temp' (autoloaded): * Chip `AMD Family 10h thermal sensors' (confidence: 9)"

    Es gibt also einen Treiber 'k10temp'- und der wurde irgendwie automatisch geladen und es gibt den zur Familie 10h gehörigen AMD Chip Wärme-Sensor auf irgendeiner Konfidenzstufe 9 befindlich...... ok

    Dann:
    "No modules to load, skipping modules configuration."


    Demnach wurden keine Module nachgeladen.

    In den Dialogen zu KSensors kann ich jetzt noch nichts von Temperaturabfrage sehen, auch in dem kleinen Fensterchen wird noch nichts angezeigt.Ich starte mal neu (kenne ich noch von Windows) und schaue mal, ob dann was kommt...

    Für den Inhalt des Beitrages 101175 haftet ausdrücklich der jeweilige Autor: Suse-Paul

  • Quellcode

    1. ich@linux64:~> sensors
    2. asus-isa-0000
    3. Adapter: ISA adapter
    4. cpu_fan: 0 RPM
    5. k10temp-pci-00c3
    6. Adapter: PCI adapter
    7. temp1: +37.6°C (high = +70.0°C)
    8. (crit = +90.0°C, hyst = +87.0°C)
    9. it8721-isa-0290
    10. Adapter: ISA adapter
    11. in0: +2.83 V (min = +0.38 V, max = +0.01 V) ALARM
    12. in1: +2.81 V (min = +0.41 V, max = +2.78 V) ALARM
    13. in2: +0.83 V (min = +1.74 V, max = +0.05 V) ALARM
    14. +3.3V: +3.29 V (min = +0.67 V, max = +0.00 V) ALARM
    15. in4: +0.40 V (min = +2.78 V, max = +0.30 V) ALARM
    16. in5: +2.52 V (min = +2.30 V, max = +0.77 V) ALARM
    17. in6: +0.00 V (min = +0.77 V, max = +0.58 V) ALARM
    18. 3VSB: +0.98 V (min = +0.10 V, max = +0.84 V) ALARM
    19. Vbat: +3.31 V
    20. fan1: 2947 RPM (min = 62 RPM)
    21. fan2: 0 RPM (min = 80 RPM) ALARM
    22. fan3: 0 RPM (min = 319 RPM) ALARM
    23. temp1: +43.0°C (low = +48.0°C, high = +70.0°C) sensor = thermistor
    24. temp2: +33.0°C (low = +49.0°C, high = +72.0°C) sensor = thermistor
    25. temp3: -128.0°C (low = +12.0°C, high = +8.0°C) sensor = disabled
    26. intrusion0: OK
    27. fam15h_power-pci-00c4
    28. Adapter: PCI adapter
    29. power1: 59.32 W (crit = 95.13 W)
    Alles anzeigen
    PS:
    lm_sensors ist gestartet und enabled?

    Quellcode

    1. systemctl status lm_sensors.service
    Links in dieser Signatur bitte zum Lesen anklicken!

    Code-Tags <<<Klick mich
    zypper <<<Klick mich
    Netzwerkprobleme <<<Klick mich

    Für den Inhalt des Beitrages 101181 haftet ausdrücklich der jeweilige Autor: Sauerland