G5 imac wake up problems

Thank you very much, Rod. I may just have to attempt to reset the PMU if having reset the PRAM has no effect. The article you referred me to has two sets of instructions, however, one for a PB G4 12" and another for a PB G4 867 MHz. Which set of instructions should I follow if mine is a combo of these paramaeters, a PB G4 12 867MHz, if you don't mind me bugging you any further?

Thanks so much once again,

Tabeer

The instructions for the PB G4 12", Tabeer. (The reference to the 867MHz is to one of the models of 15" titanium PB. Clear as mud, eh! )

Cheers

Rod

Hello Rod,

Apologies for troubling you once again, but it seems, whether the PB problem goes away or not following my having also reset the SMU, I seem to have compounded my troubles with the iMac. As I mentioned in my last message, I had spoken to an Apple Tech, but was unsure if the problem had indeed been resolved. The test would be time. Well, approximately 20 hrs following my last having checked to determine the responsiveness of the computer upon being roused from sleep, the computer once again had frozen up. Once again when i attempted to restart the computer, it took a couple of attempts. However, when the startup did proceed all the way to completion, the computer would become responsive. Even that bit of normalcy, however, has now been denied to me, after the steps I apparently took in consultation with another Apple tech I spoke with today, following the earlier problem's reappearance.

When I called Apple today and mentioned that I had been following this article http://docs.info.apple.com/article.html?artnum=301283 sent to me after my discussion yesterday, he again walked me through resetting the PRAM. During my discussion with him I was only able to elicit the startup chime during the reset process twice even though he indicated that it should happen thrice. (Later when attempting to trouble shoot on my own, I was able to elicit the apparently requisite third chime in attempting once again to reset the PRAM, apparently to no avail, however). The tech also walked me through opening the back of the computer (apparently, he was following the troubleshooting steps given in the article that I had been sent) and turning the computer on and off via the small switch next to the fan within the computer. When all three LEDs turned on, I closed up the back and the computer seemed to be working fine.

A couple of hours later, however, the computer was again irresponsive to being roused from sleep. I reset the PRAM, eliciting the three chimes prior to startup. However, when and if the computer proceeded all the way through startup, either it was unresponsive, no motion at all via the mouse or upon proceeding to the desktop screen, the screen would suddenly become enshaded and a sign with black background and writing in several languages in white would indicate to me that I ought to restart the computer. However, upon restart, either of the same tow outcomes would result at the end of the startup process-- a normally brightened screen of the desk top with no response or a shaded desktop screen with the sign to restart, also with no mouse response.

Apparently in opening up the back and starting the computer via the small switch nearest to the fan (as indicated in the image given my the article) I was resetting the SMU. This is strange I've come to think as I never pressed the actual SMU button below the power button. I am awfully flustered right now as it seems I've taken two steps backwards since my discussions with the Apple techs began. Before, at least when my computer would restart i had at least a temporarily responsive computer; now I cannot get my computer to function minimally, despite the fact that all three LEDs in the enclosure in the back turn on. All this took place, of course, after Apple had shut down for the night US time (the morning actually in Bangalore where the Techs seemed to be based), and I was unable to call them back.

I am clearly in the muck if I was only in rather muddy waters earlier. Does this turn of events with the computer operating the way it is presently have any good outcome in your experience? I am not sure,I can get away without expending some resources in taking the computer in for examination via Apple, as unfortunately I did not bother to reup on Apple care last year. Not awfully bright in hindsight. Any words of insight would me most welcomed.

Thanks,

tabeer

Tabeer,

I'm increasingly thinking that your particular problem is hardware related. Repeated "Kernel Panics" (signalled by the "sign with black background and writing in several languages in white?) like this are likely to be the product of something more than simply background software problems.

Just to be clear about your situation here (which is a little different to that experienced by the other people with problems in the thread) I'll try and sumarise the situation:

1) You have a "First generation" iMac G5 currently running MacOS 10.3.9.

2) You have tried multiple "PRAM resets"

3) A PRAM reset has sometimes appeared to fix the problem for a time, but it continues to recur eventually, and sometimes the PRAM doesn't resolve things at all. Further, teh problem seems to have been getting progressively worse.

4) You have no peripherals other than an Apple keyboard and mouse connected to the computer.

5) You have repaired the HD directory (ie "repair disk") using Disk Utility.

6) You have followed the steps in http://docs.info.apple.com/article.html?artnum=301283 up to the point of establishing that the three lights come on when you press the internal power button on your iMac (outlined in para 10 of that article). You have never pressed the SMU reset button (as outlined in para 11) , because the three lights come on (as described in para 10) without you having to do so.


If this is correct then you haven't actually reset the SMU at any stage, so it would be worth trying. In other words, follow the steps outlined in para 11 of http://docs.info.apple.com/article.html?artnum=301283, pressing the second button even though the third light is already on.

If this doesn't resolve the issue, and my summary of what you have tried is correct in terms of the other matters, then I think you should take your computer to an Apple service provider. I think you probably ARE experiencing a failure of the type which will be covered by the iMac G5 Extension Repair program.

Other slight possibilities could include defective or badly seated RAM , but a motherboard issue, despite the three lights, sounds like the most probable explanation.

Let us know how it goes.

Cheers

Rod

Rod,

Thank you for your response: grateful. I spoke with a tech this morning, explaining the situation. We repaired disk under the installer. At first run Disk Utility indicated it was unable to repair a volume, (can't recall exact language unfortunately), that "minor repair" was needed on a volume. We ran it once again and DU indicated that the volume had been repaired. We quit DU and reopened it and repaired disk again. Again the message indicated that a repair had been made. We made note of the fact that if a repair had been made previously, then DU ought not have had to (re)make a repair, as it had noted it had done. We repaired permissions, generating a significant degree of data to my view, given my experience with Macs for the past couple years, and again repaired disk, this time generating no message indicating either requiring repair or having been repaired and the message that the Macintosh HD appeared to be OK, or perhaps was OK, I forget the words. In any case, the computer started up and things seemed to be working--the mouse, other applications. I am waiting though to see how long this lasts. The representative told me re-contact them if the computer fails again when I explained to him that I was apprehensive over the permanence of such a fix, indeed that I had myself ran disk repair from the installer menu a couple of days ago, and that Disk Utility had indicated to me that nothing had been in need of repair. The necessity of repairing the disk then had popped up either through the steps I took in the course of my dialogue and the steps we took with Apple represntatives, or on its own, as the computer was run over the last 48 hrs or so. One item that it seems has not returned to its previous state, (if indeed everything else has), is the strength of the chime upon startup. Following the apparent reset conducted with the consultant of the inner power switch, the chime's decibel level has been reduced, and I made a note of it to the consultant yesterday as well as to the one whom I spoke to earlier, elciiting some mixed messages. The consultant yesterday explained the lower decibels to the fact that something had been reset, (the SMU, despite our not having manipulated the SMU button?). The one, whom I spoke to today, while inquiring about the sound level of the computer (at maximum output), stated that the chime should be at its normal degree of loudness. I am wondering if the reduced chime audio may not have something to do with the Kernel Panics that you've identified, and if so, that these may return.

Finally, I did not wish to go in and reset the actual SMU switch without it being done in consultation with, and documented by, Apple. I suppose that speaks to my degree of being technically challenged. As the machine seemed to cooperate following the procedures that I did undergo with the Apple rep, we did not go into the question of whether that ought or not be done. I also noted to the consultant (though I am not sure he made a note of it) that the iMac was a "First Generation" model and also that its couple paramaeters included it within the extended repair program. Notably, unlike the original representative whom I spoke to, he did not rule out that the computer could qualify for repair within that provision by Apple. The original representaive had stated that because the machine did not seem to be lacking power, and that the hardware check had gone OK, I most likely would not qualify.

Now, only to setup an appointment with the people at the local "genius bar" that may or may not prove incumbant. They are booked, apparently too many Apple users with difficulties in Austin.

Sorry for taking up your time, most grateful for the contact. Meanwhile to check on the machine....

Best,

tabeer

P.S. The intermittent PB issue with the blinking screen persists still unforunately after the reset of the SMU, but that is the least of my worries presently. Thank you so much again.

At first run Disk Utility indicated it was unable to repair a volume, (can't recall exact language unfortunately), that "minor repair" was needed on a volume. We ran it once again and DU indicated that the volume had been repaired. We quit DU and reopened it and repaired disk again. Again the message indicated that a repair had been made. We made note of the fact that if a repair had been made previously, then DU ought not have had to (re)make a repair, as it had noted it had done.

This is actually quite common with earlier versions of Disk Utility and OSX, Tabeer, and usually indicates fairly substantial directory damage.

With the Tiger versions of Disk Utility, DU will automatically check the drive again if it has to repair any problems. With the older ones, however, this had to be done manually. It is necessary to re-run Disk Utility after a successful repair because sometimes particular "repairs" to the directories will throw up further problems which were not evident on the first run. The mantra used to be "run disk utility to "repair disk" until you get a completely clean run".

Because the program now does this automatically it is much less of an issue than it used to be. But in your case , your Installer disc would have probably had the version of Disk Utility which came with OSX 10.3.6 (which I think is the OS version that shipped with your particular computer), even though your computer has been updated to OSX 10.3.9 (the first version which had the "automatic" re-run capability , I think). If I 'd thought about it I might have warned you of this, although, as your original check came up "clean" there wouldn't have seemed to be any need.

It is quite possible that the disk repair may have resolved your problem (athough why problems didn't appear on the first occasion you tried it is unclear).




The change in startup chime volume was probably caused by a PRAM reset, and probably isn't anything to worry about.


Cheers

Rod

This is actually quite common with earlier versions
of Disk Utility and OSX, Tabeer, and usually
indicates fairly substantial directory damage.

Hi Rod, Just to update you on what is going on. Of course after my last message when I went to check the computer it had again frozen up on waking up. So later that evening I called Apple. The agent listened to my story and said that we would probably be redoing everything only to find that later the computer would again not respond. He said he would explain my issue to a product specialist, and i felt that perhaps there had been some real movement at last. While taking note of the fact that my computer fit the parameters of the IMac G5s extended repair program, he said he wanted to try one last thing in order to rule out that this was only a software issue. He asked me to do an archive and install. After doing so, he asked me to immediately do a software update. I confess that after had rebooted following installation of disc 2 (Panther you know), I reflexively opened safari, which while responding in the dock, opened no window. (I then noted that the wireless signal showed no reception. I opened Internet connect and joined the wireless network. I attempted to open up a new window of safari, but safari wouldn't bite. I then recalled the words of the product specialist and opened up software update, installed all the available software. As the product specialist had not told me to run disk utility and reapair disk or verify permissions I am afraid I did not do so prior to the installation of the software. I wonder, however, if I've somehow ruined the purity of this test (to determine if my problem exceeds a merely software problem) in having opened up Safari, even Mail, and Internet Connect prior to installing the update to 10.3.9 along with other updates, as the product specialist seemed to warn that I not do? These are actions I reflexively take when going to the computer and I'm afraid i fell victim to habit here. If I did, I suppose I can always do another archive and install, if you advise in attempt to keep this test as uncontaminated as possible. There is more, however.

To attempt to check if disk utility would again indicate a repair being made under the installer, after having read your message that without a clean run by DU significant directory damage exists, I conducted this test. I'm afraid that that DU still indicated that one HFS volume had been repaired, even though it also said that the Macintosh HD was OK or appeared to be OK. I ought to write these things down I am sure, as I forget the actual language. Also, when the dock reappeared following the automatic reboot after the quitting of installer, it did so in a bit of a herky jerky fashion, not quite smoothly, which may or may not mean something, as I'm afraid I've become rather sensitive to the subtle indicators of the machine, a sign of directory damage, perhaps, as you have proffered.

Finally, Rod, when you suggest that DU repair of a voulme having been made is an indicator of directory dammage, would that be a software or a hardware issue?

Well, I've been told by the product specialist to give the computer a day to see what happens. Do you think I've compromised this test in some way? I hope I can get this matter resolved in some way, as I am sure we've all grown tired of my turgid messages.

Mere thanks is not enough to express my gratitude for bearing with me, but thank you.

tabeer

Mac OS X (10.3.9)

Karysheila and Rod: Your repair advice was right on the money! My computer is officially fixed!! I followed Karysheila's steps exactly and then did the disk utility repair disk from the start-up and it works fine now! Thank you Thank you Thank you!!! Have a great day!!