Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
@pkouame

That might be interesting:

In Yosemite / El Capitan there was a command you made to keep the menu bar in light mode or dark mode and the dock and other things in the dark or light mode, according to your preference, I do not remember the command, but it was via Terminal, would that work on Mojave as well? It would be one of the options.
sudo defaults write /System/Library/LaunchDaemons/com.apple.WindowServer 'EnvironmentVariables' -dict 'CI_NO_BACKGROUND_IMAGE' 1 I think that was the command by terminal it would turn your menubar white

They are all deprecated functions in Mojave, the only currently that allows some little modifications from Terminal is "NSRequiresAquaSystemAppearance", setting its value to NO enables dark mode, setting to YES enables light mode.
 
  • Like
Reactions: TimothyR734
They are all deprecated functions in Mojave, the only currently that allows some little modifications from Terminal is "NSRequiresAquaSystemAppearance".
That was the terminal command in El Captain/Yosemite to change your dock/menubar but that was based on just have a jpeg wallpaper in Mojave it is dynamic so its constantly changing every hour as it is in the HEIC format not jpeg and our dynamic walloper also uses some of our heat sensors built in as my menubar does get lighter with the change of the dynamic wallpaper and gets darker as we get closer to night time
 
That was the terminal command in El Captain/Yosemite to change your dock/menubar but that was based on just have a jpeg wallpaper in Mojave it is dynamic so its constantly changing every hour as it is in the HEIC format not jpeg and our dynamic walloper also uses some of our heat sensors built in as my menubar does get lighter with the change of the dynamic wallpaper and gets darker as we get closer to night time

Agree about your dynamic wallpaper format explanations, but on Yosemite/ElCapitan the Terminal commands to enable dark mode were:

For Yosemite:

sudo defaults write /Library/Preferences/.GlobalPreferences AppleInterfaceTheme Dark

sudo defaults write /Library/Preferences/.GlobalPreferences AppleInterfaceTheme Light


for El Capitan:

sudo defaults write /Library/Preferences/.GlobalPreferences.plist _HIEnableThemeSwitchHotKey -bool true

some blogs reported that even a keyboard shortcut could switch between dark/standard mode:
CMD + alt (option) + CTRL + T
but to me this didn't worked.

Anyway we should wait for pkouame's "hybrid light mode" patch release.
 
When are the graphics anomalies fixed? That's the only thing that prevents me from updating

I have zero graphics anomalies with the Kepler Titan GPU. Not in safe mode and not in standard boot mode.

Hopefully other Kepler cards will follow suit. And later Nvidia’s web drivers will be put after GM is released.

Will be interesting which NVIDiA cards will go beyond Metal family 1 v4.
 
I read this is no longer the case with cards that have drivers working 100%. I can't find the article at this moment but as soon as Apple started allowing PC Cards to be used in Mac OS Mtn Lion and later, that once the drivers load, it will run PCIe 2.0.

BTW, there is the post on PCI 1.0 and 2.0 with PC Cards. See #17. It doesn't mention the 3,1 only 4,1 and 5,1. So possibly it is running at 1.0 on my system, but I honestly can't tell the difference if there is. I may one day put this to a test and get another card and have it flashed, but that's gonna be long time. I would really like to know if there is a difference.

https://forums.macrumors.com/thread...out-nvidia-pc-non-efi-graphics-cards.1440150/

I also read somewhere that cards will drop up and down in speed pending how much that card is being taxed. And in many real world scenarios the difference in 1.0 vs 2.0 is minimal.

Regardless, I am super happy with the result and will be selling out my 2012 Mac mini and its Thunderbolt Display.

MacVidCards btw with the Titan X will only show 2.5GT/s even on a flashed card. He has some other way of proving it is running 2.0 speed on his site. The cost to for him to flash a Titan, Black, or X is $160.00.

There is also the bottleneck of what a 2008 can really handle. Honestly with my Titan X Maxwell (flashed) and Titan Kelper (unfleshed) there wasn't any noticeable speed difference in High Sierra. I can't say the same for Mojave because the Maxwell needs Web drivers.

I believe you can use GPU-Z under Windows to see what level the PCI-e bus is running at.
 
  • Like
Reactions: jackluke
I believe you can use GPU-Z under Windows to see what level the PCI-e bus is running at.

Not a great test though. A test under Mojave would be better. Some people say PC Cards without a Mac EFI run 1.0 on Windows 10. I have not seen this with my AMD Card, but it's flashed. But a PC Card with proper drivers on Mac or PC should run 2.0. Newer cards are now PCIe 3.0 so on these 2008-2012 Mac Pro's your never gonna reach top speed.

I'll try to dig up what MacVidCards uses for testing. And I will keep my eyes peeled for another cheap Titan card and will try to get one flashed one day to really put this to a test. It will take some time as I am slowly selling off my Mac mini stuff.

My current guess is the difference with a flashed Card and non on Mac Pro 3,1 is negligible.

Here is what MVC is using for his testing:

http://www.macvidcards.com/50-pcie-speed1.html

Will run the command line one tonight. I can run the CUDA-Z on High Sierra tonight and the command line one.

Here he is showing the Nvidia cards start out at 2.5 link speed and later switch to 5.0 link speed when under load. My guess is non-EFI cards will behave the same. We shall see.
 
Last edited:
I believe you can use GPU-Z under Windows to see what level the PCI-e bus is running at.

Provided you install first the CUDA Nvidia driver: https://www.nvidia.com/object/mac-driver-archive.html

The CUDA driver is an add-on to the stock or Web Nvidia driver, it adds CUDA framework that should enable some benefits, and I've tested, it works also on Mojave.

Then you can use a similar GPU-Z software even on Mac: http://cuda-z.sourceforge.net/#block-macosx

edit:
I wrote about months ago: Nvidia 320M CUDA framework details
 
Last edited:
  • Like
Reactions: TimothyR734
I sort of just lucked out it seems.
Some time ago I picked up this little GT 640 from ebay for less then $100, at the time I was running El Capitan.
It has served me well from El-Cap to Sierra to HighSierra and now to Mojave betas.
I like the fact that it's Metal capable plus I have a boot screen and no extra power cable required.

View attachment 780606 View attachment 780607
You have a boot screen with a GT640?? If you could dump that ROM for me, that would be awesome!
 
You have a boot screen with a GT640?? If you could dump that ROM for me, that would be awesome!
If I knew how I'd be right on it.:)
Maybe take this to a PM...
On a different note, I can't get trim enabled using TrimForce, am I alone here or is this a common problem.:(
My installation is HFS because my macpro 3,1 refuses to flash as mentioned in an earlier post.
 
  • Like
Reactions: TimothyR734
Provided you install first the CUDA Nvidia driver: https://www.nvidia.com/object/mac-driver-archive.html

The CUDA driver is an add-on to the stock or Web Nvidia driver, it adds CUDA framework that should enable some benefits, and I've tested, it works also on Mojave.

Then you can use a similar GPU-Z software even on Mac: http://cuda-z.sourceforge.net/#block-macosx

edit:
I wrote about months ago: Nvidia 320M CUDA framework details

I thought the Cuda driver was tightly tied to the macOS build like the web drivers, but will give it a whirl on a backup partition. I'll run Cuda-Z tests on High Sierra and Mojave this evening.
[doublepost=1536691915][/doublepost]
If I knew how I'd be right on it.:)
Maybe take this to a PM...
On a different note, I can't get trim enabled using TrimForce, am I alone here or is this a common problem.:(
My installation is HFS because my macpro 3,1 refuses to flash as mentioned in an earlier post.

I haven't run Trim in a long time. Don't really see a difference. Haven't flashed my 3,1 for AFPS either. Happy with HFS.
Technically I am glad I don't have to run new firmware, Mac EFI video cards, etc. Nice to have backward compatibility. :)
 
Last edited:
I thought the Cuda driver was tightly tied to the macOS build like the web drivers, but will give it a whirl on a backup partition. I'll run Cuda-Z tests on High Sierra and Mojave this evening.

I've installed only CUDA driver with the stock Nvidia kexts both HS 10.13.6 and Mojave beta 10, and it's working fine, maybe just a delay of 3 seconds during system boot, since it loads the CUDA.kext, CUDA.framework, CUDA unix binary, but it should bring some improvements to the OpenCL/OpenGL acceleration.
 
@Larsvonhier I think you have to use the same kexts for your GTX650 to enable full acceleration on Metal GPUFamily1_v4 in your Mojave beta with eGPU :

GeForce.kext
GeForceAIRPlugin.bundle
GeForceGLDriver.bundle
GeForceMTLDriver.bundle
GeForceVADriver.bundle
NVDAGK100Hal.kext
NVDAResman.kext
NVDAStartup.kext
IONDRVSupport.kext
IOGraphicsFamily.kext


Or replacing all from High Sierra 10.13.6 except don't touch this one in Mojave: IOPCIFamilly.kext
That´s really good news and worth a try - I´ll be on it coming weekend and report back "over there"!
 
This is interesting regarding the Light Mode glitches.
 

Attachments

  • Screen Shot 2018-09-12 at 7.44.23 AM.png
    Screen Shot 2018-09-12 at 7.44.23 AM.png
    61 KB · Views: 138
  • Screen Shot 2018-09-12 at 7.44.03 AM.png
    Screen Shot 2018-09-12 at 7.44.03 AM.png
    47.9 KB · Views: 155
[QUOTE="jhowarth, post: 26436602, member: 1065388"[/QUOTE]
On a different note, I can't get trim enabled using TrimForce, am I alone here or is this a common problem


In Terminal type;
sudo trimforce enable
enter password
do you wish to proceed (y/N) ?
type
y
Be patient as system will reboot
 
I am sure this has been mentioned before, but, sticking with my rule of patching everything myself, I manually followed this tutorial:

https://pikeralpha.wordpress.com/2017/01/30/4398/

Thank you for the link. I followed the steps to change the iMac minimum version from 13 to 10.
Code:
nm /S*/L*/PrivateFrameworks/CoreBrightness.framework/CoreBrightness|grep _ModelMinVersion
giving:
Code:
0000000000044260 s _ModelMinVersionBLR
0000000000044280 s _ModelMinVersionHarmony
Saved a copy of the original file
Code:
cd /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A
sudo cp -p CoreBrightness CoreBrightness_orig
With hex editor I replaced 0D in the address block starting at 44260 by 0A. The resigning
Code:
sudo codesign -f -s - /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness
The tab "Night Shift" shows now in Displays System Preferences (but still working only in Custom mode)
 
@pkouame

While the environment variable that @TimothyR734 suggested no longer works (since, like, Snow Leopard or something, I think), searching about it found me another interesting environment variable: CI_PRINT_TREE. Not sure if there will be any useful information in there, and I know you are exploring an alternate path of "hybrid" light/dark mode now, but perhaps this is interesting too. For finding the root cause and fixing that, rather than this (admittedly impressive) workaround.
 
Last edited:
[QUOTE="jhowarth, post: 26436602, member: 1065388"
On a different note, I can't get trim enabled using TrimForce, am I alone here or is this a common problem


In Terminal type;
sudo trimforce enable
enter password
do you wish to proceed (y/N) ?
type
y
Be patient as system will reboot

What part of "I can't get trim enabled using TrimForce" didn't you understand?
 
  • Like
Reactions: TimothyR734
hey has anyone figured out the mac os x mojave system update patcher yet.

testing is worthless if you cannot update to the latest version and dosdudes patcher only installs dp9 not 10 so how do we update to dp10 on unsupported platform please
 
  • Like
Reactions: TimothyR734
I've installed only CUDA driver with the stock Nvidia kexts both HS 10.13.6 and Mojave beta 10, and it's working fine, maybe just a delay of 3 seconds during system boot, since it loads the CUDA.kext, CUDA.framework, CUDA unix binary, but it should bring some improvements to the OpenCL/OpenGL acceleration.

Installed CUDA. Sadly NVIDiA system pref pane complains it does not match the Apple driver. The Kext loads.

Looks like the CUDA framework is looking for a specific Resman version. Will try changing that out with what the pref pane is seeing.

Cuda-Z fails on CUDA check.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.