[spiff72]

Hello all,

I don't know if this qualifies as a Tiger support thread, but I just want to know if a feature is included...

I want to know if programs like Temperature Monitor can get temperture updates for the "non-refreshing sensors". Currently the temperature stays the same, never updating from what the temperature was at boot.

Thanks,
Jeff

[galarneau]

I've used Tiger 8a425, and Temperature Monitor Lite works just fine.

I've also had a look into the ioreg -l output, and you can get the info from there as well as the current fan speeds (This is on a 15" PB 1.5GHz)

What model PowerBook do you have?

[spiff72]

Originally Posted by galarneau

I've used Tiger 8a425, and Temperature Monitor Lite works just fine.

I've also had a look into the ioreg -l output, and you can get the info from there as well as the current fan speeds (This is on a 15" PB 1.5GHz)

What model PowerBook do you have?

Is yours a Rev C or D?

See my (now updated) Signature...

But it is a brand new Rev D 17" 1.67 GHz. When I run Temperature Monitor, it shows a warning about the fact that it detected non-refreshing sensors (everything but the SMART HD sensor). The temperatures stay constant.

This is an issue with the current Powerbooks, from what I understand.

This is a link to the FAQ for the Temperature Monitor software (notice the first item about supported hardware)...

http://www.bresink.de/osx/DocsHardwareMonitor/faq.html

Thanks,
Jeff

[galarneau]

Mine is the last rev (i.e. not the one with the scrolling trackpad, etc).

I don't have access to a new machine, but try this out in the terminal:

ioreg -l | grep -A 6 "IOHWSensor" | grep -A 4 "current-value"

You'll get a bunch of data. Where it says "current value", take that number and divide it by 65536 to get the temperature or fan speed.

Next time I go to the Apple Store I'll give it a shot and see if the values change while the machine is running.

[spiff72]

Here is the output I got:


Last login: Sun Apr 17 17:43:41 on ttyp1
Welcome to Darwin!
XXXXXXXXXXXXXXXX$ ioreg -l | grep -A 6 "IOHWSensor" | grep -A 4 "current-value"
| | | | | "current-value" = 3112960
| | | | | "CFBundleIdentifier" = "com.apple.driver.AppleHWS$
| | | | | "zone" = <00000000>
--
| | | | | +-o IOHWSensor <class IOHWSensor, registered, matched,$
--
| | | | | "current-value" = 3014656
| | | | | "CFBundleIdentifier" = "com.apple.driver.AppleHWS$
| | | | | "zone" = <00000000>
--
| | | | | +-o IOHWSensor <class IOHWSensor, registered, matched,$
--
| | | | | "current-value" = 2899968
| | | | | "CFBundleIdentifier" = "com.apple.driver.AppleHWS$
| | | | | "zone" = <00000000>
--
| | | | | +-o IOHWSensor <class IOHWSensor, registered, matched,$
--
| | | | | "current-value" = 64732
| | | | | "polling-period" = 5
| | | | | "location" = "CPU CORE"
| | | | | "type" = "voltage"
| | | | | "polling-period-ns" = 18446744073709551615
--
| | | | | "current-value" = 0
| | | | | "polling-period" = 5
| | | | | "location" = "REAR LEFT EXHAUST"
| | | | | "type" = "fanspeed"
| | | | | "polling-period-ns" = 18446744073709551615
--
| | | | "current-value" = 0
| | | | "polling-period" = 5
| | | | "location" = "REAR RIGHT EXHAUST"
| | | | "type" = "fanspeed"
| | | | "polling-period-ns" = 18446744073709551615
--
| | | | "current-value" = 2293760
| | | | "CFBundleIdentifier" = "com.apple.driver.AppleHWS$
| | | | "zone" = <00000000>
--
| | | | | | | +-o IOHWSensor <class IOHWSensor, registered, matc$
--
| | | | | | | "current-value" = 2162688
| | | | | | | "CFBundleIdentifier" = "com.apple.driver.Appl$
| | | | | | | "zone" = <00000000>
--
| | | | | | +-o IOHWSensor <class IOHWSensor, registered, matc$
--
| | | | | | "current-value" = 0
| | | | | | "polling-period" = 1
| | | | | | "location" = "BATT-CURRENT"
| | | | | | "type" = "current"
| | | | | | "polling-period-ns" = 18446744073709551615


I was plugged in at the time, so battery current should be zero, I assume. The other values that don't show labels are the temps that don't change, I think. Those numbers didn't change between runs of the ioreg command. The fan speeds appear to be zero, and I think that might be right, since I have only heard them come on once (when the processor was loaded to 100% for a period of several minutes...

Thanks,
Jeff

[galarneau]

Hmm... the ioreg structure might be a little bit different in Tiger (which is what I was using when I came up with the command I gave you).

Here's the output from my PowerBook:


jagBook:~> ioreg -l | grep -A 6 "IOHWSensor" | grep -A 4 "current-value"
| | | | "current-value" = 3309568
| | | | "low-threshold" = 0
| | | | "location" = "CPU/INTREPID BOTTOMSIDE"
--
| | | | "IOClass" = "IOHWSensor"
--
| | | | "current-value" = 3194880
| | | | "low-threshold" = 0
| | | | "location" = "CPU BOTTOMSIDE"
--
| | | | "IOClass" = "IOHWSensor"
--
| | | | "current-value" = 3604480
| | | | "low-threshold" = 0
| | | | "location" = "PWR SUPPLY BOTTOMSIDE"
--
| | | | "IOClass" = "IOHWSensor"
--
| | | | "current-value" = 64800
| | | | "location" = "CPU CORE"
| | | | "type" = "voltage"
--
| | | | "IOClass" = "IOHWSensor"
--
| | | | "current-value" = 0
| | | | "location" = "REAR LEFT EXHAUST"
| | | | "type" = "fanspeed"
--
| | | | "IOClass" = "IOHWSensor"
--
| | | "current-value" = 0
| | | "location" = "REAR RIGHT EXHAUST"
| | | "type" = "fanspeed"
--
| | | "IOClass" = "IOHWSensor"
--
| | | | | "current-value" = 2228224
| | | | | "low-threshold" = 0
| | | | | "location" = "BATTERY"
--
| | | | | "IOClass" = "IOHWSensor"


But anyway, even with your results, you can see that those are temperature values. The first one (3112960) when divided by 65536 gives you 47.5, which is the temperature in degrees Celsius.

Try loading up a process that will peg your CPU at 100% for a few minutes (maybe an md5 checksum of a large file or a video encode) just to be sure the values aren't changing. I'd be surprised it your processor was a 47.5 degrees when you first turned the machine on. Mine is usually in the 20's.

[spiff72]

Those readings are from a reboot, so it wasn't like the computer was shut off all nite when I turned it on. I don't know when in the boot process the temperature gets "locked in". I have seen the temp as low as the 100's (F).

I just hoped that Tiger might fix this issue...

I guess we will have to wait until I get my upgrade :-)

Thanks,
Jeff

[spiff72]

Update:

The temp readouts are DEFINITELY from boot time...

I just powered up after my PB was powered down overnight, and the readings were just slightly higher than room temp (about 77 deg F). I have messed around with the energy saver settings and forced it to highest performance while plugged in, and it got very warm. I rebooted, and the temps were about 130F.

I really wish these sensors would update in real time like the older PB's. I find the temp info very useful while I use the computer.

Again, I hope that Tiger fixes this, but I am not holding my breath. Does anyone out there with Tiger have a Rev D powerbook?? I just want to know if temp monitor ever updates the readings as you work.

Thanks,
Jeff