You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.6.3 13" MacBook LCD backlight off after resume form sleep.

Hi all, 1st time poster, not had a problem with my Mac I couldnt solve until now....

I've updated to 10.6.3 using software updater. Since then when I resume from hibernate the LCD backlight of my MacBook does not turn back on. There is a very faint image on the screen, so I know its just the backlight. The F1 & F2 keys won't control the backlight in this state, I also noticed that when this happens F5 & F6 won't adjust the keyboard backlight either.

Things I've tried:
commented out my .sleep & .wakeup scripts
reset pram
Onyx
checked colour profiles
deleted com.apple.PowerManagement.plist

the problem persists. If it occurs again I'm going to try the 10.6.3 combo update. Has anyone else come across this?

13" Alu Macbook (Late 2008), Mac OS X (10.6.3)

Posted on Apr 1, 2010 3:24 AM

Reply
100 replies

Apr 4, 2010 4:03 PM in response to flemingt

ok then, this may be my last post on the matter (fingers crossed). Thanks to feedback from JimHKuo we narrowed down our problem to Applebacklight.kext. I replaced it with the file from 10.6.2 (there's only 10 lines different in a .plist) using kexthelper, and used its inbuilt permissions (advanced function) and so far so good. I hope this helps someone.

Apr 5, 2010 4:32 AM in response to macosh

i think you did too, but apple deleted all my steps.
what seems to work though is if you
1) take the AppleBacklight.kext from the 10.6.2 comboupdate (use pacifist and extract it) or your time machine backup and
2) put it in a folder on your desktop. I called the folder 10.6.2.
3) I made another folder called 10.6.3 and copied the AppleBacklight.kext from /S/L/E/ to it as a backup in case something went wrong.
4) use kext helper b7 to install the kext from the 10.6.2 folder on the desktop
5) use the advanced option in kext helper to check the permissions fo the Extensions folder.
6) reboot
7) cross fingers!

Apr 6, 2010 5:00 PM in response to macosh

macosh wrote:
That's strange....I thought I posted a reply that I have the same problem... really, what happened to the previous post?


Apple Discussions are moderated forums with a set of rules for acceptable content. You agreed to abide by them when you created your sign-in account but if you did not read the rules then, you can use the "Help & Terms of Use" link on every Discussions page to review them. Paying special attention to the "Submissions" section may explain why a post was pulled.

Most frequently, posts are pulled because they are primarily rants or focus too much on non-technical matters. They may also be pulled if they seem likely to provoke such things, or generally don't seem constructive. There can also be a cascading effect: if you reply to a post that is pulled for one of these reasons, your post may be pulled as well, since it would be confusing to users to see posts replying to missing ones.

The best thing to do if a post of yours is pulled is to try again, taking care to focus on the technical aspects of the subject, avoid rants, etc. Don't feel bad about it -- almost every user that posts a lot, including the 'top users' that have racked up thousands of points, have had posts pulled for one reason or another.

Apr 7, 2010 1:10 AM in response to R C-R

Thanks for the clarification. There are many points I could make in reply, that ma be considered a rant and in violation of the EULA but suffice it to say that the primary thrust of my posts was troubleshooting steps and narrowing down causes, there was no ranting. I apologised for any infringement that may have occured but I beloevethe response to be a bit heavy handed. I'm not going to reconstitute the missing posts as the resulting steps are outlined above.

Apr 7, 2010 4:22 AM in response to flemingt

Regarding pulled posts, note that any user reaching level 2 status or above sees a "report this post" link below every post in Discussions. There are several radio buttons in the report form & a small space for an explanation of why someone is reporting the post to the moderators. There is a button for reporting duplicate posts, for ones that need to be moved to a different category, for ones with info like serial numbers that should not be made public, etc., as well as for reporting inappropriate content. It is still up to the moderators to decide what, if anything, to do about a reported post.

Anyway, I noticed a reference in your viewable posts to commenting out .sleep & .wakeup scripts & to SmartSleep. I don't know if you explained more about the relevance of either item in a now deleted post but it would be helpful to do so now. Anything that changes normal system level behavior is suspect since it might have unexpected consequences when installing an OS update, even if it is otherwise compatible with the updated OS.

Also, regarding your steps, note that it is generally a bad idea to mix OS component files from different OS versions, especially extension (kext) files. The component files of each version are designed to be used as a set. For example, they may contain internal references to other files that would be incorrect for another version's files, expect another file to perform some step or check the replacement does not do or does differently, & so on. Plus, installers do more than just replace component files. They contain scripts & pre- & post-flight steps that integrate them properly into the OS, which may include updating other files, "sanity checks" that determine what is safe to do, & other procedures that just manually replacing a component file will not do.

Regarding that, note that Pacifist does not support running installer scripts. Although its author suggests it can be used as an alternative to the normal installer, this should be done only if there is a good reason to avoid running those scripts, & then anything necessary for normal operation they would normally do becomes the responsibility of the user to do manually. Also note that nowhere does the author suggest Pacifist should be used to mix components from different OS versions. It is primarily intended as a way to replace damaged or missing files from some package without having to reinstall the entire package, & includes tools to help with that. But using it to mix different version components, especially by manually installing them after extraction instead of using Pacifist's built-in install mechanism, is something that only expert users fully aware of the consequences should consider doing, & only for experimental or troubleshooting purposes. Doing it to "fix" some problem is almost certain to lead to more serious problems, if not immediately then when applying a future update.

Along the same lines, note that the author of Kext Helper b7 provides little documentation & warns that you use it at your own risk. It is intended as a tool for those developing & testing their own extensions. If you are not, then the risk of damage to your system is high unless you know exactly what you (& it) are doing.

In short, if you hack the OS, it is no longer the OS Apple supplied to you so you should not expect it to work as Apple intended; before, after, or during an update.

Apr 7, 2010 5:00 AM in response to R C-R

Thanks again for the clarification.

I dont mean to cause trouble but I feel that I must justify my actions. Feel free to lock this thread afterwards.

I believe I mentioned that I was using the thread as a tool to document my steps and those were the steps I tried.

Given this is a technical forum I was under the impression that those reading it would understand what was entailed in the steps. If they didn't then they were more than welcome to perform some research or ask in the forum. I would have been more than happy to explain.

Sleepwatcher is a command line tool which monitors if the computer is entering or leaving a sleep state. Sleepwatcher can then call the .sleep or .wakeup files to execute certain scripts. For instance my .sleep file ejects mounted drives (such as time machine volumes) and toggles my bluetooth before putting my machine to sleep. Whereas my .wakeup file re-toggles the bluetooth.

Smartsleep is an app / prefpane which interfaces with the OS pmset command and allows the user to control sleep and hibernate behaviours

My use of Pacifist was merely to extract a file, much like unarchiving the uninstaller, nothing more. I never endorsed its use as an installer.

My use of kext helper was to swap the one kext as outlined in my post and ensuring the permissions of the directory were correct. Granted I could have used terminal for this but there would have been a lot of su-ing chown-ing and chmod-ding. The risk can be high, as with anything that tinkers with system or firmware, but safer than missing a step in the command line. To reference your text, I was experimenting and troubleshooting.

I also shot off a mail to Apple and to the author of Smartsleep when all this started asking them to take a look at this thread and my troubleshooting efforts. I hoped that documenting my steps may have been useful for their techs & engineers.

With regard to mixing kexts and hacking the OS, I understand it is unadvised, but it was my risk to take. I had backups and backups of backups. I've since used time machine and restored to 10.6.2. It was merely to try to make the OS function correctly.

To reference your text, I would rather an OS that functioned correctly that Apple didn't supply as opposed to an OS that works incorrectly that Apple did supply. Again to reference your text, I was indeed experimenting and troubleshooting.

R C-R I value you input and again thank you for taking the time to write the clarification. To the mods, I will refrain from posting anything as technical as the posts in this topic the next time something goes wrong. I'll sit in silence, staring at a black unbacklit screen, and hope a fix is issued just like everyone else.

Slightly off topic here but one I did something like this for MS on a MS run forum and instead of deleting the thread they put me on a beta test team...go figure?!

Apr 7, 2010 8:20 AM in response to flemingt

Thanks for your clarifications as well. It is always helpful to know about anything on another user's system that isn't a standard part of the OS that might be relevant to an issue. As a practical matter there is no way for us to know about such things unless you mention them, so it is always a good idea to be proactive about that instead of waiting for us to figure it out.

Regarding that & your comment about an Apple-supplied OS that doesn't work correctly, can I assume that you are aware that a new version of Sleepwatcher (which you had not previously mentioned using & certainly is not part of the Apple-supplied OS) was released in February of this year & that only this 2.1 version claims support for Mac OS X 10.6 or uses the now preferred launchd method of starting it?

If you have not updated to this version, this may be the cause of your issue. If you do need to update to it, I strongly suggest that first you kill the running daemon and remove the old startup item by following the instructions in the new Sleepwatcher ReadMe file, then reinstall 10.6 & update it to the current 10.6.3 version using the normal installer methods to make sure you actually are starting with the Apple-supplied OS. At this point you might want to check & see what effect this has on the wake issue as a reference point.

Next, follow the instructions in the new ReadMe file to install the new version & test your existing scripts for compatibility with it. (There is no longer an installer package so you must install everything using the command line.)

Apr 7, 2010 12:10 PM in response to flemingt

There is a quite a bit of dispute here!
I think one should venture to fix some problem by themselves for we are more than a babies. And the effort of this venture should be encouraged because without effort, there will be no improvement.
Long story short. I tried twice of re-installing 10.6.3 update and failed so many times. Then I tried to remove 'smartsleep' application... then Works!
I think there was an improvement of waking up speed from hibernation, the bar charges almost twice faster than before.

I should withhold my case to be generalized, because I still do not know why this happened. I do not know the disease, but have taken care of the symptom.

Thank you for your help!
P.s. I guess I should read the terms of use first more carefully...

Apr 7, 2010 1:05 PM in response to macosh

macosh wrote:
I think one should venture to fix some problem by themselves for we are more than a babies.


Sure, but there is no reason to reinvent the wheel every time a problem occurs. That's a large part of why forums like this one exist, so we can share solutions & learn about which ones have worked for others.

Regarding that, I would still like to know if you have installed the latest version of Sleepwatcher. By itself, SmartSleep probably is benign, since it is little more than a front end for pmset. But Sleepwatcher is in effect an open ended door into any UNIX command the user has privileges to use, with corresponding responsibilities to use them properly.

10.6.3 13" MacBook LCD backlight off after resume form sleep.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.