Strona 1 z 1

brak wskazań temperatury CPU w conky

: 02 maja 2008, 18:58
autor: wilk_DB
Jak wpisuje sensors do konsoli, wyrzuca mi coś takiego :

Kod: Zaznacz cały

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Znalazłem jednego użytkownika na forum Ubuntu, który miał ten sam problem i go rozwiązał, powiedział na forum, że miał błąd w skrypcie conky.
Sam używam ubuntu 7.10 proszę o pomoc. A oto moje conky:

Kod: Zaznacz cały

use_xft yes
background yes
xftfont Bistream Vera Sans:size=8
xftalpha 0.9
update_interval 1.0
total_run_times 0
double_buffer yes
alignment top_right
gap_x 40
gap_y 100
minimum_size 200 5

draw_shades no
draw_graph_borders no

draw_outline yes
own_window yes
own_window_type override
own_window_transparent yes
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
default_color white
defalut_shade_color red
border_margin 4
border_width 0

cpu_avg_samples 2
TEXT
${color yellow}${font Bistream Vera Sans:size=15}$alignc${time %k:%M:%S}
${color yellow}${font Bistream Vera Sans:size=8}${voffset -10}$alignc${time %A, %d %B %Y}
${font Bistream Vera Sans:size=8}
${color slate grey}Kernel:
$alignc${color }$kernel
${color slate grey}UpTime:
$alignc${color }$uptime
${color slate grey}Load:
$alignc${color }$loadavg

${color slate grey}Temp: $alignc${color red}$acpitemp C
${color slate grey}${hr 1}
${color slate grey}CPU 0:${alignr}:CPU 1
${color red}${cpu cpu1}% 2.66GHz$alignr${color red}${cpu cpu2}% 2.66 GHz
$color${cpugraph cpu1 30,90 5555aa 3333bb}$alignr$color${cpugraph cpu2 30,90 5555aa 3333bb}
${color slate grey}${hr 1}
${color slate grey}RAM:
${color c54507}${membar 15,200}
${voffset -19}$alignc${color orange}$mem / $memmax $alignr$memperc %
${voffset 4}${color slate grey}SWAP:
${color c54507}${swapbar 15,200}
${voffset -19}$alignc${color orange}$swap / $swapmax $alignr$swapperc %
${color slate grey}${hr 1}
HDD Temperature ${hddtemp /dev/sda}
${color slate grey}${alignc}Transfer dysku : $color${diskio}
${color slate grey}HDD:Samsung
$alignc${color green}${fs_used /}/${fs_size /}
$alignc${color green}${fs_bar 6,200 /}
${color lightgrey}Networking:
¦ciąganie:$color ${downspeed ppp0} k/s${color lightgrey} ${offset 80}
${totaldown ppp0} ${color}Pobrałeś
${color #6B99BE}${downspeedgraph ppp0 15,200 ff0000 0000ff}
${color lightgrey}Wysyłanie:$color ${upspeed ppp0} k/s
${color #6B99BE}${totalup ppp0}Wysłałeś ${color}
${upspeedgraph ppp0 15,200 0000ff ff0000}


$color$stippled_hr
$color$stippled_hr
${alignc} ${color #ccccee} MPD:${color #88ff88}Now $mpd_status
$color ${alignc} $mpd_artist
${alignc} $mpd_title
${alignc} Głośność: $mpd_vol Prędkość: $mpd_bitrate kbps
${color #ccddff} $mpd_bar $color
${color grey}${font :size=10}Gainward GF8600GTS: ${color red}${execi 30 nvidia-settings -q [gpu:0]/GPUCoreTemp | grep '):' | awk '{print $4}' | sed 's/\.//'} ${color #ddaa00}°C

${endif}
.

: 02 maja 2008, 21:02
autor: velmafia
wilk_DB pisze:Try sensors-detect to find out which these are.
odpalałeś sensors-detect ?

: 02 maja 2008, 21:30
autor: wilk_DB
tak zainstalowałem i nic

: 02 maja 2008, 22:04
autor: velmafia
wilk_DB pisze:tak zainstalowałem i nic
co zainstalowałeś?

przecież pytałem się czy odpaliłeś sensors-detect

: 02 maja 2008, 23:30
autor: wilk_DB
wpiszę sensors -detect
w konsoli i to mi wyskakuje zawsze :

Kod: Zaznacz cały

   root@wilk:/home/wilk# 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): 
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): 
Module loaded successfully.
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): 
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: NVIDIA i2c adapter  (i2c-0)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter  (i2c-1)
Do you want to scan it? (YES/no/selectively): 
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): 

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

Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No

Client found at address 0x4f
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `Dallas Semiconductor DS1621'...                No
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
Client found at address 0x52
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

Next adapter: ISA main adapter (i2c-9191)
Do you want to scan it? (YES/no/selectively): Can't open /dev/i2c-9191

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

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): 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 `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `Winbond W83627DHG 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/modules:

#----cut here----
# Chip drivers
w83627ehf
#----cut here----


Do you want to add these lines to /etc/modules automatically? (yes/NO)root@wilk:/home/wilk# 
root@wilk:/home/wilk# 

: 02 maja 2008, 23:53
autor: velmafia
masz załadowany ten moduł (w83627ehf )?
sprawdź:

Kod: Zaznacz cały

lsmod | grep w83627ehf 
jeśli nie to go załaduj i sprawdź potem wynik polecenia sensors

: 03 maja 2008, 10:57
autor: wilk_DB
dzięki ale już sobie poradziłem

: 01 września 2008, 22:28
autor: AMartin
Mam ten sam problem, tylko że wyświetla mi na końcu:

Kod: Zaznacz cały

#----cut here----
# Chip drivers
coretemp
#----cut here----
a kiedy wpisuję

Kod: Zaznacz cały

lsmod|grep coretemp
nic mi nie pokazuje. Co z tym zrobić?

[ Dodano: 2008-09-01, 23:07 ]
Wystarczy restart systemu i wszystko działa.

: 06 września 2008, 17:53
autor: raggo82

Kod: Zaznacz cały

# Chip drivers
coretemp 

Wklej to do /etc/modules , restart compa i gotowe