Autor |
Sõnum |
Qilaq
Vana Pingviin
Vanus: 55
Liitunud: 25.10.2006
Postitused: 1219
Asukoht: Linda Nisa
Distributsioon: Mageia, Mandriva Linux
|
|
See fail peaks olema /home/marek/.kde/share/apps/superkaramba/themes/67841-ublook-0/ublook-0.1/ kataloogis asuv ublook.theme. Ja ligi saad suvalise tekstiredaktoriga - kasuta nt Katet, see on selline mõistlik valik.
|
|
|
|
_________________ Tõlkija (Mandriva Linux, KDE, Scribus, CUPS)
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Hehee, nuid mo olen küll miskit ikka väga pambusesse pannud, arvata on et installiga sest nagu sa Qilaq näitad. Mul pole üldse sellist kausta /home/iffi/.kde/ ...jne. Leidsintheme kausta sealt media:/hda8/usr/share/apps/superkaramba/themes/ ja siin ka aint default oli sees mis oli täiesti tühi fail.
Karamba installisin urpmi-ga
Ühesõnaga on mul ika miski konkreetselt mäda või ma siis tõesti ei oska kasutada?
Kas ma peaks mujalt installima?
Looma ise miskid kataloomad?
|
|
|
|
|
|
|
|
Qilaq
Vana Pingviin
Vanus: 55
Liitunud: 25.10.2006
Postitused: 1219
Asukoht: Linda Nisa
Distributsioon: Mageia, Mandriva Linux
|
|
.kde kataloog peaks sul ikka olemas olema - või ei kasuta sa KDE-d? Karamba võisid sa urpmiga paigaldada küll, aga teema, selle ublooki, paigaldasid ju juba SuperKaramba enda kaudu, ma usun? Siis peaks osutatud kaust tekitatama sinu kodukataloogi - see on sinu kohandatud SuperKaramba (erinevalt sellest, mis usr-is - too on n-ö mall ainult kõigile kasutajatele). .kde on muidugi nn peidetud kataloog, mille nägemise peab sisse lülitama: nt Kates valid Ava fail ja kui .kde kataloogi vastu ei vaata, siis mutrivõtmega ikooni alt sisse lülitada "Peidetud failide näitamine", seejärel peaks nägema ka seda kataloogi ja selle sisu (muidugi võib selle ka füüsiliselt asukoharibale kirjutada, aga ma oletan, et visuaalselt on lihtsam tuvastada ).
|
|
|
|
_________________ Tõlkija (Mandriva Linux, KDE, Scribus, CUPS)
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Igaljuhul tänud sulle abi eest ei tulnud selle pealegi, et peidetud failid
sander85 see tempi lugemise kood on järgmine kui sa mõtlesid seda!? või mõtled kogu ublook pluginat?
Kood: | ###############################################################################
# GPU
text x=20 y=110 value="Temp GPU"
text x=130 y=110 sensor=program program="nvidia-settings -q gpucoretemp |grep '):' | awk '{print $4}'" interval=10000
text x=144 y=110 value="0 %uFFFDC"
bar x=130 y=125 w=20 h=0 path="images/bar4.png" max=100. interval=10000 sensor=program program="nvidia-settings -q gpucoretemp | grep '):' | awk '{print $4}'"
###############################################################################
# CPU
#text x=30 y=188 value="CPU Temp:"
#text x=150 y=188 sensor=sensor type="M/B Temp" format="%v C°"
#text x=30 y=201 value="CPU Fan:"
#text x=150 y=201 sensor=sensor type="fan3" format="%v RPM"
#Kind of CPU
text x=20 y=140 sensor=program program="cat /proc/cpuinfo | grep 'vendor_id' | sed -e 's/.*: //' | line 1" fontsize=12
text x=20 y=158 sensor=program program="cat /proc/cpuinfo | grep 'model name' | sed -e 's/.*: //' | line 1"
#Clock CPU 1
text x=20 y=175 value="CPU 1"
text x=110 y=175 sensor=program program="cat /proc/cpuinfo | grep 'cpu MHz' | sed -e 's/.*: //'| sed -e 's/\..../ MHz/' | line 1" interval=600000
text x=170 y=175 sensor=program program="cat /proc/cpuinfo | grep 'cache size' | sed -e 's/.*: //' | line 1" interval=600000
#Clock CPU 2
text x=20 y=192 value="CPU 2"
text x=110 y=192 sensor=program program="cat /proc/cpuinfo | grep 'cpu MHz' | sed -e 's/.*: //'| sed -e 's/\..../ MHz/' | line 2" interval=600000
text x=170 y=192 sensor=program program="cat /proc/cpuinfo | grep 'cache size' | sed -e 's/.*: //' | line 2" interval=6000
#Clock CPU 1 graph
image x=103 y=210 path="images/grill.png"
text x=20 y=230 value="CPU 1" fontsize=12
text x=70 y=232 sensor=cpu cpu=0 format="%v%" interval=1000
graph x=107 y=208 w=150 h=50 points=100 color=247,1,1 sensor=cpu format="%system" cpu=0 interval=1000
graph x=107 y=209 w=150 h=50 points=100 color=1,247,1 sensor=cpu format="%user" cpu=0 interval=1000
#Clock CPU 2 graph
image x=103 y=270 path="images/grill.png"
text x=20 y=290 value="CPU 2" fontsize=12
text x=70 y=292 sensor=cpu cpu=1 format="%v%" interval=1000
graph x=107 y=268 w=150 h=50 points=100 color=247,1,1 sensor=cpu format="%system" cpu=1 interval=1000
graph x=107 y=269 w=150 h=50 points=100 color=1,247,1 sensor=cpu format="%user" cpu=1 interval=1000
################################################################################
|
Omal küll on tegemist ATI kaardiga.
Lisa infoks sain veel juhtimise keskusest järgmist :
Kood: |
SEE SII AGP Kontroller-i kohta
Identifikaator
Tootja: %u200EIntel Corporation
Kirjeldus: %u200E82865G/PE/P DRAM Controller/Host-Hub Interface
Andmekandja klass: %u200EHost bridge
Ühendus
Siin: %u200EPCI
PCI domeen: %u200E0
PCI siin #: %u200E0
PCI seade #: %u200E0
PCI funktsioon #: %u200E0
Tootja ID: %u200E0x8086
Seadme ID: %u200E0x2570
Muud
Moodul: %u200Eintel_agp
GRAAFIKAKAART
Identifikaator
Tootja: %u200EATI Technologies Inc
Kirjeldus: %u200ERV350 AS [Radeon 9550]
Andmekandja klass: %u200EVGA compatible controller
Ühendus
Siin: %u200EPCI
PCI domeen: %u200E0
PCI siin #: %u200E1
PCI seade #: %u200E0
PCI funktsioon #: %u200E0
Tootja ID: %u200E0x1002
Seadme ID: %u200E0x4153
Tootja alam-ID: %u200E0x1462
Seadme alam-ID: %u200E0x9516
Muud
Moodul: %u200ECard:ATI Radeon 9500 - X850
LSPCI käsuga veel sellist nänni:
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550]
01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)
|
|
|
|
|
|
|
|
|
Qilaq
Vana Pingviin
Vanus: 55
Liitunud: 25.10.2006
Postitused: 1219
Asukoht: Linda Nisa
Distributsioon: Mageia, Mandriva Linux
|
|
See on päris lõbus: ma paigaldasin sellise asjanduse nagu Kima - pmst samasugune asi ja sain teada, et mu GPU temperatuur on 64, aga protsessoril -269!
Mida iganes, aga midagi loetakse igatahes kuskilt valesti.
|
|
|
|
_________________ Tõlkija (Mandriva Linux, KDE, Scribus, CUPS)
|
|
|
|
Qilaq
Vana Pingviin
Vanus: 55
Liitunud: 25.10.2006
Postitused: 1219
Asukoht: Linda Nisa
Distributsioon: Mageia, Mandriva Linux
|
|
need punktiga on jah peidetud failid - enamasti on tegemist seadistustefailiga, mis kirjutatakse vastavalt sellele, mida sa (graafiliselt) oled määranud, ja üldjuhul ei ole vaja neid käsitsi torkima hakata, sellepärast ongi nad vaikimisi peidetud - aga kui tõesti peaks vaja olema, saab neid nähtavaks teha ja ära kasutada...
|
|
|
|
_________________ Tõlkija (Mandriva Linux, KDE, Scribus, CUPS)
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Ära ütlemata lõbus on jah, ja sai kah siis nuid nö. natuke muditud oma käejärgi seda ublook pluginat. tulemus siis selline http://pingviin.org/album_showpage.php?pic_id=197 aint temp ei tööta, saaks selle kah kuigi tööle siis oleks päris kaunis silmal vaadata.
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
ATI kaartidel vist temperatuuri lugemise vahendit pole, aga sa võiks panna protsessori temperatuuri sinna asemele. Selleks asenda seal temp rea juures "nvidia-settings bla bla" sellega:
"sensors | grep -m 1 'Core 0' | cut -b 14,15,16" ja kui tahad teise tuuma temperatuuri ka näha, siis asenda Core 0 1-ga.
Lm-sensors, või lihtsalt, sensors pakett peab olema paigaldatud ja töötamas.
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Tänks Zen kuid mitte ei võta miskit pilti ette.
Hetkel selline script:
text x=20 y=125 value="Temp CPU"
text x=130 y=125 sensor=program program="sensors | grep -m 1 'Core 0' | cut -b 14,15,16" interval=10000
text x=144 y=125 value="0 %uFFFDC"
bar x=130 y=125 w=20 h=0 path="images/bar4.png" max=100. interval=10000 sensor=program program="sensors | grep -m 1 'Core 0' | cut -b 14,15,16"
urpmi-ga lasin peale ka lm_sensors paki a nuid mai sa päris täpselt aru et kas ma pean loom sellise faili? Nimelt sain sellise teksti omanikuks pärast lm_sensors paigaldamist:
Kood: | Rohkem infot paketi lm_sensors-2.10.4-2mdv2008.0.i586 kohta
* To use this package, you'll have to launch "sensors-detect" as root, and ask few questions.
No need to modify startup files as shown at the end, all will be done.
* Special note for via686a and i2c-viapro : if you don t see the values, you probably have a PCI conflict.
It will be corrected in next kernel. Change the /etc/sysconfig/lm_sensors to use i2c-isa + via686a
(or i2c-viapro + another sensor)
|
kogu toiming consolis nägi välja mul järgmiselt:
Kood: |
[iffi@localhost ~]$ su
Password:
[root@localhost iffi]# urpmi Lm-sensors
Paketti nimega Lm-sensors ei ole
[root@localhost iffi]# urpmi sensors
Paketti nimega sensors ei ole
sensors sisaldub järgmistes pakettides:
gnome-sensors-applet
ksensors
liblm_sensors3
liblm_sensors3-devel
liblm_sensors3-static-devel
lm_sensors
xfce-sensors-plugin
[root@localhost iffi]# urpmi lm_sensors
Sõltuvuste lahendamiseks paigaldatakse järgmised paketid:
Pakett Versioon Väljalase Arhitektuur
(andmekandja "Main (Official2008.0-13)")
librrdtool2 1.2.23 4mdv2008.0 i586
lm_sensors 2.10.4 2mdv2008.0 i586
Kasutusele võetakse veel 2.1MB kettaruumi.
Kas paigaldada 2 paketti? (J/e) j
ftp://ftp.free.fr/mirrors/ftp.mandriva.com/MandrivaLinux/official/2008.0/i586/media/main/release/librrdtool2-1.2.23-4mdv2008.0.i586.rpm
ftp://ftp.free.fr/mirrors/ftp.mandriva.com/MandrivaLinux/official/2008.0/i586/media/main/release/lm_sensors-2.10.4-2mdv2008.0.i586.rpm
librrdtool2-1.2.23-4mdv2008.0.i586.rpm lm_sensors-2.10.4-2mdv2008.0.i586.rpm paigaldamine andmekandjalt /var/cache/urpmi/rpms
Valmistumine... #############################################
1/2: librrdtool2 #############################################
2/2: lm_sensors #############################################
----------------------------------------------------------------------
Rohkem infot paketi lm_sensors-2.10.4-2mdv2008.0.i586 kohta
* To use this package, you'll have to launch "sensors-detect" as root, and ask few questions.
No need to modify startup files as shown at the end, all will be done.
* Special note for via686a and i2c-viapro : if you don t see the values, you probably have a PCI conflict.
It will be corrected in next kernel. Change the /etc/sysconfig/lm_sensors to use i2c-isa + via686a
(or i2c-viapro + another sensor)
----------------------------------------------------------------------
[root@localhost iffi]#
|
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
Nüüd root alt käivita sensors-detect, võid rahus kõikidele yes vastata.
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Ikka miski jama, startisin peale sensos-detect ka KDE uuesti a ei mingeid muutusi
Ehk oskab siit midagi tarka välja lugeda. Kood: |
[iffi@localhost ~]$ su
Password:
[root@localhost iffi]# 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): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801EB ICH5
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: SMBus I801 adapter at 0c00 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x2f
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM78-J'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83791SD'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1029'... No
Probing for `ITE IT8712F'... No
Probing for `Fintek custom power control IC'... No
Probing for `Winbond W83791D'... No
Client found at address 0x44
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'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found `Winbond W83627THF Super IO Sensors' Success!
(address 0x290, driver `w83627hf')
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... 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 `w83627hf' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `Winbond W83627THF 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/modprobe.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----
# Chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/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 overwrite /etc/sysconfig/lm_sensors? (YES/no): y
[root@localhost iffi]# bash
[root@localhost iffi]# |
Kas ei peaks läbi viima seda muudatust?
Special note for via686a and i2c-viapro : if you don t see the values, you probably have a PCI conflict.
It will be corrected in next kernel. Change the /etc/sysconfig/lm_sensors to use i2c-isa + via686a
(or i2c-viapro + another sensor)
Faili /etc/sysconfig/lm_sensors sisu on järgmine: mida kuidas muuta kui vajadus on ?
Kood: |
/etc/sysconfig/lm_sensors - Defines modules loaded by
# /etc/init.d/lm_sensors
# Copyright (c) 1998 - 2001 Frodo Looijaard <frodol@dds.nl>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
#
#
# See also the lm_sensors homepage at:
# http://www.lm-sensors.org/
#
# This file is used by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded. This file is sourced into /etc/init.d/lm_sensors.
#
# The format of this file is a shell script that simply defines the modules
# in order as normal variables with the special names:
# MODULE_0, MODULE_1, MODULE_2, etc.
#
# List the modules that are to be loaded for your system
#
# Generated by sensors-detect on Mon Oct 22 01:07:10 2007
MODULE_0=w83627hf |
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
Mida käsk "sensors" näitab, tavakasutajana.
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
tavakasutajana paistab kõik olevat OK
Konsooli sisu
Kood: |
[iffi@localhost ~]$ sensors
w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.40 V (min = +0.70 V, max = +1.87 V)
+12V: +3.83 V (min = +8.94 V, max = +3.22 V) ALARM
+3.3V: +3.23 V (min = +3.50 V, max = +3.70 V) ALARM
+5V: +4.99 V (min = +1.89 V, max = +3.39 V) ALARM
-12V: +0.72 V (min = -5.78 V, max = -14.91 V) ALARM
V5SB: +5.05 V (min = +1.69 V, max = +2.88 V) ALARM
VBat: +3.01 V (min = +3.06 V, max = +2.75 V) ALARM
fan1: 1028 RPM (min = 2250 RPM, div = 8) ALARM
CPU Fan: 2250 RPM (min = 1318 RPM, div = 8)
fan3: 0 RPM (min = 1534 RPM, div = 8) ALARM
M/B Temp: +31°C (high = +22°C, hyst = +5°C) sensor = thermistor ALARM
CPU Temp: +71.0°C (high = +120°C, hyst = +115°C) sensor = diode
temp3: +47.0°C (high = +120°C, hyst = +115°C) sensor = thermistor
vid: +1.388 V (VRM Version 10.0)
alarms:
beep_enable:
Sound alarm enabled
[iffi@localhost ~]$ |
Kas siin scriptis ei peaks nats miskit muutma. Mõtlen seda VALUE välja? miski print käsu panema või midagi taolist?
text x=20 y=125 value="Temp CPU"
text x=130 y=125 sensor=program program="sensors | grep -m 1 'Core 0' | cut -b 14,15,16" interval=10000
text x=144 y=125 value="0 %uFFFDC"
bar x=130 y=125 w=20 h=0 path="images/bar4.png" max=100. interval=10000 sensor=program program="sensors | grep -m 1 'Core 0' | cut -b 14,15,16"
sensorid kõik nagu ju töötavad a mo arust script ei saa noid andmeid kätte või ei oska sellisel kujul väljastada?
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
Ja sensoreid sul küll, aga seda sensorite välja peab natuke muutma. \
EDIT: et prose temperatuuri näidata, vaheta karambas praegune "sensors | grep bla bla" selle vastu:" sensors | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16"
Enne proovi konsoolis läbi kas töötab.
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
hehee näitab kuigi graafilist joont http://pingviin.org/album_showpage.php?pic_id=212
consolis näitab: [iffi@localhost ~]$ sensors | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16
+53.5
täitsa huvitav ja põnev ikka surkida (ple veel eales ise midagi oma käega mudinud) huvitav, mida peaks kirjutama sinna VALUE järgi et näitaks asja ka numbriliselt?
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
Hmm võta sensors realt 16 tagant ära ja proovi kõigepealt text kuvada ja seejärel ka joon
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Suured tänud sulle Zen nuid toimib nii numbriliselt kui ka graafiliselt kõik koos http://pingviin.org/album_showpage.php?pic_id=213
Ennem oli viga lihtsalt selles et puudus " märk rea lõpust (16 järelt) ja VALUE rida pole üldse tarvis.
Hetkel töötav script on järgmine:
text x=20 y=130 value="Temp CPU"
text x=130 y=125 sensor=program program="sensors | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16"
bar x=130 y=140 w=20 h=0 path="images/bar4.png" max=100. interval=10000 sensor=program program="sensors | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16"
Igati huvitav ja põnev, eks ma nuid üritan oma peaga seda pluginat veel aretada.
Nagu ütles üks inimene--> Linuxs see on seiklus
|
|
|
|
|
|
|
|
Zen
Pingviini aktivist
Vanus: 36
Liitunud: 07.10.2005
Postitused: 155
|
|
Tore et töötab . Jah nende karamba teemadega on nii, et vahest pole mingi teema juures midagi meelepärast ja peab ise modima neid. Endal on vahest töölaual selline teema: http://pingviin.org/album_showpage.php?pic_id=215. Kõvasti moditud Inspiron teemast.
|
|
|
|
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
|
|
-IFFI-
Vana Pingviin
Vanus: 48
Liitunud: 25.06.2005
Postitused: 1411
Asukoht: Lappeenranta-Turku
Distributsioon: Linux MX
|
|
Zen kirjutas: | Ja sensoreid sul küll, aga seda sensorite välja peab natuke muutma. \
EDIT: et prose temperatuuri näidata, vaheta karambas praegune "sensors | grep bla bla" selle vastu:" sensors | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16"
Enne proovi konsoolis läbi kas töötab. |
On's kusagil miski link või midagi taolist kus saaks uurida/õppida kuidas erinevaid sensoreid kuvada sinna sysinfosse (mõtlen neid käske-väljundeid) Et kuidas koostada sellist | grep -m 1 'CPU Temp' | cut -b 12,13,14,15,16 asjandust. Mida tähendavad grep, -m 1, cut, -b jne...teeks ka omale asja selgeks
Segane a loodan, et saad aru mida mõtlen....
Hetkel panin lihtsalt program=sensors siis kuvab kogu sitta sinna
Kood: | w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.38 V (min = +0.70 V, max = +1.87 V)
+12V: +3.83 V (min = +8.94 V, max = +3.22 V) ALARM
+3.3V: +3.22 V (min = +3.50 V, max = +3.70 V) ALARM
+5V: +5.01 V (min = +1.89 V, max = +3.39 V) ALARM
-12V: +0.63 V (min = -5.78 V, max = -14.91 V) ALARM
V5SB: +5.05 V (min = +1.69 V, max = +2.88 V) ALARM
VBat: +3.01 V (min = +3.06 V, max = +2.75 V) ALARM
fan1: 1035 RPM (min = 2250 RPM, div = 8) ALARM
CPU Fan: 2250 RPM (min = 1318 RPM, div = 8)
fan3: 0 RPM (min = 1534 RPM, div = 8) ALARM
M/B Temp: +31°C (high = +22°C, hyst = +5°C) sensor = thermistor ALARM
CPU Temp: +53.5°C (high = +120°C, hyst = +115°C) sensor = diode
temp3: +47.5°C (high = +120°C, hyst = +115°C) sensor = thermistor
vid: +1.388 V (VRM Version 10.0)
alarms:
beep_enable:
Sound alarm enabled
|
eesmärk saada aint numbriline inf..mitte a'la seda sodi "sensor = thermisto" jne
|
|
|
|
|
|
|
|
|
|