文書の表示以前のリビジョンバックリンク文書の先頭へ この文書は読取専用です。文書のソースを閲覧することは可能ですが、変更はできません。もし変更したい場合は管理者に連絡してください。 ====== ハードウエア監視 (lm_sensors) ====== 本家: [[https://hwmon.wiki.kernel.org/lm_sensors|lm_sensors [HWMon Wiki]]]\\ ソースコード: [[https://github.com/lm-sensors/lm-sensors|GitHub - lm-sensors/lm-sensors: lm-sensors repository]]\\ ===== 監視ソフトのインストール ===== [[linux:commands:package_management|dnf]]、または、[[linux:commands:package_management|dnfdragora]]で <html><code>lm_sensors</code></html> および <html><code>gkrellm</code></html> をインストールする。 <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sudo</b> dnf install lm_sensors gkrellm </pre></html></WRAP> <WRAP color_result_long><html><pre> メタデータの期限切れの最終確認: 2:13:34 時間前の 2022年09月14日 17時56分12秒 に実施しました。 依存関係が解決しました。 ==================================================================================================== パッケージ アーキテクチャー バージョン リポジトリー サイズ ==================================================================================================== インストール: <b class=GRN>gkrellm</b> x86_64 2.3.11-9.fc36 fedora 681 k <b class=GRN>lm_sensors</b> x86_64 3.6.0-11.fc36 fedora 134 k 依存関係のインストール: <b class=GRN>gtk2</b> x86_64 2.24.33-8.fc36 fedora 3.5 M <b class=GRN>ibus-gtk2</b> x86_64 1.5.26-9.fc36 updates 27 k <b class=GRN>libntlm</b> x86_64 1.6-4.fc36 fedora 92 k <b class=GRN>lm_sensors-libs</b> x86_64 3.6.0-11.fc36 fedora 41 k 弱い依存関係のインストール: <b class=GRN>adwaita-gtk2-theme</b> x86_64 3.28-14.fc36 fedora 136 k <b class=GRN>libcanberra-gtk2</b> x86_64 0.30-28.fc36 fedora 25 k トランザクションの概要 ==================================================================================================== インストール 8 パッケージ ダウンロードサイズの合計: 4.6 M インストール後のサイズ: 17 M これでよろしいですか? [y/N]: y パッケージのダウンロード: (1/8): adwaita-gtk2-theme-3.28-14.fc36.x86_64.rpm 75 kB/s | 136 kB 00:01 (2/8): libcanberra-gtk2-0.30-28.fc36.x86_64.rpm 50 kB/s | 25 kB 00:00 (3/8): libntlm-1.6-4.fc36.x86_64.rpm 113 kB/s | 92 kB 00:00 (4/8): lm_sensors-3.6.0-11.fc36.x86_64.rpm 183 kB/s | 134 kB 00:00 (5/8): lm_sensors-libs-3.6.0-11.fc36.x86_64.rpm 208 kB/s | 41 kB 00:00 (6/8): gkrellm-2.3.11-9.fc36.x86_64.rpm 158 kB/s | 681 kB 00:04 (7/8): ibus-gtk2-1.5.26-9.fc36.x86_64.rpm 27 kB/s | 27 kB 00:01 (8/8): gtk2-2.24.33-8.fc36.x86_64.rpm 311 kB/s | 3.5 MB 00:11 ---------------------------------------------------------------------------------------------------- 合計 356 kB/s | 4.6 MB 00:13 トランザクションの確認を実行中 トランザクションの確認に成功しました。 トランザクションのテストを実行中 トランザクションのテストに成功しました。 トランザクションを実行中 準備 : 1/1 インストール中 : lm_sensors-libs-3.6.0-11.fc36.x86_64 1/8 インストール中 : libcanberra-gtk2-0.30-28.fc36.x86_64 2/8 インストール中 : ibus-gtk2-1.5.26-9.fc36.x86_64 3/8 インストール中 : gtk2-2.24.33-8.fc36.x86_64 4/8 インストール中 : adwaita-gtk2-theme-3.28-14.fc36.x86_64 5/8 インストール中 : libntlm-1.6-4.fc36.x86_64 6/8 インストール中 : gkrellm-2.3.11-9.fc36.x86_64 7/8 インストール中 : lm_sensors-3.6.0-11.fc36.x86_64 8/8 scriptletの実行中: lm_sensors-3.6.0-11.fc36.x86_64 8/8 Created symlink /etc/systemd/system/multi-user.target.wants/lm_sensors.service → /usr/lib/systemd/system/lm_sensors.service. 検証 : adwaita-gtk2-theme-3.28-14.fc36.x86_64 1/8 検証 : gkrellm-2.3.11-9.fc36.x86_64 2/8 検証 : gtk2-2.24.33-8.fc36.x86_64 3/8 検証 : libcanberra-gtk2-0.30-28.fc36.x86_64 4/8 検証 : libntlm-1.6-4.fc36.x86_64 5/8 検証 : lm_sensors-3.6.0-11.fc36.x86_64 6/8 検証 : lm_sensors-libs-3.6.0-11.fc36.x86_64 7/8 検証 : ibus-gtk2-1.5.26-9.fc36.x86_64 8/8 インストール済み: adwaita-gtk2-theme-3.28-14.fc36.x86_64 gkrellm-2.3.11-9.fc36.x86_64 gtk2-2.24.33-8.fc36.x86_64 ibus-gtk2-1.5.26-9.fc36.x86_64 libcanberra-gtk2-0.30-28.fc36.x86_64 libntlm-1.6-4.fc36.x86_64 lm_sensors-3.6.0-11.fc36.x86_64 lm_sensors-libs-3.6.0-11.fc36.x86_64 完了しました! </pre></html></WRAP> </WRAP> ===== sensors-detectコマンドでセンサーを検出 ===== 問い合わせはすべてEnterで答える。 <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sudo</b> sensors-detect </pre></html></WRAP> <WRAP color_result_long><html><pre> # sensors-detect revision 6085 (2012-10-30 18:18:45 +0100) # System: MouseComputer/8Pro JW6H [03] (laptop) # Board: MouseComputer Co.,Ltd. JW6H 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. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded 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/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some hardware monitoring chips are 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 LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Panther Point (PCH) Module i2c-dev loaded successfully. Next adapter: i915 gmbus ssc (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus vga (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus panel (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpc (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpb (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpd (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: DPDDC-B (i2c-6) Do you want to scan it? (YES/no/selectively): Next adapter: nouveau-0000:01:00.0-0 (i2c-7) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-1 (i2c-8) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-2 (i2c-9) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-5 (i2c-10) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-6 (i2c-11) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-7 (i2c-12) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-8 (i2c-13) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-9 (i2c-14) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-10 (i2c-15) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-11 (i2c-16) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-12 (i2c-17) Do you want to scan it? (yes/NO/selectively): Next adapter: nouveau-0000:01:00.0-13 (i2c-18) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Unloading i2c-dev... OK </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_result_long><html><pre> # sensors-detect revision $Revision$ # Board: ASUSTeK Computer INC. Crosshair IV Extreme # Kernel: 4.19.13-300.fc29.x86_64 x86_64 # Processor: AMD Phenom(tm) II X6 1100T Processor (16/10/0) 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. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... Success! (driver `k10temp') AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded 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/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8721F/IT8758E Super IO Sensors' Success! (address 0x290, driver `it87') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are 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): Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus Module i2c-dev loaded successfully. Next adapter: nvkm-0000:01:00.0-bus-0000 (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0001 (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0002 (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0005 (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0006 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0007 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0008 (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-bus-0009 (i2c-7) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-aux-000a (i2c-8) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-aux-000b (i2c-9) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-aux-000c (i2c-10) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:01:00.0-aux-000d (i2c-11) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k10temp' (autoloaded): * Chip `AMD Family 10h thermal sensors' (confidence: 9) Driver `it87': * ISA bus, address 0x290 Chip `ITE IT8721F/IT8758E Super IO Sensors' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Unloading i2c-dev... OK </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>cat</b> /etc/sysconfig/lm_sensors </pre></html></WRAP> <WRAP color_result><html><pre> # Generated by sensors-detect on Fri Sep 25 16:16:54 2020 # This file is sourced by /etc/init.d/lm_sensors and defines the modules to # be loaded/unloaded. # # The format of this file is a shell script that simply defines variables: # HWMON_MODULES for hardware monitoring driver modules, and optionally # BUS_MODULES for any required bus driver module (for example for I2C or SPI). HWMON_MODULES="it87" </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_result_long><html><pre> # sensors-detect version 3.6.0 # System: MouseComputer/7Pro32 W25AEZ [Not Applicable] (laptop) # Board: MouseComputer Co.,Ltd. W25AEZ # Kernel: 5.19.8-200.fc36.x86_64 x86_64 # Processor: Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz (6/58/9) 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. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 19h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded 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/ITE'... Yes Found `ITE IT8518E Super IO' (no support yet) Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some hardware monitoring chips are 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 LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Panther Point (PCH) Module i2c-dev loaded successfully. Next adapter: i915 gmbus ssc (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus vga (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus panel (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpc (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpb (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpd (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: AUX C/DP C (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: SMBus I801 adapter at f040 (i2c-7) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Handled by driver `at24' (already loaded), chip type `spd' (note: this is probably NOT a sensor chip!) Client found at address 0x52 Handled by driver `at24' (already loaded), chip type `spd' (note: this is probably NOT a sensor chip!) Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Unloading i2c-dev... OK </pre></html></WRAP> <WRAP color_command><code> $ cat /etc/sysconfig/lm_sensors </code></WRAP> <WRAP color_result><html><pre> # Generated by sensors-detect on Wed Sep 14 20:28:21 2022 # This file is sourced by /etc/init.d/lm_sensors and defines the modules to # be loaded/unloaded. # # The format of this file is a shell script that simply defines variables: # HWMON_MODULES for hardware monitoring driver modules, and optionally # BUS_MODULES for any required bus driver module (for example for I2C or SPI). HWMON_MODULES="coretemp" </pre></html></WRAP> </WRAP> ===== モジュールロード確認 ===== lsmodコマンドでモジュールが読み込まれているかどうかを確認する。 <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>lsmod</b> | <b class=HIY>grep</b> i2c </pre></html></WRAP> <WRAP color_result><html><pre> <b class=RED>i2c</b>_i801 18136 0 <b class=RED>i2c</b>_algo_bit 13257 2 i915,nouveau <b class=RED>i2c</b>_core 34242 7 drm,i915,<b class=RED>i2c</b>_i801,drm_kms_helper,<b class=RED>i2c</b>_algo_bit,nouveau,videodev </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_result><html><pre> <b class=RED>i2c</b>_piix4 24576 0 <b class=RED>i2c</b>_algo_bit 16384 1 nouveau </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_result><html><pre> <b class=RED>i2c</b>_i801 36864 0 <b class=RED>i2c</b>_smbus 20480 1 <b class=RED>i2c</b>_i801 </pre></html></WRAP> </WRAP> ===== sensorsコマンドで表示 ===== <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sensors</b> </pre></html></WRAP> <WRAP color_result_long><html><pre> k10temp-pci-00c3 Adapter: PCI adapter temp1: +27.5°C (high = +70.0°C) (crit = +90.0°C, hyst = +85.0°C) nouveau-pci-0100 Adapter: PCI adapter GPU core: +0.88 V (min = +0.82 V, max = +1.10 V) fan1: 1380 RPM temp1: +33.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.23 V (min = +0.80 V, max = +1.60 V) CPU/NB Voltage: +1.25 V (min = +0.80 V, max = +1.60 V) CPU VDDA Voltage: +2.52 V (min = +2.00 V, max = +3.00 V) DRAM Voltage: +1.67 V (min = +1.40 V, max = +1.90 V) HT Voltage: +1.21 V (min = +0.80 V, max = +1.50 V) NB Voltage: +1.11 V (min = +0.90 V, max = +1.35 V) SB Voltage: +1.09 V (min = +0.80 V, max = +1.50 V) +3.3V Voltage: +3.31 V (min = +2.97 V, max = +3.63 V) +5V Voltage: +4.93 V (min = +4.50 V, max = +5.50 V) +12V Voltage: +12.16 V (min = +10.20 V, max = +13.80 V) CPU Temperature: +42.0°C (high = +40.0°C, crit = +90.0°C) MB Temperature: +27.0°C (high = +35.0°C, crit = +95.0°C) NB Temperature: +50.0°C (high = +65.0°C, crit = +95.0°C) SB Temperature: +40.0°C (high = +35.0°C, crit = +75.0°C) OPT_TEMP1 Temperature: +32.0°C (high = +0.0°C, crit = +90.0°C) OPT_TEMP2 Temperature: +38.0°C (high = +0.0°C, crit = +90.0°C) OPT_TEMP3 Temperature: +26.0°C (high = +0.0°C, crit = +90.0°C) </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_result><html><pre> BAT0-acpi-0 Adapter: ACPI interface in0: 12.00 V curr1: 0.00 A coretemp-isa-0000 Adapter: ISA adapter Package id 0: +54.0°C (high = +72.0°C, crit = +90.0°C) Core 0: +54.0°C (high = +72.0°C, crit = +90.0°C) Core 1: +54.0°C (high = +72.0°C, crit = +90.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +54.0°C (crit = +120.0°C) </pre></html></WRAP> </WRAP> ===== GKrellM System Monitorを入れる ===== [[linux:commands:package_management|dnf]]、または、[[linux:commands:package_management|dnfdragora]]で gkrellm をインストールする。\\ <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sudo</b> dnf install gkrellm </pre></html></WRAP> </WRAP> GKrellMを実行すると、次のようなバーが表示される。\\ {{linux:gkrellm.png|GkrellM}} {{linux:gkrellm_001.png|GkrellM 001}} ==== 設定 ==== 必要に応じてラベルなどを修正する。\\ {{linux:gkrellm_settings_001.png?600|GKrellM 設定}} ===== テーマのインストール ===== [[http://www.muhri.net/gkrellm/|GKrellM@muhri.net]]よりテーマファイルをダウンロードする。\\ テーマはユーザー毎にインストールする必要がある。\\ <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>cd</b> ~/work <b class=GRN>$</b> <b class=HIY>curl</b> -O http://www.muhri.net/gkrellm/Acqua.gkrellm.tar.gz <b class=GRN>$</b> <b class=HIY>tar</b> zxvf Acqua.gkrellm.tar.gz -C ~/.gkrellm2/themes/ </pre></html></WRAP> </WRAP> インストールが完了したら GKrellM の再起動後に設定のテーマで選択できるようになる。\\ ===== Gnomeセッション自動起動設定 ===== Fedora 29 で Gnome セッションの自動起動設定を行うには、以下のファイルで自動起動するアプリケーションの設定を行う。\\ <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>mkdir</b> ~/.config/autostart/ <b class=GRN>$</b> <b class=HIY>nano</b> ~/.config/autostart/gkrellm.desktop </pre></html></WRAP> </WRAP> <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>mkdir</b> -p ~/.config/autostart/ <b class=GRN>$</b> <b class=HIY>cat</b> << "EOF" > ~/.config/autostart/gkrellm.desktop [Desktop Entry] Type=Application Name=GKrellM Comment=GKrellM System Monitor Exec=/usr/bin/gkrellm EOF </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>cat</b> ~/.config/autostart/gkrellm.desktop </pre></html></WRAP> <WRAP color_result><html><pre> [Desktop Entry] Type=Application Name=GKrellM Comment=GKrellM System Monitor Exec=/usr/bin/gkrellm </pre></html></WRAP> </WRAP> ^名前|GKrellM | ^コマンド|gkrellm | ^説明|GKrellM System Monitor | ※次回ログイン時から自動起動設定が有効になる。 ===== プラグイン ===== dnf でインストール可能なプラグイン。\\ <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>dnf</b> search gkrellm </pre></html></WRAP> <WRAP color_result><html><pre> メタデータの期限切れの最終確認: 0:18:04 時間前の 2022年09月14日 21時14分58秒 に実施しました。 =========================================== 名前 完全一致: gkrellm =========================================== <b class=MAG>gkrellm</b>.x86_64 : Multiple stacked system monitors in one process ========================================= 名前 & 概要 一致: gkrellm ========================================== <b class=MAG>gkrellm</b>-sun.x86_64 : Sun clock plugin for <b class=MAG>GKrellM</b> <b class=MAG>gkrellm</b>-top.x86_64 : <b class=MAG>GKrellM</b> plugin which shows 3 most CPU intensive processes ============================================= 名前 一致: gkrellm ============================================= <b class=MAG>gkrellm</b>-daemon.x86_64 : The GNU Krell Monitors Server <b class=MAG>gkrellm</b>-devel.i686 : Development files for the GNU Krell Monitors <b class=MAG>gkrellm</b>-devel.x86_64 : Development files for the GNU Krell Monitors <b class=MAG>gkrellm</b>-wifi.x86_64 : Wireless monitor plugin for the GNU Krell Monitors ============================================= 概要 一致: gkrellm ============================================= gkrellxmms2.x86_64 : <b class=MAG>Gkrellm</b>2 plugin client for XMMS2 </pre></html></WRAP> </WRAP> ==== gkfreq プラグイン ==== 本家: [[https://sourceforge.net/projects/gkrellm-gkfreq/|GKrellM-gkfreq download | SourceForge.net]]\\ \\ CPU の現在のクロック周波数を表示する。\\ <WRAP color_term> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sudo</b> dnf install gkrellm-devel </pre></html></WRAP> <WRAP color_result_long><html><pre> メタデータの期限切れの最終確認: 0:15:50 時間前の 2023年03月05日 05時46分46秒 に実施しました。 依存関係が解決しました。 ============================================================================================================== パッケージ アーキテクチャー バージョン リポジトリー サイズ ============================================================================================================== インストール: <b class=GRN>gkrellm-devel</b> x86_64 2.3.11-10.fc37 fedora 23 k 依存関係のインストール: <b class=GRN>atk-devel</b> x86_64 2.38.0-2.fc37 fedora 189 k <b class=GRN>brotli</b> x86_64 1.0.9-9.fc37 fedora 315 k <b class=GRN>brotli-devel</b> x86_64 1.0.9-9.fc37 fedora 31 k <b class=GRN>bzip2-devel</b> x86_64 1.0.8-12.fc37 fedora 214 k <b class=GRN>cairo-devel</b> x86_64 1.17.6-2.fc37 fedora 261 k <b class=GRN>fontconfig-devel</b> x86_64 2.14.1-2.fc37 updates 164 k <b class=GRN>freetype-devel</b> x86_64 2.12.1-3.fc37 fedora 895 k <b class=GRN>fribidi-devel</b> x86_64 1.0.12-2.fc37 fedora 30 k <b class=GRN>gdk-pixbuf2-devel</b> x86_64 2.42.10-1.fc37 fedora 377 k <b class=GRN>glib2-devel</b> x86_64 2.74.6-1.fc37 updates 572 k <b class=GRN>graphite2-devel</b> x86_64 1.3.14-10.fc37 fedora 20 k <b class=GRN>gtk2-devel</b> x86_64 2.24.33-10.fc37 fedora 2.8 M <b class=GRN>harfbuzz-devel</b> x86_64 5.2.0-1.fc37 fedora 391 k <b class=GRN>libX11-devel</b> x86_64 1.8.4-1.fc37 updates 1.0 M <b class=GRN>libXau-devel</b> x86_64 1.0.10-1.fc37 fedora 13 k <b class=GRN>libXcomposite-devel</b> x86_64 0.4.5-8.fc37 fedora 15 k <b class=GRN>libXcursor-devel</b> x86_64 1.2.1-2.fc37 fedora 40 k <b class=GRN>libXext-devel</b> x86_64 1.3.4-9.fc37 fedora 86 k <b class=GRN>libXfixes-devel</b> x86_64 6.0.0-4.fc37 fedora 12 k <b class=GRN>libXft-devel</b> x86_64 2.3.4-3.fc37 fedora 18 k <b class=GRN>libXi-devel</b> x86_64 1.8-3.fc37 fedora 116 k <b class=GRN>libXinerama-devel</b> x86_64 1.1.4-11.fc37 fedora 13 k <b class=GRN>libXrandr-devel</b> x86_64 1.5.2-9.fc37 fedora 19 k <b class=GRN>libXrender-devel</b> x86_64 0.9.10-17.fc37 fedora 16 k <b class=GRN>libblkid-devel</b> x86_64 2.38.1-1.fc37 fedora 17 k <b class=GRN>libdatrie-devel</b> x86_64 0.2.13-4.fc37 fedora 143 k <b class=GRN>libffi-devel</b> x86_64 3.4.4-1.fc37 updates 28 k <b class=GRN>libicu-devel</b> x86_64 71.1-2.fc37 fedora 915 k <b class=GRN>libjpeg-turbo-devel</b> x86_64 2.1.3-2.fc37 fedora 98 k <b class=GRN>libmount-devel</b> x86_64 2.38.1-1.fc37 fedora 18 k <b class=GRN>libpng-devel</b> x86_64 2:1.6.37-13.fc37 fedora 290 k <b class=GRN>libselinux-devel</b> x86_64 3.4-5.fc37 fedora 148 k <b class=GRN>libsepol-devel</b> x86_64 3.4-3.fc37 fedora 49 k <b class=GRN>libthai-devel</b> x86_64 0.1.29-3.fc37 fedora 135 k <b class=GRN>libtiff-devel</b> x86_64 4.4.0-4.fc37 fedora 546 k <b class=GRN>libxcb-devel</b> x86_64 1.13.1-10.fc37 fedora 1.4 M <b class=GRN>libxml2-devel</b> x86_64 2.10.3-2.fc37 updates 531 k <b class=GRN>pango-devel</b> x86_64 1.50.13-1.fc37 updates 161 k <b class=GRN>pcre2-devel</b> x86_64 10.40-1.fc37.1 fedora 505 k <b class=GRN>pixman-devel</b> x86_64 0.40.0-6.fc37 fedora 17 k <b class=GRN>sysprof-capture-devel</b> x86_64 3.46.0-1.fc37 fedora 58 k <b class=GRN>xorg-x11-proto-devel</b> noarch 2022.2-2.fc37 fedora 299 k <b class=GRN>xz-devel</b> x86_64 5.4.1-1.fc37 updates 65 k <b class=GRN>zlib-devel</b> x86_64 1.2.12-5.fc37 fedora 44 k トランザクションの概要 ============================================================================================================== インストール 45 パッケージ ダウンロードサイズの合計: 13 M インストール後のサイズ: 69 M これでよろしいですか? [y/N]: y パッケージのダウンロード: (1/45): brotli-devel-1.0.9-9.fc37.x86_64.rpm 89 kB/s | 31 kB 00:00 (2/45): atk-devel-2.38.0-2.fc37.x86_64.rpm 329 kB/s | 189 kB 00:00 (3/45): brotli-1.0.9-9.fc37.x86_64.rpm 489 kB/s | 315 kB 00:00 (4/45): bzip2-devel-1.0.8-12.fc37.x86_64.rpm 703 kB/s | 214 kB 00:00 (5/45): cairo-devel-1.17.6-2.fc37.x86_64.rpm 955 kB/s | 261 kB 00:00 (6/45): fribidi-devel-1.0.12-2.fc37.x86_64.rpm 146 kB/s | 30 kB 00:00 (7/45): gkrellm-devel-2.3.11-10.fc37.x86_64.rpm 89 kB/s | 23 kB 00:00 (8/45): gdk-pixbuf2-devel-2.42.10-1.fc37.x86_64.rpm 1.1 MB/s | 377 kB 00:00 (9/45): freetype-devel-2.12.1-3.fc37.x86_64.rpm 1.4 MB/s | 895 kB 00:00 (10/45): graphite2-devel-1.3.14-10.fc37.x86_64.rpm 124 kB/s | 20 kB 00:00 (11/45): harfbuzz-devel-5.2.0-1.fc37.x86_64.rpm 900 kB/s | 391 kB 00:00 (12/45): libXau-devel-1.0.10-1.fc37.x86_64.rpm 32 kB/s | 13 kB 00:00 (13/45): libXcursor-devel-1.2.1-2.fc37.x86_64.rpm 190 kB/s | 40 kB 00:00 (14/45): libXext-devel-1.3.4-9.fc37.x86_64.rpm 309 kB/s | 86 kB 00:00 (15/45): gtk2-devel-2.24.33-10.fc37.x86_64.rpm 2.0 MB/s | 2.8 MB 00:01 (16/45): libXcomposite-devel-0.4.5-8.fc37.x86_64.rpm 17 kB/s | 15 kB 00:00 (17/45): libXfixes-devel-6.0.0-4.fc37.x86_64.rpm 30 kB/s | 12 kB 00:00 (18/45): libXft-devel-2.3.4-3.fc37.x86_64.rpm 162 kB/s | 18 kB 00:00 (19/45): libXinerama-devel-1.1.4-11.fc37.x86_64.rpm 128 kB/s | 13 kB 00:00 (20/45): libXrender-devel-0.9.10-17.fc37.x86_64.rpm 128 kB/s | 16 kB 00:00 (21/45): libXrandr-devel-1.5.2-9.fc37.x86_64.rpm 90 kB/s | 19 kB 00:00 (22/45): libblkid-devel-2.38.1-1.fc37.x86_64.rpm 68 kB/s | 17 kB 00:00 (23/45): libdatrie-devel-0.2.13-4.fc37.x86_64.rpm 427 kB/s | 143 kB 00:00 (24/45): libjpeg-turbo-devel-2.1.3-2.fc37.x86_64.rpm 515 kB/s | 98 kB 00:00 (25/45): libicu-devel-71.1-2.fc37.x86_64.rpm 1.9 MB/s | 915 kB 00:00 (26/45): libmount-devel-2.38.1-1.fc37.x86_64.rpm 105 kB/s | 18 kB 00:00 (27/45): libpng-devel-1.6.37-13.fc37.x86_64.rpm 1.1 MB/s | 290 kB 00:00 (28/45): libselinux-devel-3.4-5.fc37.x86_64.rpm 528 kB/s | 148 kB 00:00 (29/45): libsepol-devel-3.4-3.fc37.x86_64.rpm 310 kB/s | 49 kB 00:00 (30/45): libthai-devel-0.1.29-3.fc37.x86_64.rpm 637 kB/s | 135 kB 00:00 (31/45): libXi-devel-1.8-3.fc37.x86_64.rpm 63 kB/s | 116 kB 00:01 (32/45): libtiff-devel-4.4.0-4.fc37.x86_64.rpm 1.1 MB/s | 546 kB 00:00 (33/45): pixman-devel-0.40.0-6.fc37.x86_64.rpm 72 kB/s | 17 kB 00:00 (34/45): libxcb-devel-1.13.1-10.fc37.x86_64.rpm 2.0 MB/s | 1.4 MB 00:00 (35/45): sysprof-capture-devel-3.46.0-1.fc37.x86_64.rpm 486 kB/s | 58 kB 00:00 (36/45): xorg-x11-proto-devel-2022.2-2.fc37.noarch.rpm 1.2 MB/s | 299 kB 00:00 (37/45): zlib-devel-1.2.12-5.fc37.x86_64.rpm 197 kB/s | 44 kB 00:00 (38/45): fontconfig-devel-2.14.1-2.fc37.x86_64.rpm 696 kB/s | 164 kB 00:00 (39/45): glib2-devel-2.74.6-1.fc37.x86_64.rpm 1.4 MB/s | 572 kB 00:00 (40/45): libX11-devel-1.8.4-1.fc37.x86_64.rpm 2.5 MB/s | 1.0 MB 00:00 (41/45): libffi-devel-3.4.4-1.fc37.x86_64.rpm 107 kB/s | 28 kB 00:00 (42/45): libxml2-devel-2.10.3-2.fc37.x86_64.rpm 1.1 MB/s | 531 kB 00:00 (43/45): pango-devel-1.50.13-1.fc37.x86_64.rpm 366 kB/s | 161 kB 00:00 (44/45): xz-devel-5.4.1-1.fc37.x86_64.rpm 383 kB/s | 65 kB 00:00 (45/45): pcre2-devel-10.40-1.fc37.1.x86_64.rpm 198 kB/s | 505 kB 00:02 -------------------------------------------------------------------------------------------------------------- 合計 1.5 MB/s | 13 MB 00:08 トランザクションの確認を実行中 トランザクションの確認に成功しました。 トランザクションのテストを実行中 トランザクションのテストに成功しました。 トランザクションを実行中 準備 : 1/1 インストール中 : xorg-x11-proto-devel-2022.2-2.fc37.noarch 1/45 インストール中 : zlib-devel-1.2.12-5.fc37.x86_64 2/45 インストール中 : libpng-devel-2:1.6.37-13.fc37.x86_64 3/45 インストール中 : pcre2-devel-10.40-1.fc37.1.x86_64 4/45 インストール中 : libXau-devel-1.0.10-1.fc37.x86_64 5/45 インストール中 : libxcb-devel-1.13.1-10.fc37.x86_64 6/45 インストール中 : libX11-devel-1.8.4-1.fc37.x86_64 7/45 インストール中 : libXext-devel-1.3.4-9.fc37.x86_64 8/45 インストール中 : libXrender-devel-0.9.10-17.fc37.x86_64 9/45 インストール中 : libXfixes-devel-6.0.0-4.fc37.x86_64 10/45 インストール中 : libXcomposite-devel-0.4.5-8.fc37.x86_64 11/45 インストール中 : libXcursor-devel-1.2.1-2.fc37.x86_64 12/45 インストール中 : libXi-devel-1.8-3.fc37.x86_64 13/45 インストール中 : libXrandr-devel-1.5.2-9.fc37.x86_64 14/45 インストール中 : libXinerama-devel-1.1.4-11.fc37.x86_64 15/45 インストール中 : xz-devel-5.4.1-1.fc37.x86_64 16/45 インストール中 : libxml2-devel-2.10.3-2.fc37.x86_64 17/45 インストール中 : libffi-devel-3.4.4-1.fc37.x86_64 18/45 インストール中 : sysprof-capture-devel-3.46.0-1.fc37.x86_64 19/45 インストール中 : pixman-devel-0.40.0-6.fc37.x86_64 20/45 インストール中 : libtiff-devel-4.4.0-4.fc37.x86_64 21/45 インストール中 : libsepol-devel-3.4-3.fc37.x86_64 22/45 インストール中 : libselinux-devel-3.4-5.fc37.x86_64 23/45 インストール中 : libjpeg-turbo-devel-2.1.3-2.fc37.x86_64 24/45 インストール中 : libicu-devel-71.1-2.fc37.x86_64 25/45 インストール中 : libdatrie-devel-0.2.13-4.fc37.x86_64 26/45 インストール中 : libthai-devel-0.1.29-3.fc37.x86_64 27/45 インストール中 : libblkid-devel-2.38.1-1.fc37.x86_64 28/45 インストール中 : libmount-devel-2.38.1-1.fc37.x86_64 29/45 インストール中 : glib2-devel-2.74.6-1.fc37.x86_64 30/45 インストール中 : atk-devel-2.38.0-2.fc37.x86_64 31/45 インストール中 : gdk-pixbuf2-devel-2.42.10-1.fc37.x86_64 32/45 インストール中 : graphite2-devel-1.3.14-10.fc37.x86_64 33/45 インストール中 : fribidi-devel-1.0.12-2.fc37.x86_64 34/45 インストール中 : bzip2-devel-1.0.8-12.fc37.x86_64 35/45 インストール中 : brotli-1.0.9-9.fc37.x86_64 36/45 インストール中 : brotli-devel-1.0.9-9.fc37.x86_64 37/45 インストール中 : harfbuzz-devel-5.2.0-1.fc37.x86_64 38/45 インストール中 : freetype-devel-2.12.1-3.fc37.x86_64 39/45 インストール中 : fontconfig-devel-2.14.1-2.fc37.x86_64 40/45 インストール中 : cairo-devel-1.17.6-2.fc37.x86_64 41/45 インストール中 : libXft-devel-2.3.4-3.fc37.x86_64 42/45 インストール中 : pango-devel-1.50.13-1.fc37.x86_64 43/45 インストール中 : gtk2-devel-2.24.33-10.fc37.x86_64 44/45 インストール中 : gkrellm-devel-2.3.11-10.fc37.x86_64 45/45 scriptletの実行中: gkrellm-devel-2.3.11-10.fc37.x86_64 45/45 検証 : atk-devel-2.38.0-2.fc37.x86_64 1/45 検証 : brotli-1.0.9-9.fc37.x86_64 2/45 検証 : brotli-devel-1.0.9-9.fc37.x86_64 3/45 検証 : bzip2-devel-1.0.8-12.fc37.x86_64 4/45 検証 : cairo-devel-1.17.6-2.fc37.x86_64 5/45 検証 : freetype-devel-2.12.1-3.fc37.x86_64 6/45 検証 : fribidi-devel-1.0.12-2.fc37.x86_64 7/45 検証 : gdk-pixbuf2-devel-2.42.10-1.fc37.x86_64 8/45 検証 : gkrellm-devel-2.3.11-10.fc37.x86_64 9/45 検証 : graphite2-devel-1.3.14-10.fc37.x86_64 10/45 検証 : gtk2-devel-2.24.33-10.fc37.x86_64 11/45 検証 : harfbuzz-devel-5.2.0-1.fc37.x86_64 12/45 検証 : libXau-devel-1.0.10-1.fc37.x86_64 13/45 検証 : libXcomposite-devel-0.4.5-8.fc37.x86_64 14/45 検証 : libXcursor-devel-1.2.1-2.fc37.x86_64 15/45 検証 : libXext-devel-1.3.4-9.fc37.x86_64 16/45 検証 : libXfixes-devel-6.0.0-4.fc37.x86_64 17/45 検証 : libXft-devel-2.3.4-3.fc37.x86_64 18/45 検証 : libXi-devel-1.8-3.fc37.x86_64 19/45 検証 : libXinerama-devel-1.1.4-11.fc37.x86_64 20/45 検証 : libXrandr-devel-1.5.2-9.fc37.x86_64 21/45 検証 : libXrender-devel-0.9.10-17.fc37.x86_64 22/45 検証 : libblkid-devel-2.38.1-1.fc37.x86_64 23/45 検証 : libdatrie-devel-0.2.13-4.fc37.x86_64 24/45 検証 : libicu-devel-71.1-2.fc37.x86_64 25/45 検証 : libjpeg-turbo-devel-2.1.3-2.fc37.x86_64 26/45 検証 : libmount-devel-2.38.1-1.fc37.x86_64 27/45 検証 : libpng-devel-2:1.6.37-13.fc37.x86_64 28/45 検証 : libselinux-devel-3.4-5.fc37.x86_64 29/45 検証 : libsepol-devel-3.4-3.fc37.x86_64 30/45 検証 : libthai-devel-0.1.29-3.fc37.x86_64 31/45 検証 : libtiff-devel-4.4.0-4.fc37.x86_64 32/45 検証 : libxcb-devel-1.13.1-10.fc37.x86_64 33/45 検証 : pcre2-devel-10.40-1.fc37.1.x86_64 34/45 検証 : pixman-devel-0.40.0-6.fc37.x86_64 35/45 検証 : sysprof-capture-devel-3.46.0-1.fc37.x86_64 36/45 検証 : xorg-x11-proto-devel-2022.2-2.fc37.noarch 37/45 検証 : zlib-devel-1.2.12-5.fc37.x86_64 38/45 検証 : fontconfig-devel-2.14.1-2.fc37.x86_64 39/45 検証 : glib2-devel-2.74.6-1.fc37.x86_64 40/45 検証 : libX11-devel-1.8.4-1.fc37.x86_64 41/45 検証 : libffi-devel-3.4.4-1.fc37.x86_64 42/45 検証 : libxml2-devel-2.10.3-2.fc37.x86_64 43/45 検証 : pango-devel-1.50.13-1.fc37.x86_64 44/45 検証 : xz-devel-5.4.1-1.fc37.x86_64 45/45 インストール済み: atk-devel-2.38.0-2.fc37.x86_64 brotli-1.0.9-9.fc37.x86_64 brotli-devel-1.0.9-9.fc37.x86_64 bzip2-devel-1.0.8-12.fc37.x86_64 cairo-devel-1.17.6-2.fc37.x86_64 fontconfig-devel-2.14.1-2.fc37.x86_64 freetype-devel-2.12.1-3.fc37.x86_64 fribidi-devel-1.0.12-2.fc37.x86_64 gdk-pixbuf2-devel-2.42.10-1.fc37.x86_64 gkrellm-devel-2.3.11-10.fc37.x86_64 glib2-devel-2.74.6-1.fc37.x86_64 graphite2-devel-1.3.14-10.fc37.x86_64 gtk2-devel-2.24.33-10.fc37.x86_64 harfbuzz-devel-5.2.0-1.fc37.x86_64 libX11-devel-1.8.4-1.fc37.x86_64 libXau-devel-1.0.10-1.fc37.x86_64 libXcomposite-devel-0.4.5-8.fc37.x86_64 libXcursor-devel-1.2.1-2.fc37.x86_64 libXext-devel-1.3.4-9.fc37.x86_64 libXfixes-devel-6.0.0-4.fc37.x86_64 libXft-devel-2.3.4-3.fc37.x86_64 libXi-devel-1.8-3.fc37.x86_64 libXinerama-devel-1.1.4-11.fc37.x86_64 libXrandr-devel-1.5.2-9.fc37.x86_64 libXrender-devel-0.9.10-17.fc37.x86_64 libblkid-devel-2.38.1-1.fc37.x86_64 libdatrie-devel-0.2.13-4.fc37.x86_64 libffi-devel-3.4.4-1.fc37.x86_64 libicu-devel-71.1-2.fc37.x86_64 libjpeg-turbo-devel-2.1.3-2.fc37.x86_64 libmount-devel-2.38.1-1.fc37.x86_64 libpng-devel-2:1.6.37-13.fc37.x86_64 libselinux-devel-3.4-5.fc37.x86_64 libsepol-devel-3.4-3.fc37.x86_64 libthai-devel-0.1.29-3.fc37.x86_64 libtiff-devel-4.4.0-4.fc37.x86_64 libxcb-devel-1.13.1-10.fc37.x86_64 libxml2-devel-2.10.3-2.fc37.x86_64 pango-devel-1.50.13-1.fc37.x86_64 pcre2-devel-10.40-1.fc37.1.x86_64 pixman-devel-0.40.0-6.fc37.x86_64 sysprof-capture-devel-3.46.0-1.fc37.x86_64 xorg-x11-proto-devel-2022.2-2.fc37.noarch xz-devel-5.4.1-1.fc37.x86_64 zlib-devel-1.2.12-5.fc37.x86_64 完了しました! </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>curl</b> <b class=HIK>-LO</b> https://downloads.sourceforge.net/gkrellm-gkfreq/2.4/gkrellm-gkfreq-2.4.tar.gz </pre></html></WRAP> <WRAP color_result><html><pre> % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 371 100 371 0 0 425 0 --:--:-- --:--:-- --:--:-- 424 100 13391 100 13391 0 0 6756 0 0:00:01 0:00:01 --:--:-- 97036 </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>tar</b> zxvf gkrellm-gkfreq-2.4.tar.gz </pre></html></WRAP> <WRAP color_result><html><pre> gkrellm-gkfreq-2.4/ gkrellm-gkfreq-2.4/gkrellm-gkfreq.c gkrellm-gkfreq-2.4/INSTALL gkrellm-gkfreq-2.4/ChangeLog gkrellm-gkfreq-2.4/README gkrellm-gkfreq-2.4/Makefile gkrellm-gkfreq-2.4/COPYING </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>cd</b> gkrellm-gkfreq-2.4 <b class=GRN>$</b> <b class=HIY>make</b> </pre></html></WRAP> <WRAP color_result><html><pre> gcc -fPIC -O2 -Wall `pkg-config gtk+-2.0 --cflags` -c gkrellm-gkfreq.c gcc -shared -Wall -o gkrellm-gkfreq.so gkrellm-gkfreq.o Compilation done! If you want to try the plugin before installing you can run gkrellm -p gkrellm-gkfreq.so Install in either /usr/lib/gkrellm2/plugins/ by running sudo make install or in /usr/local/lib/gkrellm2/plugins/ by running sudo make install-local or in ~/.gkrellm2/plugins by running make install-home </pre></html></WRAP> <WRAP color_command><html><pre> <b class=GRN>$</b> <b class=HIY>sudo</b> cp gkrellm-gkfreq.so /usr/lib64/gkrellm2/plugins/ </pre></html></WRAP> </WRAP> GKrellM を再起動して [設定] - [プラグイン] から gkrellm-gkfreq を有効にする。\\ GKrellM [設定] - [全般] の Krell と LED を1秒間に更新する回数: 1 〜 5 くらいにしておくとおとなしく更新してくれる😅\\ ==== Sun Clock プラグイン ==== 住所の緯度経度を調べる。\\ [[http://www.geocoding.jp/|Geocoding - 住所から緯度経度を検索]]\\ ==== GKrellWeather プラグイン ==== ICAO(国際民間航空機関 - International Civil Aviation Organization)を調べる。\\ [[http://ja.wikipedia.org/|Wikipedia]]\\ 例:\\ シドニー国際空港 - ICAO: YSSY\\ 新千歳空港 - ICAO: RJCC\\ 丘珠空港 - ICAO: RJCO\\ linux/lm_sensors.txt 最終更新: 2023/09/04 09:17by ともやん