Jump to content

[pre-release] macOS Mojave


2,429 posts in this topic

Recommended Posts

 
Yeah that's interesting indeed. I haven't tested Hardware Encoding Support in Mojave yet...
I'll check it out and see how it turns out.
Did you disable iGFX in BIOS/UEFI or just removed the injections from the config?


I disabled igfx in BIOS


Sent from my iPhone using Tapatalk
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, Cyberdevs said:

Use this and send me the results via PM and I'll take a look to see if I can find anything.

RunMe 1.7.app.zip

 

RunMe.app does not work for me. I always getting IOREG failed error. I am making the restart and after boot, I don't touch anything and start RunMe.app but always giving this error.

Link to comment
Share on other sites

8 minutes ago, telepati said:

RunMe.app does not work for me. I always getting IOREG failed error. I am making the restart and after boot, I don't touch anything and start RunMe.app but always giving this error.

Yeah sometimes I get the same error and sometimes after several attempts it works. It doesn't matter just send your EFI folder to start with.

Link to comment
Share on other sites

1 hour ago, Trung_Nguyen said:

Hello, can somebody tell me what's the purpose for apfssupportpkg? Thanks

apfssuuportpkg is repo for apfsDriverloader.efi. I use it in Mojave.

  • Like 1
Link to comment
Share on other sites

I recently built Clover 4586(newest) with build script on Xcode-beta. Then, the computer turned unbootable. I have to use another usb drive to get the working from my attachments. It doesn't even write any log with debug options true in config.plist.

 

EDIT: Build didn't complete successfully on AptioFixPkg but the script didn't stop

Edited by Trung_Nguyen
Link to comment
Share on other sites

12 minutes ago, Trung_Nguyen said:

I recently built Clover 4582(newest) with build script on Xcode-beta. Then, the computer turned unbootable. I have to use another usb drive to get the working from my attachments. It doesn't even write any log with debug options true in config.plist.

Why do you compile r4582. Clover r4586 is release on sourceforge.

Link to comment
Share on other sites

31 minutes ago, Trung_Nguyen said:

I recently built Clover 4582(newest) with build script on Xcode-beta. Then, the computer turned unbootable. I have to use another usb drive to get the working from my attachments. It doesn't even write any log with debug options true in config.plist.

 

For some reason new Clover (when I build it myself) unchecks the OSXAptioFixDrv during install. You probably have to click on custom and make sure its checked during install...

 

Already happened to me 2 times lol, always forget it..53668362_Screenshot2018-07-02at10_42_38.png.73477931f2e1b1822f12341c57bc68ec.png

Edited by Nightf4ll
Link to comment
Share on other sites

3 minutes ago, Nightf4ll said:

 

For some reason new Clover (when I build it myself) unchecks the OSXAptioFixDrv during install. You probably have to click on custom and make sure its checked during install...

 

Already happened to me 2 times lol, always forget it..53668362_Screenshot2018-07-02at10_42_38.png.73477931f2e1b1822f12341c57bc68ec.png

I prefer AptioMemoryFix

20 minutes ago, Matgen84 said:

Why do you compile r4582. Clover r4586 is release on sourceforge.

oops, I did compile r4586, but I wrote it r4582

  • Like 1
Link to comment
Share on other sites

4 minutes ago, Trung_Nguyen said:

I prefer AptioMemoryFix

oops, I did compile r4586, but I wrote it r4582

well, my point was just to make sure it doesn't leave some of the drivers out (which might prevent it from booting)? whats the difference between those 2 (AptioMemoryFix and OsxAptioFixDrv)???

Link to comment
Share on other sites

2 minutes ago, Nightf4ll said:

well, my point was just to make sure it doesn't leave some of the drivers out (which might prevent it from booting)? whats the difference between those 2 (AptioMemoryFix and OsxAptioFixDrv)???

AptioMemoryFix have native nvram while OsxAptioFixDrv doesn't. OsxAptioFixDrv must be used with EmuVariableUEFI and rc script to read&write nvram to nvram.plist

  • Like 2
Link to comment
Share on other sites

27 minutes ago, Trung_Nguyen said:

oops, I did compile r4586, but I wrote it r4582

 

Few day ago, I've similar issue on my HDD Mojave: unbootable. So I boot from my High Sierra HDD, mount EFI partition (Mojave HDD), copy EFI folder on High Sierra desktop. 

 

I type these commands in Terminal: 

diskutil list

newfs_msdos -v EFI -F 32 /dev/rdisk2s1 (your Mojave EFI Partition)

quit

 

Then I copy EFI folder in "new" EFI Partition on Mojave HDD. Unmount partition. I can boot again.

 

Maybe It can help you.

Link to comment
Share on other sites

2 hours ago, Nightf4ll said:

For some reason new Clover (when I build it myself) unchecks the OSXAptioFixDrv during install. You probably have to click on custom and make sure its checked during install...

Just because isn't selected by default (or if you never selected it in past on the target volume) or just is not present. Il take care to make the package always show the customize menu... 

I think that anyone should take a look on what is doing.

  • Like 1
Link to comment
Share on other sites

On 6/30/2018 at 10:45 PM, telepati said:

When I choose light mode every menu item and sidebar turning gray.

 

is it normal or is it a bug of beta? or is it jut me?

 

82712703_ScreenShot2018-06-30at23_41_43.png.3b9368d53879cf146b21ac06d6d298d7.png

 

Same for me but solved deleting Whatevergreen.kext 

 

My Hack

Gigabyte GA-Z97MX-GAMING 5 / I7 4790K / 16 Gb Kingston HyperX / Gigabyte RX460 4Gb

 

 

 

Edited by DocXavier
Link to comment
Share on other sites

46 minutes ago, DocXavier said:

 

Same for me but solved deleting Whatevergreen.kext 

 

My Hack

Gigabyte GA-Z97MX-GAMING 5 / I7 4790K / 16 Gb Kingston HyperX / Gigabyte RX460 4Gb

 

 

 

Why is it looking all white in Dark Mode, this is what mine looks like

fBEACdM.jpg

Link to comment
Share on other sites

5 minutes ago, Pavo said:

Why is it looking all white in Dark Mode, this is what mine looks like

Because it's not the Dark Mode, it was an issue in the UI which @telpati had and now it's fixed. There is no transparency and the windows and menus look a little bit dark.

 

In his case the issue was the FakeSMC which had an extra entry for activating the AirPlay.

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

6 minutes ago, Cyberdevs said:

Because it's not the Dark Mode, it was an issue in the UI which @telpati had and now it's fixed. There is no transparency and the windows and menus look a little bit dark.

 

In his case the issue was the FakeSMC which had an extra entry for activating the AirPlay.

oh ok

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...