Post your .conkyrc files w/ screenshots

[djyoung4]

be good if I could get cpu temp to work though

try:

acpi -t

in a terminal. see what it outputs

[miegiel]

try:

acpi -t

in a terminal. see what it outputs

For me 26.8°C, always 26.8°C, just like the top sensor lm-sensors lists.

user@machine:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:       +26.8°C  (crit = +127.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +51.0°C  (high = +105.0°C, crit = +105.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +52.0°C  (high = +105.0°C, crit = +105.0°C)  

user@machine:~$ acpi -ti
Thermal 0: ok, 26.8 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 127.0 degrees C

The coretemp sensor gives readings that make more sense (on my machine).

[Endomancer]

try:

acpi -t

in a terminal. see what it outputs

I entered it and it told me I have to install it and it gave me the sudo command to do so
I installed acpi and still no temp reading, I rebooted, still no temp reading, I re ran the acpi -t comand and got

endomancer@endomancer-desktop:~$ acpi -t
endomancer@endomancer-desktop:~$

I do remember reading somewhere that old some old cpu's can't do this, maybe mine qualifies

[djyoung4]

I entered it and it told me I have to install it and it gave me the sudo command to do so
I installed acpi and still no temp reading, I rebooted, still no temp reading, I re ran the acpi -t comand and got

endomancer@endomancer-desktop:~$ acpi -t
endomancer@endomancer-desktop:~$

I do remember reading somewhere that old some old cpu's can't do this, maybe mine qualifies

is this conky on your main machine or on your "dinosaur"

[Endomancer]

I run Conky on my main machine, haven't got round to trying it on the dinosaur yet

[phredbull]

My latest:

[grandsatrap]

My latest:

Very nice! What did you do with your top menu bar?

[phredbull]

It's actually 2 panels, unexpanded.

[djyoung4]

I run Conky on my main machine, haven't got round to trying it on the dinosaur yet

what do you get when you run:

sensors

[Endomancer]

what do you get when you run:

sensors

endomancer@endomancer-desktop:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
endomancer@endomancer-desktop:~$ sensors-detect
You need to be root to run this script.
endomancer@endomancer-desktop:~$ sudo sensors-detect
[sudo] password for endomancer: 
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# Board: Gigabyte Technology Co., Ltd. GA-8S661FXM-775

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
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
Intel Core family thermal sensor...                         No
Intel Atom thermal sensor...                                No
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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8705F Super IO Sensors'                        Success!
    (address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8705F Super IO Sensors'                        Success!
    (address 0x290, driver `it87')

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
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

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

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): y
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'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: NVIDIA i2c adapter  (i2c-2)
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: 

Driver `it87':
  * ISA bus, address 0x290
    Chip `ITE IT8705F Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
it87
#----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/module-init-tools start'
to load them.

Unloading i2c-dev... OK

endomancer@endomancer-desktop:~$