I have a client that just upgraded two suites with new 12-core Macs, joyously (sarcasm) firmware locked to OS X Lion which has created lots of fun issues and hurdles for us in migrating the older MacPros over. One such painful hurdle is the Panasonic P2 drivers. Both rooms have an AJ-PCD20 P2 card reader. We’ve downloaded and installed the Lion drivers and firmware off of the Panasonic site and the cards mount just fine on the desktop of each machine, but the P2 Formatter software doesn’t see any of the cards. So tired of this situation which has occurred many times with OS X upgrades over the years. Both card readers are connected via firewire 800 directly into the FW800 port on the MacPro. Anything we should be aware of?
[Keith Larsen]“I have a client that just upgraded two suites with new 12-core Macs, joyously (sarcasm) firmware locked to OS X Lion which has created lots of fun issues and hurdles for us in migrating the older MacPros over.”
You cannot do a fresh install of Snow Leopard to a new MacPro easily, though, you are correct there. You can however, run Snow Leopard from a clone.
I just upgraded my Mac Pro to Lion and the P2 Formatter works fine for me. I’m using a PCIe-based PCD35 card reader. I think your problem may be that Panasonic’s drivers have an issue in Lion with older card readers. Check the P2 site (panasonic.com/p2) and you should find some info.
Are you using USB2 or 1394b? On both Mac OS X 10.6 (Snow Leopard) and 10.7 (Lion) the P2 Formatter application does not recognize the cards when I have the PCD20 connected via USB2. But it works fine when I have it connected via 1394b. Also, when connected via USB2, the cards show up on the desktop with generic icons. When connected via 1394b, the cards have a P2 icon with the number indicating which slot they are in. Since there is no speed advantage on the PCD20 when using Firewire, I was anticipating setting up a station where it is connected with USB2… however, USB2 doesn’t appear to be fully supported.
I have the same issue on a Mac mini running 10.7 and a Mac Pro running 10.6. Anyone else experiencing this?