2018 Mac Mini - monitor problems

Could explain how to "make sure you startup security is set to allow external boot in order to do this"?

Thank you and sorry for the inconveniences.



Thank you very much!

I tried removing “File Vault”, but I have the same problem.

The problem arises sometimes when:

- I start the computer.

- I exit from stop (one or both my monitor black out).

I tried to resolve the root of the problem without success by:

- resetting the PRAM.

- trying all thunderbolt and HDMI's port in the back of the MacMini.

- changing various monitor's setting (resolution, calibration, ecc).

- changing various preferences in <Monitor> (<System Preference>).

- installing an app called SwitchResX but it didn't work.

Some temporary solution are:

- plugging out and in the monitor's cable.

- restarting one or both the monitors.

- shutdown and restart the MacMini (at least one monitor restarted).

- the command checking in/out the <Duplicate Monitor> in: System Preferences > Monitor > Disposition.

I found out that checking out all options in <Mission Control> (<System Preference>) has reduced frequency of the problem.

By the way my mac mini recognise my 2 monitors (LG 24UD58-B.AEU) as 27 inches in: Apple menu > About This Mac (it may be my fault?).

I hope Apple resolve his problem.

hardware:

Nome modello:       Mac mini

Identificatore modello:             Macmini8,1

monitors: 

2 LG Ultra HD:

Risoluzione:              3840 x 2160 (2160p 4K UHD - Ultra High Definition)

Aspetto interfaccia utente:       1920 x 1080 @ 60 Hz

Tipo di connessione:                DisplayPort

software di sistema:

Versione sistema:    macOS 10.14.2 (18C54)

I tried using a USB-C to HDMI adapter but had no luck. Maybe I should look at the windowserver.plist files?

I spoke with Apple. Their first troubleshooting step was reformat the hard drive and start over. I don't think that is reasonable. I might start with an external drive, though everyone here indicates the issue is definitely FileVault.

I don't think Apple is aware there is even a problem. It's our fault...

The monitor makers are not likely to help. I went through a long support conversation with both Apple and LG. LG agreed to send me new cables in case that's the issue, because some people have made their monitor work through an adapter (though not at the original resolution, as far as I can tell).

Apple essentially came up with the idea that the problem is on my end, in software. They asked me to wipe my drive clean and start over. Apple is really starting to sound like Microsoft...

As far as I can tell, the issue occurs with encrypted FileVault drives, during the boot phase, at that initial screen where no software has been loaded other than Apple’s “decrypt the drive or boot into Recovery” system. Thus, wiping my hard drive would do nothing but aggravate me and waste my time.

My own machine will happily boot into Recovery mode, and then reboot into the normal system and let me log in. Likewise, if I reset PRAM, it will give me a screen and let me log in. The solution is to spend nearly all my time in sleep mode, and not let the computer be off for any length of time. Both Recovery mode and PRAM seem to reset the 32-bit warning system, too.

Definitely a bug. Hopefully will be fixed in OS 14, because I don't plan on moving to 15 any time soon; I'd lose Dreamweaver, for one thing.

I posted above already and had the same issue where I couldn’t get my 4K TV to display over HDMI from the Mac Mini. With a second monitor plugged in all was fine.

I spent hours with the Apple support and they could only recommend their basic resets and then a full factory one... They really couldn’t help and claimed they had never heard about the issue. They were supposed to call me back and never did.

I figured out that the display plists config files (windowserver.plist in preferences) we’re not updating either.

I switched from HDMI to USB C using an adapter and that solved the issue. The config files now update.

However the display now wakes up on a delay which is annoying!

Agreed that Apple should look into this as there is a clear problem but they don’t seem interested....

Actually, I jumped too fast on a conclusion. Disabling FileVault made the situation a lot better – but just few hours after I posted the comment above, my Mac mini lost one HDMI connected display when resuming from sleep. It worked for few days perfectly. Weirdest thing with these problems are that they aren't happening every time and there's no obvious pattern.

I really too hope Apple will fix this, because it is a quite fundamental problem and it makes it seem like the Mac mini is just broken.

Your story is the same as mine. I have tried all your ways: - with or without <file voult>; - change position to the cable in the back of mac mini; - change the cables from HDMI to thunder; - PRAM rebuilt; - revision preference monitor setting. In summary I tried all that was possible for a generic macuser, but usual 1 or 2 monitors do not wake up from stop and in this case Apple, plese, we are waiting for a solution to this problem.

Edit: just noticed the one 10.14.4 post above. Niiiice. :-/

Apple released macOS 10.14.4 which states that it "Fixes a graphics compatibility issue that may occur on some external displays connected to Mac mini (2018)". Can anyone confirm if this has any effect on this problem?

Confirmed. Cold boot does not work in 10.14.4 with usbc monitors ( two or one)

only workaround was a single monitor via hdmi

monitors that failed include hpz30, apple 30 inch cinema, acre, Brand new LG, etc.

clearly the monitor to bus communications is not properly working . It has nothing to do with the brand of monitor as I have tried four brands in different permutations, all with entirely unreliable cold boot, and random reliable wake from 22 hour sleep

I am having a similar issue as all of you. In my particular case, I have two 27" Sceptre 4K displays, connected via USB-C to DisplayPort. I have this computer in my downstairs office and don't get to use it very often (unfortuantely), but I'll come back to it after a few days every so often and it'll be completely off.

Turning the machine back on usually doesn't work - no response from either monitor, with the exception of one of them briefly detects a signal and then goes back to sleep. I'll have to power cycle the machine several times, and only then will I'll be able to get a signal on one display and usually only after I connect an HDMI cable to it.

macOS indicates a kernel panic reboot, with BridgeOS being the underlying reason for the panic according to the console logs.

I just got mine working with usb to hdmi male cable and an adapter DVI on monitor to hdmi female! (2) bi-directional Adapter 6.99 on amazon and cord 12.99

taking back 2 35.00 cords to store for refund that did not work!!! The cords and or adapter should be sold as part of the **** computer it will not work without proper power supply! Now monitor comes on when computer comes on!!

I just got mine working with usb c to hdmi male cable and an adapter DVI on monitor to hdmi female! (2) bi-directional Adapter 6.99 on amazon and cord 12.99

taking back 2 35.00 cords to store for refund that did not work!!! The cords and or adapter should be sold as part of the **** computer it will not work without proper power supply! Now monitor comes on when computer comes on!! Red1217 apr 14 2019

So that being said and discussing the topic for a few months now, how long will it take Apple to fix this. I called the helpdesk several times and was upscaled to senior helpdesk support, but although always very kind and trying to help, it always ends with "I am sorry, I am not able to help you with this problem: ...The very short time out on my LG to go into sleep mode makes the problem even worse.

Shouldn't there be an update for the Mac Mini firmware?

Apple must be reading these messages too?

This problem has been going on for six months now, without an official response nor a solution form apple. What makes you think that swapping the cables around some will solve it? And also what makes you believe that we did not try this sort of basic troubleshooting?

Quality control at Apple has been down for the last 15 years, no surprise there, I think we have all the good reasons to be upset at this point.