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.
ctaylora1231

Thanks guys, having zero success with it, (tried twice) as I posted earlier, KP's with external 800 FW, I guess I'm going to have to suck it up & install to internal SSD. It is a test bed, 2010 iMac.
I feel you on Thunderbolt devices, expensive, to say the least, current iMac has Thunderbolt, but using Firewire 800.

I loved thunderbolt when it came out and I used to take small thunderbolt external drives and put larger SSDs in them and sell them. At my work, I tried getting our company to buy some (not from me but new ones online) for doing backups and was quickly vetoed for cheaper USB 3.0 portable drives. The Western Digital drives we got are reliable. But they are proprietary and when one died you could not just fill it with an SSD. USB 3.0 on portable self powered drives to me are slow. FW800 in my opinion is faster. Thunderbolt in Target disk mode is pretty quick too, but not as fast as copying to an internal 2015 or newer MacBook Pro SSD to itself which is really odd. It flies. I noticed this when duplicating some VMs the other day.
[doublepost=1531361017][/doublepost]I'd like to get my hands on an old ModBook. Can't find them anywhere. And the new ones under a new company are expensive.
 
  • Like
Reactions: Luckygreek
Installed Mojave Patcher from Developer Beta 3 on MacBook 5,5. 6GB RAM, NVIDIA GeForce 9400M 256GB GPU.

Runs very fast. This MacBookPro got crushed and has a broken screen and it us mainly use for my MAME system. Thanks for Breathing new life into this dinosaur.

Super responsive. Metal is over rated. Only place you can notice it being slower is the Shell 3d screensaver which is slightly choppy, but it's not bad. It's much better than other AMD patches I have seen for the 7970 for HS.

News App runs, Video runs in the news app.

Screen Shot 2018-07-11 at 10.38.03 PM.png

Screen Shot 2018-07-11 at 10.41.11 PM.png

Weird the screenshot in the left sidebar is always off, the app shows it right. Odd.

This is a very good "build" and "patch". Highly recommended. I have another MacBookPro 13" in mint condition. it will get upgraded next. And looks like I will have putting my 8800GT card back in to get a MacPro 2008 the gift of MoJavé. Moe Jaa Vay. :)

Please put something in dosdude1's tip jar today!
[doublepost=1531364174][/doublepost]
I have not yet and I'm semi-busy right now. Anybody else want to test this?

I can give this a shot.
 
There is no "AppleUSBVideoSupport.kext" inside IOUSBFamily.kext.

As anyone replaced IOVideoFamily?
[doublepost=1531367275][/doublepost]On the MacBookPro 5,5. I noticed that at first clamshell mode does not work, but here is how I got it working and it may take less steps than this.

Connect external display. Reboot. put machine in clamshell mode before rebooting. It will try to use clamshell mode but after the 2nd stage black screen boot, it will come out of it. After the machine goes to sleep, wake it up in while still in clamshell mode and wallah! You should be only using the external display now. This is handy if you have a beat up MacBookPro and don't want to use the 2nd screen or if you are like me and prefer clamshell mode.

Mojave has just become my system of choice on a Core2Duo. Great work.

--

Nvidia released 10.13.6 web drivers the same day. Let's hope they keep up that track record with Mojave. Too bad AMD and Intel does not release more generic drivers separate from MacOS. Nvidia is gonna be killin' it this Fall.

---

XArcade MAME tank stick works on Mojave on MacBookPro 5,5.
 
Last edited:
  • Like
Reactions: ASentientBot
On a 13" machine, yes. On a 15" or 17" machine, only if you have the AMD GPU disabled.

Do you think once Mojave goes live, a fix will come ? I think I just may get a 2012 board non-retina and take out the 2011 board, though my AMD chip is working just fine.
 
Do you think once Mojave goes live, a fix will come ? I think I just may get a 2012 board non-retina and take out the 2011 board, though my AMD chip is working just fine.

Reporting another successful story MacBook pro mid 2010 13" base model
 

Attachments

  • 07FFD5CB-C9DC-4CC0-BA4B-4B4E5AA0368E.jpeg
    07FFD5CB-C9DC-4CC0-BA4B-4B4E5AA0368E.jpeg
    4.4 MB · Views: 426
Nvidia released 10.13.6 web drivers the same day. Let's hope they keep up that track record with Mojave. Too bad AMD and Intel does not release more generic drivers separate from MacOS. Nvidia is gonna be killin' it this Fall.
If the quality of web drivers impact sales… How much years long that blackboxes appears on Finder filenames? Dual cards not working since at least December.

Let's forget Apple supporting native decode/encoding on Mojave with AMD GCN3-UVD6 cards. But bashing Nvidia web drivers is for another thread. =)
 
Last edited:
Installed on my MacBook Pro 2010 15 inch. Works great. Gfxcardstatus (to switch between Nvidia and iGPU) + contuinity/handoff works perfect. You guys are geniuses :p
 
Or anywhere in /S*/L*/E* for that matter, just checked myself. What were you referring to @parrotgeek1 ?

IOVideoFamily, no dice. But I did notice the camera turns on so USB must be working. I think the part that may be missing is AppleCameraInterface.kext

Also note: /Library/Plug-ins/

/DAL/
/FCP-DAL/

AppleCamera.plugin
 
Last edited:
  • Like
Reactions: parrotgeek1
Wait, you know we already have a working fix right? @parrotgeek1 just suggested this apparently nonexistent file as a "cleaner solution".

Whoops. Rewinding.

Ok.. found your fix in the thread. I'll try it on the MBP 5,5

thanks.

"As well as replacing IOUSBHostFamily.kext, you need to also replace IOUSBFamily.kext."

--

BTW, I thought clamshell mode was working after sleep. Just the backlight stays off but it does output to the MBP display in clamshell mode. Not a huge deal and its better than not work at all, meaning losing both displays in clamshell. Will see what happens to clamshell mode after the cam is back.
 
Last edited:
Whoops. Rewinding.

Ok.. found your fix in the thread. I'll try it on the MBP 5,5

thanks.

"As well as replacing IOUSBHostFamily.kext, you need to also replace IOUSBFamily.kext."

--

BTW, I thought clamshell mode was working after sleep. Just the backlight stays off but it does output to the MBP display in clamshell mode. Not a huge deal and its better than not work at all, meaning losing both displays in clamshell. Will see what happens to clamshell mode after the cam is back.

Don't think I have a working monitor to test clamshell mode, sorry. Best of luck, maybe I can get ahold of one to do some testing in a short while.
 
BTW, I have a legacy Firewire 400 / USB 2 drive that has two light up red led light sabers and is decorated under clear plastic with images of Darth Vader. I bought it a garage sale 10 years ago and it still works. I am thinking about doing a give away for it. The dark mode of Mojave really fits the external Vader drive. (IM me if interested, so I don't junk up this thread).
 
RAM is SUPPOSED to be fully utilized under Mac OS X 10.9 Mavericks and later. It's the memory pressure you need to worry about. If that's low/green, then no need to worry about RAM. You can see in this picture almost all my 16GB is being used, but memory pressure is very low.

View attachment 770165

Related to RAM, on the Mac Pro 3,1 would Mojave handle the actual Max at 64GB better vs prior versions of the OS? I recall that 56GB was tested/noted on Sierra/High Sierra as optimum before experiencing a performance hit. Referencing from this thread: https://forums.macrumors.com/thread...e-48-gb-fast-disks-why.1940030/#post-22338450
 
Wait, you know we already have a working fix right? @parrotgeek1 just suggested this apparently nonexistent file as a "cleaner solution".

I've confirmed adding IOUSBFamily from 10.13.6 works. The fix might be the Composite Kext that's inside.
[doublepost=1531372037][/doublepost]
Related to RAM, on the Mac Pro 3,1 would Mojave handle the actual Max at 64GB better vs prior versions of the OS? I recall that 56GB was tested/noted on Sierra/High Sierra as optimum before experiencing a performance hit. Referencing from this thread: https://forums.macrumors.com/thread...e-48-gb-fast-disks-why.1940030/#post-22338450

I currently am using 48GB in High Sierra on a Eight Core 3,1. And it flies like a rocket ship on High Sierra. Will be taking my 14GB QuadCore to Mojave with an older video card soon.

Now from what I read the 8 core version is supposed to handle 64GB and the Quad core is supposed to handle 32GB. However, I have run more than 32GB on my Quad Core in HS (took it to 40GB).

I think 64GB will work on Mojave, but it may also depend on how many Cores you have.

Apple originally only certified the 2008s to run 32GB.

I do think Mojave will handle whatever you throw at it and these theoretical limits may just be theoretical.

I can run 48GB of RAM in Snow Leopard and it can run in 64-bit mode. And today all of Apple's stuff is 64-bit. So quite possibly you might be able to get all the way to 64GB which would be nice and all your RAM chips would be paired exactly the same all the way through and that should give you a performance boost as well.

The MacPro 5,1's can handle up to 128GB and is supported. And now those machines are going for much more than they used to mostly because of the Mojave announcement. I've seen them go from 350 to 1000-1500 and the fixed up ones are around 2500-3000 which is crazy.

The Mac Pro 2008's are starting to gain value from 50-80 bucks to 300-400 and these are base quad and eight core systems.

The cool thing is we now have systems that can run old software (Snow Leoaprd / PowerPC) and run the latest stuff with Mojave using the same architecture. We've got some great flexibility.

BTW, the the MBP5,5 I notice Mojave has the correct pictures of the laptop in its about screen. It also goes to the right RAM upgrade pages on Apple's website. I am pretty sure at one point Apple was testing Mojave on older systems internally and up the food chain they drew the new line in the sand (Marketing). I believe the same thing happened to High Sierra.

Not sure if any of this answers your question. I am going to 64GB later this year (probably when Mojave gets released).

One thing is for certain. Our RAM may be slower than the newer machines, but we can get more than most new machines. And unless you are using a RAM disk, you'll never know the difference in real world speed between our legacy boxes to the new systems out today. I may be selling my Mac mini 2012 soon along with its Thunderbolt Display. I strongly feel my 2008 has surpassed the Quad Core mini and it used to be my workhorse. But now with 4K ASUS gaming display on a 2008 with a card that can handle 4K at 60Hz at native or scaled res', its become my go to box.
 
Last edited:
  • Like
Reactions: MP39
I've confirmed adding IOUSBFamily from 10.13.6 works. The fix might be the Composite Kext that's inside.
[doublepost=1531372037][/doublepost]

I currently am using 48GB in High Sierra on a Eight Core 3,1.

Now from what I read the 8 core version is supposed to handle 64GB and the Quad core is supposed to handle 32GB. But have run more than 32GB on my Quad Core in HS.

I think 64GB will work on Mojave, but it may also depend on how many Cores you have.

Apple originally only certified the 2008s to run 32GB.

I do think Mojave will handle whatever you throw at it and these theoretical limits may just be theoretical.

Yes, you are correct with the info above. I have the 2 x Quad Core 3.2GHz 8-Core model. Did you read the thread I previously linked? It's not so much that it doesn't recognize up to 64GB, but more around how it handles the additional memory with relation to performance. You are correct that Apple's official max for that system was 32GB.

That is what I am trying to isolate on whether anything has changed on that recommendation to not exceed 56GB to maximize performance and if that is now any different with the handling under Mojave for the Mac Pro 8 Core 3.2GHz.
 
Potential Fix for UI Glitches:
If the transparency related UI glitches are caused by a lack of correct drivers to render it then perhaps it would to possible to combine the drivers from Mojave and High Sierra in order to get proper rendering. Just an idea.
 
I want to share an interesting experiment, referred especially to Nvidia 320M owners.

When I observed the IOAccelerator framework behavior, I kept a backup of the one present in Mojave beta 1.

Comparing them I noticed that have mainly different sizes:

IOAccelerator unix exe from Mojave Beta 1 = 70 KB
IOAccelerator unix exe from Mojave Beta 2 = 158 KB

Well I have tried to replace and I noticed an overall better experience, no artifacts, no minimum glitches, and major reactivity in windows, folders and everything else.

Moreover a better characters contrast and transparency effects, bright colors, FaceTime is flowing better.

Sometimes I got some Finder folders autoclose, instead using the previous IOAccelerator from Mojave Beta 1, Finder is more quick and fluid and above all no more unwanted autoclosing windows.

I would suggest to try it, making a backup of your previous (more recent) one.


Here are the steps:

Locate your Mojave path: /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/
- Replace inside this subfolder the IOAccelerator unix exe with the one I have attached.

Trust me you will notice significative improvements, your C2D behaves like an Intel i5 Dual Core. Try to believe.
I just tried this, and I don't see any difference really. Still the graphical glitches on corners of windows, horrible black blocks in the Dashboard, etc.

What's others' experience with this? @jackluke, what exactly did you notice being better?
[doublepost=1531377017][/doublepost]Super small and not particularly relevant thing, but anybody else notice open -R /path/to/folder (reveal in Finder) not working in Mojave?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.