Firewire 410 not working

Hey guys. I'll try to make this as clear as possible. I've updated the firewire 410 driver to 1.9.3, I am receiving audio in which is visibly received on my audio track through proper input selection in Logic. but, not audio out of Logic with the 410 selected as the interface via preferences. Garageband has no issue with this. The last thing I have not considered is that if I am running Logic w/o rosetta turned on, am I using the wrong driver for the 410? I have tried setting it up as an aggregate to see my output as the built-in driver, unsuccessful. My sys. prefs show proper interface selection as well. I am running mobile so this is not a monitor output setup, just for headphones out of the 410. This is not problematic for the Firewire solo, however. It works perfect. But I need to multi track with the 410. Suggestions?
Hardware:
MBPro 2.2 2GB RAM
Logic 8.0.2
Firewire 410 1.9.3 driver
OSX 10.6.4

Double check your Sync Source, what does it say when you load Logic.
Just curious, why are you even mentioning Rosetta?
The 410 is a great device.
I wound up buying the 610 and no I didn't sell the 410 but use it on my MacBook Pro and the 610 on my iMac.

Similar Messages

20" Cinema display with USB and firewire ports not working

I have a new 20" display and was wondering why my USB and fire wire ports at the back are not working. I have an external drive that is powered hooked up to the fire wire port and a no powered piano keyboard to a usb port.
Any help please

Verify that the display’s USB and FireWire cables are firmly plugged in to the
computer. Do they show in your profiler?
Try different ports in the computer.
Verify that your computer ports are working with other known problem free device.

On Board Firewire does not work properly

I have a new Qosmio X500 with Windwos 7 Professional. The onboard firewire port has serious problems. I used Adobe Premiere CS5 and when I try to play out a clip through the firewire port, I get video reference errors, which means the port is not sending out a continuous signal. I disabled it and installed a firewire PCI Express card and it works fine. The problem is I need that card slot for other things and I paid for a firewire port and it does not work.
I looked on the internet and apparently new laptops have been having serious firewire problems. Does anyone know how to get this port to work properly? I tried going back to legacy drivers but that didn't work.

I don't have one of these machines, and my firewire stuff is in boxes somewhere.
But, perhaps it's a matter of power or level? I remember at some point USB peripherals had some issues unless used with a powered hub. Perhaps a powered firewire hub might help. I know I have a couple someplace that I used when daisy chaining wasn't working.

PCMCIA firewire adapter not working ....

with my LACie 40GB USB/Firewire mobile hard drive..
I previously posted that my TiBook 550 firewire port & the Lacie firewire
port are fried. I was hinted that the Tibook firewire port may have been
the culprit but not certain.
I bought a 3rd party PCMCIA firewire adapter IEEE 1394A
Here's the issue it works with a new firewire 3.5"drive enclosure which has
it's own power supply.
With the LAcie it runs off the power from the TiBook when I use the USB
port.
Is there a specific PCMCIA fire wire adapter I need to run the firewire bus
power of the LAcie drive?
I'm at a lost and REALLY behind in backing up data because of this.
Need help thanks ~A~

Thank you for clarifying this to me.
I went to the Apple store today, and not much was told except to buy
a new logic board!
My new 2.5" firewire enclosure does have a power supply port.
So looks like that seems to be my answer for now.
It does seem odd to have a power suppy for something portable, but
I guess when you blow firewire ports and need to go through a PCMCIA
adapter that's my best option.
The one thing I am curious about is that the LAcie firewire port & Tibook firewire port though the harddrive isn't mounting on my desktop still brings power to the drive.
Do you think on the "off the wall" chance that by adding a external power supply to the "injured" LAcie drive that it may allow my Tibook to mount
on the desktop?
A strange inquiry but worth a shot!
What do you think? ~A~
To add to Hardy's advice: Some pocket-sized FW drives
come with their own AC adapters. Others can use such
an adapter, but it's an optional accessory. Others
have no provision for connecting an external power
adapter to them, and must draw their power from the
FireWire bus. They can't do that when the FireWire
bus is on a PC card, unless the PC card adapter
itself came with a short auxiliary cord to connect it
to one of the host computer's USB or FireWire ports.
That cord is provided to draw power from one of those
ports for any bus-powered devices that are connected
through the PC Card adapter.
Therefore, you will need to do one of several things,
listed roughly in order of preference:
1. Use the AC adapter that came with your pocket
FireWire drive, if one did;
2. Buy such an adapter, if you didn't get one with it
but it can use one;
3. Use the auxiliary power cord that came with your
PC Card FireWire adapter, if one did;
4. Buy a different FireWire enclosure for your pocket
hard drive that allows the use of external power, and
comes with its own AC adapter.
5. Buy another PC card adapter that comes with an
auxiliary power cord.
#4 is preferable to #5 because it's certain to work,
not because it's necessarily less expensive.
Note that some portable hard drives need more power
than the USB or FireWire bus in a Powerbook can
supply. It sounds ridiculous — why make a portable
drive that requires you to carry an AC adapter with
it? — but it's true. This is why #5 above may not
work: even with an auxiliary power cord in use, your
drive may overdraw the power budget of the port to
which the cord is connected, and you'll be right back
where you are now.
PowerBook G4 Titanium 550Mhz Mac OS X (10.3.9) airport express, Safari, 512 MB
PowerBook G4 Titanium 550Mhz Mac OS X (10.3.9) airport express, Safari, 512 MB

Isight firewire cam not working in iChat on Leopard.

After installing Leopard on my Powerbook G4 867 dvi, my Isight Firewire Cam is not working anymore
in Ichat on Leopard.
Any solutions, it worked fine under Tiger.
Isight firewire cam works fine wirh Skype, Amsn , Photobooth and Quicktime.

Alright. I've done quite a bit of testing now.
My system is (as stated below,) a 12" PowerBook G4, 867 MHz, 640 MB RAM, 40 GB hard drive, Combo drive, AirPort Extreme. It was purchased in Summer 2003, and while the OS has been reloaded, it hasn't been for a long time, and at present, the OS was an install of Jaguar that was upgraded to Panther to Tigard, finally to Leopard.
I was experiencing the issue mentioned. In my case, I use a FireWire miniDV camcorder for video in iChat. It has worked fine in the iChat AV beta in Jaguar, and iChat AV in Panther and Tiger.
Upon upgrading to Leopard, I get the "Slow Network" explanation for why I cannot use video (or hosting multiperson audio, or screen sharing.)
My research shows the following:
This occurs both on the upgraded install, and a fresh install. (To an external hard drive.)
Using Ecamm's PowerBoost allows me to use every option that isn't barred outright by lack of hardware (video effects.) This includes both "Slow Network" issues and "Insufficient CPU" issues (essentially just multiperson video.)
So my guess is that the "Slow Network" is indeed a "bug", and will be fixed by an update from Apple.

Sandisk extreme firewire reader not working on new MBP models(unibody))

hey all,
so I have the sandisk extreme firewire CF reader since 2008. It works great on my 15" Macbook Pro2.2 (C2D 2.16ghz)
Recently(actually in march) I purchased the new thunderbolt 15" MacbookPro(2.2GHz).
At first the firewire card reader works fine on the new MBP. But somehow in May it stopped working(running SL). The CF card wouldnt mount, in System Profile it wouldn't even display the device. Even after I installed Lion it still wouldnt work. The only way for it to work is to daisychain it onto a firewire external harddrive and hook it up to the macbookpro.
It's super weird. I've contacted sandisk's web support(WHAT?! only web support but no phone, for such a big company?!), they said it was use the card-reader was due to power issues and told me to contact Apple to resolve the issue.
I later on tried the card reader on numberious mac's. Turns out that most Unibody machines wont work with it.(the weird thing is, when i just got my Thunderbolt unibody, it worked perfectly fine, for a while) But back on my old Macbook Pro2,2 from 2007(which is currently running OSX 10.6.8), it's works like a champ.(going to install 10.7 Lion and see how it goes)
And at the meantime I donno whether it's the card readers issue or not?(sandisk wouldnt replace the thing for me)
So anyone got any experience or insight of the situation?
thanks
PS.
To make things worse, Sandisk discontinued the extreme firewire reader,(they do have the expresscard reader, but the new 15" dont have a expresscard slot)
So now we're left with those stupid slow USB2.0 card readers while the size and the speed of those flash memory cards are getting faster and bigger each day.

I'm pretty much giving up on this issue.
I just found a very rare new lexar fw800 reader online for $80. Hope it works.
fun fact: the SanDisk fw card reader works on the MacPros,new MacMini's/server, even the thunderbolt display w/ the fw800.

Capturing video via Firewire does not work on CS6

I recently installed 64 bits Windows 7.
The capture function in Premiere CS6 does not work with my panasonic camcorder NV-GS500
Windows recognizes the camcorder, but I cannot do anything with it in the Capture window.
This not an Premiere-specific problem , because also wit Nero I have the same problem.
I expect that the Windows7 driver for my camera needs to be upodated, but Panasonic cannot help me.
Is there anybody out in the Premiere community who knows a solution?

Windows 7 Changed the standard 1394 driver from XP which allows Win 7 to Throttle bandwidth on Firewire devices. This is why Ann mentioned the legacy driver which is basically the old XP driver. The bandwidth throttling causes allot of issues with certain cameras during the Handshake process which is why you often have deck control but no preview or primary video stream. If you follow the instructions in the link above or the paste below to set the Legacy driver for the 1394 controller , that will often resolve these issues. However some firmware on different manufacturers Firewire controllers include these C-State Bandwidth throttling sets so it still may not work. In that case you want to get a Firewire card with a TI chipset. The firmware on TI chips are clean and dont include the C-State changes.
Solution 6: Use the Legacy FireWire driver (Windows 7 x64)
Click the Windows Start button; type "device manager" into the Search box and select Device Manager
Swivel open the "IEEE 1394 Bus host controllers" item
Right-click on your listed 1394 controller; select "Update Driver Software"
Click the "Browse my computer for driver software" button, followed by the "Let me pick from a list" button
Select the option that has "(Legacy)" at the end of the name; click Next and let Windows install the driver
Make sure you restart the system after you make the change to legacy. Also do not have the Firewire device plugged in when changing the driver to Legacy.
Close out of dialogs and retry capture'
Eric
ADK

Belkin Firewire Hub Not working

I purchased a Belkin Firewire 6-Port Hub unit and plugged all of my firewire gear into it and it is not working. The unit is glowing green and is connected to my iMac so that is all good.
I read the back of the package and it says the following....
To use the hub your computer must feature a built in firewire host adapter or be equipped with a firewire host adapter upgrade card.
Does the Intel Core 2 Duo based iMac have either one of these? Could this be my problem?

I had one external hard drive plugged in (with its own power supply), my Digi002 Rack plugged in (with its own power supply) and a cable to my camcorder. I turned my hard drive on and the icon would not appear. I just unplugged everything and now the hard drive works. I guess I will just take the belkin back or sell it on amazon.
I have a belkin usb hub and that thing works great! I guess the firewire hubs are kind of finiky.
There really was not exact place to plug the firewire cable into the hub that connects to the computer, unlike the usb hub. I thought that a bit odd. Perhaps I pluggede the cable from the computer into the wrong spot on the hub so the hub was not recognized by the computer?

Firewire 400 not working.

Heya guys,
I have a powerbook 15" which one recognise a Lacie D2 Extreme HD nor Sony DSR40P DVDECK/Sony PD170/Sony HDVZ1E. The hard drives and cameras all work fine on my other powerbook using the same cable. The HD works fine using the usb or firewire 800 port.
Weirdly enough the same is happening on my Dual G4 Powermac. Both running Pather. I haven't updated anything recently so I don't really understand it.

Thought you could use this info about getting FireWire to work!
First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
If that didn't work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try.
If that still didn't get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
For those of you with Macs that are not PowerBooks or iBooks, a bad internal PRAM battery can cause FireWire to not be recognized, so make sure it's good! Also, here is Apple KB HT1317 on getting FireWire to work.
Here's another Fw Faq.
DALE

Firewire soundcards not working under bootcamp/windows (mbp unibody)

I am reading a lot about firewire sound cards not working on the new unibody macbook pros.
I am using sp3 and trying to use my konnekt6 sound card without any luck. Will apple address this issue or is there a hotfix for this?
Best regards,,
Mark

I have the same problem and i have tried numeral suggestion and trik with no success.
it seems that the firewire driver 1394.inf in the xp or vista is not fully compatible with the chipset in the mac. any solution?
the presonus sound card is not recognized as sound card on XP, but no vista it is recognized but caused the system to crash and freeze upon plug in

Firewire Port not working, URGENT help please¡¡¡

Hello People, i´ve just got a new Mac Mini last week, and i´ve been trying to get my Alesis MasterControl audio interface, and is just a complete mess.
This happened right after i´ve upgraded to 10.8.3 so i don´t know, the weird thing is that if i connect my old iBook to the Mac Mini the FW800 port works, but everytime i connect the audio interface, nothing happens, also the drivers from alesis, are up to date. i first thought about the port of the Mixer went bad, but it has 2 and non of them works, also thought about the cable but the same cable works when i connect my iBook, and the mixer is not bus powered, it has it´s own power supply.
Needless to say i´ve already done the usual reset PRAM, turn of the Mac unplugged for 30 hour to reset the bus. etc.
This is the usual firewire only system log that i get:
31/03/13 08:01:20.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 08:01:30.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 11:33:23.529 system_profiler[528]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:35:43.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:38:55.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:42:08.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:44:39.124 CleanMyMacHelperTool[583]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671"
31/03/13 11:44:39.146 CleanMyMacHelperTool[583]: Wont clean /Volumes/AlesisFirewire-3.5.3.8671 because disk image
31/03/13 11:44:39.148 CleanMyMacHelperTool[583]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671"
31/03/13 11:44:39.149 CleanMyMacHelperTool[583]: Wont clean /Volumes/AlesisFirewire-3.5.3.8671 because disk image
31/03/13 11:44:52.727 coreservicesd[62]: Application App:"AlesisFirewireUninstaller" [ 0x0/0x7f07f] @ 0x0x7fb5c8c30050 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x80080:) ), so denying.
31/03/13 11:44:52.727 WindowServer[85]: [cps/setfront] Failed setting the front application to AlesisFirewireUninstaller, psn 0x0-0x7f07f, securitySessionID=0x186a5, err=-13066
31/03/13 11:47:28.533 CleanMyMacHelperTool[656]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671",
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:47:28.544 CleanMyMacHelperTool[656]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.3.8671",
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:49:26.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:52:39.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 11:57:22.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 11:57:34.000 kernel[0]: Alesis Firewire - 3.5.3.8671 preliminary - x86_64 CJ - May 3 2010 02:43:28
31/03/13 11:58:36.982 com.apple.launchd.peruser.501[155]: ([0x0-0x1d01d].tc.tctechnologies.AlesisFirewire.controlpanel[238]) Job appears to have crashed: Abort trap: 6
31/03/13 11:58:37.252 ReportCrash[242]: Saved crash report for AlesisFirewire Control Panel[238] version 3.5.3 (3.5.3.8671) to /Users/m1kygarcia/Library/Logs/DiagnosticReports/AlesisFirewire Control Panel_2013-03-31-115837_Mac-mini-de-Miguel.crash
31/03/13 11:58:39.831 system_profiler[267]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:58:50.676 com.apple.launchd.peruser.501[155]: ([0x0-0x23023].tc.tctechnologies.AlesisFirewire.controlpanel[274]) Job appears to have crashed: Abort trap: 6
31/03/13 11:58:50.837 ReportCrash[242]: Saved crash report for AlesisFirewire Control Panel[274] version 3.5.3 (3.5.3.8671) to /Users/m1kygarcia/Library/Logs/DiagnosticReports/AlesisFirewire Control Panel_2013-03-31-115850_Mac-mini-de-Miguel.crash
31/03/13 11:58:53.638 system_profiler[277]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 11:59:09.747 CleanMyMacHelperTool[300]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:59:09.905 CleanMyMacHelperTool[300]: Wont clean /Volumes/AlesisFirewire-3.5.6.11675 because disk image
31/03/13 11:59:09.906 CleanMyMacHelperTool[300]: Mounted devices (
    "/Volumes/AlesisFirewire-3.5.6.11675"
31/03/13 11:59:09.907 CleanMyMacHelperTool[300]: Wont clean /Volumes/AlesisFirewire-3.5.6.11675 because disk image
31/03/13 12:00:47.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:00:59.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:01:56.720 system_profiler[269]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:05:40.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:08:52.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:12:42.277 AlesisFirewire Control Panel[245]: -_continuousScroll is deprecated for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
31/03/13 12:12:42.277 AlesisFirewire Control Panel[245]: -deviceDeltaX is deprecated for NSScrollWheel. Please use -scrollingDeltaX.
31/03/13 12:12:42.278 AlesisFirewire Control Panel[245]: -deviceDeltaY is deprecated for NSScrollWheel. Please use -scrollingDeltaY.
31/03/13 12:13:53.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:25:29.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:25:38.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:28:30.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:28:33.906 system_profiler[273]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:31:41.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 12:35:16.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:35:26.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:37:53.513 system_profiler[266]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 12:39:36.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 12:39:49.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 12:42:55.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 53 bus resets in last 3 minutes.
31/03/13 12:46:50.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 68 bus resets in last 3 minutes.
31/03/13 13:01:30.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:01:41.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 13:05:27.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 79 bus resets in last 3 minutes.
31/03/13 13:06:31.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:09:43.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:13:31.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:13:45.006 com.apple.kextd[11]: Can't load /System/Library/Extensions/IOFireWireIP.kext - ineligible during safe boot.
31/03/13 13:13:45.008 com.apple.kextd[11]: Load com.apple.iokit.IOFireWireIP failed; removing personalities from kernel.
31/03/13 13:13:54.818 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:13:54.823 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:13:56.372 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:13:56.375 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:15:40.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:18:46.763 com.apple.kextd[11]: Can't load /System/Library/Extensions/IOFireWireIP.kext - ineligible during safe boot.
31/03/13 13:18:46.768 com.apple.kextd[11]: Load com.apple.iokit.IOFireWireIP failed; removing personalities from kernel.
31/03/13 13:18:46.797 com.apple.kextd[11]: Can't load /System/Library/Extensions/AlesisFirewire.kext - ineligible during safe boot.
31/03/13 13:18:46.800 com.apple.kextd[11]: Load tc.tctechnologies.driver.AlesisFirewire failed; removing personalities from kernel.
31/03/13 13:18:50.775 system_profiler[221]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:18:52.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:21:03.488 system_profiler[235]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:22:37.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:24:07.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in now active, GUID 003ee1fffe88dc6a; max speed s800.
31/03/13 13:24:19.000 kernel[0]: Alesis Firewire - 3.5.6.11675 (x86_64) Aug 16 2011 01:20:23
31/03/13 13:31:00.926 system_profiler[316]: SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
31/03/13 13:33:03.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: 134 bus resets in last 3 minutes.
31/03/13 13:35:11.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:38:24.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:41:36.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:44:48.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 13:58:13.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
31/03/13 14:01:25.000 kernel[0]: FireWire (OHCI) TI ID 823f built-in: no valid selfIDs for more than 3 minutes after bus reset.
Can somebody help, please i´d gladly appreciate it.

I have this
System Profiler[170]
SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present.
& this
kernel FireWire (OHCI) Lucent ID 5901 built-in: no valid selfIDs for more than 3 minutes after bus reset.
Pls, help!!

After Security update, FireWire iPods not working in iTunes 7.0.2

Hi all,
this past weekend, I installed the latest Apple security update and restarted my Mac.
Everything was working fine until I connected my iPod mini (via FireWire) and realized that although the iPod is mounting on the desktop, it is NOT appearing in iTunes. My other iPod, a 10GB 3G iPod, is also experiencing the same problem. The exception to this is my son's 512MB Shuffle -- it's working just fine.
I've tried all of the following, to no avail:
1. changed FW port
2. reset iPod
3. restored iPod
4. deleted and reinstalled iTunes
5. ran Disk Utility and DiskWarrior and "repaired" iPod hard drive
help!
iMac G5 Mac OS X (10.4.8) iPod mini, iPod, Shuffle, iTunes 7.0.2

Michael
I have both a frist gen. and a fifth gen iPod and both are working on my iMac, which runs iTunes 7.0.2 and it's OS is up to date with the the latest security update.
Rick

Time Machine Backup to Shared Firewire Drive Not Working

Hello
I know this may have been posted before, but I am looking for a simple troubleshooting / diagnostic process I can follow to resolve my issue:
I have a Imac running Lepoard with all possible software updates. A WD Studio 500GB drive is attached via Firewire 800. The drive has the latest firmware etc. I also have a 15" powerbook G4 (last model) running leopard. All Macs are connected to the a Netgear DG834N router, via ethernet cables.
The Imac and Firewire connected external drive works normally with time machine.
I have shared the external drive on the Imac and given all 'built in' groups read/write permissions.
I can mount the external drive on the powerbook and see the files that are backed up by the Imac, I can traverse the folder tree within the folders contrained in the backup. Double clicking on these folders invokes the 'star trek' style time machine window.
When trying to backup the powerbook, I could see the external drive as a time machine target disk.
The backup failed twice. Having checked the disk a sparse image was created. I tried again a number of times without success - I deleted the sparse image and tried to start again.
This time I could not find the disk in the selection in time machine, a reboot of everything revealed the disk, but when selecting the 'use for backup' button in time machine on the powerbook nothing happens.
Any suggestions or help would be greatly appreciated.

You have a pretty simple problem: time machine does not allow you to backup two computers to the same hard drive or partitioin. the way to fix this is to repartition you WD drive into two partitions, one for each computer. if you already have other data (not from time machine), make three partitons: one for iMac, one for PowerBook, and one for Other. do not put any data other than time machine data on the iMac and PowerBook partitons, always put it in other. you can partiton a disk easily with disk utility, but wait:
_CAUTION: THIS WILL CAUSE YOU TO LOOSE ALL THE DATA ALREADY ON THE EXTERNAL HARD DRIVE!_
to avoid this, first use disk utility to make a disk image of the external hard drive, and save it on your internal drive. if the image won't fit (your internal drive doesn't have enough capacity, then you can either erase all the data on already on the hard drive with the reformat, or buy another disk to use for the PowerBook) then, when the disk is partitioned correctly, mount the disk image and copy all the files on it back to the correct* partition of the external hard drive. *if the files on the external hard drive came from the iMac, then put them on the iMac partiton of the drive. if they came from the powerbook, put them in that partition, and if it is not from time machine, put it in othe
Hope you followed all that!
nate

File Copy to local attached Firewire "LaCie" not working any longer

Dear all,
have Updated my Mac Book to the latest 10.6.3 Release and since following is not longer working:
Copying from FinalCutPro created Quicktime *.mov Files from the internal HD via Finder to the Firewire Drive - Error Message "Der Vorgang konnte nicht abgeschlossen werden, da das Objekt „filename.mov“ in Verwendung ist."
The File is definitive not in use (I also tried it with a Copy of it - same behavior). I have tried this further with different File(sizes) - it starts copying and stops always at different timing afterwards with the same Error. Can also delete this file without any errors.
Having seen that this has also happened by some others in this forum by writing back to SMB - so removed extented attributes which seems to work with them - still no success for me.
Any ideas?
Many thanks
/Juergen

Some Update on this - Copying to another FireWire 800 attached Drive with Apple Filesystem worked. But I am still guessing what happened

New 2011 MacBook Pro Firewire Port Not Working with Firewire Solo

Kind of an odd problem:
I'm basically trying to go from my MBP through firewire to a firewire solo audio interface and then from there out to two speakers. (MBP>Firewire Solo>Speakers) The light on the firewire solo turns on when I connect the firewire cable, but when i try to play sound nothing comes out. Yes, I've checked the volume. Yes, I've checked system preferences. It's not the cable, the interface, or the speakers as I've check all these with my old computer and they work fine. Also, I've plugged in the firewire solo to check if it was a power problem -- still no sound. What's going on!?

Could it just be a hardware problem?

Firewire 410 not working

Similar Messages

Maybe you are looking for