[JeevusCompact]

Are lm-sensors incompatible with ubuntu 9.10?

I installed lm-sensors, went through the whole installing-detect procedure.

lm-sensors seem not to work at all.

 

[Melcar]

They work fine. Some boards do have problems though, but it's hard to know for sure.
Are the modules loading at start up? Check your /etc/modules file; it should have something like this at the end (not exactly mind you, since different modules are used for different hardware makes):

Code:

# Generated by sensors-detect on Fri Oct 30 21:31:57 2009
# Chip drivers
k8temp

If there is nothing there then sensors-detect did not run correctly. When you run that script it will ask you if you want to write the necessary changes to /etc/modules. At that step you should answer "yes". You should also check that there are no errors given out whle you run the script.

 

[TFB]

Nope, I'm using it just fine. You do have to reboot after install though.

 

[JeevusCompact]

Code:

# /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.

lp
rtc

# Generated by sensors-detect on Mon Feb  8 02:29:12 2010
# Chip drivers
dme1737

# Generated by sensors-detect on Mon Feb  8 02:34:57 2010
# Chip drivers
dme1737

# Generated by sensors-detect on Thu Feb 11 16:10:54 2010
# Chip drivers
dme1737

Quote:

ubuntu@ubuntu-foldng:~$ sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. ubuntu@ubuntu-foldng:~$

 

[TFB]

It looks to me like sensors detect did not find the right sensors.

I'm using EP43-UD3L and this is what I got:

Code:

# Chip drivers
it87
coretemp

Also, why is it trying to load the same sensor 3 times? Take the last two out.

 

[Melcar]

Every time you run sensors-detect it appends a section to /etc/modules. Doesn't do anything, other than clutter the file.
At OP. What does the output look like when you run sensors-detect? Get any errors while doing it? There is also some situations with certain BIOS files that causes lm-sensors to fail. Don't know if it applies to your situation, but just for the hell of it you may try appending the following to your boot parameters:

Code:

acpi_enforce_resources=lax

In the grub2 menu, just press "e" while highlighting your kernel and add the above parameter at the end of the line that starts with "linux". See if you get a reading from lm-sensors then. The above change is just for a session, so if it happens to work you will need to do a more permanent fix.

 

[JeevusCompact]

Quote:

Originally Posted by Melcar Every time you run sensors-detect it appends a section to /etc/modules. Doesn't do anything, other than clutter the file. At OP. What does the output look like when you run sensors-detect? Get any errors while doing it? There is also some situations with certain BIOS files that causes lm-sensors to fail. Don't know if it applies to your situation, but just for the hell of it you may try appending the following to your boot parameters: Code: acpi_enforce_resources=lax In the grub2 menu, just press "e" while highlighting your kernel and add the above parameter at the end of the line that starts with "linux". See if you get a reading from lm-sensors then. The above change is just for a session, so if it happens to work you will need to do a more permanent fix.

Yeah, this is on an ibm that has a 963 or 965 intel chipset, its my second folding rig, it fold's 24/7, I really do not want to reboot it. meh its all good, i will just throw a thermal probe on the heatsink to get an estimate. Ubuntu is like a car with a motor but no tires. Been having resolution prob with too. It's got me in a strungout mood.

 

[Melcar]

You *have* to reboot. You could try loading the module alone and see if that works (sudo modprobe dme1737), but rebooting is usually necessary.

 

[JeevusCompact]

I rebooted, then tried

Code:

sudo modprobe dme1737

then rebooted again.

Ran

Code:

ubuntu@ubuntu-foldng:~$ sudo sensors
[sudo] password for ubuntu: 
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ubuntu@ubuntu-foldng:~$

Same as before nothing.

 

[Melcar]

Did you try the boot parameter as well? Also, make sure you're answering "yes" to all the questions during sensors-detect.

 

[JeevusCompact]

I cannot edit at bootup, it shows up for a sec then boots up, I installed startup manager to set the timeout time to 100 seconds, it still just boots up. meaning I do not get a grub menu at all. Just "Grub" in text shows at the upper left of the screen for a Millisec, then ubuntu boots up.
Edit:
I got it to show

 

[JeevusCompact]

Quote:

Originally Posted by Melcar Every time you run sensors-detect it appends a section to /etc/modules. Doesn't do anything, other than clutter the file. At OP. What does the output look like when you run sensors-detect? Get any errors while doing it? There is also some situations with certain BIOS files that causes lm-sensors to fail. Don't know if it applies to your situation, but just for the hell of it you may try appending the following to your boot parameters: Code: acpi_enforce_resources=lax In the grub2 menu, just press "e" while highlighting your kernel and add the above parameter at the end of the line that starts with "linux". See if you get a reading from lm-sensors then. The above change is just for a session, so if it happens to work you will need to do a more permanent fix.

No errors at all.

Code:

ubuntu@ubuntu-foldng:~$ sudo sensors-detect
[sudo] password for ubuntu: 
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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 82801H ICH8

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): y
Module loaded successfully.
If you have undetectable or unsupported I2C/SMBus 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: intel drm CRTDDC_A (i2c-0)
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)
Client found at address 0x51
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)
Client found at address 0x52
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)
Client found at address 0x53
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: SMBus I801 adapter at 3080 (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'...                                 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 `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'...                                     Yes
Found `SMSC SCH5127 Super IO'                               Success!
    (address 0x500, driver `dme1737')
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 south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 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 `dme1737' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x500
    Chip `SMSC SCH5127 Super IO' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
dme1737
#----cut here----

Do you want to add these lines automatically? (yes/NO)y
ubuntu@ubuntu-foldng:~$

I've tried this as well at botup.

Code:

acpi_enforce_resources=lax

then after bootup.

Code:

ubuntu@ubuntu-foldng:~$ lm-sensors
lm-sensors: command not found
ubuntu@ubuntu-foldng:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ubuntu@ubuntu-foldng:~$

 

[Melcar]

Edit: Never mind.

Update kernels maybe? Just get the latest 2.6.32 from here (or the 2.6.33 rc if you want). Just download the headers for your achitecture, the headers-all package, and the image for your arch, and install all three.
Will try some google-fu and see if I find anything pertaining to any funky stuff with lm-sensors and your board. Lm-sensors is detecting the module during setup, but for some reason it doesn't seem to be loading it.

 

[JeevusCompact]

Quote:

Originally Posted by Melcar Edit: Never mind.

Did i do something wrong?
ah ok, by the way, I am running my hdd off of a usb hdd enclosure box, if that has anything to do with it.

 

[JeevusCompact]

Quote:

Originally Posted by Melcar Edit: Never mind. Update kernels maybe? Just get the latest 2.6.32 from here (or the 2.6.33 rc if you want). Just download the headers for your achitecture, the headers-all package, and the image for your arch, and install all three. Will try some google-fu and see if I find anything pertaining to any funky stuff with lm-sensors and your board. Lm-sensors is detecting the module during setup, but for some reason it doesn't seem to be loading it.

Installed 2.6.33rc, rebooted, goto boot into the new kernal, my screen shuts off, I have to manually shutdown then boot into my original kernal.

Edit:
Wonder what it is like to add a wallpaper

: kiddin...

 

[Melcar]

You have to build it. Well first you got to draw the thing on a console of course

.
Try the 2.6.32 kernel. The RCs lack some firmware for newer ATI cards, so maybe that's why it gave you the black screen.

 

[Melcar]

Apparently sensors-detect can sometimes load the wrong modules. I'm trying to find what driver your particular board should load.

 

[JeevusCompact]

Quote:

Originally Posted by Melcar Apparently sensors-detect can sometimes load the wrong modules. I'm trying to find what driver your particular board should load.

It's an IBM board, my second folding rig.

it has a 963 or 965 chipset.