IF-FWDM not being recognized my Mac

I didn't read all of the post above so forgive me if this has already been suggested, If the card is indeed good, did you try installing the drivers and then introducing the card into the system. The Mac should find the driver for it. (You'll have to un-install whatever your Mac thinks it is, in your device management first.)
 
Sorry for the very long delay reporting back. It took a while to get the new card. Got the new card Thursday - installed it today. Unfortunately - still having issues.

installed the card : Card status is OK
No Driver

The OS saw it as an unrecognized device (since it had no driver)

removed the current driver
dl'd the latest beta driver
OS saw the card in the system profile, (but it was not present in any of the sound settings)
1394 Status on the DM says Not Ready

a few other threads said to reboot the DM ... I did

DM says
Card: OK
1394 : Not Ready

OS doesn't recognize the card anymore says "unknown device"

This is basically what I was seeing before.

Any ideas??? I'm not sure where to go from here.
 
This is probably still the driver signing issue. I put a temporary work-around solution on the early access webpage. See V1.30f9_10.9.5

I'm working on the 10.10 compatible version this week.

RedBus.
 
  • Like
Reactions: Jeff and waterstrum
Thanks, RedBus for keeping the DM alive and kicking on the Mac side.

I'm waiting to go to 10.10 for several reasons, but knowing that you are "on the case" is very reassuring.

BTW... Is TMCompanion O.K. on Yosemite?
 
  • Like
Reactions: Jeff
TMC is working in Yosemite. It isn't developer signed, so you need to temporarily lower the gatekeeper setting in the privacy and security settings.
 
Hi RedBus,

Thanks for all your help!

I loaded the following driver, which is what i think you are referring to, and still the same result. 1394:Not ready and unknown device on the Mac

I loaded
IF-FW/DMmkII V1.30f9
IFFWDMmkII_Installer_185483_Release.dmg (MAC)

is that the one you were referring to?

PS: sorry for the long delays in updates - I'm traveling all over the place lately
 
Same result. uninstalled the previous driver and installed the V1.3of9 driver.

Is there some other data that I could provide that may help in diagnosing the issue or someway to ensure the driver installed correctly?
 
steps to verify the driver is loaded .

1. Launch the Console (Apps/Utilities/Console),
search for "IFFW" in the logs

or

2. open a terminal
type :
cd /Library/Extensions
sudo kextload -v 6 IFFWDMmkII.kext

you should see something like
/Library/Extensions/IFFWDMmkII.kext loaded successfully (or already loaded)

Make sure you got the f10 version (188754), and don't have multiple dmg files mounted.
 
This is what returns. Looks ok I think

Kext user-space log filter changed from 0xff2 to 0xfff.

Kext kernel-space log filter changed from 0xff2 to 0xfff.

Requesting load of /Library/Extensions/IFFWDMmkII.kext.

/Library/Extensions/IFFWDMmkII.kext loaded successfully (or already loaded).
 
What does system profile -> FireWire show for this new card?

Maybe your Mac has a FireWire problem?
 
It shows up as an unknown device. I've tried it in three different ports and the my FW hard drives show up and work fine.

I've tried it with the HD's connected ... without anything else connected.

I can't believe I got a second bad card??
 
What Mac is this with 3 FireWire ports?
If any of the FW hard drives has a 2nd FireWire connector, try going via that to the IF-FW/DMmkII. (daisy chain)
 
Still no go.
It's 2.66GHz Quad-Core Mac
4 FW800 ports (2-Front 2-Back)

I'm attaching a screenshot if that helps in anyway

I really appreciate you trying to help.
 

Attachments

  • Screen Shot 2014-11-07 at 8.55.09 PM.png
    Screen Shot 2014-11-07 at 8.55.09 PM.png
    905.5 KB · Views: 11
I also reset the PRAM prior to taking that screenshot
 
doubt this helps ... but ...
 

Attachments

  • dm3200.png
    dm3200.png
    5.2 KB · Views: 11
Am I verifying that it's set to Normal or trying the backup image?
 
See if running on backup changes anything, and check to see if there are any other jumpers set. I think there was a debug one for setting the UniqueID to zero which is used on the factory line.
 
Ok. it's running on normal. J16 is the only jumper set. I'm trying it with J16 (backup) set
 

New threads

Members online

No members online now.