Your ignorance is astounding. Nice personal attack, too. You could at least try to get the facts right.
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.
MacPro Harpertown Flaws - Leopard?? HELP!
- Thread starter darthraige
- Start date
- Sort by reaction score
Your ignorance is astounding. Nice personal attack, too. You could at least try to get the facts right.
Makes me wonder if this problem is isolated to just the 2600 and not the 8800GT. Makes me hesitant to order one because of this. I want one with the 8800GT but if it will freeze like the 2600 then I'll pass.
Could be anything. Until the 8800GT comes out, we won't really know. Let's just hope is SW related and the 10.5.2 resolves many of these issues.
If it was software related, why would a new machine fix it, and why wouldn't everyone be affected in the same way?
<worried>
<worried>
Great point. But the new 10.5.2 is likely to include driver updates, etc... and may address many of these issues. In darth's case, i believe it indeed was a HW issue.
If you look on the previous page you'll see that it didn't. I didn't think it would. I've been dealing with the same issue and it seems to be a pretty widespread problem from what I've read, and yes I'm sure it is the angered ones that are venting right now but that doesn't change the fact that it's not just an isolated incident. (forgive the run on sentence)
It reminds me of the recent iMac feezing problems others experienced. In fact, that's why I think that 10.5.2 will fix things (or at least some software/firmware update shortly thereafter will).
IIRC, something similar went down with the update to the newer iMacs.
In fact, I had a 24" aluminum iMac and when there was all that chatter about screen freezes, I didn't have any problems.
So, I guess it doesn't really have to affect everyone, right?
EDIT: Also might want to read this thread.
Computers can be quirky. There can be problems that affect only a percentage of them.
If it turns out that this is a widespread problem, it'll be dealt with in one of two ways. OS updates or firmware updates.
Some people reported no problems after getting their system replaced, so chances of it being software related is smaller (unless Apple is pushing some of the updates onto those new system they are giving to people having problems). I don't have a problem with mine (have mine on for the past 2 days), but I don't use the stock AMD/ATI card 
Some people reported no problems after getting their system replaced, so chances of it being software related is smaller (unless Apple is pushing some of the updates onto those new system they are giving to people having problems). I don't have a problem with mine (have mine on for the past 2 days), but I don't use the stock AMD/ATI card
There's either something glitchy with Leopard on the new MacPro or something glitchy with the ATI 2600XT card to be causing this problem. Happens on a restart or boot up every so often. Happened to me on the damaged MacPro, and now on the replaced one.
There's either something glitchy with Leopard on the new MacPro or something glitchy with the ATI 2600XT card to be causing this problem. Happens on a restart or boot up every so often. Happened to me on the damaged MacPro, and now on the replaced one.
Only reason I am saying software is "unlikely" to be the cause of the problem is that literally everyone get the same basic stuff, so if it is really software related, everyone should be seeing it, since it's happening on the "stock" configuration. It is not, so it's more likely to do with hardware, since some people did say the new system fixed the problem, and I assume they re-installed the same application that were in the old ones.
Since there is very little chance of someone getting access to another video card, so it's near impossible for almost anyone to confirm whether the video card or video card driver is causing this problem.
Okay, I understand what you're saying. The challenge is that this is real similar to what happened with the iMacs screen freeze issue. I had one of those iMacs and mine didn't have the freeze issue yet so many others complained that they did. Apple released a firmware update and it fixed this problem.
On the other hand, I have a new MacPro that is experiencing some sort of graphics issue and while I'm not the only one, there are some that aren't (yet).
So, like those others that had the issue with the iMac and were waiting for an update (wether that be firmware or software), I too am looking forward
to an update to fix this silly bug.
On the other hand, I have a new MacPro that is experiencing some sort of graphics issue and while I'm not the only one, there are some that aren't (yet).
So, like those others that had the issue with the iMac and were waiting for an update (wether that be firmware or software), I too am looking forward
to an update to fix this silly bug.
Never experience the iMac screen issue so I don't know, but if a firmware update can fix something like that, it usually means they are using BIOS or what not to "by pass" the hardware problems they are having. It can mean a lot of things (lower the threshold before fans come full blast, etc.), but at the end, it basically comes down to a hardware problem (probably AMD/ATI went cheap and ordered some "cheap" parts that doesn't work well with the released EFI/BIOS setting, or Intel did, who knows).
I am just using the old IT method of figuring out what the problem is
I am just using the old IT method of figuring out what the problem is
Here is a fix Mac Pro sleep problem.
Reset the PRAM (Boot the machine and hold ALT+COMMAND+P+R for 3 startup gongs)
Reset the SMC -> http://docs.info.apple.com/article.html?artnum=304123-en
Reset the PRAM (Boot the machine and hold ALT+COMMAND+P+R for 3 startup gongs)
Reset the SMC -> http://docs.info.apple.com/article.html?artnum=304123-en
Did that, still have the problem:
- Wakes from sleep, but screen won't return
- Wakes from sleep and restarts
Yeah, user peejack and a few others report the same thing. I'm now pretty confident that 10.5.2 will fix these issues.
BTW, you didn't happen to be in Las Vegas a couple of hours ago did you?
(just kidding)
Mines been asleep all day for the test. When I get home I will report on whether or not it restarts.
EDIT - Came home, woke up perfect. No restart.
Well that's a good thing. Glad to hear that the issues have minimized to the graphics thing. I just wish Apple would hurry up already.
Great to hear! Phew... so the debate whether these issues are SW or HW continues... I hope the 10.5.2 may resolve some of these issues (even though we know some is indeed HW.
Time will tell.
I've been using Firefox steadily and it hasn't frozen at all. 10.5.2 will be a blessing. lol
The only thing occurring here and there is this weird mirror effect on the dock. (As seen below.) Hopefully 10.5.2 is going to fix this. When it happens, all I have to do is restart it and fixes itself. But I haven't been getting any freezes so far... What's even odder is that you can't take a snapshot of the screen when it happens. Had to use a camera.
Did you use a real camera to take that picture?
If that is just a screen-shot from within OS X using the "Grab" utility, then it is not necessarily an indication of a hardware problem / failed graphics card.
The grab utility can only capture what the computer believes it is displaying. It cannot capture what is actually on the screen unless what is actually on the screen matches with what the computer believes it is displaying.
For example, if you have a stuck pixel (which is a defect of the video screen), you won't see that in a screen capture.
If you have weird artifacts showing on the screen which is being caused by the video card displaying garbage, then the screen capture won't get that either (because the computer doesn't know about the corrupted display).
Interesting you mention that. Never thought about it being the monitor. I took the picture with the camera, because when I did a screen grab it corrected it. Next time it happens I will switch monitors and see if it comes up.
Well, on the last Harpertown MacPro I would put it to sleep, and a couple hours later I would wake it up and it would just do a restart. No kernel panics. If I left it asleep for a few minutes and wake it up, it would wake up normally. On the current MacPro I am using now I don't have that issue anymore.