P2 crashing powerbook

Thanks, Bob, for those additional details which might be helpful when I get to work on it next week. Meanwhile, you might want to try turning networking off.

I also re-read the posts and it seems that some are reporting a kernel panic (for those less computer-savy, you know you have a kernel panic when you get that white box of death "Please restart your computer"). Kernel panics are usually hardware related and are caused by with hardware. That could definitely lead to either a problem specifically with the 1.67 OR to 10.4.6, which caused problems in a number of other areas.

Ned Soltz
 
i've got a 1.67 P-book, 10.4.6, P2 driver software installed, and have never had any problems with the computer crashing when i eject cards. the only issue has been that after 5 or 6 cards, the computer won't mount a card, so i've got to restart.
 
No. Using a 1Ghz PB and just said the hell with the other 1.67Ghz until someone at Apple or Panasonic comes up with an answer. I've already wasted hours testing this, but feel there is no easy answer because of it's randomness.
 
So again, to help get to the bottom and eliminate one variable-- Bob, did you update to 10.4.6 via software update or via the combo updater? Have you tried downloading and installing the 10.4.6 combo updater?

Ned Soltz
 
Ned...

My PB 1Ghz used the combo updater...I will have to check with the owner of the PB 1.67 Ghz (it is not my machine, but I was using it) if he used the updater or not. I suspect he did the software updater because he would do what ever is easiest but I do not know for sure. Will try to find out.

The problem I'm finding diagnosing this is that it's so damn intermittent. Sometimes it would seem to work flawlessly through 20 or more ejects...other times it became every 2 or 3 ejects. (And why a physical eject???) I would make a new user and it seemed to work..then a few days later it would start crashing again. I would find it a lot less frustrating if it just wouldn't work at all. And why would it be just a 1.67 Ghz machine? And only some of them?
 
For troubleshooting purposes, in order to isolate the source of the problem, do you have any problems mounting and importing via the camera (in FireWire devlice mode)? If this works like a charm, but you get crashes with the PCMCIA slot, but not on another PowerBook, then I'd start suspecting the PCMCIA slot, but not before doing a clean install.
 
Hi guys.

I have experienced this as well, mostly on the first import after a wakeup from sleep on my PB 1,25 G4.

The computer freezes for about 10 seconds, then the card is detected by the kernal (I get an eject menu in the menubar) but the card is not mounted by the Panasonic P2 driver.

I strongly believe that it's an Apple Cardbus kernal driver issue.

I had the exact same experience when I had a CF PCMCIA card reader for my DSLR.

The computer had the exact same freezes when I mounted the Compact flash cards, and the whole system would slow down when I offloaded the card. I actually bought an external CF reader instead.
 
cinemakinoeye said:
For troubleshooting purposes, in order to isolate the source of the problem, do you have any problems mounting and importing via the camera (in FireWire devlice mode)? If this works like a charm, but you get crashes with the PCMCIA slot, but not on another PowerBook, then I'd start suspecting the PCMCIA slot, but not before doing a clean install.
Click to expand...

No problems otherwise except when ejecting the P2 card from the PCMCIA slot and only sometimes and only sometimes randomly with no actual pattern that you could eliminate variables. Was thinking about a clean install because there have been reports on this forum that people have 1.62 Ghz PBs that work okay. But...it's not my PB and even if I did the clean install, would it show up again 20 or 21 or 22 cards later?
 
Anders Holck said:
Hi guys.
I strongly believe that it's an Apple Cardbus kernal driver issue.
Click to expand...

That would sound plausible if it happened to everyone but if this was the case, wouldn't all PBs have the same problem? Or do different models have different kernal drivers for their cardbus? Why would they work sometimes and not others? Why is it the physical disengagement that causes the hard crash/freeze?
 
You must log in or register to reply here.
Back
Top