Mac OS 10.6 cannot recognize Aptus 65

[evgeny]

Hi,

I connected today my Aptus 65 to Snow Leopard, which run on my new Macbook Pro (latest model "5,2" June 2009), for the first time.
The digital back is NOT recognized by the new Mac OS  10.6.
As the result the Aptus 65 cannot work tethered with the new Leaf Capture 11.2.9.

The memory card in the digital back can be read in Snow Leopard without any problem when connected via a card reader, not via the Aptus. So, it's the Aptus problem.
The Aptus back does work with older Leopard 10.5.8, I tested this connection today with another Mac computer.

Please note, in October 2009 I sent my Aptus 65 to Kodak Israel for service under warranty and received it back a week or two ago. Kodak reps said the back is in like new condition, perfect, perfect...
But why the Aptus 65 cannot connect to Snow Leopard?

(at such times I think to change platform, never had any issues with Nikon)

[Frank Doorhof]

Remove the card and does it work than ?

[evgeny]

Remove the card and does it work than ?

Frank, the Snow Leopard doesn't show the warning without the card.
The back doesn't exist in the File System (no memory attached), nor recognized in the Leaf Capture 11.2.9.
The problem still exists.

[yaya]

Hi,

I connected today my Aptus 65 to Snow Leopard, which run on my new Macbook Pro (latest model "5,2" June 2009), for the first time.
The digital back is NOT recognized by the new Mac OS  10.6.
As the result the Aptus 65 cannot work tethered with the new Leaf Capture 11.2.9.

The memory card in the digital back can be read in Snow Leopard without any problem when connected via a card reader, not via the Aptus. So, it's the Aptus problem.
The Aptus back does work with older Leopard 10.5.8, I tested this connection today with another Mac computer.

Please note, in October 2009 I sent my Aptus 65 to Kodak Israel for service under warranty and received it back a week or two ago. Kodak reps said the back is in like new condition, perfect, perfect...
But why the Aptus 65 cannot connect to Snow Leopard?

(at such times I think to change platform, never had any issues with Nikon)

If your back works on another computer then it is not likely a back hardware issue, so you should try and isolate the problem:

Do other FireWire 400 devices connect to this specific Mac without issues?
What cable is used to connect the back? Is that the same cable that was tested on the other machine? Are any adapters being used and if so which ones?
Is the Mac running on mains power or on its own battery?
When you connect it to the Mac, does the orange light come on? Do you hear the fan spinning? Do you see it in the Apple System Profiler?

Was 10.6 put on as a fresh install or an update from 10.5?
If the latter, was 11.2.9 installed after the update?
If 11.2.9 was installed AFTER 10.6, did it ask you to restart the Mac?
If not, I would suggest to re-install 11.2.9, re-start the Mac, remove any FW devices and the CF card. Then launch 11.2.9 and plug the back in. Do not press any button, just wait a few seconds and see if it initiates to connection or if it brings up an error message.

BTW when you say card reader is that USB or FW?

[evgeny]

If your back works on another computer then it is not likely a back hardware issue, so you should try and isolate the problem:

Do other FireWire 400 devices connect to this specific Mac without issues?

Yes, other devices work fine without issues.

What cable is used to connect the back? Is that the same cable that was tested on the other machine? Are any adapters being used and if so which ones?

The same Leaf FireWire cable.

Is the Mac running on mains power or on its own battery?

The Macbook Pro running on mains power.

When you connect it to the Mac, does the orange light come on? Do you hear the fan spinning? Do you see it in the Apple System Profiler?

The orange light come on, I hear the fan. I don't know where is Apple System Profiler, but it doesn't matter, it's only an indication. The VOLUMABLE appears in the file system and automatically ejected by the Snow Leopard with the warning that I provided in the first post (ejected after I press Ok on the warning, or before that after a few seconds).

Was 10.6 put on as a fresh install or an update from 10.5?

10.6  is a fresh installation.

If the latter, was 11.2.9 installed after the update?

11.2.9 was installed after fresh installation (no update).

If 11.2.9 was installed AFTER 10.6, did it ask you to restart the Mac?

11.2.9 was installed after 10.6, reboot performed.

If not, I would suggest to re-install 11.2.9, re-start the Mac, remove any FW devices and the CF card. Then launch 11.2.9 and plug the back in. Do not press any button, just wait a few seconds and see if it initiates to connection or if it brings up an error message.

It doesn't matter once again, because Snow Leopard and Aptus 65 don't like each other.

BTW when you say card reader is that USB or FW?

Card Reader via USB. Other FW devices work without issues.

[yaya]

OK,

One more question regarding the cable: is that the 400-800 cable or the 400-400 with an adapter (assuming that your MBP only has FW800 port)

The Apple System profile can be accessed by selecting "About This Mac" under the Apple menu and then pressing "more info". Go to FireWire and while the back is connected (with no card in it) see if it shows a Leaf Product.

Now I suggest that you contact your dealer ASAP with all this information, so that they can follow it up with the support team to investigate this further.

[evgeny]

OK,

One more question regarding the cable: is that the 400-800 cable or the 400-400 with an adapter (assuming that your MBP only has FW800 port)

The Apple System profile can be accessed by selecting "About This Mac" under the Apple menu and then pressing "more info". Go to FireWire and while the back is connected (with no card in it) see if it shows a Leaf Product.

Now I suggest that you contact your dealer ASAP with all this information, so that they can follow it up with the support team to investigate this further.

I use Leaf's 400-400 with 800 adapter, but I also tried 400-800 cable, guess if there any difference using these cables with Aptus 65, or please guess if my Sinarback 54H works when attached to the same port via a FireWire cable.
I sent a request to Mr. Koresh at Jugend Brothers.

But
Why should I spend a half day to drive to Tel Aviv again and another half day to take the Aptus back - after the back was just serviced and Kodak rest assured me the back is in perfect working condition??! I'm sure it was before they took the back...
Why should I feel that my expensive gear doesn't work as needed, while I can use Nikon D3x without any issues at all.

I actually feel like the Kodak did something with the back to force me to buy the long discussed here Leaf's special plan... The back returned from the service just before you posted here in the forum that Leaf reconsider their plans for LC 11.2.9 policy and Snow Leopard support...
I have no choice, will spend the TIME to go to dealer two times again. But I think I will pretty much sell the Aptus to end all this nightmare and need for the extensive "support"...
Time is (my) money.

[snickgrr]

It sure doesn't look like an Aptus problem if it tethers fine with other computers.

I remember when Apple switched to intel there was quite a problem with getting the computer to recognize the back because of firewire preferences.  There were files from the old system that needed to be trashed in the proper order with restarts in between in order for the new OS to recognize the back.

You never answered whether the Apple Profiler can see the back.

[evgeny]

It sure doesn't look like an Aptus problem if it tethers fine with other computers.

I remember when Apple switched to intel there was quite a problem with getting the computer to recognize the back because of firewire preferences.  There were files from the old system that needed to be trashed in the proper order with restarts in between in order for the new OS to recognize the back.

You never answered whether the Apple Profiler can see the back.

There is no Aptus under FireWire in System Profiler.

[asf]

Frank, the Snow Leopard doesn't show the warning without the card.
The back doesn't exist in the File System (no memory attached), nor recognized in the Leaf Capture 11.2.9.
The problem still exists.

Hi Evgeny,

So it's only a problem when there is a card in the back and it's tethered (it tethers to 10.6 without card in the back)?

There are long instructions in the release notes for 11.2.9 on how to format CF cards, it is different to previous versions. Have you done that?

[evgeny]

Hi Evgeny,

So it's only a problem when there is a card in the back and it's tethered (it tethers to 10.6 without card in the back)?

There are long instructions in the release notes for 11.2.9 on how to format CF cards, it is different to previous versions. Have you done that?

Without the card this storage device doesn't exists in the Mac OS...
I just formatted the card as specified in the release notes for 11.2.9 (Volume scheme : 1 Partition Format: MS DOS (FAT) Option: Master Boot Record), inserted the card in the Aptus, plugged-in the FireWire cable, and got the same error message.
Then I restarted Macbook Pro in 64-bit mode, plugged-in the FireWire cable, and got the same error message.

[yaya]

Trying to save you the trip:

Was the back working on this machine prior to installing 10.6 and 11.2.9?
Does the back work on the other Mac using the same cable+adapter combo?
When you say 400-800 cable is that the Leaf one that has the straight 800 connector and the L-shaped 400 connector?

When you connect the back to the computer (with no card in it and without launching LC), the Orange light should flash, the fan will spin and this is what you should see in the ASP:



If this is what you see on the other machine but not on the SL one, then it must be an issue with either the port or the bus not providing enough power or some sort of extension conflict in the system.

[evgeny]

Was the back working on this machine prior to installing 10.6 and 11.2.9?

This is a brand new Macbook Pro 2.8Ghz with 10.6.1 which I received very recently. I'm sure it is in full working condition. I have no problems with other FireWire 400 and 800 devices.
Till now I used the Aptus 65 worked on another Macbook Pro 2.53Ghz with 10.5.8 and 11.2.8 and Mac Mini with with 10.5.8 and 11.2.8 without issues. It doesn't work on 10.6.
The card appears for a short time in the Finder, then the error message is displayed, and then the back is automatically ejected by the OS 10.6.

Does the back work on the other Mac using the same cable+adapter combo?

Yes

When you say 400-800 cable is that the Leaf one that has the straight 800 connector and the L-shaped 400 connector?

I use the original Leaf cable 400-400 with 800 adapter on one side. I use same cable with all other computers.

When you connect the back to the computer (with no card in it and without launching LC), the Orange light should flash, the fan will spin and this is what you should see in the ASP:

In the FireWire section I see the following line "Maximum Speed: Up to 800 Mb/sec".
There are no new lines when I connect the Aptus 65.
The orange light is on and I hear the fan.

If this is what you see on the other machine but not on the SL one, then it must be an issue with either the port or the bus not providing enough power or some sort of extension conflict in the system.

I see no issues with all other 400 and 800 devices. I think it is a sort of firmware in the back... Once the firmware communicate with the Mac OS 10.6. it is automatically self-ejected. This is why I see the card only for a short time in the Finder...

[yaya]

In the FireWire section I see the following line "Maximum Speed: Up to 800 Mb/sec".
There are no new lines when I connect the Aptus 65.
The orange light is on and I hear the fan.

In the ASP, after plugging the back in (with no card in it), please press cmd+R (Refresh). Still nothing comes up?

I see no issues with all other 400 and 800 devices.

Other devices may have their own power supply or they might need less power. I suspect that the adapter is the weak link that somehow cuts the power down.
Do you have a powered external HD with a FW400 port that can be chained to the back?

[evgeny]

In the ASP, after plugging the back in (with no card in it), please press cmd+R (Refresh). Still nothing comes up?

Other devices may have their own power supply or they might need less power. I suspect that the adapter is the weak link that somehow cuts the power down.
Do you have a powered external HD with a FW400 port that can be chained to the back?

Without the card nothing comes up after cmd+R in Profiler and Finder. The orange light is On, the fan rotates.
I have an external HD enclosure, it works without issues via FireWire cable to the same port.

[yaya]

Without the card nothing comes up after cmd+R in Profiler and Finder. The orange light is On, the fan rotates.
I have an external HD enclosure, it works without issues via FireWire cable to the same port.

Is the HD powered from its own power supply? Does it have a 2nd FW400 port so that you can connect the back to it while it's working?

[evgeny]

HD is powered from FireWire. The enclosure has a 2nd FireWire port, but its instruction warns to not connect two cables at the same time.


Mac OS Console

11/7/09 9:41:25 PM   fseventsd[35]   check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x10047f8c8)
11/7/09 9:41:25 PM   fseventsd[35]   log dir: /Volumes/APTUS/.fseventsd getting new uuid: 79F34A00-6E05-40CF-82F0-EF5CE4541273
11/7/09 9:41:28 PM   kernel   disk1s1: media is not present.
11/7/09 9:41:28 PM   kernel   
11/7/09 9:41:28 PM   kernel   
11/7/09 9:41:28 PM   kernel   Last]
11/7/09 9:41:28 PM   kernel   disk1s1: media is not present.
11/7/09 9:41:28 PM   kernel   
11/7/09 9:41:28 PM   kernel   
11/7/09 9:41:28 PM   kernel   msdosfs_fat_uninit_vol: error 6 from msdosfs_fat_cache_flush
11/7/09 9:41:28 PM   fseventsd[35]   disk logger: failed to open output file /Volumes/APTUS/.fseventsd/000000000009cc5b (No such file or directory). mount point /Volumes/APTUS/.fseventsd
11/7/09 9:41:28 PM   fseventsd[35]   failed to unlink old log file /Volumes/APTUS/.fseventsd/000000000009cc5b (No such file or directory)
11/7/09 9:41:28 PM   fseventsd[35]   unmounting: failed to remove log dir /Volumes/APTUS/.fseventsd (No such file or directory)
11/7/09 9:42:44 PM   com.apple.launchd.peruser.501[90]   ([0x0-0x15015].com.apple.Preview[166]) Exited: Killed


Please note, that I formatted the Card as required in 11.2.9, see my post above, and the card can connect to Snow Leopard without issues via a usb card reader.


Sometimes there are other errors shown in the console. The most interesting is the following:

11/7/09 9:15:25 PM   diskarbitrationd[12]   unable to mount /dev/disk1s1 (status code 0x00000047).

This specific error can actually be the indication of BAD firmware in the device, that's what I meant in one of my posts above...


11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 10784] [LBlkNum 1344] [FSLogMsgID 410295980] [FSLogMsgOrder First]
11/7/09 9:58:54 PM   kernel   0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 13856] [LBlkNum 1728] [FSLogMsgID 37395875] [FSLogMsgOrder First]
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   diskarbitrationd[12]   unable to mount /dev/disk1s1 (status code 0x00000047).
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: I/O error.
11/7/09 9:58:54 PM   kernel   disk1s1: media is not present.

[evgeny]

I replaced the camera with another one, and:

1. "Leaf Compact Flash" and "Leaf Digital Back" appear in the "System Profiler/FireWire"
2. Digital back shown in the Finder.
3. Leaf Capture 11.2.9 can connect to the digital back, and work tethered.

So, everything is as it should be when Aptus is mounted to the second camera.

It's strange, that the Aptus works with my first camera when connected to another computer with Leopard 10.5.8. I don't see much difference: FireWire is connected to the back, not to the camera.
My Sinarback 54H can work with both cameras without issues. The cameras are mint (or like new).

Yair, and others, thank you for trying help me.

[Frank Doorhof]

It's probably a power problem.
I've had a similar problem.

When I used my Aptus22 on the AFD/II with a 10mtr firewire cable to a repeater (without power) and the original leaf cable it all worked flawless.
When I switched to the RZ the orange light would come on, the back would spin up but no connection and no connection on my macbook pro, on my macpro it did work.
When I powered my repeater it did work.
I changed the 10mtr firewire cable for a 5 mtrs and now both cameras work without any problem.

You're response that it's all the fault of the Leaf is not correct.
When a camera works on another system it's always something else that is going wrong, it's very simple when a camera works it works.
When it doesn't work under another OS or on another computer you have to look for the problem somewhere else, in this probably power.

In this case the problem is I THINK a power problem, if you want to be sure buy for a few dollars a power firewire hub/repeater and try if it works than with the other camera.
I think it will.
I know there have been serious problems tethering digital backs to Macbook pro's 17" in the past.
I know my MBP will only last 45 minutes before giving me "stripes" in my images, that's why on location we run from the applejuicze batteries which gives me app 4 hours of working time with the back connected.

[yaya]

I also believe it's a power issue as some Macs can be less consistent than others.

Like Frank said, you should use a powered repeater to eliminate any future problems. Some say it can help in fighting corporate conspiracies as well  

Yair