Beiträge von Lextor

Zitat von BananaJoe

Werde mir das ganze ansehen und probieren und testen

Kannst ja mal berichten zu gegebener Zeit...

Für Youtube nutze ich: https://freetubeapp.io/#download

Danke Dir...

Hi,

Ich hätte eine Frage zu der Tabelle.

Kann es sein, das zweistellige Nummern nicht erlaubt sind?

Gebe ich im conky.text $Color10} erscheint das Color10 vor dem entsprechendem Anzeige...bei {color9} oder wkleiner funktioniert es...

Danke...so hatte ich mir das vorgestellt...

Gruß Lextor

Nein...ich nutze den Kalender nicht...

Hallo zusammen,

Ist es möglich die Uhr ganz auszublenden unter Mint?

Ich finde nur Möglichkeiten der Anpassung...Sekunden anzeigen...Zeitzone ändern etc.

Gruß Lextor

Kein Problem...wieder was gelernt...

Aber...woher soll man das alles wissen, wenn nicht irgendwer es einem sagt?

Und wer war dann zuerst da...Huhn oder Ei?

Klasse...wieder was gelernt...ich danke Dir vielmals...

Hallo,

Es sind so die Kleinigkeiten die ich gerne wissen würde...

Warum kann ich in der Config z.B. Color1 = 'E0FFFF' angeben um damit im conky.text zu arbeiten, aber wenn ich den Hintergrund ändern möchte, muss ich own_window_colour schreiben, also noch ein "u" ?

Ich danke Dir vielmals für deine Geduld und Hilfe...

Nun hab ich noch eine Verständnisfrage...

In dieser Zeile für die CPU Package Temperatur sind die Schwellwerte in Anführungszeichen

${color1}${font Font Awesome 6 Free:style=Solid:size=10}${font}${goto 25}${font Roboto:size=10} CPU Package:$alignr${if_match "${exec sensors coretemp-isa-0000 | grep 'Package id 0' | cut -c17-23}">="75"}${color4}${exec sensors coretemp-isa-0000 | grep 'Package id 0' | cut -c17-23}${else}${color2}${exec sensors coretemp-isa-0000 | grep 'Package id 0' | cut -c17-23}${endif}${font}

Funktioniert nicht ohne...wird falsche Schriftfarbe ausgegeben.

In der deinem Code sind keine Anführungszeichen...funktioniert aber...

Warum?

Hallo nochmals,

Ich habe noch eine Frage...

Es geht um folgende Zeile:

${color1}${font Font Awesome 6 Free:style=Solid:size=10}${font Roboto:size=10}Akku: ${color2} $alignr$ {if_match "${cat /sys/class/power_supply/BAT0/capacity}"<="40"}${color6}${if_match "${cat /sys/class/power_supply/BAT0/capacity}"<="25"}${color4}${else}${cat /sys/class/power_supply/BAT0/capacity}${color2}${endif}${endif}

Ich möchte gerne die Akkuzustände farblich unterscheiden. Es geht um <=40 und <=25

irgendwie bekomme ich es nicht hin..und dann kam die Frage auf, ob es überhaupt gehen würde...denn kleiner als 25 ist ja auch zeitgleich kleiner als 40...könnt Ihr mir auf die Sprünge helfen?

Vielen Dank...

Zitat von Bleys

Nein. Die input Dateien enthalten wohl mehrere Stellen hinterm Komma aber der hwmon Befehl arbeitet mit Ganzzahlen.

OK, Danke für die Info und deine Unterstützung...hab doch so einiges gelernt...

was mir gerade auffällt...

über den Hwmon Befehl bekomme ich die Temperaturen ohne Dezimalstelle ausgegeben...beim exec aber schon..

Kann man da was machen?

Zitat von Bleys

Nebenbei fällt mir noch auf das Deine sensors Ausgabe relativ mager ist. Hast Du

sudo sensors-detect

ausgeführt?

sudo sensors-detect
[sudo] Passwort für christoph:
# sensors-detect version 3.6.0
# System: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX363EA [1.0]
# Board: ASUSTeK COMPUTER INC. UX363EA
# Kernel: 5.15.0-102-generic x86_64
# Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (6/140/1)

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): y
Module cpuid loaded successfully.
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 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): y
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 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): y
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): y
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): y
Found unknown SMBus adapter 8086:a0a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: i915 gmbus dpa (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4a
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP435'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Client found at address 0x4b
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP435'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `Analog Devices ADT7481'... No

Next adapter: i915 gmbus dpc (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc1 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc2 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc3 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc4 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc5 (i2c-10)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc6 (i2c-11)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AUX A/DDI A/PHY A (i2c-12)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x48
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410/ADT7420'... No
Probing for `Analog Devices ADT7411'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP435'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No

Next adapter: AUX USBC1/DDI TC1/PHY TC1 (i2c-13)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AUX USBC2/DDI TC2/PHY TC2 (i2c-14)
Do you want to scan it? (yes/NO/selectively): y

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

Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

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

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK

Zitat von Bleys

${hwmon asus fan 1}

Das wars...danke

Ich nochmal...

also über den Befehl Hwmon funktioniert das nicht bei jedem Sensor.

${hwmon asus cpu_fan} und es passiert nichts....über den exec Befehl ist die Drehzahl vorhanden.

Mache ich was falsch?

Zitat von Bleys

Ach ja... der Fehler. Der Cut Befehl für den Package Wert gibt das aus:

Wie kamst Du darauf? Kann ich das kontrollieren?

Ich danke Dir vielmals...werde ich ausprobieren...

Vielen Dank...

Gruß Lextor

Danke für deine Tipps....

coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +91.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +91.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +76.0°C (high = +100.0°C, crit = +100.0°C)
Core 2: +78.0°C (high = +100.0°C, crit = +100.0°C)
Core 3: +74.0°C (high = +100.0°C, crit = +100.0°C)

ucsi_source_psy_USBC000:002-isa-0000
Adapter: ISA adapter
in0: 20.00 V (min = +5.00 V, max = +0.00 V)
curr1: 3.25 A (max = +0.00 A)

nvme-pci-e100
Adapter: PCI adapter
Composite: +31.9°C (low = -0.1°C, high = +76.8°C)
(crit = +79.8°C)

BAT0-acpi-0
Adapter: ACPI interface
in0: 17.21 V

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +36.0°C

ucsi_source_psy_USBC000:001-isa-0000
Adapter: ISA adapter
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

acpitz-acpi-0
Adapter: ACPI interface
temp1: +91.0°C (crit = +103.0°C)