-
All replies
-
Helpful answers
-
Aug 9, 2012 8:08 AM in response to Dr_Zoomby Courcoul,Check the cable. This sound like a connectivity issue.
-
Aug 9, 2012 8:42 AM in response to Courcoulby Dr_Zoom,I use the same cable on the Mac Pro as on the MacBook Pro. For the Mac Pro it is working, but for the MacBook Pro it is not. So I think it can not be the cable.
On the MacBook Pro I also get this messages in the log:
FireWire (OHCI) Lucent ID 5901 built-in: 591 bus resets in last 3 minutes.
The message is repeating. On the Mac Pro, I never get this message (using the same cable).
-
Aug 9, 2012 8:40 AM in response to Dr_Zoomby Courcoul,No idea. I've been using FW since it first came out replacing SCSI way back then; have 12 FW drives or optical burners. And have never had "disappearing drives". But a friend did have a Mac with a finicky (damaged, I would call it) USB port that would suddenly disconnect like you describe.
Only thing I can think of is if you are running some sort of virtualization software, like VMware Fusion, Parallels Desktop, Oracle VirtualBox. The virtualizer may be "grabbing" the device and taking it away from Mac OS X.
-
Aug 9, 2012 1:01 PM in response to Dr_Zoomby Linc Davis,Is it bus-powered or AC-powered? If bus, try AC.
-
Aug 10, 2012 5:41 AM in response to Linc Davisby Dr_Zoom,I will try this. Bought an AC adapter, would be then this this port which can not provide enough power for the drive. The drive is working fine on the MacBook Pro using the USB port, but of course not that fast as expected.
-
Aug 10, 2012 7:33 AM in response to Dr_Zoomby Courcoul,If USB can power it (0.5A max, as per spec), it will be a piece of cake for FW (1.5A). And your Mac has native and fully compliant FW ports, in comparison to new 2012 owners who must use a TB to FW adapter that has nowhere near the current capacity of the FW spec. But i still get this gut feeling that the problem is physical. Do you have any other FW cable you can try?
Also, can try to do an SMC and a PRAM/NVRAM reset, in case the port's flaky due to to corruption of the firmware config. Occurs every so often on the USB ports ("my right USB port don't work!", lots of threads like that), might conceivably occur to FW too.
-
Aug 10, 2012 8:14 AM in response to Courcoulby Dr_Zoom,This is interesting. I didn't know that FireWire has that high specification for power.
I actually did an SMC reset. Or at least I think I did one. But there was no feedback about the reset, so I wasn't really sure if I actually did reset the SMC or not.
I followed this guide: http://support.apple.com/kb/HT3964
But, owning this MacBook Pro (Mid 2010), I wasn't sure if I should follow the instructions using the keyboard combination, or if I really can remove the battery physically. So I tried the instructions with the keys to press and the power button.
Beside of the power supply, I also bought a second FW cable. As soon they arrive I will try both.
-
Aug 10, 2012 8:51 AM in response to Dr_Zoomby Courcoul,Your 2010 model is already Unibody/non-replaceable-battery, so the key sequence procedure is the one to use. I've heard rumors that some users get flashy lights in the connector and/or the charge indicators, but mine has been totally silent when I do the deed. As for the PRAM/NVRAM reset, exercise your fingers and press simultaneously Option-Command-P-R prior to the startup chime. Even Apple recommends you hold down the keys for at least 3-4 chime repeats to make sure all the crud is flushed out. Hope it helps.
-
Aug 10, 2012 9:27 AM in response to Courcoulby Dr_Zoom,Tried this as well. Things did not change much.
Aug 10 18:21:34 ### kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in: 365 bus resets in last 3 minutes.
Aug 10 18:24:48 ### kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in: 305 bus resets in last 3 minutes.
But now it did not disconnect so far. It is just slow like ****.
-
Aug 10, 2012 10:48 AM in response to Dr_Zoomby Linc Davis,The Firewire bus is not working. Either you have a malfunctioning device, or a malfunctioning motherboard.
-
Aug 7, 2014 2:57 PM in response to Linc Davisby Laurent Seroude,we are many with this exact same problem with FireWire + this issue does not affect all drives that I have (if it was the port or motherboard, all drives should have the problem). This problem started with Lion and has been ignored buy Apple.....