Jump to content
30960 posts in this topic

Recommended Posts

Hi

 

I don't understand well commit r4692: VirtualSMC support: checkout and compilation (XCODE5 only ATM)

 

I don't have virtualsmc-64.efi when I use my build script with Xcode 10. Tell me why, please.

 

Sorry if this comment is off-topic

Just an FYI, i installed 4674 on my legacy rig and I could not boot. Just got a (non-blinking) cursor in the upper left hand corner. I had to go back to 4658 in order to boot.

 

I also have a question about BIOS boot systems. There are four kexts, that I do not believe have anything to do with FileVault, listed in the "BIOS Drivers" section. But do they need to be installed? My system runs fine without them but not sure if I need them anyway:

 

  • FSInject
  • SMCHelper
  • ApfsDriver laoder
  • AppleEfiFat

 

Also, there are always some UEFI drivers that have check marks next to them even though I am insatlling on a BIOS based system. I always have to uncheck these.

 

 

11 hours ago, Slice said:

Highlighted drivers are not needed.

As well as AppleImageLoader.

 

Hi Slice,

 

I was under the impression that both ApfsDriverLoader-64.efi and AppleImageLoader-64.efI were required if not using APFS.efi?

13 minutes ago, D-an-W said:

 

Hi Slice,

 

I was under the impression that both ApfsDriverLoader-64.efi and AppleImageLoader-64.efI were required if not using APFS.efi?

Both not required.

[mention=112217]Slice[/mention]
What is AppleImageLoader for if its not mandatory? Is it part of FV too?
read here
https://github.com/acidanthera/AppleSupportPkg/blob/master/README.md

나의 LG-F800S 의 Tapatalk에서 보냄

941775925_ScreenShot1.png.676813a70b05786d296d934cbf095994.png
 
Sorry guys, but wasn't that suggested for clearing doubts about which drivers choose during installation?
FV-UEFI Drivers was the intent..  i guess
anyway thx for doing it
i found it. i will change it

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 3
52 minutes ago, ellaosx said:

I have read that. but still, is it part of FV or partner of ApfsDriverLoder that they must exist together?

 

i saw that

AppleImageLoader -> osxfatbinary driver replacement

AppleUISupport(AIO) -> Old FV2 drivers replacement

ApfsDriverLoader -> loading original apfs driver without manually adding and checking latest apfs file when update macOS

 

anyone who check package in english?

Edited by Sherlocks
  • Like 2
19 minutes ago, Sherlocks said:

AppleImageLoader -> osxfatbinary driver replacement

Ahh, i didn't know this. :)

Because the last time i asked, it was still under developement.

So its ok to replace osxfatbinary with appleimageloader now?

 

Thanks!

 

Edited by ellaosx
Ahh, i didn't know this.
Because the last time i asked, it was still under developement.
So its ok to replace osxfatbinary with appleimageloader now?
 
Thanks!
 
not yet. appleimageloader need more development to replace osxfatbinary. i checked this result. i recommend you use appleimageloader and osxfatbinary until complete appleimageloader. hope wait and appreciate to savvass for hard work


나의 LG-F800S 의 Tapatalk에서 보냄

44 minutes ago, Sherlocks said:

AppleUISupport(AIO) -> Old FV2 drivers replacement

 

 

are we still need AppleUISupport if we don't use FV2? I think it is in the release notes AppleImageLoader and AppleUISupport must be used together is that right?

 

are we still need AppleUISupport if we don't use FV2? I think it is in the release notes AppleImageLoader and AppleUISupport must be used together is that right?

actually no need both for boot if you don't need FV2. if you use FV2, not sure that must be use both. because i can't test FV2 by myself.

 

anyway in readme, AppleImageloader doesn't have FileVault word. mentioned only Fat word.

 

i think AppleUISupport is only for FV2

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

  • Like 1
  • Thanks 1
24 minutes ago, Sherlocks said:

actually no need both for boot if you don't need FV2. if you use FV2, not sure that must be use both. because i can't test FV2 by myself.

 

anyway in readme, AppleImageloader doesn't have FileVault word. mentioned only Fat word.

 

i think AppleUISupport is only for FV2

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

You're right about AppleUiSupport. It implements FileVault support and replaces AppleKeyMapAggregator.efi, AppleEvent.efi, AppleUiTheme.efi, FirmwareVolume.efi, AppleImageCodec.efi. (Readme.md from repo AppleSupportPkg) 

Edited by Matgen84
  • Like 2

Hi

 

I don't understand well commit r4692: VirtualSMC support: checkout and compilation (XCODE5 only ATM)

 

I don't have virtualsmc-64.efi when I use my build script with Xcode 10. Tell me why, please.

 

Sorry if this comment is off-topic

Thanks folks,

 

This is what I have now and both Sierra (10.12.6) and Mojave (10.41.1) boot just fine...

1734137962_ScreenShot2018-10-03at06_49_56.png.6255a75e6237960679f414375ffa994e.png

 

Now I just need to verify if I need SMCHelper-64.efi after checking my Kexts but I am almost certain I use the Kozlek one built with HWMonitor.

 

 

EDIT: Using either FakeSMC.kext (Slice or Kozlek) and with SMCHelper-64.efi present I get this is my Config.plst...

575873765_ScreenShot2018-10-03at23_02_06.png.b5628095c926d95713413687fd66f9b4.png

 

Removing SMCHelper-64.efi and with the Kozlek FakeSMC.kext I get this...

1847728854_ScreenShot2018-10-03at23_02_38.png.92c93ec63fe6c9be14e7287d6ae309df.png

 

So it would appear SMCHelper-64.efi is having an effect with that version of FakeSMC.kext loaded?

Edited by D-an-W
  • Like 1

@Slice

i install osx ubuntu and windows on same disk in uefi mode but after installing ubuntu my clover bootloader entries  from bios also force boot to grub bootloader how to fix this.

No matter what entry i choose from boot menu it always boot to grub and from them i can only boot to windows or ubuntu but cant find clover.

how to fix this issue??

pls help me

1 hour ago, Faradis said:

@Slice

i install osx ubuntu and windows on same disk in uefi mode but after installing ubuntu my clover bootloader entries  from bios also force boot to grub bootloader how to fix this.

No matter what entry i choose from boot menu it always boot to grub and from them i can only boot to windows or ubuntu but cant find clover.

how to fix this issue??

pls help me

Boot into Windows. Download EasyUEFI, and create new boot entries for Clover and Windows. Choose the EFI boot loader for each OS located in their folder in the EFI folder of the EFI partition. The BootX64.efi is the default loader. Compare it (file size) with the Ubuntu or other loaders to see which one it is. You can replace it with the Clover or Windows efi boot loader.

×
×
  • Create New...