This discussion is locked
-
All replies
-
Helpful answers
-
Sep 6, 2007 4:21 PM in response to vislanderby Eustace Mendis,I am not sure about this, but this is a procedure I have just completed on a friend's G4 that exhibited the same symptoms and had also got a clean bill of health from TTP. My feeling is that TTP does not really test the integrity of hard drive media, i.e. whether there are sectors on the drive (on which data already resides) that are bad.
I recommend that you back up your drive and reformat it, selecting the option to write zeroes. This procedure will cordon off bad sectors on the drive. (No doubt you know this is a long process; you can run it over night.) Then restore the original data. There are two advantages; the drive surface is verified comprehensively, and the drive is de-fragmented when you "restore".
Good luck, and welcome to the discussions. -
Sep 6, 2007 8:03 PM in response to vislanderby jpl,vislander,
In addition to Eustace's comments, may I ask a few questions?
-Did these freezes and panics begin after adding memory to the Lombard? Memory in the top slot of some Lombards can cause these symptoms.
-Open your System Profiler > Hardware > Hardware Overview; is the 512K or 1MB of L2 Cache reported as present? The Lombard is known for failing backside L2 cache. -
Sep 7, 2007 3:11 PM in response to vislanderby vislander,Hi Eustace and JPL,
Thanks for the speedy response.
Regarding the things you mentioned:
Hard Drive:
The problem occurs when I use either the 4gb drive (original drive) or the 80gb drive in the media bay. (The 80gb drive is new). Also if I do a soft restart after a freeze, there is no power to the media bay drive until I do a hard reset. What parts of the system are involved in the boot process and are responsible for recognizing the start up drive? (Note a hard reset always makes the 4gb drive the start up drive.)
Memory:
The lower slot has 64mb (the original), the upper slot has 256mb bought in 2003 when I moved to OSX. Perhaps one or both is preparing to fail in a way that causes a freeze. Is memory failure binary or does it come in spasms?
Cache:
I am away from home but will check this out on Monday.
Again thanks for the thoughts and I will keep you informed.
V -
Sep 8, 2007 7:48 PM in response to vislanderby jpl,V,
Looking at the tests in TechTool Pro, running the full suite does test the L2 cache but take a look at your L2 cache as I described anyway.
Bad RAM is one of the prime causes of kernel panics and freezes. Here is an excellent troubleshooting site for KPs:
http://www.thexlab.com/faqs/kernelpanics.html
If your hard-reset means resetting the PRAM, this would explain why your powerbook always defaults to the internal HD. Startup volume selection is stored in PRAM and the internal HD is the default.
Regarding your media bay HD: There have been similar reports from other Pismo owners having problems with their media bay devices under OSX. This is usually the complaint: They cold start successfully with the optical drive in the bay; if they hot-swap the optical drive for a VST Zip100 drive, for example, the 'book freezes or just does not see the VST drive. Restarting recognizes the VST drive but then they have the same problem hot-swapping again. The usual fix is a deep flush of all the caches in OSX using a third-party utility like YASU, available at VersionTracker. If you try such a procedure, uncheck everything but the caches...see if in fact this solves the problem.
However, your problem may be different. Try this: When up and running from the 4GB HD, swap your media bay devices and see if you have the above problem.
In addition, if you get a freeze when booted to the media bay HD (and the media bay HD is the selected volume in the Startup Disk panel), force a shutdown of the powerbook. I believe pressing the power button until it shuts down works on the Lombard. Now try a cold start and see if the media bay HD will boot the Lombard. There is a difference between a soft restart and cold start but I can't tell you what that is. -
Sep 10, 2007 4:37 AM in response to vislanderby vislander,Hi jpl,
As Eustace suggested, I checked System profile anyway. The cache is showing as expected. When I check RAM it displays the correct numbers (64 and 256) but under type and speed it displays "unknown". Now these cards were supplied by Apple and (I believe) used to display the correct data.
I am leaning towards a memory problem. Time to buy new RAM?
The media bay will swap in and out without a problem.
I will zero out the 4gb default drive as a final check.
Thanks
Vislander -
Sep 10, 2007 8:18 AM in response to vislanderby jpl,Vislander,
I would try to make sure the RAM is at fault if zeroing the HD does not help. There is the possibility it could be some other component. MacFixIt has a tutorial on running Memtest or Rember:
http://www.macfixit.com/article.php?story=20050524014158525
If possible, I would run Memtest in Single-User Mode to limit the amount of memory grabbed by OSX. -
Sep 10, 2007 10:27 AM in response to vislanderby vislander,Hi jpl
Memory Failure!
I ran the memory test program and it reported memory failures in some of the loops but not others.
It would appear that the some of the ram has become borderline wrt specs.
I am convinced that it is not the hard disc because it happens with any drive that is designated the startup drive.
I will replace the ram and try again
Thanks for the help and extensive references that you provided.
Vislander -
Sep 10, 2007 12:07 PM in response to vislanderby jpl,Vislander,
I am glad you found the problem.
Please be aware that the early iMac, Wallstreet, and Lombard take special 256MB modules due to their Grackle memory controller. The 128MB and smaller can be generic if they meet the Lombards specs.
Here is an example:
http://eshop.macsales.com/shop/memory/iBooks-PowerBooks/G3-Lombard/