[SOLVED] xSensors Help Needed!

[crjackson]

I recently installed xSensors after seeing a screen shot posted on another board. Using the cli I'm able to see that I can read my core temps just fine.

So I installed xSecsors using synaptic and expected no problems but heres what I get.

A small window (framed as small as possible - Like shrinking it by draging the corner and making it very small) gets placed on the upper left hand corner of my desktop.

I grab the lower right corner of the frame and make it bigger. Inside I find a BLANK white background and no menu or clue as to how this thing operates.

What am I doing wrong, or what is wrong with my system?

TIA

[Mr_bleu]

I get the same thing. I've stopped trying to use it. I use the sensors applet instead.

[crjackson]

I get the same thing. I've stopped trying to use it. I use the sensors applet instead.

The screen shots look really nice. I sure hope someone here chimes in with a solution.

[david_2001]

If you get something like the following output from typing "sensors" at a command prompt then there is no reason why xsensors shouldn't work.
w83697hf-isa-0290
Adapter: ISA adapter
VCore: +1.26 V (min = +0.00 V, max = +1.02 V) ALARM
+3.3V: +3.36 V (min = +1.02 V, max = +0.02 V) ALARM
+5V: +5.08 V (min = +0.00 V, max = +0.22 V) ALARM
+12V: +11.37 V (min = +0.00 V, max = +0.97 V) ALARM
V5SB: +5.56 V (min = +3.44 V, max = +1.08 V) ALARM
Case Fan: 1022 RPM (min = 664 RPM, div = 8 )
CPU Fan: 948 RPM (min = 664 RPM, div = 8 )
M/B Temp: +39°C (high = +45°C, hyst = +40°C) sensor = thermistor
CPU Temp: +43.5°C (high = +50°C, hyst = +45°C) sensor = thermistor
alarms:
beep_enable:
Sound alarm enabled
All xsensors does is present the same information graphically (see screenshot).

[crjackson]

If you get something like the following output from typing "sensors" at a command prompt then there is no reason why xsensors shouldn't work.

All xsensors does is present the same information graphically (see screenshot).

Actually the only thing mine reports is CPU temp for core 0 and core 1

Something is missing on my system I guess...:(

[david_2001]

Did you run "sensors-detect" yet?

[crjackson]

Did you run "sensors-detect" yet?

No, I'm afraid I was ignorant to that command/requirement. I'll be doing that in a couple of hours when I get home from work.

I guess it can't report what it hasn't been instructed to detect...

[david_2001]

When you run sensors-detect just accept all of the default options except the last (which is to NOT save all of the information).

[crjackson]

When you run sensors-detect just accept all of the default options except the last (which is to NOT save all of the information).

Got thanks - Can't wait to try it out.

[david_2001]

Before I forget, run sensors-detect as sudo. It will generate /etc/sensors.conf, which is fully commented. You may have to edit sensors.conf to refine the information that's displayed and/or change the tag names of each sensor (I renamed the M/B and case fans, for example).

[crjackson]

Before I forget, run sensors-detect as sudo. It will generate /etc/sensors.conf, which is fully commented. You may have to edit sensors.conf to refine the information that's displayed and/or change the tag names of each sensor (I renamed the M/B and case fans, for example).

I sort of hope I don't need to edit. Otherwise I'll be asking for help again. Thanks for the sudo tip, you really have NO IDEA how lost I've been since installing this OS. I'm just thankful so many people are here to help.

[Mr_bleu]

I uploaded a screenshot of xsensors. This is after running sensors-detect as sudo.

[david_2001]

Did you reboot after running sensors-detect? It will add the necessary kernel modules to /etc/modules and rebooting is the easiest way to load them. Of course, if it didn't find any supported sensors then I'm afraid you're out of luck.
# Generated by sensors-detect on Sat Apr 28 19:26:43 2007
# I2C adapter drivers
# modprobe unknown adapter cx88[0]
# modprobe unknown adapter cx88[1]
# modprobe unknown adapter saa7133[0]
# modprobe unknown adapter NVIDIA i2c adapter 0 at 2:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 2:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 2:00.0
i2c-viapro
# Chip drivers
eeprom
w83627hf

[crjackson]

Reboot was the key. I did the sensors-detect command and didn't think that it worked. After rebooting, it works perfectly.

One question. It seems to think that my NF4 board is an NF2 chipset. Is the NF2 chipset fully supported under ubuntu?

Thanks for the help...:popcorn:

[crjackson]

w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.41 V (min = +0.70 V, max = +1.87 V)
+12V: +12.22 V (min = +6.26 V, max = +9.30 V) ALARM
+3.3V: +3.07 V (min = +2.34 V, max = +2.56 V) ALARM
+5V: +4.80 V (min = +0.27 V, max = +1.31 V) ALARM
-12V: -12.03 V (min = -13.84 V, max = -14.91 V) ALARM
V5SB: +4.92 V (min = +2.45 V, max = +2.37 V) ALARM
VBat: +3.06 V (min = +1.17 V, max = +4.05 V)
fan1: 0 RPM (min = 5625 RPM, div = 2) ALARM
CPU Fan: 6250 RPM (min = 2109 RPM, div = 8)
fan3: 8035 RPM (min = 3409 RPM, div = 2)
M/B Temp: +40°C (high = +40°C, hyst = +0°C) sensor = thermistor ALARM
CPU Temp: +44.0°C (high = +80°C, hyst = +75°C) sensor = thermistor
temp3: -98.5°C (high = +80°C, hyst = +75°C) sensor = diode
vid: +0.000 V (VRM Version 2.4)
alarms:
beep_enable:
Sound alarm enabled

charles@K8N-Neo4-Platinum-SLI:~$

This is my terminal output (I don't know how to upload the screen shot). Any idea what temp3 is? It's a strange reading...

[david_2001]

This is my terminal output (I don't know how to upload the screen shot). Any idea what temp3 is? It's a strange reading...
The datasheet for the w83627thf chip indicates that it has 3 temperature inputs. It's likely that only 2 are connected to anything, hence the nonsense reading for the third. If you want to stop the third temperature from being listed then edit /etc/sensors.conf, search for the line "chip "w83627thf-*" "w83637hf-*"" and then scroll down a little and uncomment "# ignore temp3".

PS. It you want to upload a screenshot then click the paper clip in the forum editor toolbar - see screenshot ;-).

[david_2001]

One question. It seems to think that my NF4 board is an NF2 chipset. Is the NF2 chipset fully supported under ubuntu?

The answer to that is outwith my experience - though it's support by the sensors application rather than Ubuntu that's in question.

[gam3r]

Hi all i got the same problem. I ran through the lm sensors setup guide on the ubuntu guide and it works when i type "sensors" into the terminal but when i open xsensors its just a blank background. Reboot didn't fix it for me. Any ideas?

[crjackson]

Hi all i got the same problem. I ran through the lm sensors setup guide on the ubuntu guide and it works when i type "sensors" into the terminal but when i open xsensors its just a blank background. Reboot didn't fix it for me. Any ideas?

It wasn't working for me either.

Then I went to the terminal and typed the following commands:

sudo sensors-detect

It then asked me for my password which I provided..

Then it started with a series of prompts to which I answered all except the last one where it talked about storing or saving the information. I just told it yes...

xsensors still did nothing at this point. I rebooted and bingo... It worked. That's it...

[murak]

Hi all!

I answerd Yes to the last question and my Xsensors now work fine.
However I dont know what could happen if something should go wrong when answering Yes...

I made a "How to" of this thread http://ubuntuforums.org/showthread.php?p=2998486 where I recommend ppl to say Yes to the last question. I hope that this will help others as much as it helped me.

If you have any comments on the thread please let me know. Thank you all for your help!

[ST.x]

hey guys. Im still having problems here(same as the first post). Firstly I went through and answered YES to all the questions from sudo sensors-detect and it asked if `i2c-i801' module was already in the kernel or something and if not it should be loaded, but I said yes on this and it said it was successful.

I then realised I saw the post in this thread about saying NO to the last one question, so I reran sensors-detect but that wont do anything as the run from before already wrote to the modules file right. This is what it looks like:

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

fuse
lp
rtc
sbp2

# Generated by sensors-detect on Tue Sep 25 01:00:07 2007
# I2C adapter drivers
i2c-i801
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
# Chip drivers
eeprom

Here is also the sensors-detect with default options chosen, 'sensors' also doesn't find anything while 'acpi -t' finds a single cpu temp, not for each core:

seynthan@seynthan-lappy:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
seynthan@seynthan-lappy:~$ sudo sensors-detect
Password:
# sensors-detect revision 4171 (2006-09-24 03:37:01 -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 ICH7

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):
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
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'... Success!
(confidence 1, driver `eeprom')
Probing for `EDID EEPROM'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0x56 0x57
Probing for `Maxim MAX6900'... No

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

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

Next adapter: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x52
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x69

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 `Winbond W83627HF' 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 `AMD K8 thermal 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 `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No

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

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `NVIDIA i2c adapter'
Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x57)
Chip `EDID EEPROM' (confidence: 8)
* Bus `SMBus I801 adapter at 0400'
Busdriver `i2c-i801', I2C address 0x52
Chip `eeprom' (confidence: 6)

EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.

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----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
i2c-i801
# Chip drivers
eeprom
#----cut here----


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

[jwrede]

I'm having trouble with this one too. I ran through the setup guide (http://www.xawk.com/ubuntu-cpu-temperature.html) including the sudo sensors-detect and reboot steps and am getting a blank xSensors window. When I run sensors I get the result below. Any thoughts on why xSensors isn't displaying this right?


k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +3.0°C
Core0 Temp: -3.0°C
Core1 Temp: +11.0°C
Core1 Temp: +5.0°C

w83627ehf-isa-0a10
Adapter: ISA adapter
VCore: +1.09 V (min = +0.00 V, max = +1.74 V)
in1: +12.46 V (min = +13.46 V, max = +13.46 V) ALARM
AVCC: +3.34 V (min = +3.06 V, max = +4.02 V)
3VCC: +3.34 V (min = +4.02 V, max = +4.06 V) ALARM
in4: +1.60 V (min = +2.04 V, max = +1.53 V) ALARM
in5: +1.43 V (min = +2.04 V, max = +0.98 V) ALARM
in6: +4.61 V (min = +4.48 V, max = +6.53 V)
VSB: +3.33 V (min = +4.08 V, max = +4.08 V) ALARM
VBAT: +3.02 V (min = +4.08 V, max = +4.05 V) ALARM
in9: +1.50 V (min = +2.04 V, max = +1.53 V) ALARM
Case Fan: 2109 RPM (min = 0 RPM, div = 8)
CPU Fan: 2636 RPM (min = 111 RPM, div = 128)
Aux Fan: 0 RPM (min = 0 RPM, div = 128)
fan5: 0 RPM (min = 0 RPM, div = 4)
Sys Temp: +36.0°C (high = -1.0°C, hyst = -1.0°C) ALARM sensor = thermistor
CPU Temp: +30.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUX Temp: +34.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor

[Gonkerd]

Hi jwrede,

I had the same problem, but when i ran xsensors from a terminal i found out that my chipset(it8718) isn't supported by xsensors 0.5. I ran the following command:
xsensors
Sensor 'it8718' not supported by xsensors!
Sensor 'coretemp' not supported by xsensors!
Sensor 'coretemp' not supported by xsensors!