macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

This what it looks like with reduced transparency off which is not bad maybe can figure out how to just turn on transparency for the dock I would be happy with this

@pkouame already discovered how to do that (editing the HIToolBox.framework), the only fact is, after patched the "light mode", even in "dark mode" the finder top menu bar will be turned into a solid black, no big issue, hardly noticeable a darker transparency, anyway I guess his "hybrid light mode" will be released after 9/24 at this point, since the functions and coding could change a bit within two weeks.

edit:
I've inspected too the HIToolBox.framework's Resources and there is the Extras2.rsrc that contains all the finder top menu bar graphics assets.
While the AppKit.framework manages the left side panel finder windows (together with many other things), that are used to draw almost any app in macOS.

Of course these patches pkouame will release (hope soon) have nothing to share with the "reduce transparency" that is an Accessibility feature.

 

[TimothyR734]

The Dosdude1 app downloads the Developer Preview, right? If so, I do not have a paid developer account, so I need the Public Beta, that is freeware for all. That is the point.
[doublepost=1536855066][/doublepost]
It depends. In some parts of the world, it is ok to hackintosh for personal use only, as long as the OS comes from legit sources. I subscribe, mostly, to the Tonymacx86 code of conduct regarding piracy and hackintoshing, as I this quote: ”This site does not condone piracy or the use of illegally acquired software. (...) Piracy is illegal and not tolerated. (...) Building a hackintosh is not illegal as long as you have legally acquired macOS. However by installing macOS on non-Apple hardware is a violation of the Eula. In most countries, violating the terms of the Eula is not illegal as it is a contract. You are advised to consult your local laws before continuing. ” (https://www.tonymacx86.com/rules/) .

That maybe true but there really is no difference in Dev beta or public beta and how many people do you know that have been arrested for Hackintoshing or tweaking Windows heck I have windows XP running on my iMac 8,1 not boot camp either been on there for years. I am quite sure Apple would send a warning first
[doublepost=1536859083][/doublepost]

@pkouame already discovered how to do that (editing the HIToolBox.framework), the only fact is, after patched the "light mode", even in "dark mode" the finder top menu bar will be turned into a solid black, no big issue, hardly noticeable a darker transparency, anyway I guess his "hybrid light mode" will be released after 9/24 at this point, since the functions and coding could change a bit within two weeks.

edit:
I've inspected too the HIToolBox.framework's Resources and there is the Extras2.rsrc that contains all the finder top menu bar graphics assets.
While the AppKit.framework manages the left side panel finder windows (together with many other things), that are used to draw almost any app in macOS.

Of course these patches pkouame will release (hope soon) have nothing to share with the "reduce transparency" that is an Accessibility feature.

With reduced transparency on and if we can figure out how to just turn on transparency for the dock might be a temp fix until pkouame's "fix" is released. The other thing to consider is some of the newer Mac models have True Tone which could play apart in the menubar

 

[DaniloGeekDude]

Just discovered a new glitch on my mojave unsupported MBP5,3.
I like my dock "automatically hide and show", so I checked that box. Now that I have developer preview 11, it does not work - "the dock does not show". Anyone else experienced this on the latest beta?

Thanks.

 

[jackluke]

With reduced transparency on and if we can figure out how to just turn on transparency for the dock might be a temp fix until pkouame's "fix" is released. The other thing to consider is some of the newer Mac models have True Tone which could play apart in the menubar

You know, I've done many many experiments on that, I was doing a script patch on it, but I'd have preferred to wait first for the pkouame "hybrid light mode".

To those who have an OpenGL (non-Metal) GPU, and prefer to use Mojave in "light mode":

I introduce my "hybrid reduce transparency" for Mojave "light mode" (Download link attached at bottom):

For those instead want to try to reduce transparency "saving Dock transparency" from their Terminal, here is my funny experiment:

defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder

after done, close and re-open safari (and any previous opened app) and you'll notice also the clearer Safari's Favorites front page.

Until you don't relaunch the Dock you'll have a partial transparency, but unluckily the Dock.app is strictly dependent from the Finder.app so it will work but temporary, let's say, until a reboot or logout it will work. It works also after the sleep lock screen, just avoid switching between multi-users, otherwise need to repeat using the "METHOD 2" explained further on this post.

Not only Dock's transparencies are saved but also Notification Center and some others.
The key is deny the system to relaunch the Dock and Notification Center for you.

To return with normal "transparency" use Accessibility prefpane or type from Terminal:

defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder; killall Dock; killall NotificationCenter; killall Spotlight

edit:
I will release a full shell script with more patches further on.

edit2:
Just double click on this attached shell mojavehld.command and it will launch through Terminal, anyone can try the reduce transparency patch, it's totally harmless and reversible.

Note: I like the "homebrew" shell, that's why I forced the black/green colors even on a white Terminal.

edit3:
Please re-download the mojave.command since I made some little update. I've added the "killall Dock, NotificationCenter and Spotlight", forgotten in restore Mojave defaults and transparency patch.


[METHOD 1]
After launch the mojavehld.command just follow these steps:
type 1
type 4
close Terminal (CMD+Q) and any other app previously opened.

(The choice number 3 is not mandatory)

[METHOD 2]
If for some reason after that you will still get Dock and Notification Center with "reduced transparencies" then relaunch the mojavehld.command:
type 2
type 1
type 4
close Terminal (CMD+Q) and any other app previously opened.

It will 100% work until restart or logout. Even after sleep lock screen it will still work.

Here are the proofs screenshots:

 

[Starplayr]

Let me add to that, with Mojave sleep is completely broken when waking. It has been like that all 11 builds. I'm hoping that Nvidia web drivers will fix this issue. Or I can mail my 780m to MacVidCards to be flashed. Also with my 27" 2011, one of my displayports do work and I can output 4k@60hz.

Weird sleep working with my Titan. But no video drivers are swapped out on my system.

The web drivers should fix this issue but if any base graphics drivers were either patched or replaced you may need to reinstall, boot under safe mode, install the NVIDiA web drivers and reboot.

I tried the patched Tesla drivers with the Apple Kepler drivers because I was running both cards which works in High Sierra but in Mojave the Tesla drivers disabled the Mojave Kepler drivers.

 

[highvoltage12v]

Weird sleep working with my Titan. But no video drivers are swapped out on my system.

The web drivers should fix this issue but if any base graphics drivers were either patched or replaced you may need to reinstall, boot under safe mode, install the NVIDiA web drivers and reboot.

I tried the patched Tesla drivers with the Apple Kepler drivers because I was running both cards which works in High Sierra but in Mojave the Tesla drivers disabled the Mojave Kepler drivers.

This is likely an MXM power management problem and communication with EFI waking from sleep. On earlier builds it would kernel panic waking from sleep. On the latest build, it will wake from sleep, the screen will stay black and a grey screen with purple pixilation will show up. No graphics kexts from the patcher are used.
I have expermented with Web drivers from HS forcing them to load. No acceleration of course, but it will wake from sleep with a working display.

 

[TimothyR734]

You know, I've done many many experiments on that.

I was doing a script patch on it, but I'd have preferred to wait first for the pkouame "hybrid light mode".

Ok, I introduce my "hybrid reduce transparency" for Mojave "light mode":

If you want to try to reduce transparency "saving Dock transparency" from Terminal, here is my funny experiment:

defaults write com.apple.universalaccess reduceTransparency -bool true

killall Finder

until you don't relaunch the Dock you'll have a partial transparency, but unluckily the Dock.app is strictly dependent from the Finder.app so it will work but temporary let's say, until a reboot or logout it will work. Not only Dock's transparencies are saved but also Notification Center and some others.

To return with normal "transparency" type from Terminal:

defaults write com.apple.universalaccess reduceTransparency -bool false

killall Finder

I was able to reduce the bright white dock with reduced transparency on so my dock icon don't look so blended in and easier to see. I love that the clock mini also changes from high to dark mode

 

[jhowarth]

Weird sleep working with my Titan. But no video drivers are swapped out on my system.

The web drivers should fix this issue but if any base graphics drivers were either patched or replaced you may need to reinstall, boot under safe mode, install the NVIDiA web drivers and reboot.

I tried the patched Tesla drivers with the Apple Kepler drivers because I was running both cards which works in High Sierra but in Mojave the Tesla drivers disabled the Mojave Kepler drivers.

I would assume things might improve once Nvidia actually released web drivers that are certified for 10.14.

 

[Starplayr]

I would assume things might improve once Nvidia actually released web drivers that are certified for 10.14.

Apple’s drivers are certified they just don’t cover all the available chipsets.

Technically the web drivers are beta according to the download documentation for Mac Pro 3,1, 4,1, 5,1 and PC Cards flashed or unflashed are also technically unsupported, they are just allowed every since Lion and Mtn Lion. NVIDiA does do a great job on their drivers. And they are smarter than AMD by allowing a wide range of cards to be used.

 

[thegurgz]

You know, I've done many many experiments on that.

I was doing a script patch on it, but I'd have preferred to wait first for the pkouame "hybrid light mode".

Ok, I introduce my "hybrid reduce transparency" for Mojave "light mode":

If you want to try to reduce transparency "saving Dock transparency" from Terminal, here is my funny experiment:

defaults write com.apple.universalaccess reduceTransparency -bool true

killall Finder

after close and re-open safari (and any previous opened app) and you'll notice also the clearer Safari's Favorites front page.

Until you don't relaunch the Dock you'll have a partial transparency, but unluckily the Dock.app is strictly dependent from the Finder.app so it will work but temporary let's say, until a reboot or logout it will work. Not only Dock's transparencies are saved but also Notification Center and some others.

To return with normal "transparency" type from Terminal:

defaults write com.apple.universalaccess reduceTransparency -bool false

killall Finder; killall Dock; killall NotificationCenter

edit:
I will release a full shell script with more patches further on.

edit2:
Just double click on this shell command and it will launch through Terminal, anyone can try the reduce transparency patch, it's totally harmless.

Note: I like the "homebrew" shell, that's why I forced the black/green colors even on a white Terminal.

edit3:
Please re-download I've added the "killall Dock and NotificationCenter", forgotten in restore Mojave defaults.

Downloaded and opened it. Typed 1, then 3. No change. I then decided to give up and pressed 2. Then finder/dock restarted, and now the transparency on the dock works with reduce transparency on. Weird that the numbers didn't do it, but thanks for the quick script!

Edit: Only worked on the chrome app, clicking back to desktop turned off reduce transparency in the menu bar.

 

[Macschrauber]

DP11 or GM Candidate on 3.1 and 5.1 w/ GTX680

5.1: couldn't install with a boot stick with DP11 on it, refuses the GTX680 as not metal supported !! Ran Installer from Mojave Beta directly and right now it installs over an early beta version.

3.1: Nothing to tell, everything works as before. used Mojave Patcher 1.20 - should rename disk to dp11 or gm ?

 

[jackluke]

Downloaded and opened it. Typed 1, then 3. No change. I then decided to give up and pressed 2. Then finder/dock restarted, and now the transparency on the dock works with reduce transparency on. Weird that the numbers didn't do it, but thanks for the quick script!

Edit: Only worked on the chrome app, clicking back to desktop turned off reduce transparency in the menu bar.

It works, it is intended for the Mojave "light mode", anyway, just type 1 , after typed 1 , type 4, then close Terminal (CMD+Q), close the current browser and any opened app, then open Finder and any app you want, from there you'll have solid white Finder menu bar, fixed greyed sidebars, while keeping the Dock, Notification Center and others transparencies.

If you see still "reduced transparencies" everywhere, just type 2, then type 1 again, and close Terminal and any other previous opened apps.

The choice number 3 is not mandatory.

edit:
Trust me this is the less invasive patch for Mojave light mode you can find until now.
It's perfectly working even in dark mode, you will have solid black menu bar, and you can simply revert to defaults dark/light modes.

 

[thegurgz]

Found a bug that I noticed in APFS in the past betas slightly, but never grabbed screenshots, just reformatted back to HFS+. I'll start at the beginning.
Had a Mojave disk, formatted as macOS Extended(Journaled), or HFS+ with around 30gb of data.
Then, reformatted to APFS, no issues, booted back in (previously used APFS Rom patcher), still 30gb.
Ran a reinstall of the same beta build to get everything correctly in the container and see if this glitch would happen again, as I had seen it but quickly reverted back to HFS+. Everything went flawlessly, still 30gb.
I thought that this glitch would come back after installing an OS on an APFS drive, but it did not, so I thought maybe it was a one time thing. Everything was perfect and smooth until updating from native Software Updater (OTA). After updating to the GM canidate, 18A389, my drive size was not correct, showing 50gb instead of 30gb.
What troubles me is that in "About This Mac">Storage, it shows the correct amount used an available. Clicking manage shows me all the sizes of files, which adds up correctly to the amount it should be. I booted onto my installer stick and opened disk utility from there, and it is still showing 20gb higher than it should. As I mentioned, I have seen this once more before after an OTA update, and reformatting to HFS+ fixed the issue. Anyone have any insight as to why this would happen after updating OTA?

 

[brkr1]

View attachment 779861

In this thread, advancements in running macOS 10.14 Mojave on unsupported systems will be discussed.
​

• MACHINES THAT HAVE MULTIPLE EEPROM DEFINITIONS. Relevant information can be found here and here.)

Current Hardware Support Status:

• Machine Support
  • Early-2008 or newer Mac Pro, iMac, or MacBook Pro:
    • MacPro3,1
    • MacPro4,1
    • iMac8,1
    • iMac9,1
    • iMac10,x
    • iMac11,x
    • iMac12,x
    • MacBookPro4,1
    • MacBookPro5,x
    • MacBookPro6,x
    • MacBookPro7,1
    • MacBookPro8,x
  • Late-2008 or newer MacBook Air or Aluminum Unibody MacBook:
    • MacBookAir2,1
    • MacBookAir3,x
    • MacBookAir4,x
    • MacBook5,1
  • Early-2009 or newer Mac Mini or white MacBook:
    • Macmini3,1
    • Macmini4,1
    • Macmini5,x
    • MacBook5,2
    • MacBook6,1
    • MacBook7,1
  • Early-2008 or newer Xserve:
    • Xserve2,1
    • Xserve3,1

• Video Card Support
  • Pre-Metal AMD video cards (Radeon HD 6xxx series and older)
  • Pre-Metal Nvidia video cards (GeForce 5xx series and older)
  • Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)

Current Issues

• Graphics anomalies: Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transpareny as some systems with pre-metal AMD graphics render the dock in dark gray).
• AMD Radeon HD 5xxx/6xxx series GPU acceleration: Currently, it is not possible to get graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series GPU. This includes 2010 and 2011 iMacs and 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these MacBook Pro systems, you'll need to disable the AMD GPU.
• Early-2008 Mac Pro (MacPro3,1) GPU support: When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-comptible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.
• Built-in iSight cameras: Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
• Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
• Unsupported WiFi modules in some systems. Macs that use the Broadcom BCM4321 WiFi module will not have functional WiFi when running Mojave. A fix for this is to open up your machine and install a compatible WiFi card. Machines affected include some MacPro3,1, MacBook5,2, MacBookPro4,1, iMac8,1, Macmini3,1, and MacBookAir2,1 systems. Please note that not all these machines will have an unsupported card, this is just a list of machines known to have shipped with that card in some configurations.
• App Store Crashing: Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.

Current Issues by Hardware

• Graphics anomalies:
  • All machines
• AMD GPU acceleration:
  • All machines with a Radeon HD 5xxx or 6xxx series GPU
• AMD GPU support:
  • MacPro3,1
• Built-in iSight camera:
  • All machines, hit or miss
• Trackpad:
  • MacBook5,2
• Unsupported WiFi modules:
  • All machines that use the Broadcom BCM4321 WiFi module
• App Store Crashing:
  • Machines with accelerated pre-metal Radeon HD GPUs (like Radeon HD 4xxx series GPUs)

Installing for Testing:
To install on your machine, you can download and run my macOS Mojave Patcher application, which will let you download a copy of the latest Developer Preview from Apple, and create a bootable USB installer for use on unsupported systems. It contains all the patches necessary to achieve the hardware support listed above. At this point, it is recommended that you install Mojave on one of these unsupported systems for testing only, and NOT as your main/daily use OS. Older versions of the patcher can be found here, the changelog here, and the official installation guide here.

Video Demo:
A video demo of Mojave running on various unsupported Macs can be found here.

Mojave Builds and Installer Versions (Developer Preview, Public Beta):
2018/06/04 DP1, build 18A293u, installer 14.0.08
2018/06/19 DP2, build 18A314h, installer 14.0.11
2018/06/26 PB1, build 18A314k, installer 14.0.11
2018/07/03 DP3, build 18A326g, installer 14.0.12
2018/07/06 PB2, build 18A326h, installer 14.0.12
2018/07/16 DP4, 2018/07/17 PB3, build 18A336e, installer 14.0.14
2018/07/30 DP5, 2018/07/31 PB4, build 18A347e, installer 14.0.15
2018/08/06 DP6, 2018/08/06 PB5, build 18A353d, installer 14.0.16
2018/08/13 DP7, 2018/08/13 PB6, build 18A365a, installer 14.0.17
2018/08/20 DP8, 2018/08/20 PB7, build 18A371a, installer 14.0.18
2018/08/27 DP9, 2018/08/27 PB8, build 18A377a, installer 14.0.20
2018/09/04 DP10, 2018/09/04 PB9, build 18A384a, installer 14.0.21
2018/09/12 DP11, 2018/09/12 PB10 build 18A389, installer 14.0.21

Special Thanks:
@Badruzeus - Discovered that Sierra OpenGL drivers work in Mojave.
@ASentientBot - Fixed Nvidia kernel panic, Core 2 Duo kernel panic, and iSight.
@jackluke - Narrowed down cause of Core 2 Duo kernel panic.
@dosdude1 - Developed macOS Mojave Patcher.

Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.

[doublepost=1536877859][/doublepost]Installed on my MacBook Pro 15 Mid 2009 and everything works just fine.

Installed it on my iMac 27 Mid 2011 and all seems like as if the colors are inverted. What should be blue is orange.. Has anybody got the same issue? How can I fix it?

 

[Martyimac]

@dosdude1 Okay, my mac mini 5,2 won't update, booted off the usb stick and reran the post install program ensuring the update patch option was selected.. Rebooted and alas, it will not update to the PB10 which is considered the probable GM.
Had to start from scratch, the patcher DID download the latest potential GM, installed along with deselecting the video card patch in the post mac install app and all looks good.

THANK YOU

[doublepost=1536878080][/doublepost]

[doublepost=1536877859][/doublepost]Installed on my MacBook Pro 15 Mid 2009 and everything works just fine.

Installed it on my iMac 27 Mid 2011 and all seems like as if the colors are inverted. What should be blue is orange.. Has anybody got the same issue? How can I fix it?

There is a fix for the colors, post # 6861 (PS worked on my 2011 mac mine with the exact same problem)

 

[DaniloGeekDude]

I was able to reduce the bright white dock with reduced transparency on so my dock icon don't look so blended in and easier to see. I love that the clock mini also changes from high to dark mode

I read this on Transparent Dock's readme file:

"Please note:

This application will only make changes to the dock under Mac OS X 10.2 - 10.4 (PowerPC Macs only). If run in earlier or later versions of Mac OS X, the TransparentDock application will not make the dock transparent. Currently, TransparentDock is not compatible with Intel-based Macs.


New in Version 2.3.9:

• updated for compatibility with Mac OS X Tiger 10.4.8"

Is this compatible as well to Mojave and my MBAir4,2? And if installed, can I un-install it if I change my mind?
The notes also states to register. So I am assuming it is not freeware?

Thanks @TimothyR734!

 

[Martyimac]

[doublepost=1536877859][/doublepost]Installed on my MacBook Pro 15 Mid 2009 and everything works just fine.

Installed it on my iMac 27 Mid 2011 and all seems like as if the colors are inverted. What should be blue is orange.. Has anybody got the same issue? How can I fix it?

see post 6 8 6 1 on this thread

 

[brkr1]

@dosdude1 Okay, my mac mini 5,2 won't update, booted off the usb stick and reran the post install program ensuring the update patch option was selected.. Rebooted and alas, it will not update to the PB10 which is considered the probable GM.
ALSO, I can no longer find "install macOS Mojave" or a mojave installer on the app store any more.

Any thoughts?
[doublepost=1536878080][/doublepost]
There is a fix for the colors, post # 6861 (PS worked on my 2011 mac mine with the exact same problem)

Thank you so much!!!!

 

[TimothyR734]

You know, I've done many many experiments on that.

I was doing a script patch on it, but I'd have preferred to wait first for the pkouame "hybrid light mode".

Ok, I introduce my "hybrid reduce transparency" for Mojave "light mode":

If you want to try to reduce transparency "saving Dock transparency" from Terminal, here is my funny experiment:

defaults write com.apple.universalaccess reduceTransparency -bool true

killall Finder

after close and re-open safari (and any previous opened app) and you'll notice also the clearer Safari's Favorites front page.

Until you don't relaunch the Dock you'll have a partial transparency, but unluckily the Dock.app is strictly dependent from the Finder.app so it will work but temporary let's say, until a reboot or logout it will work. Not only Dock's transparencies are saved but also Notification Center and some others.

To return with normal "transparency" type from Terminal:

defaults write com.apple.universalaccess reduceTransparency -bool false

killall Finder; killall Dock; killall NotificationCenter

edit:
I will release a full shell script with more patches further on.

edit2:
Just double click on this shell command and it will launch through Terminal, anyone can try the reduce transparency patch, it's totally harmless.

Note: I like the "homebrew" shell, that's why I forced the black/green colors even on a white Terminal.

edit3:
Please re-download I've added the "killall Dock and NotificationCenter", forgotten in restore Mojave defaults.

Good work
[doublepost=1536879110][/doublepost]

I read this on Transparent Dock's readme file:

"Please note:

This application will only make changes to the dock under Mac OS X 10.2 - 10.4 (PowerPC Macs only). If run in earlier or later versions of Mac OS X, the TransparentDock application will not make the dock transparent. Currently, TransparentDock is not compatible with Intel-based Macs.


New in Version 2.3.9:

• updated for compatibility with Mac OS X Tiger 10.4.8"

Is this compatible as well to Mojave and my MBAir4,2? And if installed, can I un-install it if I change my mind?
The notes also states to register. So I am assuming it is not freeware?

Thanks @TimothyR734!

I don't have the $ to pay for was just testing it out I got it to reduce the white color of the dock while the reduced transparency was on I used the aqua and silver colors for the dock

 

[jhowarth]

Apparently folks on supported machines are claiming that the 19A389 full installer can be gotten with the python script here...

https://github.com/munki/macadmin-scripts/blob/master/installinstallmacos.py

but the comment at http://osxdaily.com/2018/09/12/macos-mojave-beta-11-released-for-testing/ says that this approach only downloads the files for the machine it is run on. So I don't know what that means logically for unsupported machines.

 

[dosdude1]

Apparently folks on supported machines are claiming that the 19A389 full installer can be gotten with the python script here...

https://github.com/munki/macadmin-scripts/blob/master/installinstallmacos.py

but the comment at http://osxdaily.com/2018/09/12/macos-mojave-beta-11-released-for-testing/ says that this approach only downloads the files for the machine it is run on. So I don't know what that means logically for unsupported machines.

Mojave Patcher downloads the 18A389 release... (it's 18A389 not 19A389).

 

[jhowarth]

Mojave Patcher downloads the 19A389 release...

What version number should I expect for the installer? The same 14.0.21 as Beta 10?

 

[Macschrauber]

6.034.224.400 bytes (6,04 GB on disk)
8 September 2018 at 05:08
14.0.21

 

[jhowarth]

6.034.224.400 bytes (6,04 GB on disk)
8 September 2018 at 05:08
14.0.21

Okay. Wonder then if the absence of a revision bump in the installer version number since Beta 10 implies that Apple hasn't actually built a full installer for the GM?

 

[Starplayr]

After many tests, I have definitely confirmed my PC Nvidia GeForce GTX Kepler Titan on a Mac Pro 3,1 2008 with Apple's Mojave Nvidia drivers (stock unpatched), is capped at 2.5GT/s. Still a great card and experience. Just finally feeling what MVC/Rominator felt many years ago. My AMD Radeon 7970 (that's what it says), has a Mac EFI ROM and runs at 5GT/s but my processor at this time can't use the AMD drivers as this is well known. I tried using an emulator and got the X4000 ext. to load but not change even after killing the window server. I may spend more time with it later but this is what I got.

1) Nvidia card (Kepler Titan 6GB) that supports Metal GPUFamiy1 v4 with stock drivers, but on 2008 with standard PC Card is capped at 2.5GT/s

1) AMD Radeon 7xxx 4GB card capable of Metal but cannot use the AMD drivers on Mac Pro 3,1. Boot Screen. currently will run Mojave without X4000 drivers loaded or in Safe Mode. runs at 5GT/s

1) Nvidia card 8800GT 512MB that works with patched Tesla drivers. Boot screen. Will work with Safe Mode without patched drivers and handy to switch boot drivers, just have to switch Video Cable. runs at 5GT/s

Attached screenshot of Phantom screen when 8800GT has power without video drivers and no display. it defaults to 800x600. Unplugging power from card makes Phantom screen on left go away.

I may try some other intermediate ways to get the Mac think an EFI for the titan card was loaded.

here is the results from the Titan with lspci -vv under heavy load using Heaven. The card still performs really well. Just not able to top out its Max Speed. Not sure though if a patched EFI will work on the 2008. I may use MVC for this but will probably sell my AMD 7xxx card first and find Nvidia Card that's is flushable. that way I would still have two cards and not a lot of dough in one.

02:00.0 VGA compatible controller: nVidia Corporation Unknown device 1005 (rev a1) (prog-if 00 [VGA controller])
    Subsystem: eVga.com. Corp. Unknown device 2790
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 19
    Region 0: Memory at 9e000000 (32-bit, non-prefetchable)
    Region 1: Memory at <ignored> (64-bit, prefetchable)
    Region 3: Memory at <ignored> (64-bit, prefetchable)
    Region 5: I/O ports at 4000 [disabled]
    Capabilities: [60] Power Management version 3
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
        Address: 00000000fee00000  Data: 4073
    Capabilities: [78] Express (v1) Endpoint, MSI 00
        DevCap:    MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
            ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
        DevCtl:    Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
            RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 512 bytes
        DevSta:    CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend+
        LnkCap:    Port #8, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us
            ClockPM+ Suprise- LLActRep- BwNot-
        LnkCtl:    ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
            ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
        LnkSta:    Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
    Capabilities: [100] #10de
    Capabilities: [100] <chain looped>

02:00.1 Audio device: nVidia Corporation Unknown device 0e1a (rev a1)
    Subsystem: eVga.com. Corp. Unknown device 2790
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin B routed to IRQ 16
    Region 0: Memory at 9f080000 (32-bit, non-prefetchable) [disabled]
    Capabilities: [60] Power Management version 3
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Address: 00000000fee00000  Data: 4075
    Capabilities: [78] Express (v1) Endpoint, MSI 00
        DevCap:    MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
            ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
        DevCtl:    Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
            RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
            MaxPayload 128 bytes, MaxReadReq 512 bytes
        DevSta:    CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
        LnkCap:    Port #8, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us
            ClockPM+ Suprise- LLActRep- BwNot-
        LnkCtl:    ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk-
            ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
        LnkSta:    Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
    Capabilities: [100] #10de