macOS 10.14 Mojave on Unsupported Macs Thread

[Macschrauber]

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.

Typo ? This comes on a supported Mac Pro 5.1 running the script from El Cap

>
# ProductID Version Build Title

1 091-95774 10.13.6 17G2208 macOS High Sierra

2 091-82771 10.13.5 17F66a Install macOS High Sierra Beta

3 091-94326 10.13.6 17G65 macOS High Sierra

4 091-62771 10.14 18A389 macOS Mojave

5 041-03369 10.14 18A384a macOS Mojave Beta

 

[jhowarth]

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

Just to clarify, you are testing under macOS and not BootCamp Windows 10, right? I ask because what I had read about PC ROM'ed GTX 680 was that under macOS you would get 5 Gbps but under Windows you would get 2.5 Gbps. So flashing the card gets you option boot on macOS and 5 Gbps on Windows.

 

[nekton1]

PC GTX680 flashed to Mac efi rom seems to get 5GT/s in Slot 2

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

 

[brkr1]

see post 6 8 6 1 on this thread

Since you had the same issues I did, r u having lag when scrolling?

 

[Martyimac]

Since you had the same issues I did, r u having lag when scrolling?

Not really.

 

[Luckygreek]

Having had only a couple of days to evaluate the latest beta I'm not seeing the kind of high CPU usage as with previous beta's, WindowServer or Iconserviceagents in particular, fans are not ramping up, I can also watch full screen 4k video from YouTube without stuttering, some Photo editing apps as long as files remain relatively small, under 100MB's. Websites are almost instant, Safari is still slow to launch (15-20 seconds) where as Safari Technology maybe 3 seconds. Still running HS on other Mac's, but so far all apps native & 3rd party that I have work, (aside from Google Chrome) without incident, no random issues or kp's, at this point. Boot time is about 25 seconds, not bad for an 8 year old iMac w/out graphic acceleration. Interesting to evaluate but still not practical on some unsupported Mac's, internal SSD are almost mandatory, I tried running a 1TB spinner & it was painfully slow. 2010 27" iMac. IMHO
Again, many thanks to all that have made it possible to install Mojave on an array of unsupported Mac's.

 

[PBear.SF]

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.

That's odd, my Mac mini 5,1 updated from PB9 to PB10 flawlessly today from the OTA update offered internally by System Preferences. Same as with the update to PB9 last week, there was no need to interrupt the update process to reinstall dosdude1's patches before my machine completely restarted into the newest version.

Just like the PB9 update, the only things missing/broken after the restart were sound (no output - although, curiously, input seemed to be working) and Night Shift (no pref pane). Simply had to run the Patch Updater from inside PB10 to reinstall Legacy Audio and Night Shift patches (I actually reinstalled all of them, to keep it simple) and, then, reboot. Afterwards, everything working as it should be.

Don't know actually what the differences are between the Mac mini 5,1 and the 5,2 -- probably different graphics cards, maybe other things too -- but one wouldn't think they were that great to completely stymy your update attempt.

Am curious now as to what is actually occurring during these latest updates. Are the Legacy Audio and Night Shift patches the only ones that are still getting overwritten during the updates -- or are the other patches, like Software Update, SIP Disabler and Legacy Video Card, no longer needed on my machine? Was Legacy Video Card patch ever needed on my Intel HD 3000-based Mac mini 5,1 in the first place?

 

[Starplayr]

Just to clarify, you are testing under macOS and not BootCamp Windows 10, right? I ask because what I had read about PC ROM'ed GTX 680 was that under macOS you would get 5 Gbps but under Windows you would get 2.5 Gbps. So flashing the card gets you option boot on macOS and 5 Gbps on Windows.

I’m on a Mac Pro 3,1 which is card’s speed is negotiabled at startup with EFI. Since that is missing, it keeps the lanes x16 but justs at 2.5GT/s speed. So the bump to 5GT/s does not occur. If it was a 4,1 or 5,1 it would bump when called upon. All testing on Mac.

I have a Windows setup on another 3,2 but it’s a flashed and modded AMD card thst rush 5Gt/s on Windows and Mac just have a driver limitation on that card with Mojave and really Sierra and High Sierra.

What is weird is when I really tax the card in Heaven benchmark or in Fortnite the speed does get better. Got Max 120fps in Fortnite and hovers around 60-74fps. Max FPS in Heaven was 75fps And had some really high readings at times with Cl!ing with Metal. When I get those really good rates will check the speed. Could just be using more lanes.

I also got really crappy rates times as low at 3fps in Fortnite and 17fps in Heaven. So kinda weird performance. When that started it seemed to stick. Then taxing the card with the highest setting in Fortnite would increase performance.

Heaven benchmark renders really well with the Titan.

Also what is strange is Fortnite runs the same as my Maxwell Titan X thst was flashed but did not pay as much attention to when it ran at 5GT/s. I sold the card because of cost and was bored because there were not web drivers for it yet.

Overall I lucked out with the Kepler Titan card. For it being about 5 years old it’s still a stout card and in everyday use the UI keeps up nicely. The 5GT/s is more of a vanity thing than anything.

I also noticed that almost all other devices on the PCI chain run at 2.5GT/s this includes CPUs, WifFi and Ethernet.

Only my OWC PCIe 1TB SSD runs at 5GT/s but uses two lanes.

I also have a 2TB RAiD0 SSD that uses 4 500GB drives on two SATA 2 slots and each runs at 2.5GT/s but since it is using two slots I essentially get SATA 3 or 5GT/s speeds.

In everyday operation honestly in a video card you do not really see or feel the difference between a card at 2.5GT/s at x16 or a card at 5GT/s at x16. All you can do is measure the throughput.

I also get good speeds from CPU to GPU. Around 22Gb/s.

 

[Martyimac]

A new issue with the Mojave GM installed on my mini 5,2. Sleep doesn't work. Doesn't sleep at the programmed time, even stranger is I can't force it to sleep, I.E. click on the , select sleep and nothing happens.

Okay wizards, how do I fix this?

 

[pkouame]

PC GTX680 flashed to Mac efi rom seems to get 5GT/s in Slot 2

View attachment 781449

on pro 3.1 - my mac edition GTX 680 reports 5.0 GT/s in slot 1 with Link Width x8

 

[ASentientBot]

Somebody needs to add a link to the inversed colors glitch fix on the wikipost.

 

[dosdude1]

A new issue with the Mojave GM installed on my mini 5,2. Sleep doesn't work. Doesn't sleep at the programmed time, even stranger is I can't force it to sleep, I.E. click on the , select sleep and nothing happens.

Okay wizards, how do I fix this?

If it's the model with an AMD Radeon HD 6xxx series GPU, sleep mode will not work due to lack of graphics acceleration.
[doublepost=1536896915][/doublepost]

Somebody needs to add a link to the inversed colors glitch fix on the wikipost.

Nah, I'm going to revise the Legacy Video Card Patch in the post-install tool to not install by default on systems with the Radeon HD 5xxx and 6xxx series GPUs. That will make that issue not happen. In fact, I'd highly advise that you DON'T run Mojave on systems with these GPUs, simply due to the extremely poor performance, the system running much hotter than normal, and the lack of features such as sleep mode.

 

[pkouame]

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.

While reduceTransparency is a legitimate workaround for the ugly grey menu bar, I find that it has too broad a system impact: effectively zapping transparency all over the place - especially the dock etc. You're left with a dock and notification sidebar panel (for example) that are barely visually functional. At least for my poor eyes...

I found a software switch in HIToolbox that simply turns menu bar transparency OFF. Unfortunately it is not available as a setting, environment variable or default - the equivalent of an HIMenuBarOpaque application plist setting would have been really nice, but Apple doesn't always make this easy.

Anyway, it's a one byte patch that easily (and harmlessly) flattens the menu bar to white or black (Light or Dark mode) but preserves all other functional transparencies. See below:


PM me if you're interested in the details or want to test the HIToolbox DB11 patch. At least it takes care of the grey menu bar (without affecting general transparency/vibrancy) which in my opinion is the most egregious aspect of the Light mode bug.

As far as AppKit and the ugly sidebars (in Finder and other apps), swapping Light mode processing for Dark mode is still an option (per my previous screenshots) but has some side effects I am not pleased with: dark window bars and obscured function bars in some apps. I've found that these "modes" are not consistently implemented - for example while my "Hybrid" mode looks good for the Finder AppStore and Xcode, News and iTunes look a little quirky. Still work in progress.

 

[TimothyR734]

While reduceTransparency is a legitimate workaround for the ugly grey menu bar, I find that it has too broad a system impact: effectively zapping transparency all over the place - especially the dock etc. You're left with a dock and notification sidebar panel (for example) that are barely visually functional. At least for my poor eyes...

I found a software switch in HIToolbox that simply turns menu bar transparency OFF. Unfortunately it is not available as a setting, environment variable or default - the equivalent of an HIMenuBarOpaque application plist setting would have been really nice, but Apple doesn't always make this easy.

Anyway, it's a one byte patch that easily (and harmlessly) flattens the menu bar to white or black (Light or Dark mode) but preserves all other functional transparencies. See below:
View attachment 781474 View attachment 781475

PM me if you're interested in the details or want to test the HIToolbox DB11 patch. At least it takes care of the grey menu bar (without affecting general transparency/vibrancy) which in my opinion is the most egregious aspect of the Light mode bug.

As far as AppKit and the ugly sidebars (in Finder and other apps), swapping Light mode processing for Dark mode is still an option (per my previous screenshots) but has some side effects I am not pleased with: dark window bars and obscured function bars in some apps. I've found that these "modes" are not consistently implemented - for example while my "Hybrid" mode looks good for the Finder AppStore and Xcode, News and iTunes look a little quirky. Still work in progress.

I am in it looks awesome

 

[Martyimac]

If it's the model with an AMD Radeon HD 6xxx series GPU, sleep mode will not work due to lack of graphics acceleration.
[doublepost=1536896915][/doublepost]
Nah, I'm going to revise the Legacy Video Card Patch in the post-install tool to not install by default on systems with the Radeon HD 5xxx and 6xxx series GPUs. That will make that issue not happen. In fact, I'd highly advise that you DON'T run Mojave on systems with these GPUs, simply due to the extremely poor performance, the system running much hotter than normal, and the lack of features such as sleep mode.

Thanks for the info. This was more a "can I do it" project than anything else. Once the official Mojave releases, assuming it wont upgrade or whatever, I will probably retire it.

One question left though, why did sleep work before the final GM release?

 

[dosdude1]

Thanks for the info. This was more a "can I do it" project than anything else. Once the official Mojave releases, assuming it wont upgrade or whatever, I will probably retire it.

One question left though, why did sleep work before the final GM release?

Because that's probably before you modified the system to get rid of the inverted colors, in which instance you removed some of the graphics kexts.

 

[oscarodas]

While reduceTransparency is a legitimate workaround for the ugly grey menu bar, I find that it has too broad a system impact: effectively zapping transparency all over the place - especially the dock etc. You're left with a dock and notification sidebar panel (for example) that are barely visually functional. At least for my poor eyes...

I found a software switch in HIToolbox that simply turns menu bar transparency OFF. Unfortunately it is not available as a setting, environment variable or default - the equivalent of an HIMenuBarOpaque application plist setting would have been really nice, but Apple doesn't always make this easy.

Anyway, it's a one byte patch that easily (and harmlessly) flattens the menu bar to white or black (Light or Dark mode) but preserves all other functional transparencies. See below:
View attachment 781474 View attachment 781475

PM me if you're interested in the details or want to test the HIToolbox DB11 patch. At least it takes care of the grey menu bar (without affecting general transparency/vibrancy) which in my opinion is the most egregious aspect of the Light mode bug.

As far as AppKit and the ugly sidebars (in Finder and other apps), swapping Light mode processing for Dark mode is still an option (per my previous screenshots) but has some side effects I am not pleased with: dark window bars and obscured function bars in some apps. I've found that these "modes" are not consistently implemented - for example while my "Hybrid" mode looks good for the Finder AppStore and Xcode, News and iTunes look a little quirky. Still work in progress.

Yes, I'm interested in testing your patch, thank you.

 

[Balaur]

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.

On my iMAc 10,1 running DP11 I have no trouble with automatic hiding of the dock.

 

[jackluke]

While reduceTransparency is a legitimate workaround for the ugly grey menu bar, I find that it has too broad a system impact: effectively zapping transparency all over the place - especially the dock etc. You're left with a dock and notification sidebar panel (for example) that are barely visually functional. At least for my poor eyes...

I found a software switch in HIToolbox that simply turns menu bar transparency OFF. Unfortunately it is not available as a setting, environment variable or default - the equivalent of an HIMenuBarOpaque application plist setting would have been really nice, but Apple doesn't always make this easy.

Anyway, it's a one byte patch that easily (and harmlessly) flattens the menu bar to white or black (Light or Dark mode) but preserves all other functional transparencies. See below:
View attachment 781474 View attachment 781475

PM me if you're interested in the details or want to test the HIToolbox DB11 patch. At least it takes care of the grey menu bar (without affecting general transparency/vibrancy) which in my opinion is the most egregious aspect of the Light mode bug.

As far as AppKit and the ugly sidebars (in Finder and other apps), swapping Light mode processing for Dark mode is still an option (per my previous screenshots) but has some side effects I am not pleased with: dark window bars and obscured function bars in some apps. I've found that these "modes" are not consistently implemented - for example while my "Hybrid" mode looks good for the Finder AppStore and Xcode, News and iTunes look a little quirky. Still work in progress.

I would be interested (much more in the Appkit.framework) if only I was not still on Mojave beta 9, and I won't update until the 9/24, a bit lazy, so I'll wait you optimize your patch, anyway I thought your "hybrid light mode" turned the "sidebars windows" into a solid white, while from your "light mode" picture they are still dark grey, moreover I guess your previous patch inherited also the "dark mode" transparencies from Appkit into Dock and Notification Center for the Mojave light mode but from your "light mode" screenshot I can't notice that.

I can assure my "hybrid reduce transparency" keeps all the stock "light mode" transparencies for Dock and Notification Center, even switching the "dark mode" its stock ones are kept, and until a restart or logout they will work fine.

Please re-check I've added some screenshots: Mojave hybrid reduce transparency for light mode

edit:
It seems to work even after the sleep lock screen, just don't switch between users and it still stay on hybrid transparency.

 

[webg3]

jackluke / pkouame

Thanks, working for me.

The only thing that interests me is the transparent Dock and joking with its solution I got something interesting too, instead of finishing the Finder I did the reverse process.

Enable transparency reduction in the System Preferences.

At the terminal:

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

killall Finder (only on Darkmode)


and I had an excellent result.

the lateral corners were removed (Spotlight).

[doublepost=1536919348][/doublepost]

[doublepost=1536920972][/doublepost]

 

[jackluke]

jackluke / pkouame

Thanks, working for me.

The only thing that interests me is the transparent Dock and joking with its solution I got something interesting too, instead of finishing the Finder I did the reverse process.

I enabled the reduction of transparency, I made the command:

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

killall Finder (only on Darkmode)


and I had an excellent result.

those lateral corners are gone.
[doublepost=1536919348][/doublepost]View attachment 781600 View attachment 781601
[doublepost=1536920972][/doublepost]

Yes, it makes sense, you did the opposite reasoning, but first applying my Terminal reduceTransparency true is mandatory to make those following commands to work properly, otherwise Finder won't be affected by full opacity. Unless you applied first the global reduce transparency from the Accessibility prefpane.

Agree on killall Finder (only on Darkmode), to bring back the Finder transparency in dark mode, but if you use the mojavehld.command just type the choice number 2, it will be there again with the stock dark mode (and light mode too, they can't be split).

Anyway I don't understand yours "lateral corners", I mean I don't have them at all.

 

[webg3]

Anyway I don't understand yours "lateral corners", I mean I don't have them at all.

This It

Applied first the global reduce transparency from the Accessibility prefpane.

Yes.

 

[brkr1]

Thanks for the info. This was more a "can I do it" project than anything else. Once the official Mojave releases, assuming it wont upgrade or whatever, I will probably retire it.

One question left though, why did sleep work before the final GM release?

What you mean by saying "it wont upgrade" ?

 

[jackluke]

This It

Applied first the global reduce transparency from the Accessibility prefpane.

Yes.

Ok, I've re-checked, Spotlight app manages itself its own blur shadow, so for those used my method, just type from Terminal to obtain transparent shadow under Spotlight search:

killall Spotlight

I'll update my previous script.

edit:
fixed on the previous post, thanks for pointing out the "Spotlight" shadow border issue.

 

[webg3]

Ok, I've re-checked, Spotlight app manages itself its own blur shadow, so for those used my method, just type from Terminal to obtain transparent shadow under Spotlight search:

killall Spotlight

I'll update my previous script.

edit:
fixed on the previous post, thanks for pointing out the "Spotlight" shadow border issue.

@pkouame please see this also in its hybrid mode.