NVIDIA Releases Alternate Graphics Drivers for macOS High Sierra 10.13.0 (378.10.10.10.15)

[ccozmo]

So – like on your machine – with CSM disabled I get black screen with more than one screen connected while booting.
If I however enable it, I can't even get past that line while booting...

In my BIOS I have the following settings under CSM when I set it to enabled
Launch CSM: Enabled
Boot Device Control: UEFI and Legacy OPROM
Boot from Network Devices: UEFI Driver first
Boot from Storage Devices: UEFI Driver first
Boot from PCI-E/PCI Expansion Devices: UEFI Driver first

I also just tried CSM = Auto and still could boot with the monitors connected. I will set it to disable and check if my problem comes back.

One point - my main monitor is connected via D-DVI and my secondary monitor is HDMI. With CSM disabled - boot and BIOS is always on the HDMI, where as with CSM enabled, boot and BIOS is on the D-DVI monitor.

EDIT: Yeah I set my CSM to disabled and the no signal monitor problem happened when booted into High Sierra. For me - I must set CSM to Auto or Enabled

 

[Danos]

In terms of these settings I use them, too. Tried Boot Device Control set to 'UEFI and Legay OPROM' as well as to 'UEFI only' – no change.

However I found out that the mbinit error I get seems to be fixable by setting XHCI handoff to enabled. Problem is: I can remember changing this setting a few days ago. Then I made an update to my mobo to check if it changes anything – now the option is gone in advanced -> USB settings, where it should be according to the user guide. @ccozmo can you look where it is on your ASUS board?

One point - my main monitor is connected via D-DVI and my secondary monitor is HDMI. With CSM disabled - boot and BIOS is always on the HDMI, where as with CSM enabled, boot and BIOS is on the D-DVI monitor.

This is normal – it is a rule of thumb that, if CSM enabled, your mobo uses the most legacy graphics connector you have (VGA > DVI > HDMI > DP), while with CSM disabled, it is vice versa. (Another reason why I would like to stay with CSM disabled...)

 

[vulgo]

Seems like enabling CSM doesn't do the trick for me...

It won't work for every motherboard/graphics card combination, the outputs at boot time are not the same as when the OS takes over. There may be like 2 outputs shared between 4 ports rather than 4 outputs on individual ports etc. Changing the display driver for the boot process or changing the connected ports might alter things so that when boot.efi and then the Nvidia driver takes over the framebufffers, the changeover works without error.

 

[ccozmo]

One more point - I also have Fast Boot set to disabled, not sure if that impacts it or not

However I found out that the mbinit error I get seems to be fixable by setting XHCI handoff to enabled. Problem is: I can remember changing this setting a few days ago. Then I made an update to my mobo to check if it changes anything – now the option is gone in advanced -> USB settings, where it should be according to the user guide. @ccozmo can you look where it is on your ASUS board?

I checked my BIOS under Advanced -> USB Config and couldn't see the XHCI handoff setting. Also went through all the other Advanced and Boot sections and couldn't find it

 

[Danos]

Already searched your mobo's manual – they removed this toggle on yours out of box.

 

[ccozmo]

ok sorry - not sure why ACHI handoff would cause graphics issues, hopefully they release a new BIOS to fix it

 

[Danos]

ok sorry - not sure why ACHI handoff would cause graphics issues, hopefully they release a new BIOS to fix it

XHCI doesn't cause graphics issues. But if I wanted to boot with CSM enabled (like some people here suggested as a fix), I would get this error here:

mbinit: done [128 MB total pool size, (85/42) split] in verbose boot.

I found out that enabling XHCI handoff should fix this issue, but the option is not present in my UEFI after the latest update, so I guess it is in some kind of auto mode.

If it were possible to disable the GPUs output to a certain display (like Windows allows you to do ('Only display on monitor 1') and if this setting were saved between shutdown and restart, one could create a script to disable the second monitor before shutdown and to enable it after login, which could be a potential fix. But disabling displays using terminal commands or something similar doesn't seem to be possible, according to my research.

EDIT: FIXED IT!
ASUS seems to have renamed this function to 'USB Keyboard and Mouse Simulator'. Glad it works now. Now I just have to make sleep mode work. But that's another story...

 

[Clicky]

Guys, I am kind of pissed. Why can't I have CSM disabled and dual displays? I like that Hi - Res Clover and boot sequence on the DP display.

 

[ccozmo]

EDIT: FIXED IT!
ASUS seems to have renamed this function to 'USB Keyboard and Mouse Simulator'. Glad it works now. Now I just have to make sleep mode work. But that's another story...

Great - Was it CSM enabled that fixed your display issue ?

 

[vulgo]

Guys, I am kind of pissed. Why can't I have CSM disabled and dual displays? I like that Hi - Res Clover and boot sequence on the DP display.

Great - Was it CSM enabled that fixed your display issue ?

Hmm i turn off Windows 8 features, now i get full resolution boot graphics (on the wrong monitor) and can boot with both displays. This never worked before, different Clover, different ports maybe. Or buggy firmware with unpredictable results.