macOS 10.14 Mojave on Unsupported Macs Thread

[Luckygreek]

Well, that install took about 20 minutes, booted up, I haven't run the patch yet, Hmmmm that's interesting. I just ran the Patch Updater in Utilities Folder and says "All is Up to date" "no new patch updates are available at this time"
18A336e is what I get which is the latest update. Patch or no patch from USB??

Seems a little more responsive in the Finder, some of the UI glitches aren't as apparent as with the previous beta.

Edit:
Also not seeing the WindowServer taking up resources as with previous updates, that's a plus.
Actually way more responsive than the last beta, Apps open substantially faster, especially native apps, no UI glitches in the menu bar or Finder.
Thanks to all!! especially dosdude1.

 

[jackluke]

BREAKING NEWS!!!

I'm testing Mojave beta 4 on unsupported Macbook7,1 , and after applying all the known patches for this machine, especially the telemetry.plugin to allow booting from C2D, I have discovered that starting from Mojave beta 4 there could be another or more than one UserEventPlugins that cause the KP before stage2 logo.

Stay tuned.

Edit:

Then I understand why I got KP, for some unknown reason, when I replaced the telemetry.plugin from High Sierra, it hasn't copied inside it the real essential file to bypass the C2D panic, and that real required file is: /S/L/UserEventPlugins/com.apple.telemetry.plugin/Contents/MacOS/com.apple.telemetry

During replacement Mojave beta 4 kept the more recent one unix binary instead overwritten it, while the "subfolders" containing it were replaced with corrected date 2017, anyway has been my carelessness.

Sorry to have alarmed you unnecessarily. My mistake.

 

[AwlsomeAlex]

BREAKING NEWS!!!

I'm testing Mojave beta 4 on unsupported Macbook7,1 , and after applying all the known patches for this machine, especially the telemetry.plugin to allow booting from C2D, I have discovered that starting from Mojave beta 4 there could be another or more than one UserEventPlugins that cause the KP before stage2 logo.

Stay tuned.

I thought this was already solved?
[doublepost=1531868424][/doublepost]macOS Mojave Public Beta 3 came out today for all of you trying to get a Developer Profile for Developer Preview 4.

 

[Luckygreek]

What I am experiencing is iconserviceagent is taking up about 40% of CPU, so have these Terminal commands from earlier an OS, to rebuild cache, which may be corrupt;

$ sudo find /private/var/folders/ \-name com.apple.dock.iconcache -exec rm {} \;

$ sudo find /private/var/folders/ \-name com.apple.iconservices -exec rm -rf {} \;

$ sudo rm -rf /Library/Caches/com.apple.iconservices.store

restart

Anyone had this experience before on Mojave?

 

[netsrot39]

I got an instantly panic, I've checked it seems due to the only High Sierra IOUSBHostFamily.kext, so this time to avoid a quick KP all the IOUSB*** from HS are needed replacing for Mojave beta 4.

Ok after replaced them rebuilding prelinkedkernel then booted again but get a KP later before the stage2 apple logo, it seems from the panic that last kext loaded was NVAStartup, I'm continue to test.

Ok after deep investigation, applying all known patches I got this KP just before the stage2 apple logo (don't know why but seems linked to the IOUSB*** replaced kexts):
[/CODE]

Sorry I haven't checked in for a couple of days as I was busy with work. So I noticed Beta 4 has been out for a few days. I haven't installed it yet but am I getting it correctly that Mojave Beta 4 doesn't work with unsupported machines like the MacBook 7,1 anymore?? Is it mainly due to iSight kexts?

It's very interesting that from version to version there is something added that breaks the efforts made here. Maybe Apple reads this thread and does it on purpose so we have to buy newer macs (just kidding ;-) )

 

[TimothyR734]

Sorry I haven't checked in for a couple of days as I was busy with work. So I noticed Beta 4 has been out for a few days. I haven't installed it yet but am I getting it correctly that Mojave Beta 4 doesn't work with unsupported machines like the MacBook 7,1 anymore?? Is it mainly due to iSight kexts?

It's very interesting that from version to version there is something added that breaks the efforts made here. Maybe Apple reads this thread and does it on purpose so we have to buy newer macs (just kidding ;-) )

the public beta is out now to

 

[Appleak]

my iMac 11.2, on mojave10.14 b4, is able to play my heavy action games like: Deus Ex.. already played on 10.13 H S
when I first open my game it shows an error message that this game is not optimized to run on Mojave but second try it plays fine as it should, im happy now kinda feeling natively supported haha!
Tested & confirmed full acceleration for premetal AMD4600 as said Dosdude1
Thank You @Dosdude1 & Team for this awesome work!

 

[TimothyR734]

What I am experiencing is iconserviceagent is taking up about 40% of CPU, so have these Terminal commands from earlier an OS, to rebuild cache, which may be corrupt;

$ sudo find /private/var/folders/ \-name com.apple.dock.iconcache -exec rm {} \;

$ sudo find /private/var/folders/ \-name com.apple.iconservices -exec rm -rf {} \;

$ sudo rm -rf /Library/Caches/com.apple.iconservices.store

restart

Anyone had this experience before on Mojave?

that is unusual but you need to let the OS settle a bit and the more you use it the more responsive it becomes
[doublepost=1531870398][/doublepost]

Excellent, will download the latest code and see if it builds with the latest Xcode.

Unfortunately the dosdude/mojave version did not trigger an update for me (from h to e) I bounced the process, rebooted a few times and even logged in and out of App Store to no avail.

Let me check out your source code. Thanks!

I tried the newest version of the SWUSwitcher and checked the software update in the system preferences clicked on details said I was receiving updates from the developers seed so I will let you know when the next developers beta comes out that it does work

 

[Luckygreek]

that is unusual but you need to let the OS settle a bit and the more you use it the more responsive it becomes

It's definitely more responsive, yeah doing the usual & letting System recover, just a little unusual activity with "iconserviceagent" we'll see how it goes.. Not to keen on sudo commands with a beta for an unsupported iMac, some ok others a little apprehensive. Thanks Timothy

 

[TimothyR734]

Sorry I haven't checked in for a couple of days as I was busy with work. So I noticed Beta 4 has been out for a few days. I haven't installed it yet but am I getting it correctly that Mojave Beta 4 doesn't work with unsupported machines like the MacBook 7,1 anymore?? Is it mainly due to iSight kexts?

It's very interesting that from version to version there is something added that breaks the efforts made here. Maybe Apple reads this thread and does it on purpose so we have to buy newer macs (just kidding ;-) )

All you can to do is try to see if it works with the newest macOS Patcher beta 12

 

[jackluke]

I thought this was already solved?
[doublepost=1531868424][/doublepost]macOS Mojave Public Beta 3 came out today for all of you trying to get a Developer Profile for Developer Preview 4.

Irony of the fate, thanks to ASentientBot discovery, I did found it first time (page 71), and later I got a mistake in replacing. Unbelievable.

 

[videotape74]

Mojave DP4 is working really nicely so far on my 15" MBP 5,4 so I just wanna say thanks to everyone involved with this project...especially @dosdude1 !!!

Only thing that isn't working/I don't care about is the iSight camera, other than that...so far so good! Adobe Lightroom Classic CC and Microsoft Office are both good and updated. Love "Dark Mode" and it makes iTunes look great!

 

[netsrot39]

Mojave DP4 is working really nicely so far on my 15" MBP 5,4 so I just wanna say thanks to everyone involved with this project...especially @dosdude1 !!!

Only thing that isn't working/I don't care about is the webcam [...]

That's good to hear. Have you tried any kexts for the iSight cam? I mean even though you don't care about it, it could be nice to have that function as well.

 

[videotape74]

That's good to hear. Have you tried any kexts for the iSight cam? I mean even though you don't care about it, it could be nice to have that function as well.

I have not, I wasn't sure what to try/replace.

 

[netsrot39]

I have not, I wasn't sure what to try/replace.

I replaced IOUSBFamily.kext and IOUSBHostFamily.kext which I took from my HS 10.13.6 installation. Then I used KextBeast to load the kexts and the entered in terminal "command sudo nvram boot-args="kext-dev-mode=1". Then I rebooted and had a functioning iSight cam.

HOWEVER: This was my procedure on Beta 3, I have no idea if this works on Beta 4 ...

 

[visberry]

I have noticed, for anyone experiencing any performance issues. macOS Mojave speeds up *a lot* after a few hours of use. Even on supported Macs.

 

[TimothyR734]

@Czo - Thank you! I did a little sleuthing myself and realized the newer version(s) is a considerable overhaul from the original. Now I understand how you get away from checking machine identifiers, like iMac10,1 and it still works in Mojave and a new unsupported device list. Mystery solved. Keep us posted if and when a new stable version is available.

Thanks in advance for all this work and being open and transparent about your great utility! Best of luck...

macOS Dev beta 4 did break my iSight on my iMac 9,1

 

[MTYEAGLESCOUT]

My Fresh install boots to Black Screen. On Patcher Beta 12

 

[tsialex]

My Fresh install boots to Black Screen. On Patcher Beta 12

Missing SSE4.2 on your Xeon, your video card driver needs it. This combo, MacPro3,1 and AMD GCN cards don't work on Mojave.

 

[Loyd-01a]

BREAKING NEWS!!!

I'm testing Mojave beta 4 on unsupported Macbook7,1 , and after applying all the known patches for this machine, especially the telemetry.plugin to allow booting from C2D, I have discovered that starting from Mojave beta 4 there could be another or more than one UserEventPlugins that cause the KP before stage2 logo.

Stay tuned.

Edit:

Then I understand why I got KP, for some unknown reason, when I replaced the telemetry.plugin from High Sierra, it hasn't copied inside it the real essential file to bypass the C2D panic, and that real required file is: /S/L/UserEventPlugins/com.apple.telemetry.plugin/Contents/MacOS/com.apple.telemetry

During replacement Mojave beta 4 kept the more recent one unix binary instead overwritten it, while the "subfolders" containing it were replaced with corrected date 2017, anyway has been my carelessness.

Sorry to have alarmed you unnecessarily. My mistake.

@jackluke

Not at all !

I've installed a developper profile and do the update from preferences system to Beta 4 but still can't boot correctly. It reboots indefinetly.
Since I've also a macbook7,1 like you, could you please inform me about suitable patches that you applied during post install using dosdude1 Patcher ?
Thank you

EDIT :
If you applied manually all the known patches for this machine, could you please cite them ?

 

[DaniloGeekDude]

Confirming if this is Developer Preview 3 (latest available)?

Saw these lines on the Info.plist under Contents/ from "Install Mojave Beta" app.

<key>DTPlatformName</key>
<string>macosx</string>
<key>DTPlatformVersion</key>
<string>10.14</string>
<key>DTSDKBuild</key>
<string>18A336d</string>

I know the official build is 18A336e. Just need confirmation from expert folks on this thread that this is so. Thanks.

 

[tsialex]

Confirming if this is Developer Preview 3 (latest available)?

Saw these lines on the Info.plist under Contents/ from "Install Mojave Beta" app.

<key>DTPlatformName</key>
<string>macosx</string>
<key>DTPlatformVersion</key>
<string>10.14</string>
<key>DTSDKBuild</key>
<string>18A336d</string>

I know the official build is 18A336e. Just need confirmation from expert folks on this thread that this is so. Thanks.

Info.plist has the info for the macOS running on the Mac used for building the release, not the release itself.

Latest releases are Developer Preview 4, Public Beta 3, both on 18A336e.

 

[TimothyR734]

Confirming if this is Developer Preview 3 (latest available)?

Saw these lines on the Info.plist under Contents/ from "Install Mojave Beta" app.

<key>DTPlatformName</key>
<string>macosx</string>
<key>DTPlatformVersion</key>
<string>10.14</string>
<key>DTSDKBuild</key>
<string>18A336d</string>

I know the official build is 18A336e. Just need confirmation from expert folks on this thread that this is so. Thanks.

Are you sure that's on the newest macOS Mojave patcher beta 12 I did see that on 11 beta

 

[tw3nz0r]

Fresh install on iMac 9,1 -- amazing... (iSight also doesn't work as reported by someone else) The patcher comes up and wants to install the brightness patch. I reboot, and it endlessly boot loops after that, I even reran the post install, and it still does that. I guess I can skip the brightness patch for now.

 

[DaniloGeekDude]

Info.plist has the info for the macOS running on the Mac used for building the release, not the release itself.

Latest releases are Developer Preview 4, Public Beta 3, both on 18A336e.

Actually, that is the info list on the usb install drive.
/Volumes/usb.Mojave.128gb/Install macOS Mojave Beta.app/Contents  ls
Frameworks/ Info.plist MacOS/ PkgInfo PlugIns/ Resources/ _CodeSignature/ version.plist

The macOS which I used to download the beta is Sierra (10.12.6) on a supported Mac.