Mac Mini Won't Boot with VGA Monitor Connected

I have a new Mac Mini connected to an older VGA monitor using the Apple brand VGA adapter.  The mini is fully up to date and runs perfectly when booted.  However, if I reboot the mini with the VGA monitor connected, it fails to boot.  I just hear the faint chime sound every other second.  There is no output to the monitor and the only way I can get it to boot is to disconnect the monitor and then power cycle the mini.  I can reconnect the monitor just seconds after powering back on and it finishes booting properly.
Anyone else experience this?  It is very frustrating.  I've also tested with an HDMI connected monitor (without the VGA adapter) and it boots just fine and the display works properly.

Okay, I'm back with good news: I have found two remedies for the problem which will hopefully solve it for you as well.
Given that the issue only occurs when certain monitors are connected, I concluded that the root of it must be a bug in the Mac's firmware related to DDC (Display Data Channel) handling, and that the most promising way to address it should be to just disable the DDC.
Workaround #1: If your monitor has BNC connectors, use a VGA to BNC cable.
In this configuration the DDC pins are not connected to the monitor at all. This did indeed fix the problem - my Mac mini booted without a problem with the monitor connected. However, I was not completely satisfied with this solution, because VGA to BNC cables are usually quite heavy and inflexible, and do no go together well with Apple's MDP to VGA adapter and the Mini Displayport/Thunderbolt port which has no locking mechanism.
Workaround #2: Remove pin 12 of the VGA plug.
Pin 12 of the VGA plug connects the serial data line of the DDC. Pulling out this pin with a pair of needle nose pliers will effectively disable DDC. I hesitated to do this to my cable (a direct MDP to VGA cable which eliminates the need for a separate adapter dangling from the Mac) and therefore bought a tiny VGA male to female adapter (also called port saver, e.g. Delock 65250) to perform the surgery on that. This has done the trick and my Mac mini has started up fine ever since.
Of course, without DDC the Mac won't know the model name and capabilities of the attached monitor and thus offer some resolution and frequency settings which the monitor may not support, but that's a small drawback compared to having to pull out the monitor cable everytime you turn on or restart your Mac.

Similar Messages

  • Mac Mini won't boot with install disk

    tried booting with install disc in and pushing "c" on keyboard and doesn't work. Using a apple wireless keyboard. Also used the keyboard that came with Mac Pro but didn't work nor did a wired logitech.
    any ideas?

    +What is the source of the idea that the mac aluminum keyboard won't work with the mini?+
    Dozens of reports in this forum over the past year.
    Keep in mind that by "not working" what was meant was that the startup keys wouldn't work. The Alu keyboard otherwise works fine with the Mini.
    It has also been reported that the Alu Keyboard does work for startup keys if it is plugged into a hub with an external power supply.

  • Opinions about if Mac Mini 2011 works ok with VGA monitors

    Hi Community,
    I have a old HP PC, I want to buy my first Mac Mini and used the keyboard, mouse and VGA monitor (Mod. HP Pavillion mx50) that I have.
    Before I purchase the new Mac Mini 2011 and Mini DisplayPort to VGA Adapter, I would like to know if it works ok with my old components, specially with the VGA monitor? I've read on this Community there some persons have monitors problems.
    I don't want spend my money and then have problems with the Mac Mini.
    Thanks in advance,

    MiniDisplayPort-VGA adapters.  Available in the online store, at Apple stores, or at BestBuy/MicroCenter/Fry's.  Plugs into the Thunderbolt port.
    Usually works without issue.  But then I use monitors made by LG and Samsung.  Others use lesser known brands or models know to have quirks and encounter issues.
    Some things to watch for:
    Soem adapters have too much plastic coveing the "connection plate", and the cable cannot seat fully.  If you just look at one that has too much plastic, you will know what I am talking about.
    VGA signals from Macmini are not strong enough to get through mutliple adpaters.  If you want a VGA signal, buy 1 VGA adapter.  If you want a DVI signal, buy only 1 DVI adapter.  Do not get a DVI adaper, than add a mid-line converted to change the DVI adapter to a VGA port.
    If you plan to run Windows under BootCamp, the Windows driver for the Tunderbolt port does NOT output snalog (VGA), just digital (DVI, HDMI).  So if you plan to use VGA to display Windows output, run Windws under "VM software" (Parallels or VM Fusion) so that OSX can make the VGA signal for you.

  • Mac G4 won't boot with slave drive connected

    I have two G4 boxes. 1-Dual 867 Leopard and 1 -Dual 1.25 Tiger.
    I have been trying to clone the system drive of the Dual 867. Everytime I add the second drive to the 867 box and try to boot i get the "Flashing ?." I have tried various reformatted drives and the result is the same. I have even tried to accomplish this by using the 1.25 box. Same result.
    if i unhook the 2nd drive (ie backup drive) both computers will boot as usual.
    What is the problem?

    Hi larbok, and a warm welcome to the forums!
    I think it's the Jumper settings on the Hard drive.
    Older G4s should be set to Master on the end cable & Slave for the Middle of the cable.
    MDD usually use the Cable Select jumper settings on both drives.
    Jumper settings are generally shown on the HDs themselves.

  • Mac mini won't boot anymore

    My Mac mini won't boot anymore. It's been running fine for months.
    It's running Leopard Server 10.5.2 Build 9C31
    It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
    I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
    Safe mode doesn't work (same hang as above).
    Single user mode does work.
    I can connect to it via Server Admin while it appears hung.
    The last few lines of the system log are:
    May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
    May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
    May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
    May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
    May 15 18:39:20 server kernel[0]: display: Not usable
    May 15 18:39:20 server[126]: Kerberos configuration is up to date
    May 15 18:39:20 server[125]: FODBCheck: New annex file created
    May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
    May 15 18:39:21 server[132]: Kerberos configuration is up to date
    May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
    May 15 18:39:22 server[1] ( Throttling respawn: Will start in 9 seconds
    May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
    May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
    May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
    May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
    May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
    May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
    May 15 18:39:54 server[47]: Thu May 15 18:39:54 Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
    May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
    May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
    May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
    Any ideas?

    Yes, it's been running Server since I purchased it.
    I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

  • Mac Mini won't boot after failed XP installation

    Recently upgrade HD to 320GB 7200 rpm and 3GB ram. Running 10.5.8 fine.
    I tried to install Windows XP through Boot Camp, but wasn't successful, I terminated the installation. Then Mac Mini won't boot up. When powered on, you heard the chime, then grey screen showed and stayed. Tried starting with "C" (boot from CD), "OPT" (boot option), "T" (target), and reset PRAM. None of them worked.
    What should I try next?
    Message was edited by: Yijian Cao

    If you install XP on Bootcamp, your startup disc will be changed to XP Windows partitioned you did. To restore your startup disc back to Mac OS, make sure your Mac is turned off. 1. Plug the power back and press the power button ON. When you hear the power On sound, press and hold the ALT key on your keyboard until you see the hardrives. 2. Select the HD that says MAc OS, then your mac will boot back to Mac OS.
    Let me know if you have more problems, maybe I can help.

  • Mac Mini won't boot up.

    Mac Mini won't boot up! Just getting blank white screen, any ideas why? No apple, just a blank screen. It worked fine last night.

    Have you tried booting into the Recovery HD by pressing/holding COMMAND+R at system start or the Option/Alt key and choosing Recovery HD to boot into?
    If you can get into the Recovery HD, open Disk Utilities and Verify Disk. Repair if necessary.

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • Mac Mini won't boot up after disconnecting it from iMac

    I have disconnected my Mac Mini from the iMac I had it connected to, and now it won't boot up when I turn it on. Do I need to hold down a key combination to get it to boot from it's own operating system again?

    I have disconnected my Mac Mini from the iMac I had
    it connected to, and now it won't boot up when I turn
    it on. Do I need to hold down a key combination to
    get it to boot from it's own operating system again?
    You should not have to hold down any key to get it to boot to an installed copy of MacOS, though if you hold the option key down, it should take you to the Startup Manager which will give you a list of available MacOS volumes it can boot from. If it doesn't show any, then you don't have a bootable MacOS on your mini.
    Are you getting anything on your screen when you are trying to boot, such as a folder with a question mark?

  • Mac Mini Won't Boot or Internet Restore - Hard Drive Boots on Macbook

    Late 2012 Mac Mini. I cloned my 10.10.2 installation of Yosemite over from my Macbook pro 6,2 to a 1TB Samsung 840 SSD. It booted with no issues besides the keychain being lost and all passwords having to be re-entered.
    After a week of going perfectly, it stops recognizing the USB keyboard after I unplugged it and plugged it back in. So I rebooted and get the dreaded stop sign after the boot failed. Oops. I enabled trim before I cloned, but forgot to check if it was working in the cloned drive (seems it was in the end). Since there was no recovery partition, I booted into Internet Recovery, but that hung using both WPA and WPA2 router logins. It obviously was syncing with router, but I got error -2002f in every configuration I tried. It also didn't seem to recognize an ethernet connection. Weird stuff.
    I remembered I had an issue with a previous Mac Mini of the same model and the permissions after a clone. I repaired permissions and that was that. This is different because it wouldn't boot into Safe Mode. Resetting the PRAM did bring back an audible chime at least.
    I pulled the SSD out of the Mac Mini and alt booted in from my Macbook 6,2. No issues (except the keychain thing again( and it loaded quickly. Nothing seemed to be wrong.
    Then I put it back in the Mac Mini and tested it with known working RAM. Still the same thing. So now I am going to sleep on it and try to figure it out. It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?

    Fix The Bugs Please wrote:
    It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?
    Is this SSD an additional drive added to your Mac Mini or did you replace the HDD with it? If it's an additional drive and since it's a Samsung, depending where you purchased your drive doubler kit (iFixit or OWC) you can try swapping the drives in the bays. I know for a fact that Samsung SSDs do not work right with the iFixit drive doubler kit's SATA cable. But it does work correctly with the Apple supplied SATA cable. If it's the OWC SATA cable, I know for a fact those are much more reliable with Samsung, OWC, Intel, Crucial SSDs. Another thing, I would NOT enable TRIM (my opinion) using a 3rd party trim enabler if you're running Yosemite. There are issues with trim enablers and Yosemite. Just let the built-in Garbage Collection take care of things.
    If it's not an additional drive that was added, does your Mac Mini boot and work fine with the stock drive that it came with? Even though it's a 2012 model, if you purchased it refurbished from Apple in May 2014, you're still under warranty (same 1yr as new Macs) and if it's having same or similar issues working with the stock drive, you can take it to a local Apple Store for warranty repair. You would need to have only the stock drive installed (no SSD) before you setup an appointment.

  • Power Mac G5 won't boot with Lion?

    After installing Lion, my early Intel 2010 Power Mac G5 won't boot. There were no problems for the first 2 days. The third day my G5 wouldn't boot at all. Not using Lion's recovery function, many attempts to boot from a previous system disk, and firewire target mode. The keyboard seems to be dead after attempting to boot except for the DVD eject key. All I get is a grey screen with an icon of a folder with a question mark within the folder. This icon blinks on and off continuously. Since the keyboard isn't working, I can't reset the PRAM, start in safe mode, or any other keyboard commands. The failed boot doesn't even get far enough for the Apple window to open. I replaced the hard drive and accomplished nothing except for spending even more money and time.
    This is VERY frustrating! Has anyone else had a similar problem with booting after Lion't installation??

    1) you have a Mac pro Early 2009, remember this. It avoids confusion here in forum
    2) you're HDD's OS cannot be found by the firmware of the Mac hence it results to a question mark
    perform the following(recommended to use a USB keyboard)
    a) startup manager
    press and hold option on startup. Do u see your HDD?
    b) if you have a back up of your data then you can boot to the install disk and perform an erase and install
    repairing the permission will not work since the disc's OS is different from the HDD's OS.

  • Mac mini won't boot - hardware test error

    my mac mini isn't booting... stuck on the grey apple screen with spinning circle.
    have ran the hardware test on the OSX DVD and i get the following error
    2STF/8/3: ATA-100 ata-6 - Master
    i assume this means that the HDD is knackered ?

    The variable reports on the hard drive are not entirely unusual with a drive that has problems, but it's not a good sign in general that you are having issues with booting to the install disk. That has potential to reflect a controller error that could be minor in nature and even be as simple as a poor connection on the drive carrier which has both drives mounted to it.
    Try booting to the OS installer again. If you can get past the language selection screen it means OSX (the very basic version on the installer) has loaded, and that's a good sign. There's no reason from that point that the Utilities menu wouldn't pull down as normal and disk utility run from there. If you can get that far, see if the internal drive is visible on the left of the disk utility app, and if so, select it (there may be two entries for it, either will do) then click the repair disk button.

  • Mac Mini won't boot after 10.6.6 / Airport update

    I just reinstalled 10.6.3 on a unibody Mac Mini, updated to 10.6.6 - and it booted fine. I ran another software update, and it suggested two more updates - which I believe was an Airport Utility update and a Java update. Now the Mac Mini fails to boot, stopping at the Apple logo.
    The last lines of verbose startup goes like this:
    Airport: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Aut result for: (MAC address) succeded
    AirPort: Link Up on en1
    AirPort: RSN handshake complete on en1
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?

    I experienced a similar problem today after a recent upgrade to 10.6.6. I ran Tech Tool Pro 5 on the machine, which reported everything as just dandy after about 6 hours of testing, but it still wouldn't boot. Next, I tried booting in Verbose mode, which revealed that my iMac was hanging on:
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    I used Safe Single User mode (turn on power, then immediately press and hold Shift-Command-S until text starts appearing) to boot to a command line. Single User mode provides instructions on how to mount the file system read/write. I executed the `fsck` command as instructed, and after a few minutes it reported that it had made changes to the file system. At that point, I skipped the `mount` command and went directly to `exit` to continue the boot process, which completed. I turned AirPort back on (I had it turned off), then rebooted normally without any trouble.

  • Won't boot with external display connected

    My MacBook Pro (circa 1997) won't boot with the external display connected. I can connect the external display (20in flat planel) after it has started, and it works just fine.
    I have tried two different DVI cables (one of which I think is a DVI-A cable) and the DVI-to-VGA cable. The result is the same.
    During the boot phase I get the tone, the apple logo and the progress wheel. After 30 seconds to one minute those disappear to be replaced by an empty blue screen.

    In case anyone wonders, my "solution" was to change to a WB Elements Desktop 3TB (only USB 2.0 is currently available for this model). I miss the speed of USB 3.0, but it's much nicer to not have to remember to unplug and plug in the hard drive each time I boot.
    Still hoping to see a proper solution to this (since I don't have the WB My Book anymore, I can't test adaher's suggestion).

  • Mini won't boot when VGA is attached to KVM -- help!

    My mini (Core Duo 1.86MHz, all updates installed) is attached to a Belkin Pro2 4-port KVM (F1DA104T). I've read comments about issues with KVMs being picky with the mini, but the mini won't even completely boot when the VGA cable is attached. I've used this KVM with other 10.4 Macs in the past (G3's, G4's), so I didn't expect problems. The monitor is a Dell 17" LCD (E173FP), which is fine when attached directly to the mini. I've also tried another LCD (different manufacturer) with same results.
    The mini boots and I first see the gray screen with the Apple logo, followed by a light blue screen, and that's it. The finder never comes up, and I can't even SSH or VNC into it -- just the blue screen. Once I remove the VGA cable (only video - the keyboard and mouse are both still connected), it will complete the boot and launch the finder. If I boot with no display attached, or attached directly to the LCD w/o the KVM in the path, but then attach the mac to the KVM, I see the display for about two seconds, and then the monitor heads into power save mode. When I VNC into the mini to see what's going on, it's detecting two different displays; when the cable is attached but the KVM isn't on the mac's channel, it's one thing. When I switch over to the mac's channel, it's like I'm plugging in a different display. In any case, the computer is putting out 1024x768x60Hz, which is well within the specs of the monitor and KVM.
    I installed SwitchresX and under VNC retrieved the DDC info. Here's what I have for when it's plugged into the KVM and on channel:
    DDC block report generated by SwitchResX for display
    VGA/SVGA Display
    0 1 2 3 4 5 6 7 8 9 A B C D E F
    0 | 00 FF FF FF FF FF FF 00 00 00 00 00 00 00 00 00
    1 | 0A 0A 01 01 0C 1E 17 BE E8 2D C9 A0 57 47 98 27
    2 | 12 48 4C 00 00 00 01 01 01 01 01 01 01 01 01 01
    3 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    4 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    5 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    6 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    7 | 01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 20
    Valid DDC block: checksum passed
    EDID Version........1.1
    [email protected]@@
    Product Code........0 (0000) (0000)
    Serial Number.......0
    Manufactured........Week 10 of year 2000
    Max H Size..........30 cm
    Max V Size..........23 cm
    DPMS Supported Features:
    Active off Suspend Standby
    Display type:
    RGB color display
    So far, I'm stumped. This is a $200+ KVM, supposedly better than many of the cheapies, with listed Mac compatibility. Neither Apple nor Belkin wants to take ownership for this problem. If anyone has any tips on where to look next, I'd be very grateful!

    Hi BSteely,
    Thanks for taking the time to look into this.
    The blue screen I see is definitely not being generated by the LCD - it's coming from the Mac. It's coming up just after the gray Apple logo you see when booting. Normally you'd next see the finder pop up, but that never happens as long as the KVM is plugged into the mac (and it's only the VGA connection which is doing this, since the same thing happens with the keyboard/mouse unplugged from the mac). Once I remove the VGA cable, it continues to boot normally. If I hookup the LCD directly to the mac, it also boot normally.
    Sorry I wasn't clear about VNC. I'm not seeing two displays at once, I'm seeing two different displays -- one when the kvm is on the mac's channel, and another when it switches away. Funny enough, I'm getting MORE resolution choices when I'm not on channel. The DDC info I posted above is for when I'm on channel.

Maybe you are looking for