Jump to content

[pre-release] macOS Mojave


2,429 posts in this topic

Recommended Posts

1 minute ago, Muntashir said:

No, I didn't. But MBP14,1 (which I've been using) should've worked.

Nah, try updating them.. Latest @mackie's Clover Configurator.app may help? As well as provided BootROM version etc there.

  • Like 1
Link to comment
Share on other sites

9 hours ago, Havenger said:

Any News about NVIDIA and Mojave ? I don't want to buy a new GPU, because my GTX 980 is still good enough for anything I do …

We'll have to wait for the final version of Mojave and the appropriate web drive! It's supposed to work fine!

Link to comment
Share on other sites

35 minutes ago, Fergarth said:

We'll have to wait for the final version of Mojave and the appropriate web drive! It's supposed to work fine!

 

Why did I know this Answer ? It was good to see, that NVIDIA published a lot of Web Drivers for El Capitan and Sierra during the Beta, but since High Sierra it's silent. And we have to wait and pray for a Web Driver. Currently there's only one Reason for NVIDIA to update their Web Drivers : Some People could buy a NVIDIA Graphics Card for their MacPro4,1 and MacPro5,1. I don't think NVIDIA cares about Hackintosh, so the possible Users of a new Web Driver are only a few People :unsure:

  • Like 2
Link to comment
Share on other sites

2 hours ago, Havenger said:

I don't think NVIDIA cares about Hackintosh, so the possible Users of a new Web Driver are only a few People :unsure:

 

Not especially a few people - Apple introduced eGPUS system to its OS and there still some Macs with nVidia GPUs that support macOS Mojave. There's no reason to not release a beta webdriver version, if not Optimus pride.

  • Like 2
Link to comment
Share on other sites

1 hour ago, fantomas1 said:

 

Not especially a few people - Apple introduced eGPUS system to its OS and there still some Macs with nVidia GPUs that support macOS Mojave. There's no reason to not release a beta webdriver version, if not Optimus pride.

 

Yeah I forgot the eGPUs. But there's one Difference between the Macs coming with a NVIDIA-GPU and the ones with a later bought NVIDIA-GPU, so Apple has the Extensions included for all GTX 600 and GTX 700 Models ( except the GTX 750, which is the first Version of Maxwell ), so later Models need the Web Driver. I've seen so many People here with a GTX 6xx, but who has a GTX 9xx or a GTX 10xx ? These are only a few Peoples, so hopefully NVIDIA will build more eGPUs for having an Argument to create Web Drivers ( for GTX 750, 9xx and 10xx ) in the Future. Sorry, that I'm so pessimistic, but I want to have Mojave and haven't / wouldn't have the Money to buy a new GPU …

Link to comment
Share on other sites

Some workarrounds about weird tinted AppleMenu if using LightMode on non-metal capable graphics:

This is what I get when switching from Dark to Light Mode appearance under macOS Mojave 10.14 Beta 7.

Not sure why it shows me "Unable to load Info.plist exceptions (eGPUOverrides)", since my laptop only has a single Nvidia GF119 graphics. -_- and, with no eGPU for sure. Strange.

Screen Shot 2018-08-17 at 00.01.28.png

Edited by Badruzeus
Link to comment
Share on other sites

22 minutes ago, Badruzeus said:

Some workarrounds about weird tinted AppleMenu if using LightMode on non-metal capable graphics:

This is what I get when switching from Dark to Light Mode appearance under macOS Mojave 10.14 Beta 7.

Not sure why it shows me "Unable to load Info.plist exceptions (eGPUOverrides)", since my laptop only has a single Nvidia GF119 graphics. -_- and, with no eGPU for sure. Strange.

Screen Shot 2018-08-17 at 00.01.28.png

For my opinion Beta 7 is completely buggy  

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, chris1111 said:

For my opinion Beta 7 is completely buggy  

I have heavy kernel_task activity with this beta, Spotlight realtime indexing, auto storage cleanup, autobackup, spindump, photoanalyze services, crashreporter.. all are shown on Activity Monitor eating my 4+GB RAM, as well as Disk keeps spinning everytime. Though I could unload these services, but Beta 7 is still worse with big WindowServer RAM consumption, at least.. compared to prev. Beta's -_-

 

#EDIT: And there's no different between APFS or HFS+ on my 5400rpm mechanical HDD, Beta 6 is still better though.

Edited by Badruzeus
  • Like 1
Link to comment
Share on other sites

What the {censored}! I've tried 5 or more different times through different methods, through Olarila and several sites and I can not install Mojave on my Skylake 6 Gen Laptop... After instalation begins, it always reboot with a KP... :(

Link to comment
Share on other sites

12 hours ago, Fergarth said:

What the {censored}! I've tried 5 or more different times through different methods, through Olarila and several sites and I can not install Mojave on my Skylake 6 Gen Laptop... After instalation begins, it always reboot with a KP... :(

What is the verbose output from setting the following Clover boot options (-v keepsyms=1 debug=0x100, keep symbols + no reboot on panic)?  Sometimes old versions of lilu or its plugin kexts can ---> kp during Mojave install, so make sure you have the latest versions (maybe try temporarily blocking them through Clover menu).

 

Also consider using a single phase installer eg @dosdude1's macOS Mojave Patcher, or @crazybirdy MbrEasyInstallerMaker.  These are based on the old "BaseSystem.dmg restore" method ---> can easily manipulate/rebuild the installer's prelinked kernel (or replace prelinkedkernel with known working one from High Sierra).

 

 

Edited by fusion71au
update with installer links
  • Like 3
Link to comment
Share on other sites

21 hours ago, fusion71au said:

What is the verbose output from setting the following Clover boot options (-v keepsyms=1 debug=0x100, keep symbols + no reboot on panic)?  Sometimes old versions of lilu or its plugin kexts can ---> kp during Mojave install, so make sure you have the latest versions (maybe try temporarily blocking them through Clover menu).

 

Also consider using a single phase installer eg @dosdude1's macOS Mojave Patcher, or @crazybirdy MbrEasyInstallerMaker.  These are based on the old "BaseSystem.dmg restore" method ---> can easily manipulate/rebuild the installer's prelinked kernel (or replace prelinkedkernel with known working one from High Sierra).

 

 

Hi fusion71,

Thanks for the tips, but regardless of which method I use, the upgrade/installation process starts well! But after the first reboot, it always ends with this KP... yes of course, I have the last Clover! Don't know... :cry:

20180819_190334.jpg

Link to comment
Share on other sites

1 hour ago, Fergarth said:

Hi fusion71,

Thanks for the tips, but regardless of which method I use, the upgrade/installation process starts well! But after the first reboot, it always ends with this KP... yes of course, I have the last Clover! Don't know... :cry:

20180819_190334.jpg

try this before reboot after Update

 

  • Like 2
Link to comment
Share on other sites

1 hour ago, Fergarth said:

Hi fusion71,

Thanks for the tips, but regardless of which method I use, the upgrade/installation process starts well! But after the first reboot, it always ends with this KP... yes of course, I have the last Clover! Don't know... :cry:

Block "Lilu.kext".

  • Like 3
Link to comment
Share on other sites

15 hours ago, Badruzeus said:

Block "Lilu.kext".

Thank you friends! But with or without Lilu and nvram resets, the result was the same KP! It must be something else! It's strange, because my Skylake system has native support and until 13.6 always worked perfectly and without need of tricks... I leave here my EFI, if anyone wants to take a look...

EFI.zip

Edited by Fergarth
Link to comment
Share on other sites

18 hours ago, Fergarth said:

Hi fusion71,

Thanks for the tips, but regardless of which method I use, the upgrade/installation process starts well! But after the first reboot, it always ends with this KP... yes of course, I have the last Clover! Don't know... :cry:

20180819_190334.jpg

This KP come from installed system or non-install stage2 process?

And with this KP message, you still didn't know which kext or issue is the root cause.

 

I think no one knows.

Only if you can read the KP message as 10.12 before with KP with XXXX.kext kind of that.

  • Like 2
Link to comment
Share on other sites

1 hour ago, crazybirdy said:

This KP come from installed system or non-install stage2 process?

And with this KP message, you still didn't know which kext or issue is the root cause.

 

I think no one knows.

Only if you can read the KP message as 10.12 before with KP with XXXX.kext kind of that.

Yeap! I think I'll have to try an APFS SSD with nothing, no upgrades...

  • Like 1
Link to comment
Share on other sites

I have managed to install 10.14 Beta (18A365a)

it was a bit of a mission for me. on the hardware side  of things as i had to change. too a AMD Graphics card (Sapphire 280x Dual) works ootb Patched sound with Mirone sound kext patcher  bend and reroute the stainless steel in my loop 

IMAG1873.thumb.JPG.36262c821d6cc311a1edd8b50743e142.JPG

Screenshot 2018-08-20 at 16.30.24.png

  • Like 1
Link to comment
Share on other sites

40 minutes ago, BALDY_MAN said:

I have managed to install 10.14 Beta (18A365a)

it was a bit of a mission for me. on the hardware side  of things as i had to change. too a AMD Graphics card (Sapphire 280x Dual) works ootb Patched sound with Mirone sound kext patcher  bend and reroute the stainless steel in my loop 

IMAG1873.thumb.JPG.36262c821d6cc311a1edd8b50743e142.JPG

Screenshot 2018-08-20 at 16.30.24.png

Yes and what I consider the most stupid is that in X-99 Haswell-E (not natively supported), I upgraded to Mojave without any problems and everything working perfectly! And in Skylake with native support, I can not ...

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...