Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For those that have as many problems with the update like I did, here is a way to restore your old driver. I guarantee for nothing.
Download the 1.0 update from: http://www.fileavenue.net/index.php?action=categories&cat=1&pl=mac
Download Pacifist if you do not yet have it installed: http://www.charlessoft.com/
Drag the update package onto pacifist. Select the root named: Contents of iMacSoftwareUpdate1.0.pkg. Press install.
It will override all files that have been updated with 1.1.
Since then I did not have any further trouble.
Good information. Would have saved me from 20 minutes of doing an "Archive and Install" yesterday. :D
 
Hi,
I've had my 24" 2.4G iMac since the weekend after release and I had my first two lockups last night in quick succession. The first caused the mouse to freeze completely and no amount of force close or any other keypresses would help. I had to hold the power button to power off and on. I think I was doing a spotlight search when it froze.

After reboot I repaired permissions and there were a couple of repairs required but it locked up again a little while later where the mouse would still move but I couldn't click on anything and the keyboard was not responsive. Again I had to use the power button to reset. This time I also pulled out the power plug and waited 30 seconds before restarting - I did notice that the bootup time was much faster this time than after the first crash.

Okay since then but if I get any more crashes I intend to rollback my update until this issue is fixed. I'll check my log files for any information tonight and report back.

Cheers,
Craig.
 
Hi,
Well my machine just crashed again twice tonight - second time it crashed before it had even fully booted up... Not impressed Apple!!!

I have rolled my update back out and so far it seems to be back to normal. If only Apple would give more detail on what they are fixing in each update then at least we could decide if we are experiencing the issue in the first place.

I must say I am very disappointed in this - I perhaps naively expected that I could trust Apple to issue only quality updates. Come on guys...

Craig.
 
Well, even though I reverted to update 1.0 using the method posted earlier in this thread I got another lock up this morning. As usual my mouse could still be moved around but nothing else would respond. I also got the ASIC error message in my system.log.

I have sent a complaint off to Apple via the feedback page and I hope to god they sort this out soon as it is really getting to be frustrating!

Cheers,
Craig.
 
For those of you with new iMacs suffering from freezing problems and graphical glitches, I strongly urge you to call AppleCare (If you didn't already).

I just did this, and was surprised when the chap said "I've not heard of that before" when I described the problems to him. However, I spent quite some time describing in detail what the problem was, and ultimately it was decided that my brand new iMac was faulty and would need to be sent in for repair.

I dread to think how long a repair is going to take, given how many new iMacs evidently have the same fault as mine (UI Locking up, graphical glitches/corruption etc). I would rather get an exchange or refund, but im outside the 14 day return plan.

Anyway, Call AppleCare, and see what they say to you. Then there is no excuse for Apple not knowing about the problem.

Good luck..
 
Luap,
I appreciate your suggestion but with the greatest of respect this may not be quite as simple as you are suggesting. The AppleCare people will certainly not be allowed to confirm that this is caused by a bug in software update 1.1 although this certainly appears to be the case. Either that or the software update has caused a hardware issue to surface. Applecare's only option is to suggest a replacement machine and by the time this has been completed there will most likely be a new software update to resolve the issue.

I personally intend to wait a little bit longer to see if a new update appears before I even think about going to the hassle of returning my new iMac. I would be more likely to take it to an Apple Store for repair too.

Cheers,
Craig.
 
yeah, the fact that alot of people with version 1.1 are having lockup problems and version 1.0 people are not says to me it is a software issue. mine has been up for 3 days now after reverting back to version 1.0 and still no lockups.
 
Craig, thats just it. Im not saying its simple at all. Personally, I find it a massive inconvenience (not to mention highly disappointing) that my brand new iMac is likely faulty, as confirmed by Apple themselves. I wish very much that a software patch would fix it instead, as it would be much less hassle, and i'd be prepared to ride the problems out a bit longer until such a patch is made available.
However, i've installed 2 patches now, and the fault is still very much there, which doesn't bode well.

If you take a look on the Apple discussion forums, you'll find not only many very similar reports there (i've posted there too btw), but also reports from people saying that almost identical issues happen on their new iMacs when booted into windows.
So the fact it happens in 2 entirely different operating systems would suggest a hardware fault too. It could of course still be shoddy graphics drivers in OS X and XP of course, but by this point its starting to look rather more unlikely.

As for AppleCare staff not being allowed to confirm bugs and whatnot.. If that is true, then its absolutely ridiculous.
If you would prefer to wait before returning yours, then by all means do so. But I still think that if your iMac shows these symptoms, then its a good idea to at least log the problem with Apple.
The longer people leave it unreported, then the less pressure Apple have to get on with fixing the problems (be it hardware or software). Leave it too long, and you also lose option to get a refund or exchange. I say, the sooner its reported, the better it is for everyone affected.
 
Craig, thats just it. Im not saying its simple at all. Personally, I find it a massive inconvenience (not to mention highly disappointing) that my brand new iMac is likely faulty, as confirmed by Apple themselves. I wish very much that a software patch would fix it instead, as it would be much less hassle, and i'd be prepared to ride the problems out a bit longer until such a patch is made available.
However, i've installed 2 patches now, and the fault is still very much there, which doesn't bode well.

If you take a look on the Apple discussion forums, you'll find not only many very similar reports there (i've posted there too btw), but also reports from people saying that almost identical issues happen on their new iMacs when booted into windows.
So the fact it happens in 2 entirely different operating systems would suggest a hardware fault too. It could of course still be shoddy graphics drivers in OS X and XP of course, but by this point its starting to look rather more unlikely.

As for AppleCare staff not being allowed to confirm bugs and whatnot.. If that is true, then its absolutely ridiculous.
If you would prefer to wait before returning yours, then by all means do so. But I still think that if your iMac shows these symptoms, then its a good idea to at least log the problem with Apple.
The longer people leave it unreported, then the less pressure Apple have to get on with fixing the problems (be it hardware or software). Leave it too long, and you also lose option to get a refund or exchange. I say, the sooner its reported, the better it is for everyone affected.

Sorry, I thought you were only talking about issues arising from update 1.1 (as per the thread title) which is why I was taking the view that the update caused the problem and therefore another update might fix it again.

However, if you are talking more generally about video artefacts and locking issues then fair enough, it may be a hardware problem. In any event I would prefer to have a clear understanding of the problem before I go to the hassle of an exchange or refund. The iMac I have just now seems to have a good screen with no dead pixels and there are no strange noises or other problems so the last thing I want is to exchange my machine for one with 4 dead pixels only to find that it was a software update issue that was at fault.

I have experienced the video artefacts and locking problem when running bootcamp and 3D games (counterstrike and FIA GTR racing sim) but bootcamp is still in beta and the iMac is only just out so I think it only fair to give Apple some time to sort this out first. The odd thing is that the problem only occurs sometimes and if it happens then it happens almost immediately and if it doesn't happen within a couple of minutes then I can play games for hours without any issues. I am hopeful that future graphics driver updates will resolve this.

Anyway, good luck with your replacement, I really hope it goes well for you. I don't know if Applecare will admits bugs or not but Apple usually keep their cards close to their chest don't they, especially if they potentially have a design flaw on their hands (see recent press about issue in Denmark for example).

Let's hope it's just software issues or the iMac reputation will take a knock!
Cheers,
Craig.
 
In any event I would prefer to have a clear understanding of the problem before I go to the hassle of an exchange or refund. The iMac I have just now seems to have a good screen with no dead pixels and there are no strange noises or other problems so the last thing I want is to exchange my machine for one with 4 dead pixels only to find that it was a software update issue that was at fault.


yeah, that's why i have not taken mine back. i figure i still have 3 years left on apple care anyways. version 1.0 runs terrific for me and as it stands now i have no issues.
 
let us know in a week, please:eek::apple:

Hmm? Why a week? I thought I had updated after that post already. If not then perhaps it was another thread. But on my iMac the problem still exists. But after the 1.1 update it appears to only be UT2004 that suffers now. Everything else works as it should. So perhaps its just a minor glitch that lurks and only affects limited software like UT.

I spoke with some senior Apple tech today. He wanted to take the iMac in to check it out, and offered to send me a new iMac in exchange. I didnt take them up on the offer, as im not sure a new replacement iMac will be any better in my case. Plus i don't want the hassle of reinstalling everything etc. Instead i sent him some crash log files and screen shots. If they still want to take it back after that, then so be it.
[EDIT] Does exactly the same in XP now.
 
Another update.. My iMac is going to be exchanged for a new one. Apple requested I return my iMac in its current state, so that they can reproduce the problem and look into it it themselves. Evidently they still dont know what the problem is and need to research it.
The technician I spoke to said it was not a widespread issue, but that there are a 'couple' of known cases of problems.
His words, not mine ;)

Heres hoping the replacement is good..
 
Another update.. My iMac is going to be exchanged for a new one. Apple requested I return my iMac in its current state, so that they can reproduce the problem and look into it it themselves. Evidently they still dont know what the problem is and need to research it.
The technician I spoke to said it was not a widespread issue, but that there are a 'couple' of known cases of problems.
His words, not mine ;)

Heres hoping the replacement is good..

Hi,
Thanks for keeping us posted on progress and I too hope that you get your issue solved with a new machine. Well actually, I hope that it's a software issue but either way lets hope that we all get things back the way they were... ;)

I must say again, as a convert from Linux to OS X I really miss the "openness" of Linux with respect to fixes and issues. I just don't understand why Apple don't publish their issues and fixes like the open source world does. They don't need to divulge technical details or source code and they wouldn't need to provide this information to everyone actively - just make the information available for those who feel the need to know.

Good luck,
Craig.
 
Another update.. My iMac is going to be exchanged for a new one. Apple requested I return my iMac in its current state, so that they can reproduce the problem and look into it it themselves. Evidently they still dont know what the problem is and need to research it.
The technician I spoke to said it was not a widespread issue, but that there are a 'couple' of known cases of problems.
His words, not mine ;)

Heres hoping the replacement is good..

Were they actually able to reproduce? I'm still waiting for the Apple engineer who is handling my case to call me back...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.