Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › Leopard 10.5 › Firewire just stopped working )
2,861 reads · 2009-07-05
Note Leopard 10.5 Gigabyte G31M / P35

Firewire just stopped working )

Specs: Mobo: GA-P35-DS3L CPU: Intel 2.4Ghz Quadcore Memory: 2GB Video: MSI 8600GTS OS: iPC 10.5.6 updated to 10.5.7 via the iDeneb updater. Drivers & Patches: Only used the driver pack for my mobo from this forum(can't find the link at the…

Primary Author
@brannfenix Published 2009-07-05
Collection
Leopard 10.5
Archival Footprint
2,861 historical reads · 0 curated field notes (from 1 dispatches) · 2009-07-05
Credited Voices (1)
@brannfenix

Specs:

Mobo: GA-P35-DS3L
CPU: Intel 2.4Ghz Quadcore
Memory: 2GB
Video: MSI 8600GTS

OS: iPC 10.5.6 updated to 10.5.7 via the iDeneb updater.
Drivers & Patches: Only used the driver pack for my mobo from this forum(can't find the link at the second) and an audio patch.

---------------

Ok, I have some random firewire PCI card that I can not recall at the moment. I plugged my camcorder into it and poof! everything was working perfect on iMovie. I could100% control my camcorder from the software and proceeded to import some video. I used the feature after the import that tries to lessen any camera shake. It took like 40mins, but other that that that worked perfectly fine.

So, this sounds like a success story right? Where here is where things go off the rails... I am capturing more video again using the auto import from iMovie. It finishes capping the footage and asks if I want to run the anti-camera shake feature. I press yes, but decide I don't want to and hit cancel after like 30 seconds. THAT IS IT!

iMovie, System Profiler, and Final Cut Pro will not see my camcorder now. I installed no updates or any software for that matter and did only what I wrote above. Now, I can not get the OS to see my device no matter what I do. I will admit I do not have heaps of knowledge when it comes to troubleshooting OSX related issues. I have rebooted with the -f option and repaired the disk permissions. Both had no effect on fixing my problem at all

What other ways can I troubleshoot this problem? Is there a way to manually try to detect the camcorder while it is plugged in? I assume it was something where it was uncleanly disconnect, but I am lost. The only thing I am pretty sure of is that it is not a driver issue since it worked right out of the box with no patching.

,
-Brann

Sources & Contributor Provenance (1 credited usernames · Thread #3294)
UsernameDossier ContributionDispatchesActive Window
@brannfenixPrimary Author12009-07-05