"Moo" = Right fan repeatedly spinning up and down under certain conditions

I am pretty certain I have figured out what is causing the "moo". Here is my theory based on a couple of weeks of experimentation...
It is the right fan starting up and stopping. Again..and again...and again. It does this in response to temperature changes. But the threshold is too sensitive so what happens is an increase in temperature triggers the fan, the fan winds up and in so doing after a couple of seconds this immediately drops the temperature below the threshold and so the fan winds down. The temperature now builds and after a couple of seconds the fan spins up again. It will keep doing this until either activity falls so that the temperature stays below threshold or continuos activity ensures the temperature stays high enough to keep the fan on at low speed (when it is generally quiet unless there is a heavy load).
I will guess the cause is probably a faulty sensor, faulty fan or most likely faulty fan control logic since this is clearly happening with a lot of MBPs. If it is the latter then presumably they need only change the firmware controlling the fan to make it start slower and stay on longer.
Why doesn't everyone hear it?
a. Like most fan type noises they are only apparent in a quiet room - as most people work in rooms full of white noise they simply will not hear it even if it happens.
b. Some people have better hearing and are more sensitive to noise.
c. It needs the right set of hardware and sofware activities to trigger the problem...............
In my particular case I typically have my 2.0ghz MBP connected to an external monitor, ethernet and external USB mouse on the right side of the MBP. When I am using the MBP standalone (ie without more heat being generated) the noise does not occur as often, presumably because when idling less heat is generated.
As you change what you are doing with the machine (not sure if its CPU or Video related changes that matter most) the noise will start or stop happening. Doing absolutely nothing typically means the noise does not happen so often, but then again it can be sitting doing nothing and it will start happening. Doing a bit means (say 10-30% CPU) means it will make a noise , doing a moderate amount (say above 40% CPU) means it does not happen because the temperature stays high and the fan stays on - generally being quiet at low speed. If you push the machine (say 80% CPU) then a louder fan noise is noticeable. I have also found that opening/closing the lid (when using an external monitor) makes a difference, the surface it is on makes a difference and the room temperature probably does as well.
A good way to experience this is to start Garageband recording the noise when it happens since the additional load stops the noise. The spin up/down cycle will continue for 4 or 5 cycles as you record the noise but then the fan remains on very low speed as a new higher thermal equilibrium is achieved.
For reference I am on my 2nd MBP (the first also had this problem but it was less noticeable) and have experienced most the other noises:
a. Left Fan always runs on both machines
b. Screen buzz when not on full brightness on 1st MBP not in on 2nd.
c. CPU whine was not on 1st MPB but it is on the 2nd - but only at low level and only if running on battery power.
I have a couple of other irritating problems:
d. Screen dims after 2 minutes regardless of power setting etc.
e. Fit of 1st MBP was great, 2nd not so good.
Personally I find the fan spinup/down noise very very annoying, far more so than the left fan always being on. I really do need Apple to fix it, but I dont see the point of sending the machine in unless they recognize the problem and have a systemic solution since clearly this is common problem. Otherwise the chances are a tech will plug it in standalone in a noisy repair shop, hear nothing and either do nothing or never know if its fixed or not. So far no intelligent response from Applecare......If I can figure this Apple ought to be able to and get a fix.
And no I would not recommend buying a MBP until this problem is fixed if you are at all sensitive to noise and work somewhere quiet - because it appears to be a gamble as to whether you will get a quiet MBP or not. That's a shame since otherwise its a very slick machine.

I agree with u; however:
-The left fan that's always on is the Hard Drive - listen to the hard drive to the left of the trackpad and you'll realize that it is coming from there.
-My "moo" sound comes from my LEFT fan. So if it's a firmware issue, why would the side of the fan affected by the problem varry? this leads me to the worrying assumption that it is a hardware issue...If this is the case, who knows if apple will even cover it under warranty if it doesn't affect the performance of the system...

Similar Messages

Reference t osegments and displaying under certain condition

I'm trying to understand how conditions are working for DMEE tree. According to this [condition and argument description|http://help.sap.com/saphelp_47x200/helpdata/en/aa/62683864b47345e10000009b38f8cf/frameset.htm] I can't understand how these conditions are working when I'm dealing with reference id.
Lets imagine following example:
1) We have two levels
All tree has following structure:
ROOT
|- SEGM_GROUP_1, level 1, reference id REF_1
|--- ELEMENT_1_1, ouput for this node is "out_1_1"
|--- ELEMENT_1_2 output for this node is "out_1_2"
|--- SEGM_GROUP_2, level 2, reference id REF_2
|------ ELEMENT_2_1 output for this node is "out_2_1"
|------ ELEMENT_2_2 output for this node is "out_2_2"
|------ ELEMENT_2_3 outputs loop number e.g. 'loop no. 1"
How to set up conditions, using reference id to achieve following output?
out_1_1
out_2_1 loop no. 1
out_2_2 loop no. 1
out_2_1 loop no. 2
out_2_2 loop no. 2
out_1_2
What is interesting me is case when I put in condition reference id e.g. REF_1. What should I put in arg1-1? What is then a meaning of this value? Is it level? Is it number of occurrences? Is it something else?

This question is expired

Hard drive constantly spinning up and down when asleep

Hi all,
I have a problem with an external USB 2.0 hard drive connected to my Mac mini (late 2012).
When I put the computer to sleep the drive spins up to speed, stops, then immediately starts to spin up again. This goes on and on.
I understand that drives will periodically spin up when asleep for spotlight indexing etc. However this seems like strange behaviour, it just repeats spinning up and down in an endless cycle.
I have had the drive for a while now, as my time machine backup. Interestingly this problem only started after I rearranged my desk when I set up a second monitor. I have a USB 3.0 drive (my scratch disk) that behaves normally.
I have drives set to not sleep in preferences.
I have searched around but can only find posts about people not wanting to wait for drives to spin up when they open finder etc.
What do you think? Could the drive be on its way out? It is a Samsung spinpoint f3 1tb in an Iomega enclosure, for information...
I appreciate any help,
Cheers,
Mike

Hi BDAqua,
I should have noticed this earlier but it appears the problem is with the mini waking from sleep and thus causing the drives to wake.
When I put the mini top sleep (without the external drives powered on) it constantly wakes and sleeps. The displays dont come back on (untiul you click the mouse or hit a key etc.) but you can hear the internal drive spin up and the sleep light comes on, then goes back to blinking until it wakes again.
I have realised that it must be due to the second monitor that I have connected via the mini display port. It is connected using a mini display port to hdmi cable I bought from play.com. Something to do with the display and thunderbolt is casuing the sleep function to misbehave, I think.
Here is the console log that was created after sleeping the mini, allowing it to go through its weird sleep/wake cycle then fully waking it up again.
Hope that makes sense, it is late and I am tired!
Thanks for all your help.
Mike
21/05/2013 23:30:16.840 loginwindow[42]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
21/05/2013 23:30:16.000 kernel[0]: HID tickle 43809 ms
21/05/2013 23:30:18.747 WindowServer[93]: Created shield window 0xc1 for display 0x003f003f
21/05/2013 23:30:18.747 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:30:18.752 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:30:18.766 WindowServer[93]: Created shield window 0xc2 for display 0x003f003d
21/05/2013 23:30:18.766 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:30:18.784 airportd[1018]: _doAutoJoin: Already associated to “ASUS60”. Bailing on auto-join.
21/05/2013 23:30:19.169 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:30:19.206 loginwindow[42]: resume called when there was already a timer
21/05/2013 23:30:19.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:30:58.348 com.apple.backupd-helper[1028]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.
21/05/2013 23:31:02.141 WindowServer[93]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
21/05/2013 23:31:02.142 loginwindow[42]: find_shared_window: WID -1
21/05/2013 23:31:02.142 loginwindow[42]: CGSGetWindowTags: Invalid window 0xffffffff
21/05/2013 23:31:02.142 loginwindow[42]: find_shared_window: WID -1
21/05/2013 23:31:02.142 loginwindow[42]: CGSSetWindowTags: Invalid window 0xffffffff
21/05/2013 23:31:02.307 WindowServer[93]: Created shield window 0xc8 for display 0x78c8d2fe
21/05/2013 23:31:02.311 WindowServer[93]: Created shield window 0xc9 for display 0x78c8d1b0
21/05/2013 23:31:02.311 WindowServer[93]: device_generate_desktop_screenshot: authw 0x7fd5b9025b30(2000), shield 0x7fd5b3105bb0(2001)
21/05/2013 23:31:02.352 com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fc0e5906240> Tue May 21 23:42:48 2013 BST (approx)
21/05/2013 23:31:02.352 com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fc0e5906240> Tue May 21 23:42:48 2013 BST (approx)
21/05/2013 23:31:02.370 WindowServer[93]: device_generate_desktop_screenshot: authw 0x7fd5b9025b30(2000), shield 0x7fd5b3105bb0(2001)
21/05/2013 23:31:02.389 WindowServer[93]: device_generate_lock_screen_screenshot: authw 0x7fd5b9025b30(2000), shield 0x7fd5b3105bb0(2001)
21/05/2013 23:31:02.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
21/05/2013 23:31:04.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:31:04.000 kernel[0]: LE is supported - Disable LE meta event
21/05/2013 23:31:04.000 kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
21/05/2013 23:31:04.000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
21/05/2013 23:31:04.000 kernel[0]: en1::IO80211Interface::postMessage bssid changed
21/05/2013 23:31:04.000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
21/05/2013 23:31:04.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
21/05/2013 23:31:10.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
21/05/2013 23:31:10.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
21/05/2013 23:31:10.000 kernel[0]: TBT W (2): 0x0010 [√]
21/05/2013 23:31:10.000 kernel[0]: Wake reason: EC.DarkPME (Maintenance)
21/05/2013 23:31:10.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
21/05/2013 23:31:10.000 kernel[0]: Previous Sleep Cause: 5
21/05/2013 23:31:10.000 kernel[0]: en1: 802.11d country code set to 'X3'.
21/05/2013 23:31:10.000 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
21/05/2013 23:31:10.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 1
21/05/2013 23:31:10.965 configd[18]: network changed: v4(en0-:192.168.1.190, en1-:192.168.1.47) DNS- Proxy- SMB
21/05/2013 23:31:11.549 hidd[46]: MultitouchHID: device bootloaded
21/05/2013 23:31:11.632 hidd[46]: MultitouchHID: device bootloaded
21/05/2013 23:31:11.000 kernel[0]: en1: 802.11d country code set to 'US'.
21/05/2013 23:31:11.000 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
21/05/2013 23:31:11.000 kernel[0]: MacAuthEvent en1   Auth result for: 10:bf:48:3e:02:74 MAC AUTH succeeded
21/05/2013 23:31:11.000 kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
21/05/2013 23:31:11.000 kernel[0]: AirPort: Link Up on en1
21/05/2013 23:31:11.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:31:11.000 kernel[0]: en1::IO80211Interface::postMessage bssid changed
21/05/2013 23:31:12.000 kernel[0]: en1: 802.11d country code set to 'GB'.
21/05/2013 23:31:12.000 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
21/05/2013 23:31:12.000 kernel[0]: Graphics suppressed 2116 ms
21/05/2013 23:31:12.000 kernel[0]: AirPort: RSN handshake complete on en1
21/05/2013 23:31:12.454 configd[18]: network changed: v4(en1+:192.168.1.47) DNS+ Proxy+ SMB
21/05/2013 23:31:12.466 UserEventAgent[11]: Captive: en1: Not probing 'ASUS60' (protected network)
21/05/2013 23:31:12.470 configd[18]: network changed: v4(en1!:192.168.1.47) DNS Proxy SMB
21/05/2013 23:31:12.895 airportd[1030]: _doAutoJoin: Already associated to “ASUS60”. Bailing on auto-join.
21/05/2013 23:31:12.915 airportd[1030]: _doAutoJoin: Already associated to “ASUS60”. Bailing on auto-join.
21/05/2013 23:31:13.000 kernel[0]: nd6_na_input: duplicate IP6 address fe80:0005::22c9:d0ff:fe8f:b1eb
21/05/2013 23:31:14.000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,2301,0de1,0300,c5e1,3800]
21/05/2013 23:31:14.757 configd[18]: network changed: v4(en0+:192.168.1.190, en1) DNS! Proxy! SMB
21/05/2013 23:31:14.776 mDNSResponder[39]: 78: Could not write data to clientPID[-1]() because of error - aborting connection
21/05/2013 23:31:14.779 mDNSResponder[39]: 78: DNSServiceGetAddrInfo      v4v6 39-courier.push.apple.com. PID[-1]()
21/05/2013 23:31:15.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
21/05/2013 23:31:16.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 1
21/05/2013 23:31:17.426 com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7fc0e3201de0> Tue May 21 23:42:48 2013 BST (approx)
21/05/2013 23:31:17.426 com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7fc0e3201de0> Tue May 21 23:42:48 2013 BST (approx)
21/05/2013 23:31:17.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
21/05/2013 23:31:17.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:31:17.000 kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
21/05/2013 23:31:17.000 kernel[0]: LE is supported - Disable LE meta event
21/05/2013 23:31:17.000 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
21/05/2013 23:31:17.000 kernel[0]: en1::IO80211Interface::postMessage bssid changed
21/05/2013 23:31:17.000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
21/05/2013 23:31:24.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
21/05/2013 23:31:24.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 1
21/05/2013 23:31:24.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
21/05/2013 23:31:24.000 kernel[0]: TBT W (2): 0x0010 [√]
21/05/2013 23:31:24.000 kernel[0]: Wake reason: EC.DarkPME (Maintenance)
21/05/2013 23:31:24.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
21/05/2013 23:31:24.000 kernel[0]: Previous Sleep Cause: 5
21/05/2013 23:31:24.006 configd[18]: network changed: v4(en0:192.168.1.190, en1-:192.168.1.47) DNS* Proxy SMB
21/05/2013 23:31:24.010 mDNSResponder[39]: DeregisterInterface: Frequent transitions for interface en1 (192.168.1.47)
21/05/2013 23:31:24.973 configd[18]: network changed: v4(en0-:192.168.1.190) DNS- Proxy- SMB
21/05/2013 23:31:24.978 mDNSResponder[39]: DeregisterInterface: Frequent transitions for interface en0 (192.168.1.190)
21/05/2013 23:31:25.269 hidd[46]: MultitouchHID: device bootloaded
21/05/2013 23:31:25.277 hidd[46]: MultitouchHID: device bootloaded
21/05/2013 23:31:26.000 kernel[0]: MacAuthEvent en1   Auth result for: 10:bf:48:3e:02:74 MAC AUTH succeeded
21/05/2013 23:31:26.000 kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
21/05/2013 23:31:26.000 kernel[0]: AirPort: Link Up on en1
21/05/2013 23:31:26.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:31:26.000 kernel[0]: en1::IO80211Interface::postMessage bssid changed
21/05/2013 23:31:26.000 kernel[0]: Graphics suppressed 2278 ms
21/05/2013 23:31:26.000 kernel[0]: AirPort: RSN handshake complete on en1
21/05/2013 23:31:26.580 configd[18]: network changed: v4(en1+:192.168.1.47) DNS+ Proxy+ SMB
21/05/2013 23:31:26.583 mDNSResponder[39]: mDNS_RegisterInterface: Frequent transitions for interface en1 (FE80:0000:0000:0000:22C9:D0FF:FE8F:B1EB)
21/05/2013 23:31:26.583 mDNSResponder[39]: mDNS_RegisterInterface: Frequent transitions for interface en1 (192.168.1.47)
21/05/2013 23:31:26.590 configd[18]: setting hostname to "mikemini"
21/05/2013 23:31:26.592 UserEventAgent[11]: Captive: en1: Not probing 'ASUS60' (protected network)
21/05/2013 23:31:26.596 configd[18]: network changed: v4(en1!:192.168.1.47) DNS Proxy SMB
21/05/2013 23:31:27.016 airportd[1030]: _doAutoJoin: Already associated to “ASUS60”. Bailing on auto-join.
21/05/2013 23:31:27.000 kernel[0]: nd6_na_input: duplicate IP6 address fe80:0005::22c9:d0ff:fe8f:b1eb
21/05/2013 23:31:28.000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0de1,0300,c5e1,3800]
21/05/2013 23:31:28.797 configd[18]: network changed: v4(en0+:192.168.1.190, en1) DNS! Proxy! SMB
21/05/2013 23:31:28.803 mDNSResponder[39]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:AA20:66FF:FE11:3086)
21/05/2013 23:31:28.803 mDNSResponder[39]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.1.190)
21/05/2013 23:31:28.816 mDNSResponder[39]: 78: Could not write data to clientPID[-1]() because of error - aborting connection
21/05/2013 23:31:28.819 mDNSResponder[39]: 78: DNSServiceGetAddrInfo      v4v6 13-courier.push.apple.com. PID[-1]()
21/05/2013 23:31:28.835 configd[18]: setting hostname to "MikeMini.local"
21/05/2013 23:31:30.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
21/05/2013 23:31:31.000 kernel[0]: IOThunderboltSwitch(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 1
21/05/2013 23:31:33.745 loginwindow[42]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
21/05/2013 23:31:33.000 kernel[0]: HID tickle 9738 ms
21/05/2013 23:31:35.674 WindowServer[93]: Created shield window 0xca for display 0x003f003f
21/05/2013 23:31:35.674 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:35.679 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:35.700 WindowServer[93]: Created shield window 0xcb for display 0x003f003d
21/05/2013 23:31:35.701 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:35.712 airportd[1030]: _doAutoJoin: Already associated to “ASUS60”. Bailing on auto-join.
21/05/2013 23:31:36.104 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:36.129 loginwindow[42]: resume called when there was already a timer
21/05/2013 23:31:36.000 kernel[0]: en1: BSSID changed to 10:bf:48:3e:02:74
21/05/2013 23:31:36.896 coreaudiod[1003]: HALDefaultDevice::GetDefaultDevice: server returned 0 for the default device, so picking one locally
21/05/2013 23:31:36.897 coreaudiod[1003]: HALDefaultDevice::GetDefaultDevice: server returned 0 for the default device, so picking one locally
21/05/2013 23:31:37.669 WindowServer[93]: Received display connect changed for display 0x78c8d1b0
21/05/2013 23:31:37.683 WindowServer[93]: Created shield window 0xcc for display 0x78c8d1b0
21/05/2013 23:31:37.683 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:37.684 WindowServer[93]: Received display connect changed for display 0x3f003d
21/05/2013 23:31:37.684 WindowServer[93]: Received display connect changed for display 0x78c8d2fe
21/05/2013 23:31:39.009 WindowServer[93]: Received display connect changed for display 0x78c8d1b0
21/05/2013 23:31:39.026 WindowServer[93]: Created shield window 0xcd for display 0x78c8d1b0
21/05/2013 23:31:39.026 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:39.027 WindowServer[93]: Received display connect changed for display 0x3f003d
21/05/2013 23:31:39.027 WindowServer[93]: Received display connect changed for display 0x3f003e
21/05/2013 23:31:39.051 WindowServer[93]: Created shield window 0xce for display 0x78c8d2fe
21/05/2013 23:31:39.051 WindowServer[93]: handle_will_sleep_auth_and_shield_windows: no lock state data
21/05/2013 23:31:39.490 WindowServer[93]: Display 0x78c8d1b0: GL mask 0x1; bounds (1920, 0)[1920 x 1080], 16 modes available
Active, on-line, enabled, boot, OpenGL-accel, Vendor 5e3, Model 2353, S/N 572, Unit 0, Rotation 0
UUID 0x000005e3000023530000057200000000, ColorProfile { 3, "HD 709-A Calibrated"}
21/05/2013 23:31:39.490 WindowServer[93]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000007, accelerator 0x000032af, unit 0, caps QEX|QGL|MIPMAP, vram 1412 MB
texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
21/05/2013 23:31:39.490 WindowServer[93]: Display 0x003f003d: GL mask 0x2; bounds (4864, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffff003f003d
21/05/2013 23:31:39.491 WindowServer[93]: Display 0x003f003f: GL mask 0x8; bounds (4865, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffff003f003f
21/05/2013 23:31:39.491 WindowServer[93]: Display 0x78c8d2fe: GL mask 0x4; bounds (0, 0)[1920 x 1080], 16 modes available
Main, Active, on-line, enabled, OpenGL-accel, Vendor 5e3, Model 2353, S/N 63d, Unit 2, Rotation 0
UUID 0x000005e3000023530000063d00000000, ColorProfile { 3, "HD 709-A Calibrated"}
21/05/2013 23:31:39.491 WindowServer[93]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000007, accelerator 0x000032af, unit 0, caps QEX|QGL|MIPMAP, vram 1412 MB
texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
21/05/2013 23:31:39.685 WindowServer[93]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
21/05/2013 23:31:39.713 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:39.714 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:39.730 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:39.730 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:39.805 WindowServer[93]: Created shield window 0xcf for display 0x78c8d1b0
21/05/2013 23:31:39.806 WindowServer[93]: Created shield window 0xd0 for display 0x003f003d
21/05/2013 23:31:39.806 WindowServer[93]: Created shield window 0xd1 for display 0x003f003f
21/05/2013 23:31:39.811 WindowServer[93]: Created shield window 0xd2 for display 0x78c8d2fe
21/05/2013 23:31:39.841 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0: Startup Mode 1920 x 1080, CGSThirtytwoBitColor, Resolution 1, IOMode 0x80000000, IODepth 0x0, IOReturn 0x0
21/05/2013 23:31:39.841 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2: Startup Mode 1920 x 1080, CGSThirtytwoBitColor, Resolution 1, IOMode 0x80000000, IODepth 0x0, IOReturn 0x0
21/05/2013 23:31:39.842 WindowServer[93]: Display added
21/05/2013 23:31:39.842 WindowServer[93]: Display removed
21/05/2013 23:31:39.875 WindowServer[93]: Display 0x78c8d2fe: GL mask 0x4; bounds (0, 0)[1920 x 1080], 16 modes available
Main, Active, on-line, enabled, OpenGL-accel, Vendor 5e3, Model 2353, S/N 63d, Unit 2, Rotation 0
UUID 0x000005e3000023530000063d00000000, ColorProfile { 3, "HD 709-A Calibrated"}
21/05/2013 23:31:39.876 WindowServer[93]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000007, accelerator 0x000032af, unit 0, caps QEX|QGL|MIPMAP, vram 1412 MB
texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
21/05/2013 23:31:39.876 WindowServer[93]: Display 0x78c8d1b0: GL mask 0x1; bounds (1920, 0)[1920 x 1080], 16 modes available
Active, on-line, enabled, boot, OpenGL-accel, Vendor 5e3, Model 2353, S/N 572, Unit 0, Rotation 0
UUID 0x000005e3000023530000057200000000, ColorProfile { 3, "HD 709-A Calibrated"}
21/05/2013 23:31:39.876 WindowServer[93]: GLCompositor: GL renderer id 0x01024400, GL mask 0x00000007, accelerator 0x000032af, unit 0, caps QEX|QGL|MIPMAP, vram 1412 MB
texture units 8, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
21/05/2013 23:31:39.876 WindowServer[93]: Display 0x003f003d: GL mask 0x2; bounds (4864, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffff003f003d
21/05/2013 23:31:39.876 WindowServer[93]: Display 0x003f003f: GL mask 0x8; bounds (4865, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffff003f003f
21/05/2013 23:31:39.883 WindowServer[93]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x78c8d2fe device: 0x10646ea10 isBackBuffered: 1 numComp: 3 numDisp: 3
21/05/2013 23:31:39.892 WindowServer[93]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x78c8d1b0 device: 0x10646e110 isBackBuffered: 1 numComp: 3 numDisp: 3
21/05/2013 23:31:41.029 WindowServer[93]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
21/05/2013 23:31:41.059 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.059 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.062 WindowServer[93]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
21/05/2013 23:31:41.076 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.076 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.088 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.089 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.103 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.104 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.843 WindowServer[93]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
21/05/2013 23:31:41.846 WindowServer[93]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
21/05/2013 23:31:41.871 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.871 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.872 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.872 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.889 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.889 WindowServer[93]: Display 0x78c8d2fe: MappedDisplay Unit 2; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.890 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:31:41.890 WindowServer[93]: Display 0x78c8d1b0: MappedDisplay Unit 0; ColorProfile { 3, "HD 709-A Calibrated"}; TransferTable (256, 3)
21/05/2013 23:32:20.130 com.apple.backupd-helper[1043]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.

Replacement HD spinning up and down during "sleep"

I just "upgraded" the HD in my iMac Indigo to a 40GB Western Digital. Everything runs fine (things I have tried) except that it won't sleep properly. When put to sleep, the HD spins down, stops, then after a brief pause spins up again, leaving me with a blank screen and a spinning disk. Thereafter I get noises of half spinning up and down at intervals.
I have seen bad comments about Western Digital and one problem where resetting was required (PMU?) Do I have an unhappy HD?
I started up in 9.2.2 and put it to sleep and it slept properly. Does the HD just not like OSX? I'm running 10.3.9 on the Imac Indigo 350.
Any thoughts please? Thanks in advance.

OK, answered my own question (via Duane on another post). Looking at Duane's link http://forums.xlr8yourmac.com/drivedb/search.drivedb.lasso I found the exact same problem encountered with WD drive elsewhere, hence solution-send drive back and get a more compatible one (looks like Maxtor). I'll leave the post up in case it helps anyone else.
Thanks Duane

Spinning up and down lots, is this healthy?

Hi there,
I've had a TC Dual Band (500GB) for a few months now. I'm really pleased with it (except for the slight niggle I could have 1TB for the same money, lol)...
My only worry is that the hard drive spins up and down a lot. It does one machine's backup, then after about 5 minutes it spins down. Then another machine needs a backup, and it's spinning up again within a couple of minutes (it's sat on top of a side unit and makes the whole unit hum so I can hear it quite clearly!)
I always thought that it wasn't good for hard discs to spin up and down a lot because they wear out more quickly... Is it something I should be concerned about, am I going to have to replace the hard drive sooner than I'd expect?
Thanks!
:-Joe

...and you don't have your old gpu?
You do realize that not all PC cards play well, and that you read up and researched before setting on this one? even different versions and makes of the same "model" or card series differ.
AMD cards may have two BIOS, legacy and UEFI.
Thought about sending it to MacVidCards or checking?
AHT does not test GPU.
There have been issues with heatsink and paste or with upgrades - very popular to flash firmware and throw in new cpu(s)
Mac Pro 2009 upgrade running hot - MacRumors Forums
2009 Mac Pro 12-Core CPU Upgrade (Dual 3GHz Xeon X5675)
2009 8-Core Upgrade... The De-Lidded Route - MacRumors Forums
Nehalm processors with their HT can jump 20*C just launching an app or files
To see what the processor temps are, and there are many sensors and ways to monitor, you would need something more like Hardware Monitor
http://www.macupdate.com/app/mac/16609/hardware-monitor

Stop external HD randomly spinning up and down

Hi,
I have just bought and installed a LaCie P'9230 2TB external HD to use as my Time Machine disk. I was previously running Time Machine just once a day to an iOmega disk, which I would switch on only when I wanted to run the backup. With the new LaCie, I thought I would leave it on all the time and use Time Machine Editor to program Time Machine to run twice a day.
The LaCie works fine, and Time Machine runs twice a day as scheduled. However, the LaCie will go into "Eco mode" after a few minutes of inactivity, and then go to sleep. This is fine – I would be quite happy for it to go to sleep and stay asleep until Time Machine wakes it up twice a day. The problem is that something seems to be waking it up every 15 minutes or so, causing the disk to spin up. It then goes back to sleep again after a few minutes, and the cycle continues. Note that this happens even if I'm not actually doing anything on the machine at the time – in other words, it's not caused by me opening or saving files, running searches, etc.
I know that constant spinning up and down is a major cause of early HD failure, so I'd like to find a way around this. Ideally, I'd like to find a way of letting the disk stay asleep until Time Machine wakes it; failing that, I'd prefer it to stay awake all the time and not go to sleep at all. I've tried unchecking the option in Energy Saver to "Put the hard disk(s) to sleep when possible", but this seems to make no difference – presumably because the Eco mode/sleep function is baked into the LaCie firmware and cannot be overridden by the OS.
I've spent ages trawling the interwebs; I've found is that this seems to be a common complaint, but haven't found any definitive answers. Really hoping someone on here might have some insight and/or suggestions.
Thanks,
Rob

This may be a "feature" built into the firmware of your external drive. If so it will not be affected by your Energy Saver settings. I recently had to advise someone with a "Western Digital MyBook" spinning down to ask the manufacturer for help, but the outcome was that the only solution was the purchase of an uncrippled drive. Being in the firmware, the "feature" could not be erased or altered.
"Is it possible to stop…"
Yes, but only in what I would consider an unacceptable manner, e.g. by having a small script that constantly accesses the drive, but I would suggest that a) it should not be needed, and b) it would be highly likely to interfere with other things you were doing.
So, as a start, you should a) read any docs that came with that drive, and b) go to the relevant site and see what you can find out.
I hope that none of this applies to you, but I just thought you ought to be aware of the possibility.

USB Hub makes Airport Extreme HDDs constantly spin up and down

Hello there,
I have a new Airport Extreme, (newest model, but not a time capsule). I have discovered that when I plug an external USB HDD into the AE, everything is dandy. But when I use a powered USB hub, the HDDs are constantly spinning up and down. All connected computers are shut down. Nothing is accessing the AE. From my testing it seems to be the powered USB hub that is creating the issue. Has anyone else noticed this? Could it be my hub (Amazon Basics 7 port powered USB hub)? Anyone have any success with a different hub?
Thanks all!

It can be a whole lot of stuff interacting.
What are the external disks you are testing with.. as that is just as important as the hub.
I have not had issues using hub.. but I seldom try it.
Powered hubs of low quality (ie standard cheap end, rebadged made in China junk) can have substantial issues with power leaking.. ie it sources power from its own supply or the AE or the drive..
Let me suggest you test one at a time.
Plug in just one disk.. (will the hub work without the power supply plugged in.. some do).. assuming it is not a self powered drive.. see if it is ok by itself.. test each drive.. with the hub powered and unpowered.. tell us what you get.

Macbookpro Fan suddenly spin fast and loud whereas it's not hot

Hello, i have an issue with my new macbook pro 13 early 2015, i had it for about 1 month now, when i use may mac on easy task (not on high load) my fan suddenly spin so fast and make loud noise whreas my mac isn't on hot condition and i use it on room temperature enviroment, an not so long after that, it comes back to idle... anyone have solution for this?
Thanks
note : it's happened just 3 times since i bought this laptop...

A new Mac comes with 90 days of free tech support from AppleCare.
AppleCare: 1-800-275-2273
Try resetting SMC.
Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
Best.

The down arrow of the msctls_updown32 control can fail to display under certain conditions using certain Windows Desktop themes

I have a very odd issue with the msctls_updow32 control. Depending on the type of window or window heirarchy, when I click the up arrow with the autobuddy being an edit control, the down arrow disappears off the down button. I have to move the mouse back
over the down button to get it to display. At first I figured it was something in my OnCtlColor code. But I found that the updown control is never passed to OnCtlColor. I get the window class of each input and it never shows up. Nor does it's window handle
get passed in. Turning off OnCtlColor code and going default doesn't help. What I have found that helps is to turn off WIndows 7 Aero desktop and turn on Windows Classic desktop (Windows 7 Basic has the issue too). I also found that applying a skin to my app
avoids the issue. Using spy I finally found what appears to be a connection to EM_SETSEL. When that message is sent and processed, the arrow has disappeared. I finally gave up and created my own subclass of a CEdit control (MFC) and called SubclassDlgItem.
Then I implemented WindowProc and trapped the EM_SETSEL. Then I had to call UpdateWindow on the spin control and finally get the rectangle of the edit (buddy) and spin control and use that in a call to the parent (dialog) window's RedrawWindow.
So there appears to be an issue with the updown control paired with an edit control that shows up depending on what desktop theme I am using. And to top it off, the window heirarchy seems to matter too (or perhaps the styles of the parent make a difference
as I found the issue doesn't show up on every window that may contain such a configuration). Consider this a heads up regarding the issue! One other note, changing to any of the "High contrast" Windows 7 desktops also avoids the issue. So Aero and
Basic seem to be the key.
R.D. Holland

Fails on Win 8.1 too. As with Win 7, changing the desktop display to one of the high contrast ones avoids the problem. My work-around is below. I have a video showing the problem. It also shows the display being changed to high contrast and how the problem
goes away. If only I could figure out how to use this web page to upload the zip file containing the video ...
LRESULT Myedit::WindowProc( UINT message, WPARAM wParam, LPARAM lParam )
LRESULT lr = CEdit::WindowProc( message, wParam, lParam );
if( message == EM_SETSEL )
CDialog* pParent = (CDialog*) GetParent();
if( pParent )
CSpinButtonCtrl* pSpin = (CSpinButtonCtrl*)pParent->GetDlgItem(IDC_SMALL_PARTS_SPIN);
if (pSpin)
CRect rectSpin;
pSpin->GetWindowRect( &rectSpin );
CRect rectEdit;
GetWindowRect( &rectEdit );
CRect both;
both.UnionRect( &rectSpin, &rectEdit );
pParent->ScreenToClient( &both );
//pParent->InvalidateRect( &both );
//pParent->Invalidate();
//pSpin->Invalidate();
pSpin->UpdateWindow();// skip this and the problem remains.
pParent->RedrawWindow(&both);// skip this and the problem remains.
return lr;
R.D. Holland

Help MSI GE60 Fan keeps spinning to 100% and down every 10 seconds.

Hello,
I just bought an MSI GE60 and after 4 days of using, The fan keeps spinning up and down every 10 seconds even when nothing is running on the laptop. Have tried updating the BIOS and the drivers, but no change.
Every time i turn on my laptop this always happen. It goes on when my laptop is on. Even if im not doing anything it still keeps spinning up and down. I checked the temperature and its at 40+ C and my CPU usage is normal. Basically im not doing anything and it keeps doing this fan spin up and down.
Even when the cooler boost is on or off, its still does the same thing, the fan keeps spinning up to 100% and down.
Do you think this is a software issue or hardware? It is very annoying to hear the fan go 100% for 10 seconds then back to normal then back to 100% speed again and when i press cooler boost it doesnt do anything. So even tho the cooler boost button is off, it still keeps doing the 100% fan speed and back to normal again. It keeps repeating.
Can anyone help me solve this problem please? Thank you very much.

Quote from: reprieve.nagrand on 03-May-13, 08:35:31
I have already tried uninstalling the S-bar and SCM drivers but still getting the fan noise. Also tried the no-battery and no-power reset for more than 24 hours but still having the same problems. The only thing that worked was changing the values in the RWeverything software. The only problem here is that it will work only until I shutdown the laptop. Once I do a cold boot I have to redo the RWeverything changes again.
@reprieve.nagrand
thanks for your case. Can I ask you a few questions more, please?
1. According to your model id your notebook came with just FreeDos, right? Could you please enter the Bios and go to System Information to confirm that you are using Bios 10F and EC version 14.04 (or 4.04)?
2. I urgently need a screenshot of your EC-Page within RWeverything after a cold boot without any modifications. Please try to make the screenshot at that time, when you can barely hear the fan anymore during the spin-on / spin-off cycle.
3. CoolerBoost: with a laptop that has been sitting idle for at least 20mins since last cold boot (no load, please!), can you turn on coolerboost by pushing the button somewhere to the left of the Powerbutton and let coolerboost run for at least 30 seconds. Then turn coolerboost off again and wait for the fan to slow down. Does the fan run continously after applying coolerboost or does it enter its off/on-cycle again. Please try it for at least 5 times and repeat it during other Windows sessions for two times. If this trick works, you are the man to make the video! Please help me out here. Please note, that the coolerboost trick will only work until there is load on the system again. If the fan speed picks up again due to load and slows down again, it will enter the annoying pattern, again.
4. While still reviewing the case and going through my notes, I came across an entry that I reflashed the EC-Controller with the same firmware one or two nights before the problem disappeared. This happened after uninstalling S-Bar and SCM earlier. So, if you are familiar with DOS-Flashing using USB-Sticks you could try to reflash the EC-Controller, than remove all power sources for at least 20 mins. If anyone else is experiencing the problem, please go ahead and report your findings. But please do the reflash only if you are familiar with such things and of course, please do so on your own risk!
Current status and work in progress:
As I haven't gotten hand on a video proofing that simply pushing the coolerboost fan button makes the problem temporarily go away, I am still stuck on there. The coolerboost solution works until the system load increases so much, that the fan level has to be raised. When the system load goes back to idle again, the fan level decreases and enters the off/on-cycle again.
The good news is I managed to customize a programm called fan control tools to somehow automatically apply the changes in RWeverything via a small GUI. This tool will also allow you to set fan profiles for Office, Games, etc. The bad news is, that this will trigger UserAccountControll at least once and it doesn't reapply after a cold boot or returning from hibernate, yet. I am now currently working on a solution that allows the new fan values to be set by Windows automatically using a batch file. This will apply the new values after a normal Windows boot, but not when returning from hibernate, though.
However, if you have found your remedy value for the fan issue within RWeverything, you can turn to Svet in the subforum "Notebook Modified & Private BIOS'ses & EC-FW". He will certainly be able to create you a custom EC-FW with those values written permanently in it.
My case:
The fan problem with my notebook has not (yet) returned. It has been running without S-Bar/SCM just fine. It can even process all fan profile alterations I have made. So, am I just lucky? While I do believe, that the fans of those notebooks experiencing the issue could be "somewhat odd", I find it hard to believe that my fan really suffered a mechanical problem. Without doing anything mechanical wise, my problem went away.
@Warner: I promised to present more videoproof of the case, but unfortunately I haven't managed to get a hold on a suitable video, especially since my unit has been running fine for the last weeks. Please be patient, if I have enough evidence I will post it asap.
One question bothers me though: looking at the EC-page of RWeverything, I was wondering if these are really all values, that the EC handles and checks. Are there any other values, variables that the EC manages and that are not displayed on the EC-page of RWeverything? The reason for asking this, is because I have a video showing the ECpage of RWeverything while the fan does his off/on-cycle and you can clearly see the RPMvalue correspond to the actions of the fan. As you pointed out, the boosts occur because the EC is missing a fan signal, I could clearly see the RPM value at offset 0xCD respond to the actions of the EC. If the controller looks for that value only, it should surely see the RPMs of the fan, as I can see them in RWeverything. So, I was wondering if the EC has other values not shown in RWeverything, that determine if the EC should enter the boost cycle?
While having another look at that video again, to me it appears as if the EC does this really on purpose. It tries to reduce the voltage of the fan to a point so low, that the fan simply starves. Then it boosts the fan up again. The only question is: why does the EC do that? Is there a leftover setting inside the EC - perhaps from another notebook - where such low RPMs were achievable?
You can find the video here in this zip-file: http://www.file-upload.net/download-7371226/MSI.rar.html
In the zip-file you will find three numbered videos, the first one is the most interesting as it shows the annoying fan cycle while the laptop is running idle. In the second one, the user put load on the system using prime95. The third one shows the system while it cools off again after prime95 has been stopped. Sadly, the video is too short as the system doesn't reach its lowest fan state again. The videos were taken in march in Germany, so the ambient temperature is around 20-21 °C or less (normal room temperature in Germany).
Regards,
jku

Fan not spinning up/no module for ACPI PM

I'm a little confused here.
First off, this is a laptop (an old Toshiba) with a Celeron-M (420?). It can't run too long before shutting down because it gets too hot because the fan will not spin up. The actual fan is fine, as it runs properly on windows.
I looked around when I was trying to get ACPI up and running for power management(it couldn't find a proper module to use) and found this:
http://aur.archlinux.org/packages.php?ID=33104
Do I need this?
I did try installing it yesterday (with the working pkgbuild in the most recent comment) and while building the kernel, it "spammed" warnings all over and I didn't bother using it. I didn't change anything in the kernel config menu.
Last edited by JerichoKru (2010-05-06 21:00:06)

Toshibas for whatever reason are not friendly to Linux. I'm running one with "acpi=ht" in the grub boot line (results in "select() to /dev/rtc to wait for clock tick timed out" error for both cores, but does not with acpi=off). There are no ACPI functions (nothing in /sys whatsoever) but the fan does speed up and down at times (unlike with acpi=off, where it always runs at default speed) (temperature from the only hardware monitor found hangs around 64 degrees celsius, usually),
[skyalmian@alcyone ~]$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +63.0°C (high = +70.0°C, crit = +100.0°C)
and no power management to speak of, including battery -- it's all unrecognized by the system, even with installed packages. Meh, I'm fine with it, though. It just means that without knowing the status of the battery I keep mental track of how long the system is on when not plugged in. This Toshiba L505D-S5983 had a poor battery rating on Windows @ only 2 hours max doing generic things, so I round down to just one hour. I was using it one day without it plugged in and it just shut off when the battery went empty.
Threads you should see about Toshibas
http://bbs.archlinux.org/viewtopic.php?id=87573
http://bbs.archlinux.org/viewtopic.php?id=90942
http://bbs.archlinux.org/viewtopic.php?id=87213
http://bbs.archlinux.org/viewtopic.php?id=86802
(For anyone with ArchWiki access, can/maybe add this.)
Last edited by Skyalmian (2010-05-07 17:28:45)

Coming 10.6.8 my right fan is down and left fan is overworked

Coming OS 10.6.8 my right fan is down but my left fan is overworked; it works all time more than 4800 RPM.
may I go back to 10.6.7 ?

Hi Ray,
Try a SMC reset...
http://support.apple.com/kb/HT3964
Failing that you could download and install the Combo Update:
http://support.apple.com/kb/DL1399
Hope this helps,
Cheers,

IMac won't/doesn't start up - spinning gear and fans forever

Hi,
My iMac won't get past the Apple Logo/Spinning gear progress indicator. It started two days ago after I swapped out some USB devices (pulled my headset and inserted Photo card reader with an SD card in it) It didn't mount the SD card so I restarted. Wish I hadn't. It now will not complete start-up. I also get the jet-engine fans after about 30 sec (but I read this is normal). The only other thing I can think of that I have done recently that might be a problem was download some shareware games from www.macgamer.com which didn't install correctly and wouldn't run.
I have done everything I know or have found on this website. I have found a few posts where the problem looks just like mine, but none have posted solutions. (and a bunch with a similar sounding problem but always with some different detail).
Here is what I have done so far. After each of these a fresh reboot just hangs at the spinny thing:
- rebooted from the install DVD (it will do this), repaired both hard drive and permission several times each. Some pemissions were repaired but no repairs were made to the hard drive, it checked out OK each time.
- Ran the "Quick" hard ware test. Everything passed
- Reset the PRAM (or at least held down the PR+shiftCMd combo, not sure if that had any effect).
- tried to start in safe mode, but can't because after the second chime, it just hangs again at the Apple logo.
- Started in single user mode, ran fcsk twice (NO PROBLEMS FOUND) then did the steps from single user mode to delete cache and prefernce files found in this thread (http://discussions.apple.com/thread.jspa?messageID=1484205)
None of this has helped. Right now I see only two possibilities, Archive and Install or take it up the street to the Apple Store (really close, but its the first one in Portugal and the store has only been there for about 3 months, so I have to wonder if they know what they are doing).
Does anyone have any suggestions before I take either of these drastic steps? Which one should I do first?
iMac G5 Mac OS X (10.4.4) 1 Gb

thanks for the suggestions but I have tried both those. I can´t boot up in safe mode, because it simply doesn´t get that far, always getting stuck at the apple log/spinning thing, and the disc utilities (which I have now run several times) don't find any problems.~
I have now followed all the steps in the apple support "my computer won't start" guide (106464 or whatever it is called), which I was at first hesitant to do becasue that doc is for up to OS 10.3.9 and I am running Tiger 10.4.5 (or was running it before this happened, that is). Still nothing has helped.
However, I did make a discovery. After booting into single user mode and deleting/moving some of the preference files, as instructed in the above help doc, I tried to "boot the system in single user mode" (it tells you the command for that when you first enter single user mode). And after showing some start up codes, which go by really fast, but don't seem to show any errors, the screen displays three line of text, which I wrote down but don't have on me at the interennt cafe I am now forced to visit to get on this forum. The first two are the same and I can't remember exactly what they say, but the third says:
root user not found. sleeping and trying again.
It then sits for about 3 seconds and then displays the three lines again, over and over. I have let it go for upt ot 10 minutes. So does anyone know what that means, if that is the true problem or how to fix it without reinstalling? Let me repeat, numerous "repair disc" using disc utility and "fsck" in single user mode have not returned one single problem or error code since this problem started. Unfortunately I don't have disc warrior, but it has been ordered and is one its way.
iMac G5 Mac OS X (10.4.4) 1 Gb

Right fan not working and temperature rising

Hi guys (and ladies...)!
I've installed SMC Fan Control on my MBP because it was running hot. Last summer (no, no, I didn't give you my heart...), I sent my MBP in for a logic board replacement, because one day the screen stayed obstinately dark, though I could hear the hard drive spinning... and the fans too!
Recently, I noticed that the right fan was making a real racket, like a ball bearing going sour. I'm planning on bringing my MBP back in for repair (I've got a three-year warranty plan from the French retailer where I bought my machine), but I'd like to know if someone has already experienced a total and sudden fan breakdown such as this.
In System Preferences under PrefPanes, I can access my Fan Control preferences, and it shows one fan (the left one) running at almost 5000 rpm, and the other (guess what? yeah, the right one!) at 0, repeat, zero.
Something's wrong, right?

Just what I thought... OK, thanks, I'll bring it back in. I just hope they won't keep as long as they did last year (5 weeks to change a lousy logic board, can you believe it?)...
Thanks, mate!

Repeatedly getting stuck on spinning wheel and grey screen, even after multiple re-installs of the OS

Ok, so running Lion on a MacBook, (2010 i think) and the OS got corrupted(stuck on spinning wheel and grey screen on boot)
Tried to repair the disk via disk utility using an install CD, no go, couldn't repair, so, did a clean install.
New install went fine, computer worked for about 3 days and then stuck on the spinning wheel again.
suspecting physical damage to the harddrive, I installed the OS to an external, and booted from there. Worked for a couple days and then stuck on the spinning wheel.
I have repeated the process 5 times now, each time it works for a little and then craps out again.
What's going on?
as a note, when I say it gets stuck on the spinning wheel, I have left it for 12 hours trying to boot to no avail.

The Apple Hardware Test doesn't always detect all errors.
Next time you get the gray screen/spinning wheel, try booting into the Safe Mode to see if it will boot.
Shut down the computer and then power it back up. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart. For each disable/delete, you will need to restart if you don't do them all at once.
Safe Mode
Safe Mode - About
Startup Gray Screen
Startup Issues - Resolve
Startup Issues - Resolve (2)
Startup Issues - Resolve (3)

"Moo" = Right fan repeatedly spinning up and down under certain conditions

Similar Messages

Maybe you are looking for