Apple has posted a new update for the MacBook and MacBook Pro which corrects an incorrect default setting on some MacBooks and MacBook Pros:
Article Link
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MacBook, MacBook Pro Software Update 1.0
- Thread starter MacRumors
- Start date
- Sort by reaction score
Apple has posted a new update for the MacBook and MacBook Pro which corrects an incorrect default setting on some MacBooks and MacBook Pros:
Article Link
My MBP has been absolutely perfect for the last four months. No yellow screen, no static through the headphone jack, never had a kernel panic.
I installed this update and now I'm having serious banding issues on my screen... it looks like there are bands moving up my screen; although I don't really understand why an update to enable journaling would create display issues.
I don't know what to do!
I installed this update and now I'm having serious banding issues on my screen... it looks like there are bands moving up my screen; although I don't really understand why an update to enable journaling would create display issues.
I don't know what to do!
I checked disk utility and I have journaling enabled, and yet software update still finds this update and says I should install it.
Why would this be?
I'm nervous! My system is running very well as it is!
Why would this be?
I'm nervous! My system is running very well as it is!
I'm in the same boat as you for my sisters MB. Journaling is enabled, so do I just ignore this update forever, or install it anyway knowing full well it's not going to do anything.
I booted off the disc afterwards and my volume passed verification fine.
That's weird. I had noticed that it wasn't Journaled when I ran Onyx. Since then, I've done an Archive and Install so it's all better.
By the way, I installed the update (but obviously didn't do the rest of the steps since it's already journaled) and nothing different happened.
By the way, I installed the update (but obviously didn't do the rest of the steps since it's already journaled) and nothing different happened.
AMAZING!!! After several months of my 17? MBP deciding it didnt want to boot, constant FSCKs and the such, calling Apple, and visiting several stores. They finally found the problem!
Too bad I already figured it out a few weeks ago and fixed this myself.
Oh well glad to see they are taking care of others.
Too bad I already figured it out a few weeks ago and fixed this myself.
Oh well glad to see they are taking care of others.
Disk Utility
Select Macintosh HD
Check the "Format: " at the bottom, should be "Mac OS Extended (Journaled)"
Well, damn. I've had now 4 instances of my 17" MBP (2.33 C2D) either corrupting its own hard drive beyond bootability (requiring reformat) or destroying it altogether (requiring replacement). I've had three different hard drives from two different manufacturers have failures in the past 6 months I've owned this machine. It's got to be something on the logic board that's off, as this can't just be bad luck.
I was hoping for an update like this that would (a) apply to my machine, and (b) patch something on the logic board. Sigh...
I guess for now my MBP will still continue to eat hard drives, and I'll continue never being able to trust it. :/ I look forward to my next AppleCare call, where I'll be within protocol to receive a new machine.
I was hoping for an update like this that would (a) apply to my machine, and (b) patch something on the logic board. Sigh...
I guess for now my MBP will still continue to eat hard drives, and I'll continue never being able to trust it. :/ I look forward to my next AppleCare call, where I'll be within protocol to receive a new machine.
Someone asked how this could happen-presumably someone just forgot to turn it on on their default software loadout.
This shouldn't be causing those issues, and shouldn't fix them. Enabling journaling should help prevent file corruption, but OSes never used to have it and did fine, and you shouldn't need that kind of constant intervention just because journaling was off. I'd think something else is wrong with your system (or software install).
No, it's only the newest models.
Yeah, sounds like something wrong.
This shouldn't be causing those issues, and shouldn't fix them. Enabling journaling should help prevent file corruption, but OSes never used to have it and did fine, and you shouldn't need that kind of constant intervention just because journaling was off. I'd think something else is wrong with your system (or software install).
No, it's only the newest models.
Yeah, sounds like something wrong.
Wirelessly posted (Mozilla/4.0 (MobilePhone SCP-2300/CA/1.0) NetFront/3.1 MMP/2.0)
haha, i noticed journaling was turned off about two months ago and wondered why. i knew it was supposed to be enabled...
haha, i noticed journaling was turned off about two months ago and wondered why. i knew it was supposed to be enabled...
Why didn't they mention this in the update - is it necessary? I verified and repaired permission and when i did verify HD it said it was OK.
Thisupdate is only for the mid 2007 (2.2ghz + 2.4ghz) models
looks like only a few where missed on there way out the door.
Think it'll fix BootCamp?
I *just* tried installing the public beta of BootCamp last night on my 2.2MBP, and it said it couldn't partition the drive b/c journaling wasn't turned on.
... Disk Utility says that it is Journaled, though... I wonder if this patch would fix it.
If people are getting screen banding issues with the patch, though, I'm reticent to install it.
I *just* tried installing the public beta of BootCamp last night on my 2.2MBP, and it said it couldn't partition the drive b/c journaling wasn't turned on.
... Disk Utility says that it is Journaled, though... I wonder if this patch would fix it.
If people are getting screen banding issues with the patch, though, I'm reticent to install it.
They did mention it in the update. It was in the description, where it said click *here* for what to do after installing.
If journaling is enabled this won't really do anything.
No banding here, but all this did was verify that mine was journaled...