severe boot problem on powerbook g4

darknote

Registered
Hi there,

The job that i am affiliated with owns a Powerbook G4 that was purchased in 2004. in the past few months it's been having some freeze-and-then-boot problems which after some rebooting and resetting has come back fine, but today i've hit a brick wall in terms of troubleshooting.

when my coworker first called me up, he said that it froze and when he rebooted it gave the prohibitive sign. he tried to reboot again and it did the initial chime sound, but the screen remained black.

i went over to troubleshoot. of the twenty or so times that i attempted to boot the machine, it would chime and then stay black every single time except twice:

- one was in single-user mode (command-s). I ran fcsk -yf and it came back and said that everything was okay. when i hit "reboot", it booted up, but as soon as i attempted to put in my coworker's jump drive to backup files he had not updated since yesterday, it froze beyond help.

- one was a random occurrence, but rather than boot it gave me a kernel panic screen with a 0x300 kernel trap error of which i was not able to garner useful information.


I tried the following to boot up:

-resetting pram. It did not successfully reset the pram, screen remained black and did not chime a second time.
-single-user mode. This was successful once as stated above, but did not work again.
-holding down [shift] (to disable extensions?). Again, did not get past black screen.
-holding command-v. i'm not sure what this was supposed to do, but it did not do anything different.
-holding down C with a boot disk. the DVD drive churned and was clearly spinning the whole time i was holding down C, but it still did not move past the black screen after the initial chime.

i have not yet tried target mode to get the files off that we need - i'll likely do that later today, but i want to address the root issue because this is beyond my troubleshooting experience. Even when there have been certain issues that i've had to deal with, i've never gotten to a point where it refuses to move past the initial chime with no indications whatsoever.

A few other notes:

some months back when we were having problems, i did reinstall the OS (with Tiger, not Leopard). I did a clean install that separated the previous system folder as opposed to overwrite (i think that's called "archive and install" now). This seemed to resolve the issue for a few months before it started acting up again.

i'm fairly positive that in the time that we've reinstalled the OS and even before, the only software that was installed were an upgrade of MakeMusic's Finale and a copy of Microsoft Office X including Entourage.

Push comes to shove, i'm going to take it to a genius at an apple store to diagnose, but i was hoping that i could get an idea from people here. everything i see points to this being a hardware issue. does that seem likely? If so or if not, does anyone have any words of wisdom? Is the whole thing just f'ed, should we try to replace the CPU?...

Thanks very much for your input.

-d
 
Try swapping around the RAM. Some of the Powerbooks are famous for bad RAM slots on the logic board. If I remember correctly it is the lower slot that goes bad. Apple actually had a Repair Extension Program (REP) out for some of the Powerbooks which has since expired. So try one RAM chip in the upper slot then lower slot. No love there try the other chip in either slot. It could also just be a bad RAM chip as well. I had a Powerbook in last week where it wasn't the slot but the chip itself and had the exact same symptoms. Took out the affected chip and it worked fine.
 
Last edited:
thanks for the recommendation. we put the ram in the upper slot and it seemed to *sort of* improve things in that i was able to go into safe mode successfully again (again, fsck said everything was okay), but i still was not able to get it to boot normally or reset the pram or boot by DVD.

it's also hard to know whether or not it was putting the ram in the upper slot that did it or if it needed to sit for a while. i'm going to let it sit and then troubleshoot it some more this evening. i wish i had some spare RAM to see if that would help the problem.

thanks!
 
hi,

just to follow up on what's occurred since this first happened in case anyone is curious:

putting the ram into the upper slot did not end up fixing the problem.

When i put the computer into target mode, it was able to mount, but as soon as i tried to copy over some relevant files for backup purposes (mostly pdfs and finale files), it ended up freezing my computer; not with the black "you must repower your computer" screen, but it just froze.

I restarted the computer and tried to mount the drive again, but this time the drive in disk utility was greyed out and not mountable. I tried to run first aid on it, and it basically said, "sorry, can't help you."

I downloaded a copy of Drive Genius, and while it wasn't able to repair the drive, it gave me a more specific error message, something about a btree error at a particular node. I googled that and found that most people recommended DiskWarrior to deal with this sort of problem.

I've never used DiskWarrior, and am now convinced i need to buy my own copy. I found an illegal copy of it online that i downloaded to test the software and see how it did, and it was able to do what the other programs were not able to do. it rebuilt the directory tree to a point where the laptop's hard drive could at least mount as a target drive and i could take the files off.

After that, i attempted to boot up the computer in the various modes and with the various options, and did not meet with any success. However, every time i put the hard drive up in target mode - even before i repaired it - it pulled up the firewire screen and recognized that the drive existed even if it couldn't mount it.

So at this point i think the problem was two-fold - the hard drive needed rebuilding and there could be an issue with the RAM - and now the issue may still be the RAM, but at least the hard drive isn't having problems anymore.

As per work instructions, i'm not going to be dealing with the RAM myself, i'm setting up an appt. with a genius guy over the weekend.
 
Its a good possibility the RAM corrupted the directory structure when the contents in memory were written to the disk to where you needed to run DW to straighten it out. I've ran into that a few times. If it was saying overlapping files when running DW, that would be a clue. With test RAM its pretty straightforward to troubleshoot, without test RAM its speculation.
 
Back
Top