Jump to content

[pre-release] macOS Mojave

fantomas

By fantomas,
in New Releases and Updates

 Share
2,429 posts in this topic

Recommended Posts

MorenoAv
MorenoAv
Posted
Posted (edited)

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
Link to comment
Share on other sites
Fergarth
Fergarth
Posted
Posted (edited)

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???
  • Like 4
Link to comment
Share on other sites
iRipper
iRipper
Posted
Posted
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. 

  • Like 2
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
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

  • Haha 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted (edited)

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
  • Like 4
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
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.

Link to comment
Share on other sites
memedmedio
memedmedio
Posted
Posted (edited)

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
  • Like 1
Link to comment
Share on other sites
fusion71au
fusion71au
Posted
Posted (edited)
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
  • Like 2
  • Thanks 4
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
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

Link to comment
Share on other sites
al6042
al6042
Posted
Posted

@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

  • Like 2
Link to comment
Share on other sites
HBP
HBP
Posted
Posted
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

  • Like 1
Link to comment
Share on other sites
edy
edy
Posted
Posted

Thank for everybody. Now working like that - old board, old CPU, old graphics adapter -but new OS .Last update was not easy, now I have such a system. Original's system Dell Vostro  230. Problem off/sleep 

Снимок экрана 2018-08-22 в 17.44.31.jpeg

Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted

Guys is it just me or the AirPortAtheros40.kext won't work on TP-Link WD4800 WiFi in DP8 any more??

I just copied the kext from High Sierra like I did with all the betas but it won't load in DP8.

 

@SavageAUS does it work on your end? Have you tested it yet?

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted
Guys is it just me or the AirPortAtheros40.kext won't work on TP-Link WD4800 WiFi in DP8 any more??

I just copied the kext from High Sierra like I did with all the betas but it won't load in DP8.

 

[mention=1083558]SavageAUS[/mention] does it work on your end? Have you tested it yet?

no more load 40.kext in DP8? really? yet, i'm not test it on 4230s

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

  • Sad 1
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
Just now, Sherlocks said:

no more load 40.kext in DP8? really?emoji27.png

Yup, it's not working anymore, Apple removed support for Atheros wifi adapters in Mojave but I could add the AirPortAtheros40.kext in the /S/L/E from High Sierra but it doesn't seem to work in DP8 anymore. :no:

I'm still waiting for other guys to confirm it! 

  • Like 1
Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted
Yup, it's not working anymore, Apple removed support for Atheros wifi adapters in Mojave but I could add the AirPortAtheros40.kext in the /S/L/E from High Sierra but it doesn't seem to work in DP8 anymore. :no:
I'm still waiting for other guys to confirm it! 
how about 40.kext in DP7? now i don't have time for 4230s. i'm fucus on clover. 4230s's 40.kext is no problem in DP7.

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...