LM Sensors Help, Can't access procfs/sysfs file Unable to find i2c bus information;
 

I installed lm sensors and its libraries via rpms made for mandrake 10. I am running Mandrake 10.0 official with the stock 2.6.3 kernel.

[rob@Oneniisama rob]$ sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs!
For older kernels, make sure you have done 'modprobe i2c-proc'!

rob@Oneniisama rob]$ sensors -s
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs!
For older kernels, make sure you have done 'modprobe i2c-proc'!

I have an Asus A7n8x E Deluxe Motherboard.


is it possible to get LM sensors for this board and distro, or is this a lost cause?

No, it's not a lost cause; I'm almost certain you can get lm_sensors to work. But it may be a long twisty path getting there.

See this thread:

http://www.linuxquestions.org/questi...hreadid=253204

I finally got lm_sensors working under Mdk 10.1 with an older Asus motherboard (ca. 1999--how ancient, in computer terms...) mainly by running sensors-detect MANY times with various "y" or "n" responses. I think it's important to respond "no" when it offers to install the i2c module--because that's already in the 2.6.x kernel, and to install it again is to confuse the system. You also probably do NOT want to cut and paste the stuff that sensors-detect instructs you to cut and paste, because that, too, will result in duplication.

But exactly what I did to finally get it to run, I cannot tell you. I just tried things till it did.

But now it's reporting screwy voltages that trigger alarms every second, so I've disabled it. Cannot find how to fix that, even by commenting out all the voltage lines in the configuration file that seem to apply to my setup.

Lm_sensors worked just fine under 9.2. Oh, well. I guess I can live without it.

Good luck to you. Hope this helps.

sensors-detect wasnt seen as a command :(

Did you su to root user first?

If that doesn't work, I wonder if the package is all the way installed. It should do something...

OK, I just tried "sensors-detect" with lm_sensors STOPPED and it went ahead and started asking me how to proceed as normal.

But if I just gave the "sensors" command I got the response you copied in your first post here. Then I started up lm_sensors again and gave the "sensors" command and got the information (including the bogus voltage stuff that made me stop them in the first place).

So I wonder if you ever did "/etc/rc.d/init.d/lm_sensors start" as root. For it to start, the file "sensors.conf" has to be in the /etc directory, too. You might check to see if it's there first.

If it's not there, search for "sensors.conf.eg" on your system: it's a pre-made file that can be copied over to /etc under the name "sensors.conf" and then can be altered to suit your setup (with luck that I apparently don't have).

ok, i didnt know i need to be su to do the -detect command.

I ran it and i copied a bunch of stuff it spit out. it asked about is or smbbus, i dont have an isa slots so i chose smbus


Driver `asb100' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x2d (and 0x48 0x49)
Chip `Asus ASB100 Bach' (confidence: 8)

Driver `lm75' (may not be inserted):
Misdetects:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x48
Chip `National Semiconductor LM75' (confidence: 6)
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x49
Chip `National Semiconductor LM75' (confidence: 6)

Driver `smbus-arp' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x61
Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at 5500' (Algorithm unavailable)
Busdriver `i2c-nforce2', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)


To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-nforce2
# I2C chip drivers
modprobe asb100
modprobe smbus-arp
modprobe eeprom
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.

I have a 2.6 kernel, do i have the nforce module built in or do i want to use the module it gives?

this is very confusing for me :(

I agree it is VERY confusing. The comments in the pre-supplied sensors.conf file are even more confusing! The FAQ on the lm_sensors website are baffling in many places. I must say, though, that the people responsible for the lm_sensors project seem to be bending over backward to try to inform users and provide precise information--it's just that for average non-techie users like you and me, that doesn't quite get the job done. And this is one of those areas where it's hard or impossible to put things in "layman's" language, because it's all very technical and sometimes obscure and even self-contradictory by nature. So I applaud the lm_sensors team loudly, but at the same time their files aren't much help to me.

You DO have the ISA feature, the site assures me--every computer does, even though it's often not referred to by name any more; it's provided, and just about has to be, as a "legacy feature." So when it asks about the ISA probe I'd go ahead and do it.

Now that you can run sensors-detect, try it with various "nos" as well as some "yeses". That's what I did. And don't paste ANYTHING it recommends into your files. With the 2.6.x kernel this just screws things up, apparently.

I think I was about at the point you're at when, by trial and error, I got the thing to go. I just haven't figured out yet how to get rid of all those alarms from phony voltage readings. This is caused, apparently, by a motherboard that doesn't quite conform to how any of the ones they've tested work. I've got an old one, as I said.

Here is a page of FAQ that might help if you're patient enough.

http://howto.gp.mines.edu/local-apps...-2.8.1/doc/FAQ

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----


did that


now it says


To load everything that is needed, add this to some /etc/rc* file: which file? there are many folders and files!!!

#----cut here----
# I2C adapter drivers
modprobe i2c-nforce2
# I2C chip drivers
modprobe asb100
modprobe smbus-arp
modprobe eeprom
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

Without having this part

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-nforce2
# I2C chip drivers
modprobe asb100
modprobe smbus-arp
modprobe eeprom
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here-

sensors works, but i cant config it
i go to the asus asb100 section and try to change to values, but it doesnt recognize them
i even did the sensors-s as root, and then rebooted but thigns are still wacky.

[rob@Oneniisama rob]$ sensors
eeprom-i2c-0-51
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

eeprom-i2c-0-50
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

asb100-i2c-1-2d
Adapter: SMBus nForce2 adapter at 5500
VCore 1: +1.68 V (min = +1.55 V, max = +1.73 V)
+3.3V: +3.30 V (min = +3.12 V, max = +3.46 V)
+5V: +4.97 V (min = +4.73 V, max = +5.24 V)
+12V: +11.67 V (min = +10.76 V, max = +13.19 V)
-12V (reserved):
-12.13 V (min = -0.00 V, max = -0.00 V)
-5V (reserved):
-5.12 V (min = -0.00 V, max = -0.00 V)
CPU Fan: 11637 RPM (min = 1997 RPM, div = 4) <------------- this is double what it really is
Chassis Fan:
12500 RPM (min = 3994 RPM, div = 2) <------------- this is double what it really is
Power Fan:3994 RPM (min = 3994 RPM, div = 2) ALARM <---------------variable speed fan, 3000 sounds like a safer min
M/B Temp: +52°C (high = +0°C, hyst = +0°C)
CPU Temp (Intel):
+40°C (high = +45°C, hyst = +40°C)
Power Temp:
+127°C (high = +0°C, hyst = +0°C)
CPU Temp (AMD):
+25°C (high = +80°C, hyst = +75°C)
vid: +1.650 V
alarms:


MB and CPU temp are swapped, and went to change options for that too, but its not responding to my changes in the .conf file

You can add those lines to rc.sysinit. I suggest if you want to do that, put them at the bottom and put comment
lines (starting with #) to say you did it and when, for future reference, for you'll probably end up taking them out again!

I put them in, and did the other thing, and it didn't get lm_sensors to work. Only after I REMOVED all that stuff did they work--more or less. (The temperature and fan part work beautifully, but the voltages are all screwed up and give alarms every second, and I cannot figure out how to fix this.)

Works without having that stuff in either, but the changes i made in the config arent reflected in sensors. :(

Tried 2.8.8 version, it didnt work, so reverted back to 2.8.4

Do you have gkrellm (or other graphic front-end) installed? lm_sensors reads the values from the sensor chips, but having a graphical program (gkrellm) to display and configure the output makes things much easier.

Let us know how 2.8.4 goes... I'm very interested that you mentioned the changes you made in the conf file are not reflected in the sensors. I made all sorts of changes in the conf file and it made ABSOLUTELY NO DIFFERENCE either. That seems really odd.

And I even ran sensors -s after making the changes, as the lm_sensors website instructs to do when you change the conf file, and then I ran "sensor" twice separated by five seconds, as they also instruct to do. (I got this information by reading responses to some trouble tickets.)

OK, I started to wonder if the sensors.conf file was even making any impact, so I renamed it and then replaced it with an empty (0 bytes) file named sensors.conf.

It made no difference to my readings at all. The temperatures and fan speeds are still fine, and the voltages still bogus.

So I filed a trouble ticket at the lm_sensors site.

Problem solved!
 

The support persons at lm_sensors had me supply the complete sensors.conf file along with system data, and found that the "set" lines given in the via686a chip voltage section in the default file didn't work for my system. They promptly sent along lines to replace the default lines with, along with several additional ones; once I did that and ran sensors -s and then sensors, lm_sensors was doing its job correctly. No more alarms, no obviously messed-up voltage values, and I can once again display temperature and fan speed in gkrellm as I wanted to.

In the course of the investigation, they asked me to replace the Mandrake package with an 8.7 or later version from lm_sensors, which I did, but that in itself didn't fix the problem.

Very pleased by the clear instructions and speedy response I received from lm_sensors support!

If you suspect you have a similar problem, or would be interested in the troubleshooting procedures followed, the trouble-ticket thread can be read at:

http://archives.andrew.net.au/lm-sensors/msg28463.html

An update, about how easier it is now to install lm_sensors

In lm_sensors 2.9.0 (mandrake 10.2 / mandriva LE2005 rpm), no need to do the cut and paste to do the
modprobe of modules; this is done automatically via /etc/rc.d/lm_sensors
(the doc tells you that but it is not easy to find)
All sort of modules are tested and give a confidence out of 10,
but then some are chosen.

If you then type sensors -s - c /etc/sensors.conf
a module name will appear just before or after the temperatures (say sb100)
This is the one module used, for which its section in /etc/sensors.conf
will need tweaking.
The section starts with the name of the module you have identified (for example sb100)

In the A7N8X-E deluxe the fan speed needs dividing by 2. (@/2,@*2)
The mobo and processor T are inverted (change the input number)
You need to add ignore in places for the AMD or intel cpu,
and ignore some other input if they are not used. (use ignore statement)

NB: I boot with option acpi=ht
if you have a problem with procfs/sysfs, maybe look into acpi option
(a shot in the dark because I think lm_sensors doe not need acpi anyway)

LM Sensors Help, Can't access procfs/sysfs file Unable to find i2c bus information
 

Can you provide with the sensors.conf file which helped you figure out what was missing? That could help me make changes in my file and get it working.