Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm using lm_sensors-2.10.0-3.1 on RHEL5 with kernel 2.6.18-8.1.8.el5.
I've run sensors-detect and taken the actions it says. The modules it recommends seem to be loaded. But running sensors -s gives me:
[root@vera ~]# sensors -s
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Many people have reported this error, and they say it is related to i2c modules being loaded in the wrong order. I can't seem to find the right order. Has anyone gotten lm_sensors to work on this motherboard?
That would have been useful info, thanks. I did end up going to a 2.6.21 kernel, which fixed everything. And with the temp readings and lots of testing, I determined that the mobo had bad RAM slots. So I returned it and got the newer GA-P35-DS3, on which the sensors also work just fine.
The CPU temp is the same on this board, but the other temp (I guess it's the north bridge?) is a good bit higher than on the 965P-DS3.
The remaining nagging but noncritical issue is getting the reported voltages into a meaningful format. The lm_sensors sensors.conf file has a stanza on how to massage the raw readings for the older ITE8712 chip, but not my ITE8718 chip, and what works for the 12 isn't working for the 18. I put in an email to Gigabyte, but I have little hope they'll take the time to get me the info. I think it involves more than just multipliers, maybe voltage additions or subtractions too. So far, I haven't found anyone on the web with the same issue.
Nice board though. Tons of USB and SATA ports, 1333Mhz FSB, and lots of overclock controls in the BIOS.
That would have been useful info, thanks. I did end up going to a 2.6.21 kernel, which fixed everything. And with the temp readings and lots of testing, I determined that the mobo had bad RAM slots. So I returned it and got the newer GA-P35-DS3, on which the sensors also work just fine.
The CPU temp is the same on this board, but the other temp (I guess it's the north bridge?) is a good bit higher than on the 965P-DS3.
The remaining nagging but noncritical issue is getting the reported voltages into a meaningful format. The lm_sensors sensors.conf file has a stanza on how to massage the raw readings for the older ITE8712 chip, but not my ITE8718 chip, and what works for the 12 isn't working for the 18. I put in an email to Gigabyte, but I have little hope they'll take the time to get me the info. I think it involves more than just multipliers, maybe voltage additions or subtractions too. So far, I haven't found anyone on the web with the same issue.
Nice board though. Tons of USB and SATA ports, 1333Mhz FSB, and lots of overclock controls in the BIOS.
Hi you might want to send an email to lm-sensors@lm-sensors.org the lm-sensors mailing list they seem very helpful, I have been reading it months now ever since I needed it for my old board and never seen any go away puny user posts that some technical lists have. So give it a shot oh and I forget if I had to register to be able to post so you might want to go to http://lm-sensors.org first to check.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.