Jump to content
fantomas1

[pre-release] macOS Mojave

2,463 posts in this topic

Recommended Posts

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.

Share this post


Link to post
Share on other sites
Advertisement
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...

Share this post


Link to post
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

Share this post


Link to post
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 ...

Share this post


Link to post
Share on other sites

Hi all, after a few days absence,

I'm back and made all the updates successfully and just now made the last update Mojave beta8 (build 18A371a), and all works as it should... not necessary to update or re install any kexts...

Captura de ecrã 2018-08-20, às 18.17.13.png

Edited by MorenoAv

Share this post


Link to post
Share on other sites

Update on X-99 to 18A371a

Captura de ecrã 2018-08-20, às 23.37.36.png

Captura de ecrã 2018-08-20, às 23.37.56.png

Edited by Fergarth
Yeap, plus a Mojave update on the X-99 with Haswell-E without any problems and as always with everything running, even without native support! The question is: Why do I always have KP on the Skylake Laptop with native support???

Share this post


Link to post
Share on other sites
4 minutes ago, Badruzeus said:

Thanks to @savvas, afaik we currently have our own OpenSource version of APFSDriver*.efi here, if I'm not mistaken.

 

Thanks, that's pretty cool. Is it better/more stable/something something more features, than the vanilla Apple driver? :lol: Lke, we have an open source vbox driver, but everyone says that the vanilla HFS is better. 

Share this post


Link to post
Share on other sites
34 minutes ago, iRipper said:

 

Thanks, that's pretty cool. Is it better/more stable/something something more features, than the vanilla Apple driver? :lol: Lke, we have an open source vbox driver, but everyone says that the vanilla HFS is better. 

 

Depends. But it seems, there's no difference on my 5400rpm SATA Mechanical HDD #LoL :P

Share this post


Link to post
Share on other sites

Successful upgrade of all my systems in signature to DB8_18A371a.

 

Skylake NUC6i5SYH, legacy BIOS GA-P55AUD3 desktop and legacy notebook Dell XPSM1530...

Spoiler

 

NUC6i5SYH_DB8_18A371a.thumb.png.d4415e7adc9b3d017a9b6fab24fb6683.pngGAP55AUD3_DB8_18A371a.thumb.png.f75d4108a90cf2ae2cc97f59e5d3941b.pngXPSM1530_DB8_18A371a.thumb.png.c30c1bb98e149cb4b8335002f73f4a0d.png

 

 

 

The legacy systems were upgraded in place after making a full installer USB, patched with @dosdude's macOS Mojave patcher - XPS with Mojave on HFS+ and P55AUD3 with Mojave on apfs volume.  The AMD HD5770 works OK but unfortunately without graphics acceleration, despite adding graphics kexts for HD5000 from High Sierra.  On the other hand, QE/CI was still possible with legacy GeForce tesla kexts for the 8600M GT.

 

As before, on first boot (in single user mode) for my Core2Duo laptop, I ran @crazybirdy's mojave2core ---> patch com.apple.telemetry.plugin, then updated system caches/prelinked kernel...


 

fsck -fy

mount -uw /

/usr/bin/mojave2core

touch /System/Library/Extensions && kextcache -u /

reboot

 

The Skylake NUC upgraded painlessly by directly running the full installer "Install macOS Mojave Beta.app"  :).

 

16 hours ago, Fergarth said:

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

 

Hi @Fergarth,

 

Your kernel panic log unfortunately doesn't point to a specific culprit :(.

 

However, I noticed that unlike my Skylake NUC, your system needs IntelGraphicsDVMTFixup.kext.  The version in your EFI folder is 1.2.0, but the latest v1.2.2 requires Lilu 1.2.4 or newer (you have v1.2.3) ---> maybe worth upgrading both your Lilu & IntelGraphicsDVMTFixup kexts.

 

Alternatively, you might be able to substitute IntelGraphicsDVMTFixup.kext with Clover patching of AppleIntelSKLGraphicsFramebuffer.kext.

 

On an unrelated note, I would recommend @savvamitrofanov's ApfsDriverLoader-64.efi instead of apfs.efi and ApfsJumpStart.efi in /drivers64UEFI.

 

Good Luck!

Edited by fusion71au
Comment for @Fergath's question

Share this post


Link to post
Share on other sites
7 hours ago, fusion71au said:

On an unrelated note, I would recommend @savvamitrofanov's ApfsDriverLoader-64.efi instead of apfs.efi and ApfsJumpStart.efi in /drivers64UEFI.

 

 

Hi,

 

On a HDD with High Sierra, I use apfs.efi patched without apfsJumpStart in /drivers64UEFI: it seems to work fine; On my HDD Mojave, I use ApfsDriverloader and AppleImageloader in drivers64UEFI: works fine of cause. I don't understand well the difference between these two method.

Can you explain, please

 

 

Sorry for my bad English.

Share this post


Link to post
Share on other sites

Some strange error for me when trying to update via software update... I thought at first it's because I having long old build (DP1) but after I download DP7 from MAS and (clean) reinstalling it, the problem still there, can't update via SU.

822759681_ScreenShot2018-08-21at14_53_48.png.33237c9d83579a9cc2c172f4c14fb143.png

 

no ethernet error btw, because I can connect into my iTunes/iCloud account. And no problem at all on updating Mojave beta on my MBA & MBP...

 

561376846_ScreenShot2018-08-21at15_34_41.thumb.png.0e13bfe35a8c2565051f962a8f018aa3.png

log related to this...

 

UPDATE:  the update works after I plugged my ethernet cable, turning off my wifi. click update, progress bar shows but no sign of life. click update again and that error shows again. this time with wifi turning on and ethernet plugged, clicked again and works....

 

1416986397_ScreenShot2018-08-21at15_46_39.png.75d95cf2c2e3d1f846b006db122c59ca.png

Edited by memedmedio
update

Share this post


Link to post
Share on other sites
41 minutes ago, Matgen84 said:

 

Hi,

 

On a HDD with High Sierra, I use apfs.efi patched without apfsJumpStart in /drivers64UEFI: it seems to work fine; On my HDD Mojave, I use ApfsDriverloader and AppleImageloader in drivers64UEFI: works fine of cause. I don't understand well the difference between these two method.

Can you explain, please

 

 

Sorry for my bad English.

 

Hi @Matgen84,

 

From the readme for ApfsDriverLoader, it is an

 

Open source apfs.efi loader based on reverse-engineered Apple's ApfsJumpStart driver

  • Loads apfs.efi from ApfsContainer located on block device.
  • Apfs driver verbose logging suppressed.
  • Version system: connects each apfs.efi to the device from which it was retrieved
  • Supports AppleLoadImage protocol provides EfiBinary signature check
  • WARNING: Please load AppleImageLoader.efi right before ApfsDriverLoader, or just put it inside drivers64uefi folder of your Clover bootloader

In other words, it is chain loading the apfs.efi driver that is already embedded in the apfs volume, just like Apple's EFI firmware.  Advantages include much smaller file size compared to including apfs.efi in the Clover.pkg, no verbose output and no need to update Clover.pkg with each macOS update (the driver always loads the correct version of apfs.efi that is appropriate to the macOS being loaded).

Edited by fusion71au
typo

Share this post


Link to post
Share on other sites
45 minutes ago, fusion71au said:

 

Hi @Matgen84,

 

From the readme for ApfsDriverLoader, it is an

 

Open source apfs.efi loader based on reverse-engineered Apple's ApfsJumpStart driver

  • Loads apfs.efi from ApfsContainer located on block device.
  • Apfs driver verbose logging suppressed.
  • Version system: connects each apfs.efi to the device from which it was retrieved
  • Supports AppleLoadImage protocol provides EfiBinary signature check
  • WARNING: Please load AppleImageLoader.efi right before ApfsDriverLoader, or just put it inside drivers64uefi folder of your Clover bootloader

In other words, it is chain loading the apfs.efi driver that is already embedded in the apfs volume, just like Apple's EFI firmware.  Advantages include much smaller file size compared to including apfs.efi in the Clover.pkg, no verbose output and no need to update Clover.pkg with each macOS update (the driver always loads the correct version of apfs.efi that is appropriate to the macOS being loaded).

Thanks a lot for your explanation

Share this post


Link to post
Share on other sites
13 hours ago, al6042 said:

Runs over here too:

macOS10.14DevBeta8.png.e385aafd4d5bf4d96dfb4adea5ecf1c8.png

And the USB-Port-Limit-Patch still works... :D

Which USB patch are you using? 

Share this post


Link to post
Share on other sites

@DocXavier I use the following KextToPatch:

 

Name = com.apple.driver.usb.AppleUSBXHCI
Find [HEX] = 83FB0F0F 83030500 00

Replace [HEX] = 83FB1A0F 83030500 00
Comment = Remove 15 port limit completely 10.14 sin DevBeta2

Share this post


Link to post
Share on other sites
17 hours ago, memedmedio said:

Some strange error for me when trying to update via software update... I thought at first it's because I having long old build (DP1) but after I download DP7 from MAS and (clean) reinstalling it, the problem still there, can't update via SU.

822759681_ScreenShot2018-08-21at14_53_48.png.33237c9d83579a9cc2c172f4c14fb143.png

 

no ethernet error btw, because I can connect into my iTunes/iCloud account. And no problem at all on updating Mojave beta on my MBA & MBP...

 

561376846_ScreenShot2018-08-21at15_34_41.thumb.png.0e13bfe35a8c2565051f962a8f018aa3.png

log related to this...

 

UPDATE:  the update works after I plugged my ethernet cable, turning off my wifi. click update, progress bar shows but no sign of life. click update again and that error shows again. this time with wifi turning on and ethernet plugged, clicked again and works....

 

1416986397_ScreenShot2018-08-21at15_46_39.png.75d95cf2c2e3d1f846b006db122c59ca.png

 

I had a similar issue, I reran the Beta Auth tool from page 1 and it updated just fine.

 

HBP

Share this post


Link to post
Share on other sites
10 hours ago, al6042 said:

@DocXavier I use the following KextToPatch:

 

Name = com.apple.driver.usb.AppleUSBXHCI
Find [HEX] = 83FB0F0F 83030500 00

Replace [HEX] = 83FB1A0F 83030500 00
Comment = Remove 15 port limit completely 10.14 sin DevBeta2

It works fine in my hack. Thanks ¡¡¡

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×