FireWire fried by power cut?

Discussion in 'iMac' started by Phil.E., Dec 20, 2009.

  1. Phil.E. macrumors newbie

    Dec 20, 2009
    Someone switched off the power to my iMac the other day. Since I've rebooted:

    a] System Profiler shows no awareness of FireWire ("Unable to list FireWire devices" in red)
    b] Every boot takes about five minutes, 3+ of which seems to be spent waiting for a response from the FireWire socket (the logs show a 3-minute gap followed by a line that goes something like this:
    "/usr/lib/exec/hidd: Timeout waiting for IOKit to be quiet")
    c] if it's idle long enough to go to sleep, it goes into a kernel panic (the last line in the log before the panic says
    "kernel[0]: IOPMSlotsMacRISC4::determineSleepSupport has canSleep true")

    b] looks connected to a], but I can't see any connection with c] (apart from the reference to IO).

    This is a last-generation PowerPC G5 from 2005, recently fitted with a new logic board after repeated kernel panics (where 'recently' = 'over 90 days ago'). I'm wary of doing anything too drastic with it, as my TM disk and my alternative boot partition are on a FireWire-attached drive & are hence both inaccessible precisely when I'd most like to see them. I have tried flashing the PRAM, though - it made no difference at all.

    Any thoughts on what's going on and what (if anything) I can do about it?

  2. ljonesj macrumors 6502a


    Oct 20, 2009
    Kingsport TN
    no good can u unstall the fire wire from the device listing then reboot to see if will come up i know on windows sometimes it looses usb and u ahve to to do that to get it to work again
  3. Alrescha macrumors 68020

    Jan 1, 2008

    "If the issue persists, try these steps:

    Shut down the computer.

    Disconnect all devices and all other cables, except the keyboard and mouse cable(s).

    Disconnect the computer from the power outlet and wait for 3 to 5 minutes.
    Plug the computer back in and turn it on.

    Reconnect the device(s) (one at a time if there is more than one) and test. Test with each port if you have more than one."

Share This Page