Firewire Device Issues

It's Firewire 400. Connected to one of the two G4 Firewire ports is my Digi002 audio interface. Connected to the other port are two OWC Firewire disk drives and an OWC CD/DVD burner.
Have never had any communication problems with either of the two disk drives, but recently some issues with the Digi002 and the brand new disc burner have surfaced. The Digi002 uses the CoreAudio driver to interface with my audio apps. When I launch an audio app, the CoreAudio driver launches the CoreAudio Manager, which wakes up the Digi002, thereby giving me audio inputs and outputs. The CoreAudio Manager is supposed to automatically quit when the audio app quits. Sometimes, after doing an audio project, I'll quit the app and go about working on something other than audio. But when I launch an audio app again, it tells me it can't connect with the Digi002 because it's already being used. I'll look at the Digi002 and the display shows it's idle and not connected. Then I'll discover that the CoreAudio Manager is still running (even though I'd quit the audio app). Wait. It gets more intriguing.
Apple System Profiler shows the Digi002 on the Firewire bus, but the Digi002 does not show up in either the sound pane of System Preferences (where it's supposed to), nor does it show up in AudioMIDI Setup. Manually quitting the CoreAudio Manager will not make everything right. Only a restart will. But things will be right for only so long before the problem happens again.
Now, onto the Firewire disc burner. It's only 2 weeks old. And beginning with only the 3rd or 4th time I attempted to use it, I put a blank disc in and told iTunes to burn to it. Either the burner isn't showing up on the Firewire bus, or iTunes tells me it's unable to configure (not the exact word) the laser at the selected speed. The first couple of times I saw this message, I lowered the burn speed to 12x (the drive is capable of 24x) and it worked. But sometimes it doesn't. I finally reached around the thing and unplugged the Firewire cable, waited a couple of seconds and plugged it back in. Voila! It was suddenly fine again.
Do these issues sound like device trouble, software trouble, or Firewire trouble? Again, there's no issue with either of the two hard disk drives. The Digi002 is only 6 feet from the computer, and the disk drives and burner are only 5 feet away. I've posted a similar report on the Digidesign User Conference.
Curious... no?

Thanks, Bruce and BD...
With the exception of the CD/DVD burner (which is Firewire 400 compatible), I've been using all these devices and they've all been getting along fine for five years. I can't imagine why all of a sudden now there would be problems.
And, none of the devices are bus-powered.
But as for Spotlight, one of the two Firewire disk drives is in Spotlight's Privacy window (not to be cataloged), but I'm not able to add the second drive for some reason. I click the plus sign and select the drive, but it doesn't show up in the window.

Similar Messages

New iMovie '08 problems -- FireWire or new device issues?

Not sure if this is an iMovie '08 problem or an OS X problem. Here's the story --
Prior camcorder was a Panasonic, MiniDV format. Hooks up nicely with iMovie, via FireWire (400). I also have a WD My Book (500 GB) device to store the raw data (Event Library), which connects via FireWire (800). In the past, all three devices (Panasonic, My Book and MacBook Pro) all played nicely together.
Fast forward to now. Bought a new camcorder (problems with the Panasonic). It's a Canon ZR950 (MiniDV). With iMovie running, I first connect the WD device which is successfully mounted. I then hookup the new Canon and within a few seconds I get an error about a "device not cleanly shut down" (or words to that effect). Odd .... and when I try to connect to my new camcorder, I get a "no camera connected" error.
Rebooted, retried .... same issues. Another time I first connected the Canon and this time, iMovie successfully sees it. I go to connect the My Book and then the camcorder drops out.
So, it seems I can have only one FireWire device connected at a time, which is odd since I didn't have this issue with the old Panasonic.
Help!

Interesting that you based your purchase on CR magazine because I too use it like a bible. However, when it comes to video cameras, I think they are way off base when not considering the editing side of video making that goes along with any camcorder. Who shoots video simply to plug it into a TV for playback?? If they were doing responsible reporting on this particular subject, they would also include computer capture and editing details in the reviews. Lots of the new format cams don't even work with Macs and the ones that do generally give lesser quality after conversion than what you can still get with tape. At least you made the right decision there!

Re: Issues with a Firewire device

I have a Firewire device (M-Audio Firewire 410) audio interface that will crash my Win7 on Start-Up. If I shut down the computer with it connected, windows has trouble "closing" the program. So, I now log off - turn it off, and then log back in
to shut down - which works 80% of the time. I was wondering if there was a way I could stably stop it via PowerShell without disabling the Firewire port. Obviously from how I have worded the question, I have a limited understanding the issue.
Any suggestion would be appreciated.
Jeremy

The only legitimate recommendation we can make is that you need to fix the issue. I recommend posing in the vendors forum for the PC or the device.
Treating systems is always a bad idea in medicine and in computers.
¯\_(ツ)_/¯

Monitoring Issue with firewire device (M-Audio) HELP

Essentially I am trying to hear my music track while recording live audio. I'm using my M-Audio Firewire 410 with Soundtrack Pro. This device seems to work fine with FCP, but in STP I am unable to monitor properly. I am getting input fine, but am not getting output into my firewire device. (I have selected this device as my output device, therefore STP does recognize it)
I have updated drivers. I'm running the new 5.x crossgrade on Tiger. What am I doing wrong? I've toggled every button possible!
JCB123

When you are going to record, the Recording panel pops up (with the level meter, etc). Make sure that, in the Monitor section, the correct soundcard is selected and the "Mute Project" button is not selected. That should solve it.
cp
powerbook g4 Mac OS X (10.4.6)

Seagate Ex-HD with IMac - How to connect 2nd Firewire Device

I just bought a new Seagate ExternalFree Agent HD to use with my IMac on a Firewire 400 but was wondering if I keep the HD connected what can I do to connect another device (video camera) at the same time with another firewire? I thought my IMac had 2 Firewire ports but it looks the 2nd port is for something else. Is there some kind of Hub I could buy or could I connect the camera through the HD, it appears there is another Firewire connection there? Thanks and any advice would be helpful?
Message was edited by: 27993buck

If yours is an early through late iMac G4 LCD flat panel computer
which shipped between 2002 and 2004, they all have the same
number of FireWire ports: 2 - 400 MBit/s (8W total power.)
You may need to look into a FireWire Hub, one that is self-powered
from an external AC power adapter and not use limited FW port
power from the computer, as that is limited.
' firewire hub, powered ' - google search:
http://www.google.com/search?hl=en&q=firewirehub+powered&aq=3&oq=FireWirehub
{If you have a different configuration of iMac than the one with
the half-dome white base & chrome display arm, you may need
to compare your machine with either the iMac G5 or Intel iMac
forum areas, since the hardware did change over the years.}
Be sure to not overload the FireWire, or other ports on the Mac;
no matter which model or version you may have. In the case
of USB, a self-powered (uses AC adapter) hub is recommended
and in the case of FireWire, some products may have a port in
them, but to daisy-chain these is a mistake. Underpowered
device issues, or overtaxing the Mac power supply may result.
An external firewire enclosed hard disk drive with accessory FW
port may have been supplied with that port given extra power;
if the FireWire drive uses an AC power supply and not port power.
If the external FW drive is in heavy use, you may be able to tell
if the port on there can support a camera. It probably won't.
By the Mid-2007 Intel iMac, there was a difference in the FW
port configuration: 1 - 400 MBit/s, & 1 - 800 MBit/s (7W each.)
So, you may have an iMac with two different FireWire ports.
Some towers also have or had support for both FW types;
and Ethernet, USB ported devices, and audio options.
For those machines with a less than desired FireWire
support, there are FireWire Hubs, in both specifications;
and retailers or online store links show them in both
Mac and more general PC listings. These would be
self-powered Hubs and not rely on the Mac port power.
These are a bit different and not all peripherals that say they
may work with one or the other will necessarily do so in both.
An example maybe if you buy a FW 800 external HD enclosure
and it says it also supports FW400. It may not boot OSX in 800.
The computer specifications should be available in Apple Support
in that section; and a current version of the MacTracker download
database of most things Apple computer should; see: mactracker.ca
In any event...
Good luck & happy computing!

Using Firewire devices results in desktop stuttering

Firewire traffic is causing desktop performance to decline. On my Mac Mini (late 2009, 4 GB RAM) even slow amounts of firewire traffic is causing bad spaces performance (stuttering while moving from space to space) and jerky window movement. I have tested this with several cables and 2 different firewire devices. Device 1, a Canon HDV camcorder, is bringing the window movement to stutter when imovie is detecting the connection and showing the import screen (no transfer initiated, not even playback). Device 2, a Western Digital My Book Studio with FW800 ports, is making the desktop jerky even if it is only playing a mp3 file.
Notes:
Spotlight was disabled on the mentioned fw800 hdd. Disk activity monitor shows normal operation, very low cpu workload. The system log also does not show any suspicious messages.
USB devices like harddisks do not trigger this behaviour. The mentioned fw800 disk also has an USB port. Connecting the device using USB does not slow down desktop performance, even when transfering large files.

Thanks for you suggestions. I tried them out (and some more).
Here are the results:
You can test to see if the Virtual Memory system is getting overworked by running Utilities Activity >Monitor, click on the System Memory tab and look at PageOuts and PageIns.
I kept an eye on the virtuel memory for a while now. Seems to be fine, even after hours of my usual working procedure there are virtually no page outs.
But if your ratio is good (10% or less), then I'm would suspect instead that you need to re-install a >full combo update of the latest version of OSX.
I reinstallad the 10.6.4 Combo Update. No difference.
Then I installed a fresh copy of OSX on the firewire drive. Running an unpatched OS from the drive is not bad in regards of system response time (actually it's pretty good). But the desktop jerkyness is present all the time.
Then (after switching back to my internal drive again) I stopped keeping an eye on window movement etc. and tried out some games. The results: There is a major difference in performance when the fw drive is working in the background in contrast to an usb2 drive (or even the same fw drive attached using usb). When I am playing the game (in this case it was an opengl port of Doom) there is virtually no performance penalty when I am playing the game while transfering a huge file to an usb2 drive in the background. But when I am transfering a file to the FW drive, there is huge drop in frames per second (roughly 25 - 30 %).
I am wondering if this has anything to with fact that firewire is using dma access to the system memory (in contrast to usb) an there is some sort of congestion on the memory bus. Especially since my issues are linked to gpu performance and the 9400M in the Mini uses shared memory.

Firewire device looses connection when external screen is inserted into the thunderbolt port? HELP

HI
I am a recording studio engineer. Ive got a Firewire AD/DA Converter (Focusrite Saffire Pro 56) running from my Firewire port of my MacBook Pro, which is running OSX Mavericks. I've also got an external Screen I want to use as an extended display. I'm using a HDMI cable from the screen to a HDMI to Thunderbolt Converter which I then plug into my Thurderbolt Port.
As soon as I plug the screen in, the Firewire Port looses connection completely and I cant use or even choose the Saffire Pro 56 as audio driver. Another thing happens where the Thunderbolt port replaces the Saffire Pro 56 Driver with the screen as the audio output source.
Please help, there's nothing I can find to fix this.
Thanks Maurice

You don't mention which model you have, but this is from the M-Audio Firewire 410 Manual Troubleshooting section:
The FireWire 410 has been designed to give you high performance and professional quality audio. It has been tested under a wide range
of systems and operating conditions. In the real world, however, there is a nearly infinite number of possible operating scenarios, any of
which could affect your system’s performance. Much like owning an automobile, “your mileage may vary.” This section can not begin to
cover all possible issues you may encounter, however we want to give you some suggestions on common problems you may experience.
One thing to avoid is connecting too many devices. The FireWire bus is a dependable, high-speed, high-bandwidth protocol which is ideally
suited for digital audio. Nonetheless, it’s important to remember that audio and multimedia streaming places considerable demands on
your processor and the FireWire bus. Although it is theoretically possible to chain many multiple FireWire devices in series, doing so may
potentially degrade your audio performance.
I guess this degradation could also affect the Firewire HD. Maybe there is a simple fix, but it sounds like the M-Audio people have been down this road before.

Trying to use FireWire devices with a W540 through a Thunderbolt adapter

We have a camera that we need to use that has FireWire 800 as its sole interface, and because it needs to be mobile we had to use it with a laptop. After some research we decided that the best course of action was to purchase a ThinkPad W540 and connect the camera to the Thunderbolt port with a Thunderbolt to FireWire Adapter, as this should give us plenty of bandwidth for the camera.
Unfortunately, we haven't been able to connect any FireWire devices to the laptop in this way. We have tried connecting both the camera and a FireWire hard drive through the adapter, and while the power lights will come on for both devices the computer resolutely refuses to even acknowledge their existance.
I have tried everything that I can think of to get this to work, updating all of the dirvers on the laptop, checking all of the settings in the BIOS, and searching the forums for similar issues, but now I have run out of ideas. What can I do to get this laptop to play nice with my FireWire devices?
Solved!
Go to Solution.

Good afternoon and welcome to the community.
Sorry you're having issues using a Thunderbolt-2-Firewire adapter.
Not much I can offer on that as I've never used one, but an alternative might be to try an Expresscard Firewire adapter. A number of them I've seen offer 2 ports, so that might be useful also.
Regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

FIX: FireWire communication issue solved - What worked for me

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

FireWire devices doesn't mount nor are recognized by OSX

A known issue but with several solucions posted but nothing seems to help me out...
Something is wrong with the FireWire of my Powerbook G4 667 MHz. External harddrives as soundcards as iPods as anything with a FireWire interface won't mount. However, it seems that the devices are getting electricity, Ipods charge for example. But doesn't appear on the desktop. Nor in the System Profiler. Disk Utility doesn't "see" the drives either. I have been trying with reseting the computer, the VRAM and the VPRAM. Also taken out the battery and left the computer alone for a while. No results. And of course, I have been searching the forums and diskussions like crazy but haven't found a solution.
Anyone who can give me some leads about what I can do next? A clue in this mystery is that I used a Pocketdrive to move files in between the Mac and a PC. I worked fine for 10 times or so, but then suddenly the Mac didn't mount it. First I thought that it was just that harddrive that had some problems (from the PC, I might haven't emptied the trashbin the last time I disconnected it from the PC) but then I realized that no FireWire deviced worked any longer.
Thanks in advance

Hi, jorgengun. Try running the Apple Hardware Test CD that came with your Powerbook, and see whether it reports any problem with your FireWire controller or port. It's possible that your port has gone bad, in which case the timing was probably just coincidental — it's unlikely that anything that happened on the PC could have caused your Powerbook's port to be damaged.
If you don't have Apple Hardware Test, a TechTool Pro or TechTool Deluxe CD has similar hardware testing abilities. (TTD was supplied by Apple to the purchasers of AppleCare Extended Protection plans, and is not available otherwise as far as I know. TTP is a commercial product.)
If you don't have any of the above, and all of the devices that no longer work when connected to the port did indeed work in the past, take the Powerbook to the Genius Bar at an Apple Store, or to a local Apple dealership, and have the port tested.
A bad port would necessitate one of two things: a logic board replacement, or the purchase of a CardBus-slot Firewire card.

In system profiler it says "unable to list firewire devices"

I have been trying to figure out for days why when I hook up my camcorder with a firewire that all that comes up on my screen is the isight camera and not my camcorder. I have tried everything. I finally went into the system profiler and checked my firewire bus and it said it was unable to list firewire devices. My computer is only a few weeks old. Do I need to take it in or is this something I can fix?

Any word on a solution? I also have this problem. My Panasonic DVX100AP works great with my MacBook Pro (10.4) but when I try to use it with the same version of Final Cut Studio (5.1) on my new iMac with Leopard, it's not recognized at all. It wouldn't recognize in iMovie 08 either. I then checked the system profiler and found the "Warning: Unable to list FireWire devices." message.
I called AppleCare and they had me try and connect my MBPro via firewire for target disk mode. Sure enough, the MBPro's hard drive mounted fine on my new iMac via firewire. So the firewire port is fine.
The rep suggested that I contact Panasonic as she believes it's an operating system issue and that Panasonic needs to offer some sort of software solution (driver?) to fix this. I've contacted Panasonic and am waiting to hear back from them.
If you have any tips, please let us know.

10.4.6 -- no firewire devices show-up

I upgraded to 10.4.6 on Sunday and everything was fine until this morning. Now, no firewire devices will appear (I have an iSight and two external drives).
Please, please, please help!!!
Thank you.

From MacFixIt, regarding inability to see FireWire devices after upgrading to 10.4.6:
"We should note that various FireWire issues can be caused by outdated firmware. Run Software Update and make sure there are no firmware updates available for your Mac.
Also, as with previous instances of this issue, some users have reported success by performing a hardware reset that involves holding down the power key for 10 seconds or so while the system is off."
If those suggestions fail, and you used Software Update to go to 10.4.6, you might try downloading the Mac OS X Combo Updater for PPC and applying it.
Bob N.
Mac Mini 1.5 GHz; iBook 900 mHz; iPod 20 GB Mac OS X (10.4.5)

10.6.4 and firewire device - FCA202

I've just installed 10.6.4.using software update and now my Behringer FCA202 is not showing up - in 'About my mac' it shows in Firewire - Unable to list Firewire devices.
I wonder if reducing the noise on some firewire devices has been taken to the extreme?

actually, i have finally gotten quicken 2010 to work properly again (i hope!) though not sure how or why. was attempting to restore to 10.3 as allan suggested (thanks, allan) but ran into problems w/ that. then i couldn't empty my trash. did a google on error code (8003) and did a "safe reboot" as follows: shut down mac, waited 30 seconds, restarted while holding down left shift key until after apple logo and spinning ball appeared, after which i had to re-login. still had some problems emptying all trash at first but finally got it all emptied. have restarted several times today btw. went back to quicken afterwards and suddenly it's working properly again though at first i had to re-enter password to re-connect. so there's hope. try rebooting in safe mode and see if that helps. but again, i have no idea if that's really what solved the issue. this is strange but good luck!

Mountain Lion crashes when plugging in firewire device.

I am running Mountain Lion (10.8.2) on an Early 2008 Mac Pro. Everytime I plug in a firewire camera to capture video the OS crashes and reboots my machine. This also happens on my late 2011 MacBook Pro. Any help is appreciated.
Here is the crash report:
Interval Since Last Panic Report: 254878 sec
Panics Since Last Report:          1
Anonymous UUID:                    C0397782-6778-A6D2-BFD3-9128AE02CB8D
Thu Sep 27 11:39:39 2012
panic(cpu 4 caller 0xffffff80042b83c9): "Double fault at 0xffffff7f849187da, registers:\n" "CR0: 0x000000008001003b, CR2: 0xffffff80d4be3e38, CR3: 0x00000000066d0000, CR4: 0x0000000000000660\n" "RAX: 0x00000000fffffff0, RBX: 0xffffffffffffffef, RCX: 0x000000000000001c, RDX: 0x0000000000000000\n" "RSP: 0xffffff80d4be3e40, RBP: 0xffffff81d4be3e90, RSI: 0xffffff81d4be3e04, RDI: 0xfffffffffffffff0\n" "R8: 0x0000000000000004, R9: 0x7ffffffffffffffe, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80\n" "R12: 0xffffff80262a6279, R13: 0xffffff81d4be3ef0, R14: 0xffffff81d4be3ef0, R15: 0xffffff8040de3980\n" "RFL: 0x0000000000010206, RIP: 0xffffff7f849187da, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2050.18.24/osfmk/i386/trap_native.c: 280
Backtrace (CPU 4), Frame : Return Address
0xffffff81cb44eec0 : 0xffffff800421d626
0xffffff81cb44ef30 : 0xffffff80042b83c9
0xffffff81cb44f0a0 : 0xffffff80042ceddf
0xffffff81d4be3e90 : 0xffffff7f8491803c
0xffffff81d4be3ed0 : 0xffffff7f8492459b
0xffffff81d4be3f40 : 0xffffff7f84923d1a
0xffffff81d4be3f90 : 0xffffff7f84923bde
0xffffff81d4be3fb0 : 0xffffff80042b26b7
      Kernel Extensions in backtrace:
         com.apple.iokit.IOFireWireFamily(4.5.5)[A045A111-194F-3E54-A63E-E015DC69B862]@0 xffffff7f84917000->0xffffff7f84989fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C54
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000004000000
Kernel text base: 0xffffff8004200000
System model name: MacPro3,1 (Mac-F42C88C8)
System uptime in nanoseconds: 264156192824443
last loaded kext at 196614206697331: com.apple.filesystems.msdosfs    1.8 (addr 0xffffff7f860ed000, size 65536)
last unloaded kext at 196734915261076: com.apple.driver.AppleUSBCDC    4.1.22 (addr 0xffffff7f8606c000, size 12288)
loaded kexts:
com.apple.filesystems.smbfs    1.8
com.apple.iokit.IOBluetoothSerialManager    4.0.9f33
com.apple.filesystems.autofs    3.0
com.apple.driver.AudioAUUC    1.60
com.apple.driver.AppleHWSensor    1.9.5d0
com.apple.driver.AppleUpstreamUserClient    3.5.10
com.apple.driver.AppleMCCSControl    1.0.33
com.apple.driver.AppleUSBDisplays    353
com.apple.kext.AMDFramebuffer    8.0.0
com.apple.iokit.CSRBluetoothHCIControllerUSBTransport    4.0.9f33
com.apple.driver.AppleHDA    2.3.1f2
com.apple.ATIRadeonX2000    8.0.0
com.apple.driver.AppleLPC    1.6.0
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleMCEDriver    1.1.9
com.apple.iokit.IOUserEthernet    1.0.0d1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.ApplePolicyControl    3.2.11
com.apple.iokit.SCSITaskUserClient    3.5.1
com.apple.driver.XsanFilter    404
com.apple.iokit.IOAHCIBlockStorage    2.2.2
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.BootCache    34
com.apple.driver.AppleUSBHub    5.2.5
com.apple.driver.AppleIntel8254XEthernet    3.1.1b1
com.apple.driver.AppleFWOHCI    4.9.6
com.apple.driver.AppleAHCIPort    2.4.1
com.apple.driver.AppleIntelPIIXATA    2.5.1
com.apple.driver.AppleUSBEHCI    5.4.0
com.apple.driver.AppleUSBUHCI    5.2.5
com.apple.driver.AppleEFINVRAM    1.6.1
com.apple.driver.AppleACPIButtons    1.6
com.apple.driver.AppleRTC    1.5
com.apple.driver.AppleHPET    1.7
com.apple.driver.AppleSMBIOS    1.9
com.apple.driver.AppleACPIEC    1.6
com.apple.driver.AppleAPIC    1.6
com.apple.driver.AppleIntelCPUPowerManagementClient    196.0.0
com.apple.nke.applicationfirewall    4.0.39
com.apple.security.quarantine    2
com.apple.driver.AppleIntelCPUPowerManagement    196.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice    3.5.1
com.apple.iokit.IOUSBMassStorageClass    3.5.0
com.apple.iokit.IOSerialFamily    10.0.6
com.apple.kext.triggers    1.0
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.driver.AppleUSBAudio    2.9.0f6
com.apple.driver.DspFuncLib    2.3.1f2
com.apple.iokit.IOAudioFamily    1.8.9fc10
com.apple.kext.OSvKernDSPLib    1.6
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport    4.0.9f33
com.apple.kext.AMD2600Controller    8.0.0
com.apple.kext.AMDSupport    8.0.0
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.driver.IOPlatformPluginFamily    5.2.0d16
com.apple.driver.AppleHDAController    2.3.1f2
com.apple.iokit.IOHDAFamily    2.3.1f2
com.apple.iokit.IOFireWireIP    2.2.5
com.apple.iokit.IOSurface    86.0.3
com.apple.iokit.IOBluetoothFamily    4.0.9f33
com.apple.driver.AppleSMC    3.1.4d2
com.apple.driver.AppleGraphicsControl    3.2.11
com.apple.iokit.IONDRVSupport    2.3.5
com.apple.iokit.IOGraphicsFamily    2.3.5
com.apple.iokit.IOUSBHIDDriver    5.2.5
com.apple.driver.AppleUSBComposite    5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.5.1
com.apple.iokit.IOBDStorageFamily    1.7
com.apple.iokit.IODVDStorageFamily    1.7.1
com.apple.iokit.IOCDStorageFamily    1.7.1
com.apple.iokit.IOATAPIProtocolTransport    3.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily    3.5.1
com.apple.iokit.IONetworkingFamily    3.0
com.apple.iokit.IOUSBUserClient    5.2.5
com.apple.iokit.IOFireWireFamily    4.5.5
com.apple.iokit.IOAHCIFamily    2.2.1
com.apple.iokit.IOATAFamily    2.5.1
com.apple.iokit.IOUSBFamily    5.4.0
com.apple.iokit.IOHIDFamily    1.8.0
com.apple.driver.AppleEFIRuntime    1.6.1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.security.sandbox    220
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    7
com.apple.driver.DiskImages    344
com.apple.iokit.IOStorageFamily    1.8
com.apple.driver.AppleKeyStore    28.21
com.apple.driver.AppleACPIPlatform    1.6
com.apple.iokit.IOPCIFamily    2.7.1
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.corecrypto    1.0
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 16 GB, SMC 1.25f4
Graphics: ATI Radeon HD 2600 XT, ATI Radeon HD 2600, PCIe, 256 MB
Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser B/DIMM 3, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser B/DIMM 4, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser A/DIMM 3, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Memory Module: DIMM Riser A/DIMM 4, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x02BA, 0x202020202020202020202020202020202020
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
Network Service: Ethernet 2, Ethernet, en1
PCI Card: ATI Radeon HD 2600, sppci_displaycontroller, Slot-1
Serial ATA Device: Hitachi HDS721010KLA330, 1 TB
Serial ATA Device: Hitachi HDS722020ALA330, 2 TB
Serial ATA Device: Hitachi HDS721010KLA330, 1 TB
Serial ATA Device: SAMSUNG HD103SI, 1 TB
Parallel ATA Device: PIONEER DVD-RW DVR-112D
Parallel ATA Device: PIONEER DVD-RW DVR-112D
USB Device: hub_device, apple_vendor_id, 0x912f, 0xfd500000 / 2
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc50c, 0xfd530000 / 4
USB Device: Apple Cinema HD Display, apple_vendor_id, 0x9221, 0xfd520000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x5d200000 / 2
USB Device: SoundSticks, 0x05fc (Harman International), 0x7849, 0x3d100000 / 2
FireWire Device: built-in_hub, 800mbit_speed
FireWire Device: unknown_device, unknown_speed

Yes, I have tried different firewire cables and such. Removed my firewire hub, tried plugging into the actual ports on the MacPro and plugging in the firewire ports on the back of my Cinema 30 display. I even bought a new firewire cable just to make sure. So for now I guess I am going to downgrade my MacMini to Snow Leopard and use that machine to do video capture.
So last night I removed the primary harddrive from the MacPro. I installed a new 1TB harddrive. Formatted that drive and did a clean install of Mountain Lion and ran all software updates. Crashes when I plugin my firewire cameras with no other software but the OS.
So then I reformatted the drive and did a clean install of Lion and did all software updates. Still crashes.
I formatted the drive for a third time, this time installing Snow Leopard. Did all software updates. Plugged in my cameras one at a time and no crash. I installed iLife '11 and was able to video capture with iMovie via the firewire port.
I am pretty convinced that my hardware (at least) is in working order, otherwise it would have crashed with Snow Leopard also (correct me if my conclusion is incorrect). So I am inclined to agree with you that I may have triggered a bug in the OS.
Thank you for your insights. How do I go about reporting this issue to the Apple Software Engineers?

Firewire problem (the old 'Warning: unable to list firewire devices')

Hello everyone,
I am having a very big problem with my 13" Macbook Pro since yesterday. I took it to work and hooked it to a RME Fireface 800 audio interface we have in there, and for some odd reason it didn't recognize the interface. After a few tries, it suddenly came alive. I did the recording session as usual, turned the notebook off and brought everything home. Today, I hooked it to my own RME Fireface 400, and one of the firewire ports on it wasn't working - I plugged on the other and started audio playback. After a few minutes, the audio stopped and the host connection problem led the Fireface has turned on. AFter this, I couldn't get the fireface to be recognize on its own - more on this later.
I went to system profiler and got a 'WARNING: Unable to list firewire devices' message. I already googled it and it seems I am not the only own having this problem. I already clean PRAM, SMC, ran disk utility to repair disk and disk permissions and nothing has worked. HOWEVER, one external HD (firewire) i have is working just fine on this same firewire interface. I also tried daisy chaining the Fireface to the Hard disk, the later being connected itself to the Macbook, and using this method the interface works. I also tried the interface on another computer and it works just fine - so the problem lies on my Macbook Pro.
Now, I went to the Console application to see if there was any error messages, and in fact there are plenty. I got a bunch of 'FireWire (OHCI) Lucent ID 5901 built-in: Bad selfIDs, issuing bus reset (retry 2)' and then 'Missing self ID for node 0!'. Also got some 'Firewire (OHCI) Lucent ID 5901 built-in: 4403 resets in last 3 minutes'. Also 'SPFWR ERROR: Firewire bus may be unstable. Other Firewire devices may be present.'. Right now, If i plug the interface and look for something on the console, I get nothing. I only get something when I look on the System Profiler.
So, obviously, there's a problem between my interface and the MBP. Anyone has ANY clue on what to do? BTW, the interface don't work when booting to bootcamp using W7 (it is also not recognized).But like I said, it works when daisy-chained to the hard disk or in another computer.
Thanks a lot,
Ivan

Does the RME device have its own AC power supply brick? If so I would suspect that it is failing and the system is pulling too much juice from the MBP. When you have a drive daisy-chained the interface is able to get the juice it needs from that drive and not from the Mac itself.
If it has no power supply brick you will have better luck with a powered hub.

Firewire Device Issues

Similar Messages

Maybe you are looking for