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.

iphone2g&3gfan

macrumors regular
Jun 14, 2013
147
103
Orlando, Florida
VoodooHDA is not a real solution. It was a workaround that we used back in the Mavericks/Yosemite Unsupported Mac threads from the Hackintosh community but you'll easily find that it is rather annoying to configure and work with on actual Mac hardware.

You'll be better off finding Audio Kexts from previous versions of macOS that could work in Mojave.
eventually this will break when apple makes a major kernel update, like the broadcom kexts that wouldn't load in sierra. Like it or not, It may be voodoohda, or we have to try an Info.plist patch on the mojave native AppleHDA.kext.
True, my initial experience with beta 3 on my 2011 MBP has not been completely positive. Things seem a bit more unstable (had VLC crash twice and a Safari page once), and the speed / responsiveness is mostly unchanged from beta 2. On my supported 2012 MBP, I had the system become partly non-responsive with the 2011 MBP mounted as an external drive using Target Disk Mode as well. These issues will hopefully be sorted out in a later beta.

However, there is one issue specific to my unsupported 2011 MBP: I'm seemingly unable to load the AMDRadeonX3000.kext from Sierra or High Sierra, needed to power off the dedicated GPU for cooler temps / battery battery life when only the integrated GPU is being used. It loaded fine in beta 2.

There's a resistor mod that will cut power (vcore) to the gpu die itself, and will make the gpu invisible in the pci express device tree, rendering the X3000 loading obsolete. I think it is just one resistor to clip, the guide's out there somewhere.
 
Last edited:

TimothyR734

macrumors 68030
Apr 10, 2018
2,723
2,753
Logsden Oregon
Can someone shed some light on why videos aren't running in Chrome (youtube) on a supported 2012 Mac mini quad core. Videos run in Safari from youtube but zero on Chrome. Video seems to load cause you can scroll through to see preview shots. Just won't actually play.
do you have flash player installed for chrome or enabled
 

BookEmDanno

macrumors 6502
Nov 9, 2010
266
200
State of ~Aloha!~
The version 3 public is it 10.14.0.11, that's it?

I believe public beta is still at 1 (equivalent to developer beta 2).

upload_2018-7-4_15-57-41.png
 
  • Like
Reactions: TimothyR734

Starplayr

Cancelled
Jun 13, 2018
557
1,048
Can someone shed some light on why videos aren't running in Chrome (youtube) on a supported 2012 Mac mini quad core. Videos run in Safari from youtube but zero on Chrome. Video seems to load cause you can scroll through to see preview shots. Just won't actually play.

What version of Mojave are you running? Developer Beta 1,2,3 or public beta? And is it the latest version of Chrome? I have a 2012 Mac mini and will try to reproduce.
 

andrey_russian

macrumors newbie
Jul 4, 2018
23
18
Try following my steps I posted for my MacBook Pro 2011 model. I found out that if I install it on a APFS format drive, it will not boot up and show what showing for you. So I had to format it to another format for it to work. This is because for some reason, the APFS patch is greyed out, so I could not apply the patch for it to work.

Here is my post with the steps I took, https://forums.macrumors.com/thread...ted-macs-thread.2121473/page-56#post-26202624

Let me know how it goes. This should allow you to install it.
Thank you! My iMac 12,2 (SSD Drive) working only with your decision.
[doublepost=1530767354][/doublepost]
Report: Successful install on 2011 iMac
iMac12,2 2.7 GHz Core i5-2500S, 12 GB RAM, AMD Radeon HD 6770M 512 MB


Install to Firewire 400 disk formatted as APFS worked, but wouldn't boot. I got the no symbol. I didn't try reformatting it as HFS+. So I created a new APFS partition on my internal drive and that worked. (I love how easy this is to do via APFS.)


Initial impression:

System was very, very, very slow during setup and early use. It seemed to progress to just being slow after a while.
Youtube HD videos play correctly in Safari.
The News application is interesting, but content is too dense. It needs more white space.
Chrome seems to work OK.


Problems:

"Automatically adjust brightness" doesn't work.
Lots of video tearing when moving windows, many windows don't redraw until they take damage.
Lastpass application crashes, lastpass Safari extension doesn't work until you restart Safari.
Home application won't launch, says that it's damaged or incomplete (?).


So kudos to dosdude1 for getting this to work at all, but while it's interesting to play with it's really not usable for day to day use.
My Mac12,2 2.7 GHz Core i5
Report: Successful install on 2011 iMac
iMac12,2 2.7 GHz Core i5-2500S, 12 GB RAM, AMD Radeon HD 6770M 512 MB


Install to Firewire 400 disk formatted as APFS worked, but wouldn't boot. I got the no symbol. I didn't try reformatting it as HFS+. So I created a new APFS partition on my internal drive and that worked. (I love how easy this is to do via APFS.)


Initial impression:

System was very, very, very slow during setup and early use. It seemed to progress to just being slow after a while.
Youtube HD videos play correctly in Safari.
The News application is interesting, but content is too dense. It needs more white space.
Chrome seems to work OK.


Problems:

"Automatically adjust brightness" doesn't work.
Lots of video tearing when moving windows, many windows don't redraw until they take damage.
Lastpass application crashes, lastpass Safari extension doesn't work until you restart Safari.
Home application won't launch, says that it's damaged or incomplete (?).


So kudos to dosdude1 for getting this to work at all, but while it's interesting to play with it's really not usable for day to day use.

My Mac12,2 2.7 GHz Core i5 (SSD Drive) working after formatting as HFS+ only.
 

Aletancredo

macrumors member
Jun 8, 2018
50
27
Hey guys I need your help. I am running macos mojave on my macbook pro 11 late but there is no sound.
Could you help me?

Tks,
 

bosozoku

macrumors regular
Feb 23, 2018
227
112
Tokyo
So, light mode grey bar and menu borders glitch both are still in beta3? Too bad...
as many of us want macOS 10.14 Mojave only for dark mode, maybe it is possible to port this to High Sierra with some kind of patch? I am good on High Sierra. Do not want to use 10.14 with minor but still graphical glitches on my i7 13" 2011 mbp.
[doublepost=1530774385][/doublepost]use
Hey guys I need your help. I am running macos mojave on my macbook pro 11 late but there is no sound.
Could you help me?

Tks,
use sound kext from macOS High Sierra 10.13.5
 

iphone2g&3gfan

macrumors regular
Jun 14, 2013
147
103
Orlando, Florida
It's possible to update from beta 2 to beta 3?
I'm sure it is, but since nearly all the kexts were (probably) updated, even though the ones we backported wouldn't be overwritten (since they dont exist in the update package), we:

probably should not update yet because there could be dependency problems.

When dealing with kexts without 1) a stable api at all, plus 2) added instability due to the early beta status of Mojave, I would wait until some testing is done.

Since the kexts we're dealing with are proprietary, by nature they will 1) not have a stable API, and adding on top of that that 2) this is a beta OS (by itself means instability), then because of those two elements combined the APIs are more likely to change and prevent our backported kexts from loading at all, due to missing/renamed functions found in other updated kexts, that our backported kexts depend on...

Excuse the tech gibberish, my advice/opinion is to wait until we heard from the main devs about compatibility with Developer Beta 3/likely to become Public Beta 2.
 
Last edited:

kinetos

macrumors member
Oct 1, 2015
72
45
I'm sure it is, but since nearly all the kexts were (probably) updated, even though the ones we backported wouldn't be overwritten (since they dont exist in the update package), we:

probably should not update yet because there could be dependency problems.

I've tried since pref panel but nothing appears
 

parrotgeek1

macrumors 6502
Jun 14, 2016
309
377
CA, USA
True, my initial experience with beta 3 on my 2011 MBP has not been completely positive. Things seem a bit more unstable (had VLC crash twice and a Safari page once), and the speed / responsiveness is mostly unchanged from beta 2. On my supported 2012 MBP, I had the system become partly non-responsive with the 2011 MBP mounted as an external drive using Target Disk Mode as well. These issues will hopefully be sorted out in a later beta.

However, there is one issue specific to my unsupported 2011 MBP: I'm seemingly unable to load the AMDRadeonX3000.kext from Sierra or High Sierra, needed to power off the dedicated GPU for cooler temps / battery battery life when only the integrated GPU is being used. It loaded fine in beta 2.
What error do you get in dmesg when you try to load it?
[doublepost=1530777953][/doublepost]
I'm also waiting for Core2Duo, dosdude, please,

We have no idea why it crashes. We've tried at least 6 things and none of them help.
 

kenau

macrumors newbie
Jul 3, 2018
27
3
I tried installing the beta 3 version on my macbook pro 2011 13", but unsuccessful. I downloaded it from the patcher. First I disabled the firmware password. Then I install the Mojave b3, after that, I applied the macOS post install app from the patcher on my SSD, then I tried to boot again but directly from SSD, and received the symbol that the initializing disk it is not found. When I boot and press command+R and choose the initializing disk, my SSD appear as having the MacOS 10.14 on it. So I have certain that the OS it is installed in my SSD, but it is not recognized.
 

kinetos

macrumors member
Oct 1, 2015
72
45
I tried installing the beta 3 version on my macbook pro 2011 13", but unsuccessful. I downloaded it from the patcher. First I disabled the firmware password. Then I install the Mojave b3, after that, I applied the macOS post install app from the patcher on my SSD, then I tried to boot again but directly from SSD, and received the symbol that the initializing disk it is not found. When I boot and press command+R and choose the initializing disk, my SSD appear as having the MacOS 10.14 on it. So I have certain that the OS it is installed in my SSD, but it is not recognized.

Start the machine from the USB stick, Open terminal en type:

csrutil disable (only needed if you did not allready disable SIP)
nvram boot-args="kext-dev-mode=1 -no_compat_check"

Reboot machine

THX to iApply for the tips
 

litania72

macrumors newbie
Jul 5, 2018
2
0
Big thank you to all of you...was waiting for this just to be able to use the dark mode....my experience with Mojave beta on a MacBook Pro 15 inch late 2011 is great...all works....but....I am using only the intel hd 3000 due to the ati 6750 being focked (needs a reball)....make sure it boots with the intel gpu, smc is disabled and followed instructions on this blog to install Mojave (using hfs journaled as apfs does not boot) then restart again on usb, click on post install app then choose your Mac model and restart to finish off the installation....no issues whatsoever....tried youtube, sound....obviously the intel hd 3000 will mean no sleep or brightness control but who cares, for the time being I am happy....thanks

no glitches for me...
 
Last edited:

reperok95

macrumors newbie
Jul 3, 2018
14
11
Have you tried to copy /System/Library/Privateframeworks/coredisplay.framework from 10.14 beta 1 ? It might work
Hi
Experimented with Mojave Patcher.
I'm trying to get a GeForce GTX 260.

Also copied a file about which parrotgeek1 wrote - /System/Library/Frameworks/coredisplay.framework from 10.14 beta 1.
The result is identical.

I tried all patches of models in Mojave Patcher.
For patches under imac11.2, imac11.3, imac12.1, macbookair4.1, macbookair4.2, macbookpro6.1, macbookpro6.2, macmini5.1, macmini5.2, macmini5.3 - the result is bad.
Unless on patches from laptops that were started both monitors, but the second monitor went duplicating.

For patches under imac11.1, imac12.2, macbookpro8.1-8.3, macpro4.1 - the most successful result at the moment:
namely to define 2 monitors, the resolution on the second monitor is also identical, on the first 1024x720;
and only on these patches after the login screen allows to log into the system, but after almost complete initialization of the system hangs tightly, also the top bar menu as if it is not active and darkened.

Also I want to note that the system runs without any correct drivers and everything works there, only friezes and artifacts.
NVDANV50HalTesla is loaded without errors, only as I understood the identification of the NDRVShim load can not be determined.

My system Hackintosh - identify imac11,1.
Intel i5-750 3Ghz (Overlocking)
GeForce GTX 260
MSI P55-CD53
SSD Kingston 240GB

Successfully run macOS 10.13.5.
 

litania72

macrumors newbie
Jul 5, 2018
2
0
...just noticed trick to exclude ati radeon resets itself once rebooted, which in a way is good, as this confirms that possibly all works good even when the dedicated gpu is active, however I am scared to do any benchmarks....will try opening sn app which triggers the dedicated gpu....
 

kenau

macrumors newbie
Jul 3, 2018
27
3
Start the machine from the USB stick, Open terminal en type:

csrutil disable (only needed if you did not allready disable SIP)
nvram boot-args="kext-dev-mode=1 -no_compat_check"

Reboot machine

THX to iApply for the tips
Thank You kinetos!
Ita worked for me. Mojave beta 3 It os now installed And working in my MacBook pro late 2011 13" with 16 Gb RAM, Intel HD 3000 512 Mg And Intel core i5.
[doublepost=1530788876][/doublepost]
Thank You kinetos!
Ita worked for me. Mojave beta 3 It os now installed And working in my MacBook pro late 2011 13" with 16 Gb RAM, Intel HD 3000 512 Mg And Intel core i5.
760635_560a7458939246e9808a8f29bd4791ea~mv2.png

760635_eafb114408964d67bbff466657ca7de1~mv2.png
 
Last edited:

Aletancredo

macrumors member
Jun 8, 2018
50
27
So, light mode grey bar and menu borders glitch both are still in beta3? Too bad...
as many of us want macOS 10.14 Mojave only for dark mode, maybe it is possible to port this to High Sierra with some kind of patch? I am good on High Sierra. Do not want to use 10.14 with minor but still graphical glitches on my i7 13" 2011 mbp.
[doublepost=1530774385][/doublepost]use

use sound kext from macOS High Sierra 10.13.5
Hi thanks could you please post how to do it?
[doublepost=1530793191][/doublepost]
Thank You kinetos!
Ita worked for me. Mojave beta 3 It os now installed And working in my MacBook pro late 2011 13" with 16 Gb RAM, Intel HD 3000 512 Mg And Intel core i5.
[doublepost=1530788876][/doublepost]
760635_560a7458939246e9808a8f29bd4791ea~mv2.png

760635_eafb114408964d67bbff466657ca7de1~mv2.png
Hi Kenau the sound is working well? I installed the Mojave and the sound is not working well. Thanks
 

patseguin

macrumors 68000
Aug 28, 2003
1,713
513
I have an early 2011 15" MBP with a 2GHz i7, 16GB RAM, and 1 TB SSD. Is there any reason why the Mohave update would not work on it? Is it the video card that it going to be the limiting factor?
 

kenau

macrumors newbie
Jul 3, 2018
27
3
Hi thanks could you please post how to do it?
[doublepost=1530793191][/doublepost]
Hi Kenau the sound is working well? I installed the Mojave and the sound is not working well. Thanks

I would say that my sound its working better in Mojave than in High Sierra. Because in High Sierra when I adjust the volume to the maximum, the sound present a noise, so the sound not was perfect, but in Mojave I don't experience any noise when I adjust the sound to the maximum.
 

Aletancredo

macrumors member
Jun 8, 2018
50
27
I would say that my sound its working better in Mojave than in High Sierra. Because in High Sierra when I adjust the volume to the maximum, the sound present a noise, so the sound not was perfect, but in Mojave I don't experience any noise when I adjust the sound to the maximum.
Hi Kenau are you Brazilian correct? Eu instalei o mojave e o mesmo está funcionando bem porém ao tentar ouvir uma música não sai som. Queria saber o que você fez para funcionar o som se foi alguma linha de comando...
 

kenau

macrumors newbie
Jul 3, 2018
27
3
Instalei pelo pendrive bootável, apliquei a patch do dosdude1 após a instalação (macOS post Install encontrada dentro da patch), abri o terminal e digitei:
csrutil disable dei enter
nvram boot-args="kext-dev-mode=1 -no_compat_check"

rebootei, selecionei a partição na qual instalei o Mojave e aqui estou. :)

PS: Como você sabia que sou brasileiro? Meu inglês tá tão ruim assim? kkkkkkkkkkkkkk
 

Aletancredo

macrumors member
Jun 8, 2018
50
27
Instalei pelo pendrive bootável, apliquei a patch do dosdude1 após a instalação (macOS post Install encontrada dentro da patch), abri o terminal e digitei:
csrutil disable dei enter
nvram boot-args="kext-dev-mode=1 -no_compat_check"

rebootei, selecionei a partição na qual instalei o Mojave e aqui estou. :)
Então fiz a mesma coisa que você e de fato ele funciona como esperado em se tratando de uma versão beta 3 mas o som não sai de jeito nenhum. Um colega sugeriu que eu use o kext do macos high sierra 10.13.5. Você pode me orientar como devo proceder? Obrigado ... ah estava usando o macos high sierra 10.13.6 beta 5 developer.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.