MandrivaThis Forum is for the discussion of Mandriva (Mandrake) 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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to monitor my CPU and motherboard temperature, i had installed lm_sensors and i2c with Mandrake Linux 10 but i formatted and installed 10.1
Now...
Is i2c integrated to kernel on MDK 10.1?
What do i need and in what order do i have to install them if i want to monitor my PC temperature?
Is there rpm packs for these? (i don't really like compiling the source.. )
Getting lm_sensors to work can be tricky and time-consuming. I finally got them to work but it took a lot of inquiry, more patience than I usually have, and help from the lm_sensors people themselves (who are VERY helpful and respond very fast to queries).
Do a search on LQ for various threads describing obstacles and solutions, and you may find what you need already here.
As a last resort, you can file a trouble ticket with lm_sensors (Google will quickly show you where to go) with a detailed description of your problem(s), and they will help you.
Originally posted by Padma Fow what it's worth, when I installed 10.1, I just installed the lm_sensors module from urpmi, ran "sensors-detect", and voila!
I'd say, from my experience and what I've found through Googl'ing and here on LQ, that you're one very lucky Linux user!
The biggest problem is usually to get the reported temperature/voltages reported by
sensors to match the ones BIOS reports.
Depending on your MB you might have to search the net for proper values to add to /etc/sensors.conf
For users of Via MB's sometimes replacing i2c-viapro with i2c-via (or vice versa) does the trick if things
aren't working (at least on my GA-6VXC7-4X).
Strangly what gkrellm sees is different from what "sensors" reports, because of preset multipliers.
You can look at the results of "sensors" and dial down gkrellm until it corresponds.
Having to manually set up the formula can be a pain though.
I never would have got it right myself. A very kind member of the lm_sensors team wrote a section for my file for me, after seeing my results, and it worked.
This was under 10.1. Under 9.2, I was able with some finagling to get lm_sensors to work properly. Something (probably the kernel, since it went from 2.4x to 2.6x) changed that screwed up the available lm_sensors packages in relation to my motherboard/chipset(s).
Go there, look at the FAQ's, documentation, etc. and see if there's already a solution for your situation, and if need be, file a trouble ticket. They will require as much information as possible so they can see where the problem lies. As I recall, there's an outline of what's needed when you file the trouble report. Usually the trouble comes from the fact that it's impossible for them (or anybody!) to inspect and test all the combinations of chips and motherboards that exist, and what works for something similar to yours or mine may not work at all, or only work part way, for our specific setups. That's where their help can come in handy--plus they may be able to expand their database for future users.
I hope this procedure works for you; it's what I did.
You can always take the .conf file that came with the lm_sensors package and install it in place of the one you've messed with to see if it's better, worse, or about the same. Chances are, though, that some of the values in it, as well as in the one you're using, are just way off for the particular setup you have. After viewing all my results from scanning, my .conf file, etc., etc., the lm_sensors developer wasn't sure what was causing it to be wrong, but he knew how to fix it anyway! It required a whole different set of voltage values in the .conf file.
After I got proper readings from the corrected file, they asked me to come back here and report on the success, which I did.
I recently had a very major system crash (caused by deleting some essential libraries by accident) and had to completely reinstall Mdk 10.1 and set up lm_sensors again. After that, I was getting alarms going off so often it was slowing down the system noticeably due to all the alarm messages writing to disk. Luckily I still had the .conf file lm_sensors had sent me, and installed it--no more alarms.
Just one more example of the importance of backups.
how to understand what's needed by means of modules for my board? for proper lm_sensors functioning? I have GB GA-7N400L MCP Nforce2 with AMD athlon XP 266Mhz @ 300Mhz
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.