Jump to content

[pre-release] macOS Mojave


2,429 posts in this topic

Recommended Posts

12 minutes ago, arsradu said:

 

Then it beats me.... I have no idea. I mean, you should see at least SOME changes.... Both to the boot, and to the actual issue... Do you have acceleration? Full resolution? Both in Clover GUI and OS? I don't see any reason why it wouldn't work...

 

But maybe you can try what cyberdevs suggested before. And see if that works.

 

Which is to manually remove:

1. com.apple.finder.plist from Library/Preferences

2. com.apple.QuickLookDaemon.plist from the same place

 

3. Kext cache remove (it will be rebuilt on the next reboot). Which you can do using Terminal, and doing:


sudo -s
[password]
rm -R -v /System/Library/Caches/com.apple.kext.caches/Startup/*

 

4. Reboot

5. On Clover GUI, press F11 to reset NVRAM.

 

Let's see if THAT makes any difference. I mean, I'm honestly surprised it made absolutely no difference. It instantly fixed the issue in my case. And it does make the difference even without the patches. As long as you can boot your system and use Apple driver. You don't even need acceleration. It makes no difference in this case.

 

But anyway...let's try this, as well.

Yeah I know, it's frustrating lol. I just did all that but nothing has changed. Issue is still there.

Thank you, I really appreciate your help.

 

7 minutes ago, Badruzeus said:

It seems beta bug for me, also happened on my mach on prev. macOS 10.13 Beta last year, till Nvidia give WebDriver update then all went fine (or wait for Stable release if graphics=Supported Intel/AMD)

 

macOS_10.14_beta_2_18A314h_Release_Notes.pdf

macOS Mojave (10.14) - Bugs and bug fixes

 

Tnx, I'll read it

  • Like 1
Link to comment
Share on other sites

15 minutes ago, dzontra said:

Yeah I know, it's frustrating lol. I just did all that but nothing has changed. Issue is still there.

Thank you, I really appreciate your help.

 

 

Tnx, I'll read it

 

Did you set the IGPU as primary in your BIOS? Also, you need at least 64MB or shared memory (but that's usually the default value anyway).

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

9 minutes ago, arsradu said:

 

Did you set the IGPU as primary in your BIOS?

 

If you ask about Initial Display Outpot, it's set to PCIe slot

Btw, Intel Processor Graphics is set to Disabled in BIOS

 

Edited by dzontra
Link to comment
Share on other sites

12 minutes ago, Cyberdevs said:

Set Intel GPU to enabled in BIOS and use this folder and see if that helps.

https://www.dropbox.com/s/1dwgnj3iym67itd/EFI-3.zip?dl=0

 

9 minutes ago, arsradu said:

Please, enable the iGPU in BIOS and try again.

 

Awesome, it's fixed now. I did all those steps all over again.

Deleted 2 .plist files, rebuild cache, reset nvram, set Initial Display Output to IGFX, set Intel Processor Graphics to enabled and reboot.

Preview and quicklook can open .jpg files.

 

Thank you guys for helping me with this. It was so frustrating.

Beer on me.

  • Like 1
  • Haha 1
Link to comment
Share on other sites

1 minute ago, dzontra said:

Awesome, it's fixed now. I did all those steps all over again.

Deleted 2 .plist files, rebuild cache, reset nvram, set Initial Display Output to IGFX, set Intel Processor Graphics to enabled and reboot.

Preview and quicklook can open .jpg files.

 

Thank you guys for helping me with this. It was so frustrating.

Beer on me.

That's great! Congrats :)

  • Thanks 1
Link to comment
Share on other sites

37 minutes ago, dzontra said:

If you ask about Initial Display Outpot, it's set to PCIe slot

Btw, Intel Processor Graphics is set to Disabled in BIOS

You can set the PCIe as the primary GPU. I have the RX580 as the primary for better performance and only iGPU is enabled as the secondary GPU to handle the Metal on the UI and to enable the Hardware Encoding Support.

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

12 minutes ago, Cyberdevs said:

You can set the PCIe as the primary GPU. I have the RX580 as the primary for better performance and only iGPU is enabled as the secondary GPU to handle the Metal on the UI and to enable the Hardware Encoding Support.

 

Yeah, I was wondering about that.

It's done.

  • Like 1
Link to comment
Share on other sites

22 hours ago, arsradu said:

 

Could you, please, upload your Clover folder for analysis? Once fixed, you should not have any issues with it. Unless you've changed something else in the meantime.

 

So, let's see.

Also, don't forget to clean your config.plist SMBIOS/RT variables of of any serials. We're not interested in that.

Here you goCLOVER.zip

Link to comment
Share on other sites

Just now, MorenoAv said:

A new beta, I ask because today was released a new beta High Sierra 10.13.6 beta 4...

Nope there isn't a new beta for Mojave I just checked. Still the same Beta 2 

Link to comment
Share on other sites

42 minutes ago, Badruzeus said:

As what I read, Apple Releases First Public Beta of iOS 12, macOS Mojave 10.14, and tvOS 12 on 25th June '18

Not sure if it just has a same build number as Dev. Beta 2 (18A314h), I could be wrong or any info from you? Thanks.

 

I think, it's ..

Monday 6/25 for 10.13.6 beta release.

Tuesday 6/26 for 10.14 beta release.

 

like as

Monday 6/18 for 10.13.6 beta release.

Tuesday 6/19 for 10.14 beta release.

Edited by crazybirdy
  • Like 2
Link to comment
Share on other sites

@Sherlocks what were the steps for installation in your case, did you use different SMBIOS than macbookpro 8.1 ? and what kexts did you only add for QE/CI, public beta went out so i wanted to give it another shot, only QE/CI was missing, i had everything sorted out.

Link to comment
Share on other sites

Looks like I was wrong... MacOS Mojave PB1 build numer is actually 18A314k. Now, I'm not sure it's any different in terms of actual fixes. But that's another story.

Edited by arsradu
Link to comment
Share on other sites

Here is my Mojave problem list;

 

- Boot is so slow I am waiting almost 5 min sometimes much more (is it because of HDD installation or something else)

- After Boot everything is so slow inside of Mojave (Attached my files with ioreg could someone please check)

- No Sound I used AppleALC.kext v1.2.7 with -lilubetaall arg nothing change (can somebody share with me v1.2.8v2 I search but didn't find inside of thread)

 

@arsradu I am waiting your Skylake config.plist thank you.

 

Archive.zip

 

@Poco Thank you fixing for the upload files section.

Edited by telepati
  • Like 2
Link to comment
Share on other sites

40 minutes ago, telepati said:

Here is my Mojave problem list;

 

- Boot is so slow I am waiting almost 5 min sometimes much more (is it because of HDD installation or something else)

- After Boot everything is so slow inside of Mojave (Attached my files with ioreg could someone please check)

- No Sound I used AppleALC.kext v1.2.7 with -lilubetaall arg nothing change (can somebody share with me v1.2.8v2 I search but didn't find inside of thread)

 

@arsradu I am waiting your Skylake config.plist thank you.

 

Archive.zip

 

@Poco Thank you fixing for the upload files section.

Hi man,

 

You know, I didn't forget about you. I just thought you don't need the config anymore since you fixed the issue. :)

 

Anyway, here's the Skylake config.

And here are the updated files for AppleALC and Lilu kexts in order to have sound in Mojave.

 

Not sure about the boot speed. Sounds a little bit too much though. If this is after the installation, it's definitely too much.

Do you need USBInjectAll kext? Cause I don't. Do you need that weird boot arg "uia_exclude=HS03;HS04;HS07;HS08;HS11;HS12;HS13;SS03;SS04;SS07;SS08;SS09;SS10;"? Cause I most definitely don't.

 

Try a fresh config. You can try the one I posted above for comparison. You could also try installing the other drivers that Clover adds by default during installation, and see if that makes any difference. Also, try to add Apfs.efi instead of ApfsDriverLoader. Yes, I know it's supposed to replace apfs.efi and give you more flexibility. But let's see if it actually makes a difference in this case.

Make sure you use apfs.efi from Mojave Beta. Just in case older versions might not work as well with mechanical HDDs.

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

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...