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.
Since nobody replied, I will. Steam's working perfectly fine. I dunno about Counterstrike but Portal 2 works fine and since it's the same engine, I imagine you'll have no trouble.
I'll second that. Not only does it work, but it is smoother than HSierra for some OpenGL games. I recently tested an old classic Homeworld : DOK and was pleasantly surprised.

So I went back to my benchmarks (buried earlier on this forum) : Cinebench OpenGL scores are consisently higher and, since dp3, performance has roughly increased by 5 frames per second. Not bad.
 
I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave

This has been an issue since 10.13. I have a 660 in my hackintosh and I’ve been stuck on 10.12.6 because of this issue. I was hoping for a fix in Mojave but I’m guessing since there’s been no improvement in the past year that Apple isn’t going to fix this. There’s been a thread about it on the TonyMac forum since High Sierra came out, and it seems like the cause has been figured out (VRAM leak) but nobody has figured out a solution.
 
I dont know if any one has come across this or not, but I'll ask anyways

I have 2 2008 Mac Pros both running Mojave on my secondary drives, everything works fine except I'm getting GUI artifacting and glitches with one of my GPUs, GTX 660 2gb. The other Mac Pro's GPU which is a GTX 760 4gb works perfectly, Prior to the 760 4gb I had a different 660 2gb in that machine with the same issue. So now I know that theres nothing wrong with both of my 660s and the problem is with Mojave.

According to dosdude GUI artifacting and glitches should only happen with NonMetal Fermi based or prior GPUs, so I dont know why I'm getting this with Kepler Cards on Mojave
[doublepost=1535048690][/doublepost]

Im still on Developer Preview 4, dose any one know if latter versions of Mojave Beta fixed this? The glitches are not present all the time, they start on their own but when I restart the machine they are fixed temporarily but start up again at a later time

The 660/660 ti and the 650 ti boost have been broken since high sierra. The problem is that the VRAM fills up. There is no solution for this at this time.
 
No I didn't bug reported to them the grey finder menu bar in light mode. I meant I never encountered that on supported Mac or if noticed just for less than one sec, no material time to take a snapshot.

If I'm not wrong your menu bar issue occurred on MacBook Pro mid 2012 with IntelHD4000 and that was your friend's laptop, anyway we could have much support if someone will report the menu bar grey bug from a Mac Pro 2010 or 2012 with an unsupported Metal Video Card Nvidia or IntelHD3000 or AMD/ATI with QE/CI at least.

I think if they make the Light Finder menu bar much closer to white, it could work for anyone, with enough luck. Or in worst case we'd have a whiter non-transparent Finder menu bar, but at least we have translucent dock and other transparencies somewhere.

Here's a comparison screen shot with Finder menu bar in light mode between my supported 2012 13" MBP vs 2010 Mid MPB 13".
darker gray color vs normal white color for 2012 MBP.
 

Attachments

  • 2010 MBP.png
    2010 MBP.png
    782.2 KB · Views: 222
  • 2012 MBP.png
    2012 MBP.png
    868.1 KB · Views: 209
I was telling my friend something similar the other day.





I reckon if the T2 is required, then it would be about 5-7 years after the last non-T2 is sold (if Apple still decides when to not support a Mac based on its obsolete/vintage status.


totally agree.
I think all Macs without a T2 chip will be updated to include one or be removed from Apple’s lineup within the next two years, but we’ll see.


i’d say 6 months
 
  • Like
Reactions: TimothyR734
Another question about installing a new SSD. Is there any benefit to replace the optical drive with a second SSD? It’s around the same price to get the doubler along with the SSD, and I never considered this path. Would it be better to have both the HDD and the SSD, or just replace the HDD with the SSD sand use a USB-SATA converter?
 
The elephant in the room is the departure from Intel CPUs.
Oh yeah. Forgot that one. Geez, I remember the mess during the PPC to Intel conversion. Being stuck with "fat" binaries for years. Not looking forward to it at all, but yes I believe it's inevitable. ARM just published their roadmap and it promises a return to Moore's Law faster and cheaper than Intel can compete with. We all know they have macOS running on A1X chips in research labs. If Intel stumbles one more time on 10nano chip technology, it's over...
[doublepost=1535089715][/doublepost]
Another question about installing a new SSD. Is there any benefit to replace the optical drive with a second SSD? It’s around the same price to get the doubler along with the SSD, and I never considered this path. Would it be better to have both the HDD and the SSD, or just replace the HDD with the SSD sand use a USB-SATA converter?
I would opt for replacing the optical with SSD. It's the last upgrade I am considering on my mbp 5.3. Unless of course you have an extra HDD gathering dust...
 
Oh yeah. Forgot that one. Geez, I remember the mess during the PPC to Intel conversion. Being stuck with "fat" binaries for years. Not looking forward to it at all, but yes I believe it's inevitable. ARM just published their roadmap and it promises a return to Moore's Law faster and cheaper than Intel can compete with. We all know they have macOS running on A1X chips in research labs. If Intel stumbles one more time on 10nano chip technology, it's over...
And your forgot Murphy's law too :)
 
Last edited:
  • Like
Reactions: olad and jackluke
Strange! :O This Kepler graphics should to be natively supported under Mojave.

1st, plz make sure that nvAccelerator is properly loaded //Terminal: $
Code:
kextstat | egrep "GeForce|NVD|IOAccel"

2nd, rebuild prelinkedkernel, kernelcache && dyld.. //with SIP: Disabled.
(no graphics acceleration enabled w/o these, sometimes they are not rebuilt correctly for unknown reason)
Code:
- Boot to Recovery, Terminal: csrutil disable
- Boot to Desktop, Terminal: sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force
- Re enable SIP within Recovery environment: csrutil enable

3rd, the last.. is Apple bugs. No idea with this one; FYi I got no fully graphics acceleration with my Fermi Graphics (GF) since 10.14 Beta 5: but only CI (Core Imaging) without Quatz Extreme (QE), native "GeForce - NVDAGF100Hal - NVDAResman - IOAccelerator" all are properly loaded though.

#EDIT: Also try using more recents or even latest Mojave Beta release.

from memory (while pulling x3000 out of the kextcache) I have seen those geForce kexts causing error messages in kextcache
 
  • Like
Reactions: TimothyR734
I don't have Xcode installed on my MacBook yet but maybe something useful in these
 

Attachments

  • com.apple.colorsync.useragent.plist.zip
    734 bytes · Views: 160
  • com.apple.WindowServer.plist.zip
    555 bytes · Views: 141
Here's my issue with OWC. When they knew full well that a product they were selling had a firmware issue, rather than stepping-up and offering immediate replacement with SSDs known to be OK, they kept perhaps tens of thousands of customers (some of whom are Apple employees and devs) hanging for months until a firmware fix was cobbled together. If a company treats its customers that way, do you REALLY want to do business with them in case you might need assistance in the future? If you do, go ahead, but I'll spend my $ somewhere else, because I think treating customers with disdain should have sales consequences.
Any of the Samsung 850, 860 EVO range will do the job at the same or a lower price.

I'm using a "Mercury Electra 3G" in my MacBook7,1 with zero issues.
 
made another find regarding HD5xxx and HD6xxx and legacy video:

Mac Pro 3.1 and a HD5770

when legacy video patch is installed then I have seen that

AMDRadeonX3000.kext is loaded

wtf !?

so disabling AMDRadeonX3000.kext just by renaming it to AMDRadeonX3000.kex

and

sudo kextcache -I /

and rebooting

cured the trail glitches without re-installing

doesn't bring OpenGL and such, but better disabling x3000 than a re-install :)

Of course, renaming a .kext into something else corresponds to unload the kext, involving auto-rebuilding the kextcache and prelinkedkernel at the next reboot, as known you don't have trail glitches cause you actually don't have both QE and CI acceleration but only a standard GPU kext loaded, exactly like the one used into the USB Mojave Installer or Recovery HD.
 
  • Like
Reactions: TimothyR734
Here's my issue with OWC. When they knew full well that a product they were selling had a firmware issue, rather than stepping-up and offering immediate replacement with SSDs known to be OK, they kept perhaps tens of thousands of customers (some of whom are Apple employees and devs) hanging for months until a firmware fix was cobbled together. If a company treats its customers that way, do you REALLY want to do business with them in case you might need assistance in the future? If you do, go ahead, but I'll spend my $ somewhere else, because I think treating customers with disdain should have sales consequences.
Any of the Samsung 850, 860 EVO range will do the job at the same or a lower price.

Fair enough. Just cause I haven't had issues yet doesn't mean they're necessarily the best option. Oh well, I just hope mine keeps working smoothly.
 
I'm looking to flash my late-2013 rMBP bootrom /w Samsung Evo 970 with the NVMe driver to get it running non-Apple SSDs with hibernate working correctly; from various threads it seems the file one needs to use is MBP114_0182_B00.fd. I've already used dosdude1's romtool to dump my bootrom. My question is two-fold:

1. Has there been a bootrom in Mojave that updates my MBP? Currently its sitting on MBP111.0146.B00 and I'm on the latest Mojave DP (18A371a). This bootrom was latest as off High Sierra's 10.13.6 if I recall; subsequent bootrom updates may have been missed as they do not get installed unless you have an Apple SSD (which I do; just not currently installed atm)

2. Bar buying a J6100 adaptor from South Korea and a CH341a programmer; are there any other ways to flash a modified bootrom to my MacBook?

Thanks :-D
 
  • Like
Reactions: TimothyR734
I don't think if I understand about the Transparency issue, I did install Windows 10 on my iMac and was able to get the Glass Theme using an app called Glass8 making everything inside parallels transparent, how come there is not a similar app for Mojave?
 
  • Like
Reactions: TimothyR734
Hello everyone, I've got a problem while installing Mojave with the latest Mojave patcher. MacOS post install tool doesn't work on my MB5,1. If I check it manually then it just crashes.
 

Attachments

  • 5YDJN818374.jpg
    5YDJN818374.jpg
    179.7 KB · Views: 206
  • Like
Reactions: TimothyR734
So I have an update on the 5,1 I bricked flashing it .The good news is it lives !! I ordered a cheap eeprom reader and soic clip off amazon ( £17 ) but it was interesting experience. I practiced on mx
chip and detected and programmed the chip very quickly . The stt chip that’s on my board was different story . I had to tell it which chip ( I know it’s a cheap reader ) and after much messing around and things such as writing timeouts i managed to erase what was on eeprom and wrote my backup to it . Took nearly 5 hours !! But hey the machine now boots again so I am happy out .

I just thought I’d share in case anyone else is in the same boat . Thanks again all for the patience and suggestions
[doublepost=1535104636][/doublepost]
Hello everyone, I've got a problem while installing Mojave with the latest Mojave patcher. MacOS post install tool doesn't work on my MB5,1. If I check it manually then it just crashes.
Have you tried the making the installer or a different usb . I had no problems on mine
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.