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.
Did had a similar issue in past, it's due to the wrong Mediatek/Ralink Driver pkg installer, there are many floating in the web, if you find the right one for your dongle it will work on any MacOS release starting from El Capitan till Mojave.
[doublepost=1532353863][/doublepost]

TimothyR734 has uploaded some pages ago all the 5 Kexts. But I don't understand if you need them for your High Sierra installation or Mojave adaptation.

edit: page 136
I need them to update my MB7,1 from Mojave DP 3 to DP 4. I have those from 10.13.6 but I read That those from 10.13.5 are better. Do you confirm that ?
Thank you
 
  • Like
Reactions: TimothyR734
I need them to update my MB7,1 from Mojave DP 3 to DP 4. I have those from 10.13.6 but I read That those from 10.13.5 are better. Do you confirm that ?
Thank you

They are almost the same, use those from TimothyR734 if you intend to do a manual patching.
I'm using those from 10.13.6 same your machine, everything work fine.
 
  • Like
Reactions: TimothyR734
They are almost the same, use those from TimothyR734 if you intend to do a manual patching.
I'm using those from 10.13.6 same your machine, everything work fine.
Yes I intend to do a manual patching in my MB7,1 from Mojave beta 3 to beta 4.
So I have to replace those 5 IOSUB*.kext from 10.13.6 before updating. Is that correct ?
 
  • Like
Reactions: TimothyR734
Yes I intend to do a manual patching in my MB7,1 from Mojave beta 3 to beta 4.
So I have to replace those 5 IOSUB*.kext from 10.13.6 before updating. Is that correct ?

Correct, for a better installation instead of KextUtility use the pkouame steps same thread page 136.

You will need also to replace the com.apple.telemetry.plugin take a copy from your current Mojave beta 3!

Or if you don't care as me, delete it completely from /S/L/UserEventPlugins/ after you have upgraded to Mojave beta 4.

Also AppleHDA.kext is needed again to bring you the sound/mic.
 
  • Like
Reactions: TimothyR734
Correct, for a better installation instead of KextUtility use the pkouame steps same thread page 136.

You will need also to replace the com.apple.telemetry.plugin take a copy from your current Mojave beta 3!

Or if you don't care as me, delete it completely from /S/L/UserEventPlugins/ after you have upgraded to Mojave beta 4.

OK I will replace the 5 IOSUB*.kext from 10.13.6 before updating

Also AppleHDA.kext is needed again to bring you the sound/mic.
So Do you think that it will not bootloop after updating before I can replace the com.apple.telemetry.plugin take a copy from your current Mojave beta 3, or delete it completely from /S/L/UserEventPlugins/ after you have upgraded to Mojave beta 4 ?
By the way, do you still use IOAccelerator unix exe from Mojave Beta 1 ?

Thank you
 
  • Like
Reactions: TimothyR734
So Do you think that it will not bootloop after updating before I can replace the com.apple.telemetry.plugin take a copy from your current Mojave beta 3, or delete it completely from /S/L/UserEventPlugins/ after you have upgraded to Mojave beta 4 ?
Thank you

A couple of boot loop after a version upgrade are mandatory I would say.
Take a copy of telemetry.plugin, but the first immediate boot loop is caused by IOUSB*** or invalid new prelinkedkernel/kextcache file generated. The telemetry KP if occurs very later after the main boot sequence.

A simple solution, is to create with latest Mojave Patcher an USB installer, then upgrade from that and follow the Post Install guide.

I discourage upgrading from MacBook7,1 , unless it's an external disk that you intend to upgrade from a supported Mac.

So only in the second case you could try, otherwise no.
 
  • Like
Reactions: TimothyR734
A couple of boot loop after a version upgrade are mandatory I would say.
Take a copy of telemetry.plugin, but the first immediate boot loop is caused by IOUSB*** or invalid new prelinkedkernel/kextcache file generated. The telemetry KP if occurs very later after the main boot sequence.
Thank you ! I was confused...
 
  • Like
Reactions: TimothyR734
Please re-read the edited message, I often change my mind, trying to suggest risky free solutions.

Ok for AppleHDA ! Thank you

By the way, do you still use IOAccelerator unix exe from Mojave Beta 1 ?
[doublepost=1532357171][/doublepost]
A simple solution, is to create with latest Mojave Patcher an USB installer, then upgrade from that and follow the Post Install guide.

So only in the second case you could try, otherwise no.

Edit : I don't understand. How to upgrade from the USB installer ?
Edit 2 : I intend to upgrade from MacBook7,1 because I don't have a supported Mac.

Thank you
 
  • Like
Reactions: TimothyR734
Ok for AppleHDA ! Thank you

By the way, do you still use IOAccelerator unix exe from Mojave Beta 1 ?

I do use IOAccelerator beta 1, but all the others work, I use only because without it I have issues in Finder Views Sorting List.

Anyway you can safely upgrade in-place from your MB7,1 since ASiententBot done it too, and has written also a tutorial about on page 147
 
  • Like
Reactions: TimothyR734
I do use IOAccelerator beta 1, but all the others work, I use only because without it I have issues in Finder Views Sorting List.

Anyway you can safely upgrade in-place from your MB7,1 since ASiententBot done it too, and has written also a tutorial about.
Please re-read my edited message. I put another precision.
Thank you
 
  • Like
Reactions: TimothyR734
Please re-read my edited message. I put another precision.
Thank you

1) Yours is a good question, I don't know if Mojave Patcher can do an in-place version upgrade after booting from it.
2) You can, because ASiententBot done it too, I was just worried if an in-place upgrade could call a risky EFI firmware upgrade for your unsupported machine, but apparently it will not happen, so you could upgrade from MB7,1 to Mojave beta 4.

Anyway for these stuffs I use EVER a supported Mac.

Even if I haven't used yet I am sure that Mojave Patcher is 100% safe.
 
  • Like
Reactions: TimothyR734
1) Yours is a good question, I don't know if Mojave Patcher can do an in-place version upgrade after booting from it.
2) You can, because ASiententBot done it too, I was just worried if an in-place upgrade could call a risky EFI firmware upgrade for your unsupported machine, but apparently it will not happen, so you could upgrade from MB7,1 to Mojave beta 4.

Anyway for these stuffs I use EVER a supported Mac.

Even if I haven't used yet I am sure that Mojave Patcher is 100% safe.
Great thansk. I'll test and I'll report..
 
  • Like
Reactions: TimothyR734
@ASentientBot - A few questions about the graphics patches:
- Which release do they all come from?
- It looks like the GeForceTesla NOP bypasses a call to free memory and buffers. Is it still relevant for my GeForce GTX 680 (on macpro 3,1) and is it related to a specific Nvidia web driver version?

@dosdude1 - feel free to chime in if you can.

Thanks.
 
  • Like
Reactions: TimothyR734
@ASentientBot - A few questions about the graphics patches:
- Which release do they all come from?
- It looks like the GeForceTesla NOP bypasses a call to free memory and buffers. Is it still relevant for my GeForce GTX 680 (on macpro 3,1) and is it related to a specific Nvidia web driver version?

@dosdude1 - feel free to chime in if you can.

Thanks.
They come from 10.13.5. Newer cards don't even use the GeForce Tesla kexts, so nothing to worry about in that regard with a GTX680.
 
They come from 10.13.5. Newer cards don't even use the GeForce Tesla kexts, so nothing to worry about in that regard with a GTX680.
Thanks - I'll experiment with the 10.13.6 versions when I have time to play with my 3,1. Do you think the native Mojave betas may also work? This would make my post install even simpler.
 
  • Like
Reactions: TimothyR734
Thanks - I'll experiment with the 10.13.6 versions when I have time to play with my 3,1. Do you think the native Mojave betas may also work? This would make my post install even simpler.
Yes, you don't need to apply the Legacy Video Card patch at all with the GTX680 (which is why it's not installed by default on any machine with an upgradeable GPU).
 
They come from 10.13.5. Newer cards don't even use the GeForce Tesla kexts, so nothing to worry about in that regard with a GTX680.

The patched GeForceTesla comes from Mojave DP2 though right? We should probably get that updated for final release at least.
 
  • Like
Reactions: TimothyR734
Enough. Since I got work offer in Japan, I am buying 2018 4core version of MBP 13" with Touch Bar (ofc with of 16Gb RAM) this Christmas. I gave up with my 2011 13" MBP. It is too old, for 7.5 years it was a good run!
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.