I installed my first program ever not using a manager (I'm a Linux novice). I downloaded KSensors 0.7.3 onto my desktop.I extracted the files.I brought up a terminal, went into the KSensors directory and ran the configure file. It ran just fine.I typed in make. It went just fine.I typed in make install. It went fine too.I typed in make clean. No problem.I looked for a KSensors program. Nothing.In the install text it says that the files are usually installed in the /usr/local/bin and /usr/local/man. They aren't. I searched for KSensor* files on the entire hard drive and came upon a bunch that were marked inaccessible, but none of them looked liked the main program.Any help would be appreciated. Thank you.

./configure --prefix=/usrThat way binaries will go into /usr/bin/ , images / sound files into /usr/share/ etc. If you don't specify a prefix, most programs assume that the prefix = /usr/local, so the most logical place to look would be /usr/local/bin. for kde programs, VL uses --prefix=/opt/kde

checkinstall -LThis will create a .tlz vector package that you can easily install and remove. It won't exactly be repo ready but it works great. Also, you'll be able to search for the binary in the package info file:

grep bin/ /var/log/packages/ksensors-0.7.3"make clean" just cleans the building directory. The best way to get a clean building directory is to remove the thing and extract the tarball again. It's not needed after installing something.

Try searching for ksensor instead (no capitals!), that should find you something. Also, if you're using slocate make sure you run "updatedb" first, as files that are newly installed are not in the database yet.

I tried checkinstall and I kept getting told that it didn't exist. So I Googled around and discovered that for make install or checkinstall you have to be in root mode (told ya I was a novice ). So I used su to get into root mode and then ran checkinstall -L.Everything seemed to work as there is now a ksensors executable program in usr/bin, except it doesn't do anything. When I first double clicked it and it started to show up on the taskbar, but then vanished, and when I've tried double clicking it anytime afterwards, nothing happens. I tried logging into root mode and and add write permission to the group (group only had read permission) but that didn't make any difference. I even tried running it from a terminal, but that doesn't work. It doesn't give an error message or anything.Well, at any rate it's 2:31 in the morning here, so I'm off to bed. I can try to play around with it some more tomorrow.Thank you for your help.

./configure --prefix=/usrThat way binaries will go into /usr/bin/ , images / sound files into /usr/share/ etc. If you don't specify a prefix, most programs assume that the prefix = /usr/local, so the most logical place to look would be /usr/local/bin. for kde programs, VL uses --prefix=/opt/kde

checkinstall -LThis will create a .tlz vector package that you can easily install and remove. It won't exactly be repo ready but it works great. Also, you'll be able to search for the binary in the package info file:

grep bin/ /var/log/packages/ksensors-0.7.3"make clean" just cleans the building directory. The best way to get a clean building directory is to remove the thing and extract the tarball again. It's not needed after installing something.

Try searching for ksensor instead (no capitals!), that should find you something. Also, if you're using slocate make sure you run "updatedb" first, as files that are newly installed are not in the database yet.

The most recent version of KSensors is three years old, so I would be inclined to try something different, such as GKrellm (which is in the repos) or SuperKaramba.

Out of curiosity I just downloaded SuperKaramba, and it built and installed with no issues at all on my VL5.8-SOHO system, and added a KDE menu entry in the right place. When I've got a moment I'll package it up for the repos.

The most recent version of KSensors is three years old, so I would be inclined to try something different

Another option is conky, which is in the testing repository.Although it might need a bit of tweaking and has some issues with drawing directly to the root window in KDE.It works fine if you keep it in its own window, though.

You might need to install lm_sensors for it to show temperatures, voltages and whatever else.

(I'll be uploading a new conky package soon, that already contains a customized preferences file).

EDIT: I've just checked, and ksensors is actually a frontend to lm_sensors... Do you have lm_sensors installed?Maybe that is why it isn't working...

roseway, I have GKrellm but it doesn't seem to do what I want, which is show the temp of the CPU. A few days ago on my VL computer I put in a new CPU and I just want to make sure that the fan and heatsink from my old CPU are adaquite. The computer seems to be running OK, but I just want to be sure.wcs, thank you, but when I tried to look up conky in gslapt, but it doesn't come up. And yes, I already have lm_sensors installed.

You have to set up lm_sensors before any of these utilities will display temperatures and fan speeds.

As root, type 'sensors-detect' (without the quotes). The script asks you several questions, to which you can generally just hit Enter to give the default response.At the end of the process, the script will display a list of relevant commands, and ask if you want it to add these commands to your startup scripts. Answer Yes.Now reboot and run GKrellm again; right-click on it and select 'Configuration'. In the 'Builtins' section you should now be able to set up the sensors you want.

Well, I tried it and it didn't work. So I tried running lm_sensors and was told that it couldn't find any sensors. So either I didn't quiet do things right, or else it's the motherboard itself that's the problem.I'm leaning towards the motherboard because when I tried installing a program called Motherboard Monitor (A Windows program, I have Wine installed) I had to stop installation when I saw that my specific motherboard (msi 6191) wasn't on the list of supported motherboards.Anyway, the computer has been running fine since the cpu upgrade so I'm fairly sure that the cpu isn't overheating. Thank you all for your help.

You have to set up lm_sensors before any of these utilities will display temperatures and fan speeds.

As root, type 'sensors-detect' (without the quotes). The script asks you several questions, to which you can generally just hit Enter to give the default response.At the end of the process, the script will display a list of relevant commands, and ask if you want it to add these commands to your startup scripts. Answer Yes.Now reboot and run GKrellm again; right-click on it and select 'Configuration'. In the 'Builtins' section you should now be able to set up the sensors you want.

What was the output from sensors-detect? Did it actually detect any sensors after your "Yes" responses?If so, I would say the problem has to do with the loading of the required modules and not with the motherboard.

Given that fact and the fact that WinXP software couldn't detect any either I'd say there is a 95% chance that mobo has no sensor chip, it is not working, or is so weird that it is not detected. I'd say you are out of luck. Most modern BIOSes have a diagnostic page that shows CPU temperature and PS voltages. I would get into your BIOS setup and see if it has such a page and if there is any data there.

Logged

"As people become more intelligent they care less for preachers and more for teachers". Robert G. Ingersoll