Mac Pro 2009 audio problems

Hi there.
I have a mac pro 2009 quad-core intel xeon and since i've updated to 10.7.3 i've started to have problems with audio.
Sometimes when i turn on the mac, the audio doesn't work (the audio icon in the menu bar is shown grey, and if i try to rise the volume using the keyboard it doesn't work.
I've tried to get inside the audio preferences and select a different audio output like the internal speakers (i currently have speakers connected into the jack output) but it doesn't work too.
The only way to resolve this seems to do a RAM reset during the boot, but it's very annoying do this every time.
Anyone can help me to resolve this? Is it a software problem? Or my logic board is going to die?
It never did anything like this before the update.
Thanks for the support and forgive me for my bad english.
Greetz,
Lorenzo

I'm having similar problems with a brand-new Mac Pro 8-core. Mouse cuts out (I'm using a wired keyboard thankfully) and my Jawbone headset will work wonderfully with my old MacBook Pro but will only pair (maybe) on my Mac Pro.
Called and spoke with an expert and feel I get the run around. He had me shut down and unplug everything for 30 seconds. I did it but felt he was just having me "do something" to get me off of the line.
Apple has a problem with Bluetooth on their Mac Pros and isn't dealing with it.

Similar Messages

Mac Pro 2009 Bootcamp problem

I have a fresh install of the Snow Leopard and I was about to install Windows XP on the bootcamp partition but to my surprise I've got this error:
http://content.screencast.com/users/idertkin/folders/Jing/media/64fb8a21-d49c-47 4e-a629-26163daa2ea0/00000001.png
Boot Camp Assistant cannot be used. You must update your computer's BOOT ROM.
What gives? I was running Boot Camp with no problems with Leopard.
My Boot ROM Version: MP41.0081.B03

Hi,
Did you attempt an EFI flash bios(efi) update? Sounds like the update either didn't finish correctly, or something happened where you or something caused the computer to shut down inadvertantly. My next advice to you:
Did you try to reset the SMC? If that does not work, then to restore the mac pro's EFI, you will need to download from another mac computer, EFI Firmware Restoration CD 1.8(I think).. Burn it to a CD.. and insert it into another mac and use that mac to FLASH the EFI to your non-working mac pro.. I will provide the link for you..
http://support.apple.com/kb/DL976
Hopefully, this will resolve your problem.. Please note: This does NOT update an existing firmware version, it is only used to restore the original firmware in the event of an unsuccessful flash.
Good luck!
P.S.: Before you do this, follow the normal trouble shooting procedures.. check that your memory is installed firmly in the dimm sockets.. try one at a time.. if the memory checks out clean and working, then try the video card.. if you have another known working video card, use that as a test... if that fails... then RESET THE SMC... To do this, you need to power down the mac pro.. Unplug it and let stand for 15 seconds while holding the main power button.. Plug back in and that should restore things... IF NOT, then download the firmware restoration cd and burn to a disk.
Report back and let me know if you get it to work... IF you did all the above and still nothing, I suspect a faulty logic board and or processor board, or possibly a faulty processor(You would hear a series of beeps to indicate this).

Mac pro 2009 bluetooth problems

Hey guys. gals... so... if you followed y previous saga of the quad core, you know it just got replaced by a eight from mac fro various maladies and problems. Yay me. Except..... the bluetooth f'n ***** on this thing....
It took an incredibly long time for it to pair with the keyboard... then the ghost pop up says "connection lost" like every 4 minutes if you aren't typing on it. which if you run photoshop day and night like never happens. So..... yeah. Mouse practically doesn't work either works half the time or super slow or like not at all.....
So....whats going on? I tried to plug in my old bluetooth adaptor from the quad core (which had an airport card that also died) and it tried to set up some sort of pan network, then the almost working bluetooth died, so I couldn't click around..
oh.. and I restored my entire system from time machine if that matters...?
Questions... if this is the fatal flaw in the mac pro line.. thats bad. So.....how do i
-turn off onboard bluetooth
-engage usb mounted bluetooth.
Thanks
m

I'm having similar problems with a brand-new Mac Pro 8-core. Mouse cuts out (I'm using a wired keyboard thankfully) and my Jawbone headset will work wonderfully with my old MacBook Pro but will only pair (maybe) on my Mac Pro.
Called and spoke with an expert and feel I get the run around. He had me shut down and unplug everything for 30 seconds. I did it but felt he was just having me "do something" to get me off of the line.
Apple has a problem with Bluetooth on their Mac Pros and isn't dealing with it.

Mac Pro 2009 - Kenel panic problem, any ideas?

My Mac Pro 2009 is nearly 3 years old, haven't had any problems with it but in the last day i've had a crash and a kernel panic. 1st time a grey box came down over a quarter of the screen and the machine froze and I had to hold th power button to restart.
2nd time I had a kernel panic with the following error, I haven't added any new hardware for months. The kernel panic I got is as follows:
[COLOR="Teal"]Interval Since Last Panic Report: 3567480 sec
Panics Since Last Report:          2
Anonymous UUID:                    89C272F3-CAEE-467F-B957-F2D902168859
Mon Dec 19 07:00:42 2011
Machine-check capabilities (cpu 10) 0x0000000000001c09:
family: 6 model: 26 stepping: 5 microcode: 17
Intel(R) Xeon(R) CPU           E5520 @ 2.27GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000800 invalid
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f valid
MCA error code:            0x0e0f
Model specific error code: 0x0040
Other information:         0x00000000
Threshold-based status:    Undefined
Status bits:
   Processor context corrupt
   ADDR register valid
   MISC register valid
   Error enabled
   Uncorrected error
IA32_MC1_ADDR(0x406): 0x0000000000000280
IA32_MC1_MISC(0x407): 0x0000000001061d50
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0000000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0000000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0000000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0000000000000000 invalid
Package 1 logged:
IA32_MC8_STATUS(0x421): 0x0000000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0x0000000000000000 invalid
panic(cpu 10 caller 0x2aaf41): Machine Check at 0x00f039c6, thread:0x198cdb7c, trapno:0x12, err:0x0,registers:
CR0: 0x80010033, CR2: 0x000f7000, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x00000006, EBX: 0x16b18c00, ECX: 0x859250a8, EDX: 0x00000000
ESP: 0x93352680, EBP: 0x93352758, ESI: 0x16a2ca00, EDI: 0x00000003
EFL: 0x00000046, EIP: 0x00f039c6
Backtrace (CPU 10), Frame : Return Address (4 potential args on stack)
0x85981fb8 : 0x21b837 (0x5dd7fc 0x85981fec 0x223ce1 0x0)
0x85982008 : 0x2aaf41 (0x59dfe4 0x59e0d1 0xf039c6 0x198cdb7c)
0x859820f8 : 0x2a29f2 (0x1 0x28 0xe8243489 0xfffeed30)
0x93352758 : 0xf04c58 (0x9fd722e8 0x76 0x3 0x2b1f6a)
0x93352858 : 0x2ad0c5 (0xffffffff 0x7fffffff 0x93352898 0x858ae000)
0x93352878 : 0x225bba (0x858ae49c 0x9fd6e6f1 0x76 0x858ae488)
0x933528d8 : 0x22698c (0x1 0x198cdb7c 0x16b030dc 0x0)
0x93352948 : 0x2275b0 (0x198cdb98 0x2198ae 0x0 0x0)
0x933529b8 : 0x227654 (0x0 0x0 0x0 0x0)
0x933529d8 : 0x2199ab (0x0 0x76 0x933529f8 0xbcb382)
0x93352a08 : 0x535547 (0xa 0x3e8 0x93352a58 0xbcb3d5)
0x93352a28 : 0xbcb348 (0xa 0x304 0x0 0x38377073)
0x93352a58 : 0xbcb6c5 (0x1791c300 0x93352a7e 0x0 0x93352b2c)
0x93352a98 : 0xbcb759 (0x1791c300 0x544d4133 0x93352df8 0x5526cf)
0x93352ab8 : 0x5542d0 (0x1791c300 0x544d4133 0x93352df8 0x0)
0x93352b08 : 0xbc742c (0x17760fc0 0xbcb726 0x544d4133 0x93352df8)
0x93352b48 : 0xbc98a7 (0x1791c300 0x544d4133 0x93352df8 0x2)
0x93352b98 : 0x56d196 (0x1791c300 0x18563c70 0x93352ddc 0x50)
0x93352bd8 : 0x56e2d8 (0xbcf570 0x19298700 0x18563c70 0x50)
0x93352c28 : 0x56eb59 (0x19298700 0x2 0x93352c70 0x0)
0x93352d48 : 0x286638 (0x19298700 0x2 0x18563c6c 0x0)
0x93353df8 : 0x21dbe5 (0x18563c44 0x191e05a0 0x8f9f0 0x6377)
0x93353e38 : 0x210a86 (0x18563c00 0x0 0x19815310 0x18717d90)
0x93353e98 : 0x216f84 (0x18563c00 0x0 0x0 0x0)
0x93353f18 : 0x295914 (0x93353f44 0x0 0x0 0x0)
0x93353fc8 : 0x2a20f8 (0x19274940 0x0 0x10 0x0)
      Kernel Extensions in backtrace (with dependencies):
         com.apple.driver.AppleSMC(3.1.0d5)@0xbc6000->0xbcffff
            dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0xbc2000
         com.apple.driver.AppleIntelCPUPowerManagement(142.6.0)@0xf02000->0xf25fff
BSD process name corresponding to current thread: TemperaturMonito
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacPro4,1 (Mac-F221BEC8)
System uptime in nanoseconds: 509488144627
unloaded kexts:
com.apple.driver.AppleIntel8254XEthernet    2.1.3b1 (addr 0xee5000, size 0x118784) - last unloaded 126385491163
loaded kexts:
com.bresink.driver.BRESINKx86Monitoring    8.0 - last loaded 38786563416
com.parallels.kext.prl_vnic    6.0 11994.637263
com.parallels.kext.prl_netbridge    6.0 11994.637263
com.parallels.kext.prl_usb_connect    6.0 11994.637263
com.parallels.kext.prl_hid_hook    6.0 11994.637263
com.parallels.kext.prl_hypervisor    6.0 11994.637263
jp.plentycom.driver.SteerMouse    4.0.3f1
com.Cycling74.driver.Soundflower    1.5.1
com.apple.driver.IOBluetoothSCOAudioDriver    2.4.5f3
com.apple.filesystems.ntfs    3.4
com.apple.filesystems.autofs    2.1.0
com.apple.driver.AppleTyMCEDriver    1.0.2d2
com.apple.driver.AGPM    100.12.31
com.apple.driver.AppleHWSensor    1.9.3d0
com.apple.driver.AppleMikeyHIDDriver    1.2.0
com.apple.driver.AppleUpstreamUserClient    3.5.7
com.apple.driver.AppleMCCSControl    1.0.20
com.apple.driver.AppleHDA    2.0.5f14
com.apple.driver.AppleMikeyDriver    2.0.5f14
com.apple.kext.ATIFramebuffer    6.3.6
com.apple.ATIRadeonX2000    6.3.6
com.apple.driver.AudioAUUC    1.57
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AudioIPCDriver    1.1.6
com.apple.driver.AppleIntelNehalemProfile    11
com.apple.driver.ACPI_SMC_PlatformPlugin    4.7.0a1
com.apple.driver.AppleLPC    1.5.1
com.apple.iokit.SCSITaskUserClient    2.6.8
com.apple.BootCache    31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.driver.AppleUSBOHCI    4.2.0
com.apple.driver.AppleFWOHCI    4.7.3
com.apple.iokit.IOAHCIBlockStorage    1.6.4
com.apple.driver.Intel82574L    2.1.8b1
com.apple.driver.AppleUSBHub    4.2.4
com.apple.driver.AppleAHCIPort    2.1.7
com.apple.driver.AppleUSBEHCI    4.2.4
com.apple.driver.AppleUSBUHCI    4.2.0
com.apple.driver.AppleEFINVRAM    1.4.0
com.apple.driver.AppleRTC    1.3.1
com.apple.driver.AppleHPET    1.5
com.apple.driver.AppleACPIButtons    1.3.6
com.apple.driver.AppleSMBIOS    1.7
com.apple.driver.AppleACPIEC    1.3.6
com.apple.driver.AppleAPIC    1.4
com.apple.driver.AppleIntelCPUPowerManagementClient    142.6.0
com.apple.security.sandbox    1
com.apple.security.quarantine    0
com.apple.nke.applicationfirewall    2.1.14
com.apple.driver.AppleIntelCPUPowerManagement    142.6.0
com.apple.driver.AppleHIDKeyboard    141.5
com.apple.driver.IOBluetoothHIDDriver    2.4.5f3
com.apple.driver.AppleProfileReadCounterAction    17
com.apple.driver.DspFuncLib    2.0.5f14
com.apple.driver.AppleProfileTimestampAction    10
com.apple.driver.AppleProfileThreadInfoAction    14
com.apple.driver.AppleProfileRegisterStateAction    10
com.apple.driver.AppleProfileKEventAction    10
com.apple.driver.AppleProfileCallstackAction    20
com.apple.iokit.IONDRVSupport    2.2.1
com.apple.driver.AppleSMBusController    1.0.10d0
com.apple.kext.ATI4800Controller    6.3.6
com.apple.kext.ATISupport    6.3.6
com.apple.driver.AppleUSBMergeNub    4.2.4
com.apple.iokit.IOFireWireIP    2.0.3
com.apple.iokit.IOSurface    74.2
com.apple.iokit.IOBluetoothSerialManager    2.4.5f3
com.apple.iokit.IOSerialFamily    10.0.3
com.apple.iokit.IOAudioFamily    1.8.3fc2
com.apple.kext.OSvKernDSPLib    1.3
com.apple.driver.AppleHDAController    2.0.5f14
com.apple.iokit.IOGraphicsFamily    2.2.1
com.apple.iokit.IOHDAFamily    2.0.5f14
com.apple.iokit.AppleProfileFamily    41
com.apple.driver.AppleSMC    3.1.0d5
com.apple.driver.IOPlatformPluginFamily    4.7.0a1
com.apple.driver.AppleSMBusPCI    1.0.10d0
com.apple.driver.BroadcomUSBBluetoothHCIController    2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController    2.4.5f3
com.apple.iokit.IOBluetoothFamily    2.4.5f3
com.apple.iokit.IOUSBHIDDriver    4.2.0
com.apple.driver.AppleUSBComposite    3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice    2.6.8
com.apple.iokit.IOBDStorageFamily    1.6
com.apple.iokit.IODVDStorageFamily    1.6
com.apple.iokit.IOCDStorageFamily    1.6.1
com.apple.driver.XsanFilter    402.1
com.apple.iokit.IOFireWireFamily    4.2.6
com.apple.iokit.IOAHCISerialATAPI    1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily    2.6.8
com.apple.iokit.IONetworkingFamily    1.10
com.apple.iokit.IOUSBUserClient    4.2.4
com.apple.iokit.IOAHCIFamily    2.0.6
com.apple.iokit.IOUSBFamily    4.2.4
com.apple.driver.AppleEFIRuntime    1.4.0
com.apple.iokit.IOHIDFamily    1.6.6
com.apple.iokit.IOSMBusFamily    1.1
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    6
com.apple.driver.DiskImages    289
com.apple.iokit.IOStorageFamily    1.6.3
com.apple.driver.AppleACPIPlatform    1.3.6
com.apple.iokit.IOPCIFamily    2.6.5
com.apple.iokit.IOACPIFamily    1.3.0
Model: MacPro4,1, BootROM MP41.0081.B07, 8 processors, Quad-Core Intel Xeon, 2.26 GHz, 16 GB, SMC 1.39f5
Graphics: ATI Radeon HD 4870, ATI Radeon HD 4870, PCIe, 512 MB
Memory Module: global_name
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: pci1033,35, sppci_usbopenhost, Slot-3@4,1,0
PCI Card: pci1033,35, sppci_usbopenhost, Slot-3@4,1,1
PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-3@4,1,2
PCI Card: ATI Radeon HD 4870, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N, 67.1 MB
Serial ATA Device: WDC WD6400AAKS-41H2B0, 596.17 GB
Serial ATA Device: WDC WD6401AALS-00L3B2, 596.17 GB
Serial ATA Device: Hitachi HDT721010SLA360, 931.51 GB
Serial ATA Device: Hitachi HDT721010SLA360, 931.51 GB
Serial ATA Device: SAMSUNG HD103SJ, 931.51 GB
USB Device: Hub, 0x050d (Belkin Corporation), 0x0234, 0xfa200000 / 2
USB Device: iP4300, 0x04a9 (Canon Inc.), 0x10b6, 0x41400000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x5a110000 / 4
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc52b, 0x3d100000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec[/COLOR]

Uninstall the Hardware Monitor kernel extension, reboot, and see whether there's any improvement.

After update to OS X 10.7.5 on my Mac Pro (2009) USB ports don't work at all after wake up from sleep mode; with 10.7.4 there was (nearly) any problem.

hello,
after update to OS X 10.7.5 on my Mac Pro (2009) USB ports don't work at all after wake up from sleep mode; with 10.7.4 there was (nearly) any problem.
the used ports appear to be "killed"; the unused USB ports seem to work, but the Mac works in slow-motion.
The only "solution" is to restart my Mac.
- SMC-reset, PRAM-reset or repairing user rights had no positive effect; what is the solution - a bug-fix-update???

I have a mac mini (A1283) with OS 10.7.4. Upon upgrading to 10.7.5 it did not start up again. Instead, the light was on and the hard drive did not start up. The light on the connected USB mouse was not lit.
My solution:
Cold start with Command-v pressed.
This should start Verbose mode (see http://support.apple.com/kb/HT1492 ).
What happened on my mac mini was that the grey startup screen with the Apple logo appeared for a long while before the login screen came.
Maybe Cmd-v set open firmware params and fixed some corruption.
Anyway: my mac mini works again.

Mac Pro 2009-2010 firmware tool

Has anyone tried the Mac Pro 2009-2010 firmware tool hack that is floating around out there? It seems to work with no problems. A cheap way to turn your 2009 quad core into a 2010 hexacore. The price on the Xeon W3680 3.33Ghz Westmere has come down out of the stratosphere into the $500 range. $500 for that kind of speed improvement and the ability to run 1333Mhz RAM seems like a no brainer if one were thinking about upgrading. Have other people tried this?

This is not the place and no I have not heard, if there is/was it would be talked about on MacRumors, netkas or others. And I don't think it would be just firmware update. OWC Turnkey program involves more than just firmware change.
The W33680 was $590 but has gone up (popularity and supply/demand) to $620. Not $500 (though if you sell your cpu later then the out of pocket might be more like $400).

Mac Pro 2009 8 core with an endless cycle while booting up

Dear all,
My Mac Pro 2009 edition (2.26 GHz,8-cores) is suffering from a weird situation which I can't solve, so I post the message and hope someone can help me to find a solution.
On Monday Morning, I found the rainbow cycle is running behind the screen saver after shifting my mouse. The Mac Pro was not responding (can move mouse), so I pressed the button for 5 secs to shut it down. Then, I pressed the start button and saw there is a folder with question mark on the screen. After looking several web pages, I realized that it might be the RAID is failed for some reasons. I used the OS X installation disc to boot up and found that the RAID card was not recognizing the original RAID 0 build while the RAID card was shown to be healthy. I decided to restore my system from the time machine (WD Green 2TB x2, RAID0), so I checked the content of the time machine and hoped that I can find since when the machine is not responding. Then, it was 5:36PM on Friday, the last backup (backup per hour). So, it has been freezed for more than 2 days right after I left my office! Anyways, I used RAID utility to rebuild the RAID 0 (1TB x 4) and started recovering the last backup. After 11 hrs, the restore had been successfully done, so I clicked the restart button. However, after booting up, I got a grey apple and a running circle below it. The loading screen remained for 10 hrs and wouldn't get in.
I sensed that there is something wrong. It couldn't be fixed by simply restoration by time machine. Therefore, I started exhaustively surffing the internet and looking for an answer. Here are things I have tried but didn't work:
1. Restoring from three different time points: last time point, 1 hour before the last time point, and midnight on Thursday. Not working.
2. Remove Mac Pro RAID Card and use Disk Utility to build SoftRAID 0. Not working.
3. Remove ATI Raedon 5770 and replace with the original GT120. Not working.
4. Use Apple Hardware Test from Application installation disc to perform both default and extended tests. Found no problems.
5. Replace SDRAM with the originial 6GB (1GB x 6) SDRAM.
6. Tried reseting PRAM (3 to 4 times each)
7. Tried reseting logic board by following the instructions from macusersguide (http://www.macusersguide.com/2009/06/reseting-the-logicboard/).
(*)8. I tried to boot from another HardDisk, which I installed Win7 on it a few months ago (including all needed drivers for the Mac Pro). It is an originial Win 7 and it works! I also tried to test the 4 HDs by using the windows experience index. I tried 5 times (1 disks individually and all 4 disks enabled). All tests passed.
So far, I can only conclude that the hardware seemed fine, and it could be a software thing which blocks me from getting into the Mac OS.
I have been working on this for 3 days, and I am really tried. Could someone help me addressing this issue? Is there anything I can do to test which part is doing wrong? Should I test more time points in the time machine? Should I just hand my Mac Pro to Apple retail stores and asking for fixing (apple care expired and they would charge fees..)?
Thank you so much

Frankly, if you want a reliable backup from which you can boot the computer, then don't use TM. Use a backup utility that makes bootable backups starting with the Restore option of Disk Utility. Here are others:
Backup Software Recommendations
Carbon Copy Cloner
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

10.8.2 Mac Pro 2009 4 Apple Monitors = doesn't keep the display order and configuration. Please Help me!!

Guys i have a Mac Pro 2009 with 4 monitors attached.
Since i upgrade to 10.8, then to 10.8.1 and now to 10.8.2 my Mac Pro every time it starts, cannot remember the order and appearance of my displays so ihave to reorder them every single time.
Can somebody tell me what to do???
Please help me either wise i ma going to burn it!

I have brand new 10.8.2 Mac Tower with two matching video cards ordered from Apple directly and have the same problem. It wont save the display settings and also cant seem to tell which video card is which either.
In addition, the screen display images if loaded from a personal folder, is also not remembered after startup.
Please advise us what to do, Apple!!!! This is urgent for me. I am proifessional user and this machine is for use on live projection shows. We put a ton of money into this machine and it can't even remeber the displays! Not very amusing.

HT2090 External iSight camera video feed working fine but mic is not working Mac Pro 2009 and Mountain Lion 10.8.4

Finally I decided to move forward and installed Mountain Lion 10.8.4 (with all the updates). Now I am facing a dilemma, my external iSight Camera is working fine regarding the video fee but the Mic is useless. I am using a Mac Pro 2009 and a Apple Cinema Display 30". I checked all the trends about iSight External devices but no one has a really specific solution for my problem. Firewire is not longer supported with Mountain Lion? By the way my iSight was working perfectly before. So I am wondering if something wrong happened with the OS and the support for this kind of device?   I reset the PRAM, the SMC, even I reinstalled the MAC OS X Mountain Lion (10.8.4) from scratch. So I am wondering if the problem is that ML is not longer supporting this device or what is the issue here.
Hope someone can help me with it!
Thanks
Jalcom

Jalcom wrote:... Firewire is not longer supported with Mountain Lion?...
Not true. External iSight works fine with my '09 Mac Pro and 10.8.4.
Jalcom wrote:... So I am wondering if something wrong happened ...
So it must have.
Jalcom wrote: ... help me with it!...
You have tried several good things, but there may be other suggestions from http://support.apple.com/kb/HT2090 that you have not yet considered. Be sure to check more than one Apple app in more than one user account to help you pinpoint the cause of your trouble. Then you will know what to fix.
In addition to the Apple troubleshooting, check your  > System Preferences... > Sound > Input to verify that your iSight's mic is selected, not muted, and that its volume setting is properly adjusted. You may need to check this again after restarting Mac or changing apps that use the mic.
Also, be certain that the apps you are testing are configured to use iSight's mic. Different apps select the mic in different ways. For example, QuickTime X allow selection among various microphone alternatives via one of its preferences as shown in the image below:
(I was using my Display microphone and did not have my external iSight connected when I made this image. Therefore, there is no iSight mic shown in my list of mic choices above. If your iSight's mic is properly connected, turned on, and recognized by your Mac, iSight will show in your QTX microphone preference choice list.)
If you are trying to use your iSight with a Flash based web site, also check your Mac's  > System Preferences... > Flash Player > Camera and Mic settings to verify that your Flash system preferences are not blocking your mic.
Some other apps may offer mic and or camera selection via their application menus. If you have trouble finding out how to select the iSight internal mic in other apps, check each apps' Help or post back the name of the app whose selector you cannot locate here so we can try to help.
Message was edited by: EZ Jim
Mac Pro Quad Core (Early09) 2.93Ghz OSX 10.8.4 24" LED Cinema Display          External iSights

Sony DSR-1500a not recognized by Mac Pro 2009

My first post. Hope I'm doing this right....
I have been working with a Mac Pro 1,1 Quad (OS 10.5.6) using a Sony DSR 1500a DVCAM player/recorder with out any issue using firewire 400 and Adobe Premiere and FCS2. I have recently purchased a Mac Pro 2009 (OS 10.5.7) with FCS2 and with Avid MC 3.5.
I cannot get the DSR-1500a to be seen by the OS or FCS2. The only twist is that if I daisy chain my DSR-1500a thru my Avid DNA Mojo. I can capture into Avid Media Composer no problem. I use a FW400 (6pin) from the DSR to the Mojo and a FW400 (6pin) to FW800 cable from the Mojo to the Mac Pro.
I am starting to assume that using a FW400 (6pin) to FW800 cable does not work with the 1500a. I do not see it listed in system profiler when connect directly to the Mac Pro. I have adjusted the DSR setting to iLink and also have tried 9Pin setting but neither work. Tried more than one cable as well.
I can successfully connect my cheap Sony TRV38 via a FW400 (4pin) to FW800 cable but not the professional deck...Go Figure...
I know it's not the deck as it works with the Mac Pro 1,1 using the FW400. Is there an OS setting I am missing? Do I need to buy a FW 400 card? Please help! Thanks

As I suspected... I had to buy a 1394a firewire card to enable the communication between the Mac Pro and the Sony DSR-1500a. Apparently the DSR does not subscribe to the reverse compatibility that Apple has forced on us of going from a FW400 (6pin) to FW800 (9pin) in reverse compatibility mode. I guess Apple can take the Sony DSR-1500a off of their qualified hardware list. If I have missed something, someone please enlighten me. Until then, looks like Apple has struck again. Oh I know, I'll go out and buy a $1000 capture card. Wow! I thought I was getting a well engineered product, instead I got a money pit! Forcing a Mini Display Port down our throats, NO firewire 400 ports, 8 slots of ram on tri-channel memory...Who's the engineer that came up with that one? Screeeaaammm!!!
OK I feel better now... Who do I make the check out to? %#@^

Nvidia Quadro 4000 is Freezing / shutting down / Buggy with Mac Pro 2009

I currently have two Nvidia Quadro 4000 mac cards and there causing my Mac Pro 2009 machine to kernel Panic and freeze or shutdown my machine.
I dropped it off at the Apple store for them to diagnose the problem for 9 days and they went ahead and confirmed that it was the card which was causing the problem.
NVIDIA PLEASE UPDATE YOUR DRIVERS FOR THIS CARD FOR MAC.
Its ridicules that if you spend $1200 (apple store) that it will crap out your Mac Pro. I'm waiting for a updated driver in order to test the stability with the Mac Pro
I'm almost 100% sure I did the 10.6.6 update with the stock card, then installed the most updated drivers from Nvidia website and then installed the Cuda Drivers, then finally installing the Video card in the machine. After two days, system was acting up.
Once I get my machine back from Apple tomorrow, I will go ahead and give it one more last try to see if it works. I'm mean the cards are amazing with Adobe Premiere and Media Encoder (super fast), but at the cost that your machine will be very buggy.
Lets wait and see what Apple, Nvidia or PNY will do about the big problem. I'm wanting to keep these babies, so make some moves people and fix the issues for the Professionals.

I hadn't been experiencing the problems you have, but I have been having issues, and yes it absolutely is a case of immature drivers. When the card was released in December, nVidia merely did a simple patch job on the 256.01.00f03 driver that shipped with 10.6.5 rather than include an optimized driver that was comparable to the 259.x driver available on the Windows platform at the time.
Since then, nVidia's engineers have been hard at work doing what appears to be nothing for the Mac. On the Windows side, the Quadro drivers have progressed to 267.11. Rather than provide Apple with updated drivers to include with 10.6.6 or this week's 10.6.7 release, they chose to sit back and wait for the 10.6.7 release and then release their own update.
After 4 months, their best and brightest have brought us <drumroll> driver version 256.01.00f03. To be fair, they changed it from "v5" (the patch job to enable Quadro 4000 compatibility) to "v6". The idea was that it would add compatibility for the Quadro 4000 running under 10.6.7, Sadly for nVidia's Quadro engineers, that driver's installer didn't actually work. It took them nearly a full day to fix that, finally releasing 256.01.00f03v7. As expected, there are no improvements in either performance or stability. In fact, what happened to me is that the new driver actually broke compatibility with Adobe Premiere Pro CS5's Mercury Playback Engine GPU acceleration feature.
Fortunately, I still had my GTX-285 card available, and this evening I pulled the Quadro and re-installed the older GTX card. I really wish nVidia would care enough to release a solid driver update, I really want to like the Quadro 4000. On paper the potential for video production and OpenGL rendering performance should be huge.

Why my Mac Pro 2009 became too slow after updated Yosemite?

Why my Mac Pro 2009 became too slow after updated Yosemite?

When the slowness is especially bad, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Will Remote Desktop allow me to access and use my Mac Pro 2009 from my MacBook Pro 2011?

Own a small business, have two locations, I need to use Windows via Parallels on my Mac Pro 2009, but I am forced to spend most of my time at the other location which has a MacBook Pro 2011. Will Remote Desktop allow me to use the MacBook Pro 2011 to access the Mac Pro and use Windows via Parallels?

If all you need is to be able to control another computer, then ARD would be overkill. If the systems have Mac OS X 10.5 or later you can use the Screen Sharing built into those versions of Mac OS X to control the system.
Another and perhaps easier option is to use a service such as LogMeIn or TeamViewer. Either option may be significantly easier than dealing with screen sharing or ARD.
You'll want to confirm that any solution you choose will work with Parallels, of course. I haven't tried remote control of a system to use Parallals, so there may be special considerations there. If you don't get useful comments here, you might try Parallels' forums.
Regards.

Mac Pro 2009 won't boot.

Hello,
Since yesterday my computer simply refuse to boot (Mac Pro 2009, Quad-Core 2.93 with a flashed Radeon 5870).
It was working fine the day before, I shut it down, unpluged it and when I came back the following day it wasn't working anymore.
When I try to boot it I can hear the fans but not the starting "DONG" it should do.
I tried to replace the graphic card with my old ATI 4870, tried to switch with some old RAM I had and tried to disconnect my hard drives one by one but it did nothing at all.
The only thing I have is this red dignostical LED you can see on this picture. I tried to find it's meaning but I wasn't able to find anything.
It would be nice if someone was able to tell me what this LED meant (and even nicer if it wasn't something expensive to replace !).
Thanks !

Hello once again,
So, I finally had time to look a little deeper into this processor board and after removing the heatsink and cleaning the processor I noticed two little plastic screws (the ugly little red arrow on the picture I took from macbidouille.com, not the nice and big one) maintaining another heatsink on the board.
I'm not sure what is the component under this heatsink but one of these screws was broken (they aren't really screws but I don't know how to explain in English) and the heatsink wasn't correctly positioned anymore so I replaced these two screws, put everything back in order (with some thermal grease on the processor and the unknown component) and everything worked like a charm when I was done.
Thanks everyone for your help !

Mac Pro 2009 won't boot after airport installation

Hey everyone, looking for some insight here.
I recently bought a Mac Pro 2009 running Mavericks (at time of receipt). It didn't come with an airport card so I purchased one to install myself. The Mac was running fine until this evening when I finally got around to installing the card, however since then it won't get past the grey boot screen with apple logo. I've tried disconnecting the airport card to see if that reverted it, but no change. I also can't boot into safe mode, so that's no good. The only thing I can do is bring up the giant padlock with the option key held, which I saw elsewhere was connected with a firmware password (my admin doesn't work).
Any advice here would be greatly appreciated. Thanks!

It wouldn't be much of a lock if you could circumvent it with advice from a forum.
Obviously a valid point, although possibly somewhat niaive where forums are concerned (no disrespect intended).
It was more an expression of frustration than anything else, to be honest, though. It's kind of absurd that this happened following a simple hardware upgrade. Most people I know aren't even aware they can set a firmware password, so basically what it means is don't upgrade a machine that's intented to be upgraded (I'm aware of the hyperbole here).
Looks like it will be a Mac store trip, though, yes. A pain in the arse since even my nearest authorised technician is miles away.

Mac Pro 2009 audio problems

Similar Messages

Maybe you are looking for