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.
Hi @jackluke - an obvious question I forgot to ask: did your camera work on HS (13.5 or 6) as a "supported" machine"? I'm not sure when your mbp 7,1 went "unsupported". Then, it would make sense to experiment with those kexts.

Of course it worked, my macbook is completely supported until High Sierra 10.13.6

Oh my mistake, you're right your machine supports until El Capitan, so my solution could won't work for these machine, even if similar, instead why don't you try to replace those IOUSBHostFamily.kext IOUSBFamily.kext from El Capitan? Maybe in this way iSight could work for you.
 
Last edited:
That file doesn't need chown/chmod since it has already Mojave signature by apple, so in this case a simple copy works.
Page 88 at bottom.

I'm 90% sure the kexts still need to have correct permissions (root:wheel, 755)

To rebuild prelinkedkernel:
sudo bash
<enter password>
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -i /
 
Had great success installing Mojave Public Beta 1 in the above machine with macOS Mojave Patcher; then downloaded latest patcher and installed Public Beta 2 (no joy reinstalling over PB1 -- massive installer errors :( -- so had to wipe partition and install again from scratch, then joy). After booting the new Mojave Beta, I had a similar experience to Larsvonhier (Msg #2799) with the Patch Updater popping up as soon as I booted into the new Public Beta 2, saying I should update the Legacy Video Card patch.

Unlike Larsvonhier's experience, the patch updated successfully (although it did take quite a long time, maybe 10 minutes) -- but the results were not pleasing. Having had no video problems (in Dark Mode) using the previous Legacy Video Card patch, in fact no problems at all, with zero kernel panics, this new Legacy Video Card patch (version 3, I believe) resulted in repeated spinning pinwheels for several seconds when changing focus between various running programs, or between the desktop and active programs, as well as video glitches, such as various menu and tab bar elements going dark (i.e., greyed out) in active windows, until I would click on the desktop and, then, back on the active window again. There was also a general slowdown in the responsiveness of the system, compared to when using the previous Legacy Video Card patch.

In other words, I don't think this latest Legacy Video Card patch is a good match for my mid-2011 Mac mini running on an Intel HD 3000 GPU. (I rebooted into the installer USB and re-ran the Post Install routine for the previous Legacy Video Card patch, booted back into Mojave Public Beta 2, and now it is running perfectly.) But now, of course, the Patch Updater pops up again, urging me to install the latest Legacy Video Card update. I wish there were some way to tell the internal Patch Updater that I do not wish to install the new Legacy Video Card patch update and have it remember my choice (some sort of "hide update" option), so it would stop popping up all the time. I also wish too here were a way to run the Patch Updater and see the list of currently installed patches -- which is currently only possible when there are no available updates showing.

If you have are installing a full installation, why are you installing over another installation? Backup any important data and erase the disk first. Then do a clean install. You can also partition a disk with a second partition and put the newest install there and later get rid of the old partition or just have multiple disks or partitions to test with. I use about 10 partitions on my Mac Pro with 6 drives/ssds and I do just 1-2 on my Mac Books, but by then I usually know what I have to work with because I did so much testing on the Mac Pro.
 
Of course it worked, my macbook is completely supported until High Sierra 10.13.6

Oh my mistake, you're right your machine supports until El Capitan, so my solution could won't work for these machine, even if similar, instead why don't you try to replace those IOUSBHostFamily.kext IOUSBFamily.kext from El Capitan?
Ahhh! - Now it make senses why you can swap in HS kexts.

I think we poor mbp 5.x unsupported owners need to dig further down the release chain for compatible ones. I will pull up some old extensions and experiment. Thanks.
 
If you have are installing a full installation, why are you installing over another installation? Backup any important data and erase the disk first. Then do a clean install.

You don’t have to do a clean install. At least you shouldn’t have to.
[doublepost=1531682005][/doublepost]
Ahhh! - Now it make senses why you can swap in HS kexts.

I think we poor mbp 5.x unsupported owners need to dig further down the release chain for compatible ones. I will pull up some old extensions and experiment. Thanks.

You should be able to find compatible ones from El Capitan.
 
  • Like
Reactions: Larsvonhier
Hello guys,
I just wanted to give you an update. The issue that the system becomes painfully slow after a certain period of time (1 hour usually) is really gone now since I applied b10 Patcher. I'm really impressed how well Mojave works on my MacBook Mid 2010 (it also boots very quickly). I wonder why Apple decided to stop supporting our old machines but I guess they don't have any interest in keeping those old Macs alive since it won't get them any money. So big thanks to everyone who contributed to getting this macOS-Version up and running (especially dosdude1 and ASentientBot).

My MacBook has been on now for about 8 hours. I did some video converting, browsing the web and video playback. The swapping of kexts in order to get the iSight camera to work didn't affect performance nor stability of the OS. In other words, I didn't notice any side effects as a result of kexts swapping. I'm just hoping this will be the case with future versions of Mojave.


Apply typically supports machines with OS updates for about 7-10 years. That's really not bad considering. Could you imagine a car company sending you updates to your card 7-10 years later? It's definitely not because they aren't making any money at all, I can still use the App Store and iTunes on unsupported OSes. Last time I used my iMac G4, I was able to access the iTunes Store. That's pretty crazy.
 
  • Like
Reactions: Larsvonhier
Here's my observations running Mojave for the last 2 days on 2010 iMac, internal SSD, no kp's to date, some artifacts in Finder Windows, ie move an item and artifacts left behind of item, a little jerky moving windows around, to be expected without full graphics acceleration, boots fast, most 64bit apps are working well, aside from Google Chrome, opens but can't get to any sites, some 32bit will not open, open but quit, videos from YouTube play with no slowdown or fragments/artifacts, the system does NOT slow down during the course of the day. I've been pushing it pretty hard. I'm using Menumeters to monitor processor (which was 80-100% for almost 20 minutes on initial boot, WindowServer being prime culprit) use & even going to Dock takes a lot of Processor use, however, the system quickly recovers, most native apps, Safari, Photos in general bounce in Dock for 10-15 seconds before opening, once open pretty snappy. 3rd party 64bit apps, some open extremely fast, 1Password, iTerminal, DetectX Swift, Avast to name a few. So in a final analysis, Mojave beta 2 works well, with current patches, I wouldn't make it primary OS, although I do use it on 1 of my Mac's as "prime" test OS, others running HS, which is main sys. Many thanks to dosdude1, Badruzeus, ASentientBot, jackluke & others to make this possible for Unsupported Mac's to run Mojave.
For 2nd beta release remarkably stable, I remember beta testing OSX Kodiak, (to become Cheetah) what a nightmare that was, kp's a mainstay thru multiple betas.
Avast looks like it didn't like Backup&Sync.app/Contents/Helper/GoogleDrive Icon helper see Avast.png.
 

Attachments

  • Avast.png
    Avast.png
    67.8 KB · Views: 164
  • MenuMeters.jpg
    MenuMeters.jpg
    9.3 KB · Views: 138
Last edited:
I'm 90% sure the kexts still need to have correct permissions (root:wheel, 755)

To rebuild prelinkedkernel:
sudo bash
<enter password>
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -i /
Actually, the best (and proper) way to rebuild the prelinkedkernel is to use the following commands:

sudo kextcache -system-caches
sudo kextcache -system-prelinked-kernel
 
Bear with me a moment this IS about 10.14 beta - but background first..

I have a white MB early 2009 running 10.13.5 - thanks to the support/patches you and the crew here provide

screen-shot-2018-07-13-at-12-46-32-pm-png.770498

I applied the bootROM patch using your tool found here. I knowingly did this AT MY OWN RISK. My machine was NOT bricked as a result of this.... it works BUT...

BUT...when I power on at first I get a long full volume tone for about 4 seconds and the DVD drive starts, the power light stays on but the screen is black. It stays like that even if I leave it for 10 minutes.

If after this ‘almost start’, I hold the power button down to force a shut down, wait a couple of seconds, then press the power button again it boots again - but this time normally.

Should it do this? If not, have you any suggestions as to how I should fix it, so it just boots first time.

I'd like to use the patcher for macOS 10.14 Mojave on this machine but I'm nervous about using it if I have somehow not applied the bootROM patch for HS correctly.

(I have a copy of the removal tool through the link posted some time ago if I need to use that???)


Thanks again for all the work in getting these patches to work.
I would remove it and see if that fixes your issue. If so then try reapplying it and hopefully it will work correctly this time.


Well I thought I knew how to remove the APFS bootROM patch and go back to the original (which I have backed up safely in several places)... but I don't. I've failed to get it to work.

Can anyone who has tried tell me how they did it?

Thanks
I would remove it and see if that fixes your issue. If so then try reapplying it and hopefully it will work correctly this time.
 
You don’t have to do a clean install. At least you shouldn’t have to.
[doublepost=1531682005][/doublepost]

You should be able to find compatible ones from El Capitan.

@jackluke

Just tried swapping in El Cap 10.11.2 IOUSBFamily and IOUSBHostFamily extensions and no go: same lock up.
The extensions come from Apple's latest kernel debug kit for El Cap (10.11.12_Build_15C50)
I made sure to regenerate caches and prelink etc.

Hope this helps anyone who decides to dig into it further (for mbp 5x family)

Otherwise all seems to work well after a few days of banging on Mojave. iSight can (should) be replaced by a more capable external HD camera if need be anyway.
 
  • Like
Reactions: jackluke
Good news for Mojave beta testers!

If you need to back up your system from Mojave, there is now a provisional Mojave beta for Carbon Copy Cloner. This is handy for not only backing up your Mojave installation but you can also use it to back up a base install test on other unsupported systems.

download the latest beta of CCC 5 here
Just tried Mojave version CCC v.5.1.3-b3 to Clone new 250 SSD to swap out (old & slow PNY) 120 SSD, works great, have "new" bootable SSD. WindowServer again taking 80-100% of processes, to be expected.
Footnote;
Had to start up from external as got ? when booted, ran disk utility, twice from ext, reboot & up & running. That being said if you choose this route perhaps it's best to run Disk Utility prior to the swap as I did get some errors which were repaired.
 

Attachments

  • Screen Shot 2018-07-15 at 17.24.28.png
    Screen Shot 2018-07-15 at 17.24.28.png
    53.9 KB · Views: 107
Last edited:
Thanks for the information. Always thought it was equivalent, what's the difference?
While playing around in Mojave Recovery mode, I noticed that the prelinks are all regenerated automagically when removed from <your boot volume>/S/L/PrelinkedKernels. It's been awhile, but I don't remember that happening before. My three prelinkedkernels (normal, debug, development) were re-created (after a few seconds) when removed.
 
  • Like
Reactions: Luckygreek
There was a problem with the camera and with the definition of USB.
MacBook Pro 5.5 now works as it should!
It is necessary to make so:
Burn bootstrap with patch HighSierra 10.13.5 from here http://dosdude1.com/highsierra/
From the image, select two IOUSBFamely.kext and IOUSBHOSTFamely.kext from the System / Library / Extensions
Then in Mojave, run the Kekst Utilities program and drop these two keksts
Enter the password twice when processing the caches and at the end, restart the computer.
The camera and USB ports work correctly.
00e5eb4a1eaf865f6d9cb5e6a2b56510cc1b7080.jpg


Thank you for this decision!
 
Last edited:
There was a problem with the camera and with the definition of USB.
MacBook Pro 5.5 now works as it should!
It is necessary to make so:
Burn bootstrap with patch HighSierra 10.13.5 from here http://dosdude1.com/highsierra/
From the image, select two IOUSBFamely.kext and IOUSBHOSTFamely.kext from the System / Library / Extensions
Then in Mojave, run the Kekst Utilities program and drop these two keksts
Enter the password twice when processing the caches and at the end, restart the computer.
The camera and USB ports work correctly.

Thank you for this decision!

Well done!

pkouame give it a try too for your MBP 5,3

And thanks to dosdude1 that has an ace up his sleeve!
 
[QUOTE = "chris1111, post: 26246103, member: 978241"] Melden Sie das Gigabyte GeForce 210 1gig
61p3as11.jpg


funktioniert gut DVI Port voll QE / CI mit dem Fix alten Nvidia
Danke: an alle Benutzer und bestimmte dosdude1, ASentientBot [/ QUOTE]

@chris1111.....work this device without nVidia Web-Driver ? and without change the kexte (tesla etc. in Mojave) ?
 
Last edited:
hi. Please, tell me about updates from beta to beta? how it will be? can i install it normally from appstore, on download new beta version, write on usb and install without cleaning ssd? thanks!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.