2010 Mac Pro Monitor not working

Discussion in 'Mac Pro' started by osxabsd, Apr 15, 2012.

  1. osxabsd macrumors member

    Joined:
    Sep 28, 2009
    #1
    I have a Mac Prod 2010 with a ATI Radeon HD 5870 1GB card and a 27inch apple disply. When I power it on I get no video. The keyboard connected through the monitor appears to work (i.e., control-eject-enter can shut down the machine) When I connect the monitor to a Mac Book Pro the monitor works, likely eliminating the monitor as the problem.

    Is the anything else I can try other than having Apple look at the video card?

    Thanks
     
  2. minifridge1138 macrumors 6502a

    Joined:
    Jun 26, 2010
    #2
    Try another monitor.
    Try using a different port on the Video Card.
     
  3. DanielCoffey macrumors 65816

    DanielCoffey

    Joined:
    Nov 15, 2010
    Location:
    Edinburgh, UK
    #3
    Are you still under AppleCare? If so, it is a no-brainer. Take it in.
     
  4. digitalhen macrumors regular

    Joined:
    Jan 10, 2006
    #4
    Indeed. I've found the sockets on my card to be quite fussy. While appearing to be fully inserted, I got no graphics on the screen. Re-inserting the cable resolved it.

    NB. The keyboard is connected via the display's USB hub, and will most likely work without the display itself being connected to the graphics card.
     
  5. osxabsd thread starter macrumors member

    Joined:
    Sep 28, 2009
    #5
    Thanks for your response.

    This problem started after I had been away for a week (the machine had not been booted).

    I tried:
    1. Using different ports.
    2. Checked the monitor with a Mac Book Pro and it worked, eliminating the monitor as being the issue.
    3. I replaced the 16 of memory with the 3G of factory original memory.

    Then I opened a ticket with Apple support, and when I tried recreating the problem for them I never could, even though I did recreate it several times previously. So at this point, the problem magically went away.

    I have a hypothesis that it might have had something to do with the internal battery since the machine had not been booted in a week.
     

Share This Page