Kernel Panics - OSX 10.5.2 - Qtime 7.4.5 - and a Duel Adapter on a MBP

daybreak

Member
I just bought a new MBP (Penryn) and a duel adapter.

I am running:
OSX 10.5.2
Quicktime 7.4.5
P2CMS 1.1.9
FCP 5.1.4

in a MBP and Duel Adapter. I am getting kernel panics when using the duel adapter and Barry's Mac P2 workflow. I am not getting kernel panics when using Barry's Mac P2 workflow and offloading straight from the HVX through firewire. I am also not getting kernel panics when using the duel adapter and copying the P2 cards' contents (drag and drop).

I have not run into any other issues in FCP or with any of my footage using the drag and drop method or using Barry's Mac P2 workflow through HVX ->firewire->MBP->HDD. So far the only kernel panics are when using the duel adapter and Barry's Mac p2 workflow.

Is quicktime 7.4.5 the likely culprit or is it my duel adapter? Sorry in advance for cross posting this, and thank you in advance for ANY input/suggestions.
 
David,

With my MBP off, I insert the duel adapter without the P2 card in it.
I boot up my MBP.
I shot to P2 using an HVX and 720/24pn and an 8gb card.
I write protect the card and stick it in the Duel Adapter and the P2 card mounts fine.
I launch P2CMS and then select the P2 card as the source and then I select all the clips and right click -> export to a bus-powered firewire400 drive (I have also tried exporting to the MBPs hard disk and same result) .

After about 1gb in or so through the transfer, I am getting a kernel panic, 5 times out of 5. The screen freezes and I can't move my mouse and the pop-up window telling me I need to restart by holding the Power button comes up.

I have done the drag and drop method using the duel adapter and I had no issues. I have also done the same method as above (Barry's Mac P2 workflow), instead using the HVX in firewire mode instead of using the duel adapter, and exporting to the MBPs hard disk instead of an external firewire400 drive. That method works fine.
 
turn on macbook pro
insert duel adapter
turn on write protect on the card
then insert card into adapter

but if your card mounts then that doesn't matter as much.

are you using p2cms version 1.1.9?

i was using an older version one time and it was giving me similar issues, it would lock up but no kernal panic.
 
Since the Panasonic now has P2Formatter utility for the Mac, I've become daring and have gone back to my lazy method of drag and drop...without incident.

turn on macbook pro
insert duel adapter
turn on write protect on the card
then insert card into adapter
drag and drop contents and lastclip.txt to folder
sometimes use Raylight to make sure viewable with QT to check clips
remove and unprotect P2 then reinsert
use P2Formatter utility to reformat the card
ready to go

P2CMS is a productivity killer and confusing. I would rather start using my old workflow of dumping to an XP PC and then using a USB drive to xfer to the Mac than to use P2CMS. (the PC has P2 Viewer for logging and QC.)
 
The Duel Adapter is inserted without the p2 card AFTER the MBP is powered up and has launched the OS.

Then the p2 card is inserted into the MBP.
 
update:

Just loaded P2CMS and the appropriate drivers into my girlfriend's identical Penryn MBP. I had zero issues using the same workflow that is causing kernel panics in my Penryn MBP. The only difference I can think of between our MBPs is that I have FCP 5.1.4 loaded on mine and she does not. Also I have 4gb of third-party ram and she has the stock 2gb of ram.

Could FCP 5.1.4 or my third party ram possibly be the culprits?
 
update:

Just loaded P2CMS and the appropriate drivers into my girlfriend's identical Penryn MBP. I had zero issues using the same workflow that is causing kernel panics in my Penryn MBP. The only difference I can think of between our MBPs is that I have FCP 5.1.4 loaded on mine and she does not. Also I have 4gb of third-party ram and she has the stock 2gb of ram.

Could FCP 5.1.4 or my third party ram possibly be the culprits?

I would think that might be the reason for the problems, fcp 5 + the new quicktimes, ect.
 
David,

I have tried all different kinds of ways. Inserting DA after boot-up and P2CMS has launched, and THEN inserting P2 into DA. Inserting DA before boot-up with p2 in it, with p2 without it, every possible combination or order I can think of.

Every single time offloading straight from the DA-P2 through P2CMS I am getting kernel panics at around 1gb through the transfer.

I can however, use FCP to import the P2 card using the DA without any problems. Is this workflow safe? There are a few more steps, but I actually like this workflow because I don't end up with .mxf versions AND .mov versions of my files. What is everyone's opinion of this? Of course i'd be making back-ups of my .mov files but I would not have any of the .mxf files.
 
I used the DA to easily and conveniently transfer footage from cards to laptop.

I write protect the cards, and then use FCP or P2 Log to access the footage after it's copied to the MBP, and after I've ejected the card and disconnected the DA.

Repeated kernel panics with your workflow isn't good for either the p2 cards or the OS, much less the computer

Sometimes we need to assess what is important and what has priority. And with this EC/34 adapter, I realize that all I want it to do is to transfer the volumes.

Nothing more
 
Back
Top