LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kima, KDE 3.5.8, , hddtemp, Slack 12.1 (https://www.linuxquestions.org/questions/slackware-14/kima-kde-3-5-8-hddtemp-slack-12-1-a-608936/)

Woodsman 12-24-2007 02:42 PM

Kima, KDE 3.5.8, , hddtemp, Slack 12.1
 
I've been testing Slackware Current (12.1). I'm unable to get Kima (0.7.4) to display the hard drive temperature from hddtemp.

Everything works fine in Slackware 12.0.

In 12.1 hddtemp starts and displays the temperature just fine from the command line.

In 12.1 Kima finds and displays all other motherboard sensors from lmsensors.

Any thoughts about where to troubleshoot?

bsdunix 12-24-2007 04:06 PM

Quote:

I'm unable to get Kima (0.7.4) to display the hard drive temperature from hddtemp.
How about this?

the termal sensors provided by hddtemp daemon (make sure hddtemp runs on 127.0.0.1 port 7634 before kima starts)
http://kima.sourceforge.net/

Woodsman 12-24-2007 04:32 PM

Thanks. I'm running in daemon mode and the default port is 7634 --- so there wasn't much to check. :)

Edit: Well, I'm assuming hddtemp is running on port 7634 only because that is the default and I specified nothing different. Is there a way to verify the actual port?

Edit 2: I ran gkrellm and the hddtemp displayed fine there too. When I ran gkrellm in 12.1, nothing displayed. I booted 12.1 with the huge kernel in case I incorrectly recompiled my kernel, but nothing there either. Perhaps I need to recompile hddtemp?

Woodsman 12-24-2007 07:23 PM

Update: I tested gkrellm in Xfce and had the same results. Regardless of whether I use the hddtemp plugin or hda built-in monitor, no temperature appears in gkrellm. I also recompiled hddtemp within 12.1 to no avail. So the problem is not kima or hddtemp but something more fundamental.

Which options should I check in the kernel?

bsdunix 12-24-2007 10:30 PM

Quote:

Which options should I check in the kernel?
lm_sensors on 2.6.x kernels
http://www.lm-sensors.org/wiki/Kernel2.6

What Pat used as the kernel configurations for Slack 12.0:

http://slackware.mirrors.tds.net/pub...neric-2.6.21.5
http://slackware.mirrors.tds.net/pub...p-2.6.21.5-smp

Quote:

I've been testing Slackware Current (12.1). I'm unable to get Kima (0.7.4) to display the hard drive temperature from hddtemp.
Everything works fine in Slackware 12.0.
Compare the device permissions/ownership between Slack 12.0 and Current to see any differences.
Code:

89 char        I2C bus interface
                  0 = /dev/i2c-0        First I2C adapter
                  1 = /dev/i2c-1        Second I2C adapter
                    ...

Are you using the current hddtemp.db file for both Slack 12.0 and Current?
http://download.savannah.nongnu.org/...emp/hddtemp.db

Woodsman 12-25-2007 12:43 PM

Thanks for the response.

I'm using lmsensors 2.10.3. Should be no problem there. As I shared earlier, both kima and gkrellm have no problem finding hwmon sensor data. The only data neither can find is hda temps, although hddtemp works fine from the command line.

Running lsmod shows that the i2c modules are running, which makes sense because gkrellm and kima show that data.

However, in my kernel config I found most of the I2C Hardware Sensors Chip support not selected. I don't know whether that makes a difference on these old boxes and I think I had a minimal selection under 2.6.21.5 too. There is a note on the lmsensors page that sysfs support changed in 2.6.22, but my config file seems okay.

Regarding Pat's kernel config files, I don't think he compiles any specific i2c or lmsensors support. Possibly in huge he does, I don't know at the moment. I recall the first time I tried to install lmsensors I had to recompile the kernel to support that.

Device permissions are the same between both versions.

The hddtemp.db is current.

I'll have to wait until next weekend to recompile the kernel with all hardware sensor chips configured. On the other hand, does lmsensors play a role in requesting hda temperature? I thought that was all done through SMART. If that is the case, then recompiling likely will produce no different result.

bsdunix 12-26-2007 12:01 PM

I'm able to use Kima without problem on both Slack 12.0 and Current. I didn't recomple the kernel, just used the default installed kernel.
Code:

# cp hddtemp.db /usr/share/misc
# cd hddtemp-0.3-beta15
# ./configure && make && make install
# cd ../kima-0.7.4
# ./configure && make && make install
# echo "/usr/local/sbin/hddtemp -d /dev/hda -l 127.0.0.1" >> /etc/rc.d/rc.local
# /etc/rc.d/rc.local <- To start hddtemp in daemon mode
# netstat -ln | grep 7634 <- To verify hddtemp is running
tcp        0      0 127.0.0.1:7634    0.0.0.0:*    LISTEN
$ startx

I then added the Kima applet to the KDE panel and saw HDDTemp0 with hard drive temperature.

I did a clean Current install (no upgrade from 12.0) so don't know if that had anything to do with it.

Woodsman 12-29-2007 09:22 PM

Problem Solved
 
bsdunix provided me the hint I needed. In my Current partitions I had no network services enabled. The problem was caused by not executing rc.inet1. To be precise, the problem was caused because lo was not configured, which normally is performed in rc.inet1. I tested keeping all of my rc.d network scripts disabled and manually ran ifconfig lo 127.0.0.1 and then kima and gkrellm correctly displayed the hard drive temperature.

So in my rc.local I added the following just after running hddtemp in daemon mode:

# ensure kima (kde) and gkrellm can find hddtemp
if [ ! -x /etc/rc.d/rc.inet1]; then
ifconfig lo 127.0.0.1
fi

Thanks everybody for helping!


All times are GMT -5. The time now is 12:10 PM.