Showing posts with label Apple - Mac OS X. Show all posts
Showing posts with label Apple - Mac OS X. Show all posts

Friday, July 10, 2009

Macbook Air and kernel_task - Apple speaks

Happy Friday everyone!

As promised our sources at Apple have forwarded information to us regarding the Macbook Air and the "kernel_task" process spike.

According to them the kernel_task process basically under clocks the CPU by running in the background (we can only assume similar to a "system idle" process). This allows temperatures to be reduced or to be maintained at safe levels.

Our Apple contacts recommended that we make sure the Macbook Air is on a smooth surface and the vent ports should be free of obstruction. They also mentioned there should be no unexpected processes running in the background.

Now, the above is not public information and so we are as usual grateful to them for what they were able to send to us but we do wish they had gone a bit further and at least hinted as to why Apple has not made this information public after such a long period of time. Or even why Apple chose to replace the default Core Shutdown safety feature with just another under clocking method (kernel_task). Readers of our previous article will note that here at Go Go we have a few ideas on this subject...

Go Go

Monday, July 6, 2009

Macbook Air - kernel_task process and overheating

Although here at Go Go we are specialist at both Apple and Windows technology we definitely have a bias towards Apple hardware.

This case is no different for Apple's thin and luxurious Macbook Air.

However, like many Apple designed products some sacrifices are made for aesthetic purposes. In the case of the Macbook Air, things like sufficient amount of vent holes or an appropriately sized heat sink got in the way of Apple's Macbook Air design plans.

This is at least the case for the first generation Macbook Air in which the user community has documented overheating issues. These overheating issues can happen when doing intensive or even moderate tasks such as playing back video or surfing flash enabled sites.

At Go Go we are lucky enough to have access to 3 first generation Macbook Airs. Each of which was bought at separate times and so are not off the same assembly line. However, two of these are configured with 1.8Ghz CPUs and one is a 1.6Ghz. All have the SSD option.

Each one, when pushed with moderately intensive tasks or exposed to less than absolutely stellar environmental factors (rooms temperatures above 79 degrees), will exhibit heat issues that seem to induce the dreaded "kernel_task" process spike (kernel_task CPU usage can reach a steady rate of 150% from the Activity Monitor).

In one test, we had the 1.6Ghz Macbook Air in a room setting of 75 degrees on a nice flat desk surface area clear of any obstructions (so as to not block the vents) and connected to an Apple Cinema Display. We went to Apple's Movie Trailer site and decided to try to run a 1080p trailer. Using the Activity Monitor we set our timers to see how long it would take for the "kernel_task" process to spike in CPU usage.

Two minutes. Two minutes is all it took in playing an H.264 trailer from Apple's own site to bring the Macbook Air literally to its knees.

We also took the time to run temperature benchmarks and noticed that the CPU and Heat Sink temperature was almost directly correlated to the kernel_task process spike. When running normally the CPU and Heat Sink temperature were 134 and 125 Fahrenheit respectively but when running things such as video the CPU and Heat Sink reached levels of 147 and 134 Fahrenheit. Each time the kernel_process would spike in CPU usage when temperatures reached these levels. Even after quitting the video playback it would take sometime for the kernel_task to come down in usage levels until temperatures were back at nominal levels.

It's painfully obviously that Apple's cooling system for the Macbook Air is inadequate.

This is probably related to the almost useless thin heat sink employed in these Macbook Airs and the lack of adequate amount of vent ports to circulate air.

I should note that prior to the "kernel_task" issue was the Core Shutdown issue. Essentially, when Macbook Airs first shipped if the CPU would overheat the Macbook Air would shutdown one of the CPU cores as a safety measure. Obviously, customers complained and so Apple released a "fix" for this in the form of a firmware update.

Except that Apple didn't actually fix the overheat issue but instead stopped the CPU core from shutting down and implemented another type of fix to seemingly achieved the same results while keeping both Cores alive. Confused? That was Apple's point unfortunately in this scenario.

We will be contacting our sources at Apple to investigate the issue as standard support channels do not even acknowledge that an issue exist even though the first generation Macbook Airs have been out for a year and a half.

Our hope is to at least understand the role of the kernel_task process and see whether Apple is internally aware of the problem but publicly denying it.

Go Go

Friday, July 3, 2009

Remove ACLs recursively in Leopard 10.5

Have a folder in Leopard with many sub files and sub folders that each have their own set of unique ACLs and don't want to remove each ACL one at a time?

Open up the Terminal and do the following:

sudo chmod -R -N

Example, "chmod -R -N myfolder"


Go Go

Monday, June 29, 2009

Creating Groups, Adding Users and Sharing Out Folders in Leopard 10.5

We get this question asked frequently as techs. For the uninitiated, here it is:

You go to System Preferences in the Apple Menu and to Accounts Preference Pane.

Click on the "+" button and choose Group from the New Account pop down menu.

Create a Group name and check off the members you want to add.

Go to the folder you are sharing out and do a Get Info. Under permissions click the "+" sign and add the Group you just created. Choose the correct permissions (Read Only;Read/Write). Use the Action button to Apply to Enclosed folders.
Check off "Shared Folder" if you haven't done so already.

That should be it. Now, regardless of whether a connecting user is in the Staff group or not as long as you have added them to your custom group they should not get any kind of ownership or permission issues..

As for where Mac OS X keeps all its directory information it is now under /var/db/dslocal/
(versus localdb as in the NetInfo of past)

The precise location of the group listings is /var/db/dslocal/nodes/Default/groups/
(kept in plist files).

Go Go