Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Help! This brand new system is killing me.

  • Help! This brand new system is killing me.

    Posted by Kylecine on July 27, 2005 at 4:35 am

    I’m trying to narrow down some ridiculous performance issues I’m facing. It’s locking up like crazy and I keep getting kernal mac error messages. I’ve been forced to reboot some 10 times today alone.

    Since the only third party component in my system (apart from Crucial RAM) is a Sonnet Tempo-x 8-port esata PCI card, I’m wondering if that is where my problem lies. I have it in slot 2. I know slot for is the fastest, but the card is too big for it. I have my dual monitors in slot 1. It’s a brand new system, but is acting like it’s ten years old. I wish I could even give a more specific scenario in which these problems occur, but it is all over the map. I can’t find any consistent triggers.

    Here is what I am running. Any feedback would be greatly appreciated.

    Kyle

    Dual 2.7
    250 gig system drive
    400 gig internal drive for graphics
    6 gig of Crucial RAM
    FCP 5 (haven’t done the update yet…thought I’d wait a little longer)
    OS 10.4.2 (waiting a hair longer)
    AJA io (drivers updated to newest on AJA’s site)
    Sonnet Tempo-X 8-port ESATA card
    8-bay hotswappable enclosure from MacGurus with 300 gig Seagate drives stripped as RAID 0

    Capturing/editing 10-bit uncompressed component

    Shawn Bockoven replied 21 years, 1 month ago 4 Members · 8 Replies
  • 8 Replies
  • Michael Alberts

    July 27, 2005 at 5:55 am

    Seeing as how your getting kernal panics, my first guess would be the RAM. Take out all RAM that wasn’t native to the system at purchase. This will probably bring you down to 512MB or RAM, but try running in that config for a day and see if the issues go away. Then add back several sticks and continue on for another day. Do this until you can narrow down the possible bad RAM chip. Kernal panics are almost always hardware related, and most of those are bad RAM.

    Michael Alberts
    Ambidextrous Productions, Inc.

  • Walter Biscardi

    July 27, 2005 at 12:26 pm

    [kylecine] “I have it in slot 2. I know slot for is the fastest, but the card is too big for it.”

    what do you mean it’s too big for slot 4? There’s a lot of room in a G5 for full sized card like the nVidia Ultra 6800 in one of my machines. What slot do they recommend that card be in? Most external drive controllers want to be in Slot 4 since that’s the fastest slot in the machine. Make sure you’re running whatever the lastest driver is for that particular card.

    Have you run the machine with the card removed and the drives disconnected? This would help you see if it’s the card and/or drives.

    Walter Biscardi, Jr.
    Creative Genius, Biscardi Creative Media
    https://www.biscardicreative.com

    Now in Production, “The Rough Cut,” https://www.theroughcutmovie.com

    “I reject your reality and substitute my own!” – Adam Savage, Mythbusters

  • Kylecine

    July 27, 2005 at 2:57 pm

    The end of the card (toward the back of the computer) is too thick to be inserted. The physical space/hardware conflict is that, next to slot 4, there’s a power connector on the motherboard that “conflicts” with the “fatter” 8 port assembly. You could unplug the “offending” motherboard connector to make the Sonnet eSATA 8 fit in slot 4, but the two fans behind the G5’s CPUs will stop spinning. That’s not a realistic solution.

    I had at one point taken out that card all together to see how it ran. And although it seemed to run a bit better, the test was really too short and inconclusive; that essentially takes all my media offline and I didn’t feel that performance could be accurately tested if I ran 10-bit uncompressed video on the internal drive, even if it is my second drive for graphics.

    Someone else suggested the some of the kernal mac errors are due to bad RAM. This is actually the second set of RAM I’ve gone through. And in addition to that, while I was waiting for my replacement RAM, I ran it for two days on the native Apple 512 that the machine shipped with. I experienced similar problems then as well. I’m beginning to wonder if it is my motherboard.

  • Kylecine

    July 27, 2005 at 3:00 pm

    This is actually my second set of RAM since I drew much the same conclusion as you did. However, while waiting on my new set of RAM to come in, I ran on the native 512 for a couple of days and still experienced kernal panic errors.

  • Shawn Bockoven

    July 27, 2005 at 4:29 pm

    You are not alone. I suspect there is a bad batch of dual 2.7

  • Kylecine

    July 27, 2005 at 4:51 pm

    That is extremely valuable info. I had not heard of Apple responding that way. I’ll see what I can do. Thanks a lot.

  • Kylecine

    July 27, 2005 at 4:56 pm

    Quick question. You went though general AppleCare, not Apple’s ProVid support, right?

  • Shawn Bockoven

    July 27, 2005 at 5:45 pm

    AppleCare and good luck.

    System configuration:

    Processor 065-5747 Dual 2.7GHz PowerPC G5
    Memory 065-5702 2GB MB DDR400 (PC3200)-4X512
    Hard Drive 065-5711 2X400GB Serial ATA-7200rpm
    Optical Drive 065-5537 16x SD DL(DVD-R/CD-RW)
    Graphic Support 065-5539 ATI Radeon 9650 XT w/256MB
    Modem 065-5719 None
    Wireless 065-5723 None
    Gigabit Ethernet PCI 065-5734 None
    Fibre Chl PCI 065-5736 None
    Keyboard Language 065-5531 Apple Keyboard & Mouse
    Mac OS Language 065-5543 Mac OS X-Multilingual
    Server Mac OS Language 065-5738 None
    Apple Software Applications 065-5796None…
    Spare Characteristic 065-4681 None….
    Country Kit 065-5529 Country Kit
    _______________________________________________________________________________

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy