Q: OS X Lion freezes at login screen + App Store is slow

i'm sorry its 11D42 . well its not the final 10.7.3 code but not hopeful that it will fix our SBBOD issues.

another update . tried metallizer's root permission fix too after 10.7.3 update. no solution. guys got this msg each time i repeated permission repair .

Repairing permissions for “Macintosh HD”

ACL found but not expected on “private/var/root”

Repaired “private/var/root”

ACL found but not expected on “private/var/root/Library”

Repaired “private/var/root/Library”

ACL found but not expected on “private/var/root/Library/Preferences”

Repaired “private/var/root/Library/Preferences”

Permissions repair complete

this msg was present wen i tried the fix wth 10.7.2 . the msg below appears after the 1st permission repair but is not repeated again as the above mentioned ones.

Group differs on “private/var/db/GPURestartReporter”; should be 0; group is 80.

Permissions differ on “private/var/db/GPURestartReporter”; should be drwxr-xr-x ; they are drwxrwxr-x .

Repaired “private/var/db/GPURestartReporter.

pls advice

I got the same problem but.

I'm using mac book air 11" original install OS X lion.

it's freezes sometime when start up.

it's happen since December 2011.

Raj: As you have already noticed - the rumored Lion 10.7.3 update is not yet available. I just ran Software Update a minute ago and it said my "... software is up to date". I am running 10.7.2 (11C74).

Is  there any way you can report this to the Apple OS X team?

I mean, anyhow, there must be a few official testers out there with MBP 2010s etc. (including the MPros, iMacs, Minis and Airs that have reported to this forum)

It's like Terry says, the official release is not available, but let's keep our fingers crossed that the right feedback got to the OS X team, this time.

In the meantime, stay with Snow Leopard if it works fine for you. Best advice is to  partition your HD and keep

SL there permanently. Lion seems to be very much a work in progress – almost harkens back to the days of OS X 10.1

hi metalizer and terry , thanks guys . ur right . showed the macbook pro to 2 service centers. both claimed its a hdd error. i disagreed . i am using a seagate momentus xt 500gb hdd . it runs absolutely fine with SL. however i bought a seagate momentus 5400.6 500gb drive too. same SBBOD at login screen along with random panics usually once a week. guys enabling automatic login is how i'm managing right now. havent tried Terry's AGPM kext fix. i'm not a techie. i somehow dont beieve it's a hardware malfunction . how come so many logic boards suddenly konk out with lion but work fine with SL

I received my Macbook pro back from repair this morning.  The Logic board, the hard drive replaced not sure why because it was fine when I sent it and a cable 604-1067.

First boot from a cold start, very cold since it was 38 outside and the box had been outside at least 2 hours. 

After about 15 boots since this morning, no beachball at logon at all.

I will tell you the 10.7.3 did not fix the issue, at least the latest developer version.  I tried it and was able to make it fail many times over. 

Take it for what you want, I am not going to get into a discussion war of hardware vs software.  Until it fails consistantly again, the problem is fixed. Have a good night.

The change of logic board fixed my same problems too, no more freeze at login since then (Nov. 2011)

But... I understand that many people doesn't have the laptop under any warranty and it is very expensive.

My machine was not under warranty anymore and it was replaced becuase the engineers found something in the diagnostic that was run with the tool they sent me.  All I did was call support and used the fact that I downloaded Lion with the time of its warranty and got the support need to get it done.

The case in here, I believe is not actually 10.7.3, this bug is too critical so that we can say apple would wait until 10.7.3, it would probably come as an update like they did with Video Update 1.0 to fix black screen on resume for mid 2010 models.

Even though I can say that many people argue that the problem got fixed with a logic board replacement, this is actually some sort of policy of apple. Once a friend of mine got his iphone broken, it was not physically broken, and the problem could be easily fixed through a simple reinstall of IOS, but instead of that the apple care, just gave him a completely new iphone.

It is possible that your logical board could have a fix, but instead of making fixes, to assure some sort of quality control, they prefer to replace it, and be sure that your problem have actually been gone.

I'm saying this because, people reading may think that the problem is a hardware one, but I do see this problem as a software one, and people who are getting that loagic board replaced is actually a consequence of apple's policy concerning product quality control.

It's good to see that people are getting fixes, but I can say as well that the home made fix of AGPM.kext also does the trick. And people should not think that a fix will come with 10.7.3, the same way that the fix for black screen for mid 2010 didn't come with 10.7.2, and actualy came with "Video Update 1.0". Critical bugs will not come with maintenance updates.

Also people should check around release history, that every single operating system that is release, either apple's, microsoft, or linux distributions, the first 4 or 5 months are around people saying something is very wrong with it. The same thing happened with SL (different things), but it did happen, otherwise, we would have stayed at 10.6.0 and not be at 10.6.8 right now. Lion is actually using some technologies that are brand new, one of them is openCL (brand on usage not existance), so that means that there wasn't many testings over this technology before Lion. So for those that sees it, they do expect a little grip at first.

What I mean in sum is: Lion still has some bugs (mainly this one) which can be fixed by software changes, if you look for apple care, they may give a completely new hardware, but not because your hardware was bad,actually it is an apple's policy to assure quality. And so if you have SL and don't want to dig in the files to check for a solution, just wait apple fix this and, well, you will know through the forums when people start saying "Hurray Apple fixed it" and etc.

Hi terry i googled for it n found it. anyways ultimately i applied ur info plist fix by removing the p3 history length value from device id 029 and 034 . just a side note if u see in system properties under graphics/displays u'll see GT330M as device id 029 and intel HD graphics as device id 046 . device id 034 is as u correctly mentioned GT240M and not present in macbook pro 6,2 ie our system . getting back to the topic ur fix works and now i can wait for 30 seconds before entering the password at login screen. Thanks a lot terry ur a champ

Raj: Good to know the kext info.plist modification worked for your MBP 6,2.. I just wish someone could come up with a similar fix for other Mac models.

Clearly, WE know that a straightforward software patch - the kext info.plist - will definitely fix the SBBoD-freeze problem for those of us who have MacBook Pro 6,2.

This may not help others who may have an actual hardware problem.

And there may be a few Apple service people who are actually using the same fix that we discovered, for some cases.

But diogenque has a point: A simple patch release would fix the problem for most MBP6,2 owners. but probably not for all of us.

Hi terry an update. it is still hanging in 1 out of 3 boots and the safari and mail apps are crashing now . can u just put down a step by step guide . i may be doing something wrong

Raj: I have posted "how to ..." steps once or twice before on this thread. But the simplest way to do it would probably be to somehow get a copy of your original

/System/Library/Extensions/AppleGraphicsPowerManagement.kext/Contents/info.plis t

file from an up-to-date Snow Leopard 10.6.8 installation and use it to replace the one in your Lion machine.Also might be best to get a local Apple Certified Tech to do it for you. If you have Time Machine backups that would ba simpler way to recover the kext file than a reinstall of Snow Leopard.

Another Approach is th swap in a new (large capacity) dual-boot hard drive with both Snow Leopard and Lion on it - and use that to play with Lion unril it's ready for prime-time.