Well I downloaded the keychain update and my mouse still won't respond upon wake up so its hasn't fixed the problem for me.
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.
Freezing with 10.5 on iMacs?
- Thread starter colorspace
- Start date
- Sort by reaction score
Wait, so did this update fix the lockups? You say it fixed it, yet you also say your mouse still won't respond upon wakeup.
Sorry it was typo that I have corrected. I meant to say that the keychain update hasn' t fixed my problems.
The update is some keychain update or something, anyway, it worked. No more lock ups on anything. I have put it through the mill and nothing.
I am convinced they fixed it in the update.
That fix has NOTHING to do with the iMacs freezing...
Hmmm.
I hear ya, but mine is either fixed by the update or just magically started working properly on it's own. I have loaded this thing down with all the graphics intensive programs I could give it and it hasn't skipped a beat.
What are your thoughts?
UPDATE...
Freezing again....
I hear ya, but mine is either fixed by the update or just magically started working properly on it's own. I have loaded this thing down with all the graphics intensive programs I could give it and it hasn't skipped a beat.
What are your thoughts?
UPDATE...
Freezing again....
It happens to me sometimes when I just log in from a fresh boot up. Give it time and it may return, I'm afraid to say.
But doesn't that confirm that it's not a hardware issue after all? If it's a hardware issue the freezes should remain constant.
IT freezes... brr... damn winter!
It was running almost perfectly (downgrading my iMac to 1.0 update)... now... with Leopard we're in constant freezing mode (guess it "includes" the 1.1 imac update).
Apple really makes me sad this time, I am thinking of all PC switchers who bought a bugged iMac and makes me laugh... and cry a bit.
Apple solve this problem OR clearly tell us that is an HW issue before our warranty goes out.
It was running almost perfectly (downgrading my iMac to 1.0 update)... now... with Leopard we're in constant freezing mode (guess it "includes" the 1.1 imac update).
Apple really makes me sad this time, I am thinking of all PC switchers who bought a bugged iMac and makes me laugh... and cry a bit.
Apple solve this problem OR clearly tell us that is an HW issue before our warranty goes out.
I have now noticed that if I wake my machine via the mouse, I can move the cursor but if I wake it via key press, the cursor won't move and I have to do shutdown to get back in control. Weird.
I think you are experiencing a different problem from the rest of us...
Every time my computer freezes I am still able to move the cursor.
Yeah, the classic freezing iMac is the video stops but everything else keeps going.
I just discovered in another thread here that iMacs do not all have the same ROM revision for the 2600 Pro video chipset.
Mine has the 212 revision. (no freezing or other flaws in performance or reliability)
Others have the 207 revision.
https://forums.macrumors.com/showthread.php?p=4404932&posted=1#post4404932
Mine has the 212 revision. (no freezing or other flaws in performance or reliability)
Others have the 207 revision.
https://forums.macrumors.com/showthread.php?p=4404932&posted=1#post4404932
Are you sure that these different ROM revisions might be attributed to the 24" and 20" screen sizes?
The 2 different revisions in that thread are from 2 different sized computers...
Yes, that might explain the difference in the ROM revision, although the display itself should have a profile that defines the default resolutions and display characteristics.
Otherwise, connecting a 23" ACD to the iMac would result in incorrect resolutions and display profile.
For all intents and purposes, a 2600 pro should just be a 2600 pro, and the ROM should always be the same, regardless of the display it happens to be connected to.
Otherwise, connecting a 23" ACD to the iMac would result in incorrect resolutions and display profile.
For all intents and purposes, a 2600 pro should just be a 2600 pro, and the ROM should always be the same, regardless of the display it happens to be connected to.
In Theory....
You would think that the iPod touch and iPhone share the same screen (as advertised), but they don't... You Never know with Apple.
I honestly think this is a software issue.
Don't think it is overheating because the temps I see are very normal for a modern day GPU.
APPLE LETS RELEASE THIS FIX ASAP!!!
20 and 24 iMacs use the same computer; just the display differs.
(I can't imagine why ATi would have two ROM revisions for the same chipset anyway, unless some iMacs are simply receiving earlier revisions of the video chipset.)
(I can't imagine why ATi would have two ROM revisions for the same chipset anyway, unless some iMacs are simply receiving earlier revisions of the video chipset.)
I'd had no problems until I enabled spaces.
Once enabled, my screen, without notice would sleep although the machine was still active and when the machine was woken extreme artefacting was usually followed by a kernel panic.
Anyone else enabled spaces?
I have a 20" from a month ago with the 212 ROM, which is what the 24" machines were running in the linked thread.
The only problems I've had with the display was related to .plist corruption.
Which sucked had to delete all Apple preferences -- and set the machine up again.
One of two apps corrupted my system, and I'm going to likely have to risk running one of them to rescue some data.
Fresh install of Leopard on to my 24" aluminum iMac. Had to load Tiger back on because my iMac became COMPLETELY unusable!!!! Freezing, Freezing, FREEZING!!!!!!
Things were working perfectly under Tiger until the last software/driver update. That is why the spotlight has been on drivers and software.
Leopard has improved performance. While better, still not perfect. Blizzard has also said they there has been great strides done on fixing this issue. These driver issues happen with new hardware.
Mine freezes randomly in OSX. Less so in Windows. I am hoping for a fix in the next few days as I really want to put Leopard on it.