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

Click here to return to the 'Repair a broken FireWire interface' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Repair a broken FireWire interface
Authored by: on Nov 29, '05 09:30:21AM

I had an issue similar to this with my flash card reader. What I usually do is:
1) Unplug the device
2) Go in Apple System Profiler under Hardware>FireWire and refresh the screen with APPLE+R key.
3) Plug device back in and refresh the screen with APPLE+R key.
4) Put my compact flash card back in the device and it normally comes back on the desktop...

I don't know if it would work with an iPod or Harddrive, but it worth the try.


[ Reply to This | # ]
Repair a broken FireWire interface
Authored by: allanmarcus on Nov 29, '05 11:28:57AM

The same problem started to happen to me recently, and the only change was the addition of a $10 lexar (purple) firewire compact flash card reader.

[ Reply to This | # ]
Repair a broken FireWire interface
Authored by: jessifer on Oct 14, '08 08:17:24AM

WOW! This worked for me.

From time to time, many of my system apps will lock up (beachball) after what I know to be an attempt at accessing one of my many firewire drives, which have a tendency to overheat and become unresponsive until I flip the switch of the offending drive off then on. Guessing is easy enough using touch (which one inspires "ouch!"). Once I address the right drive, the beachball becomes pointer and the Finder lodges its usually complaint.

please note: I'm not a total dope… this system is non-critical—a convenient personal file-server—and all the data is redundantly backed up. I use a fan in the summer but these failures are rare enough and more would be overkill.

The overheating inspired beachball just struck a few minutes ago, and after resetting the two "ouch?", faced with 5 more drives and no likely pending IO tasks on the bus, I unplugged the lot at the computer…
After plugging the FW cable back in, no drives. I've seen this more than once before…
Googling with expectations of a non-Restart resolution involving kext[un]load, I tried this seemingly unlikely but quick-enough suggestion and, to my delight it worked!

So cferron, thanks for the contribution! Your instructions were clear and spot on.

[ Reply to This | # ]