Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Diagnosing a bad FireWire port' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Diagnosing a bad FireWire port
Authored by: obiwan2u on Jun 16, '03 01:03:09AM
Hmmm, I recently had a problem booting my dual 867 MHz CPU G4, and after much gnashing of teeth, figured out that I had to unplug my Firewire CameraMate digital photo card reader (by MicroTechInt).

Whatever the problem was, it prevented the G4 from even booting up enough to open the CDROM door to boot of the emergency CD. Ie. I think it even prevented the firmware boot from executing (this is not a good feeling). All I had was a completely dark screen.

Unplugging the card reader made everything work fine.

I need to see if my card reader is bad and/or if the port on the G4 is bad. Hmmm, I hope the G4 hasn't gone bad.

Ben Slade

Put 030516 in the email subj to get mail thru to me.

[ Reply to This | # ]

Diagnosing a bad FireWire port
Authored by: ajayj3 on Jun 16, '03 10:17:52AM

This sounds like what I was experiencing -- as soon as you disconnect offending device, processes seem to continue...

Merely having a device connected is preventing the startup routine to run, so the port might not be fried. You can always volt-test the motherboard directly to test the hype.

In your case, as mine, I suspect it's something that could be fixed by resetting the PMU.

[ Reply to This | # ]