Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Funky frank
Funky frank
Posted
Posted

Is there any really recent DSDT from Apple hardware available?  I have seen that the Sierra 10.12.4 update ships with lots of EFI updates, I guess to fix the new installer path, but also to exclude old Macs?   Anyway maybe those updates then contain a recent ACPI / DSDT, too?

mhaeuser
mhaeuser
Posted
Posted

Is there any really recent DSDT from Apple hardware available? I have seen that the Sierra 10.12.4 update ships with lots of EFI updates, I guess to fix the new installer path, but also to exclude old Macs? Anyway maybe those updates then contain a recent ACPI / DSDT, too?

EFI does not contain installer paths and because there is one image for every model, excluding Macs is nonsense. And even if either was the case, it would not be done via ACPI.
Funky frank
Funky frank
Posted
Posted

EFI does not contain installer paths and because there is one image for every model, excluding Macs is nonsense. And even if either was the case, it would not be done via ACPI.

Huh but cover does... By installer paths I mean paths to boot.efi, that path had changed with 10.12.4. If there are more efi updates missing, for example for late imac 2007, this device won't be able to load boot.efi.

mhaeuser
mhaeuser
Posted
Posted

Huh but cover does... By installer paths I mean paths to boot.efi, that path had changed with 10.12.4. If there are more efi updates missing, for example for late imac 2007, this device won't be able to load boot.efi.

One more time, EFI does not contain installer paths and that Clover does is irrelevant.
apianti
apianti
Posted
Posted

 

This really should not be coded like this, why have that array of paths if you are going to hard code it in two other locations as well? Those two sections should be rewritten to use that already created array of paths to prevent having to add three separate things if a path is changed. You can make the array into an array of arrays of two strings (CHAR16 *[COUNT][2] = { { Path1, Desc1 }, { Path2, Desc2 } }; ) that way even the last one can just loop through the array and add the loaders...

 

EDIT: Didn't want a blinky emoji, wanted a semi colon and a close parenthesis.

Is there any really recent DSDT from Apple hardware available?  I have seen that the Sierra 10.12.4 update ships with lots of EFI updates, I guess to fix the new installer path, but also to exclude old Macs?   Anyway maybe those updates then contain a recent ACPI / DSDT, too?

 

Actually there is a mechanism in EFI called BootNext, which is assigned to the loader to boot next, which is all the installer does. For some reason, I think because the loader entry it points to is in the wrong format, PC UEFI does not boot using this variable when the mac OS installer sets BootNext. It is immediately cleared upon read for use by the firmware, so it is not available to anything but the pre initialization boot, which you can't access unless you mod your firmware.

 

EDIT: More information.

Will clover soon support AFS? Just curious, since Apple seems to roll out AFS in next Upgrade 10.13...

 

Silly question. How will old macs support it? Through a firmware upgrade that will add a driver just like HFSPlus.efi and then it will be extracted and used.

  • Like 1
smolderas
smolderas
Posted
Posted

apfs.efi is located in /usr/standalone/i386 under 10.12.5 Beta. (Sorry. IDK what about 10.12.4...)

 

Well, but I guess Apple just adds it for experimental purposes.

Most interesting...

 

Edit: So sierra supports bootable apfs containers?

apianti
apianti
Posted
Posted

The installer uses bless. Maybe BootNext too, but not to store the boot file path.

 

The installer uses Boot0082 (I think thats the one) to store boot data and BootNext is a number pointing to which Boot variable to use in booting this one next time. The path in Boot0082 is possibly just to the volume (I'm pretty sure it is), making it not suitable for PC UEFI booting and moves onto the BootOrder list, etc. However, Apple EFI inspects the volume for the blessed boot data because bless is filesystem based NOT firmware and will then boot that before moving onto the BootOrder variable and the rest of the boot options.

 

apfs.efi is located in /usr/standalone/i386 under 10.12.5 Beta. (Sorry. IDK what about 10.12.4...)

 

Well, but I guess Apple just adds it for experimental purposes.

Its also there.

 

Then there's the answer take that driver and put it in the appropriate drivers folder for clover and you can read AFS volumes. Note you won't be able to boot clover from an AFS volume but mac OS, yes.

 

Most interesting...

 

Edit: So sierra supports bootable apfs containers?

 

I'm guessing if you decide to create an encrypted volume then this driver will be on the recovery which actually boots and decrypts the volume to boot. Or in the firmware. It couldn't actually be started without loading that driver from some already readable filesystem.

apianti
apianti
Posted
Posted

Oh I mentioned this to others but I forgot to mention it to you, Slice. There is a bug in EDK build system that it doesn't properly rebuild an object if a file it includes changes. So in order for a build that's not messed up in some way you need to completely clean the build and rebuild.

  • Like 1
mhaeuser
mhaeuser
Posted
Posted

The installer uses Boot0082 (I think thats the one) to store boot data and BootNext is a number pointing to which Boot variable to use in booting this one next time. The path in Boot0082 is possibly just to the volume (I'm pretty sure it is)

Yes, I only said it is not used to store the boot file path, because that's done via bless. Though seems like an endless list of boot.efi paths looks nicer than just using bless...

making it not suitable for PC UEFI booting

Except for these solutions that add proper 'Apple compatibility'. :P

Apple EFI inspects the volume for the blessed boot data because bless is filesystem based NOT firmware

'NOT firmware' as in it's not an EFI concept? Not sure what you mean, but the blessed path is deffo stored in the FS header, yeah.

  • Like 1
PMheart
PMheart
Posted
Posted

Its also there.

Thanks for you confirmation!

 

 

Most interesting...

 

Edit: So sierra supports bootable apfs containers?

 

Well, perhaps, I don't think so though... (I guess they should bring full compatibility at least on 10.13...)

 

Then there's the answer take that driver and put it in the appropriate drivers folder for clover and you can read AFS volumes. Note you won't be able to boot clover from an AFS volume but mac OS, yes.

All right, don't tend to say anything here... Just waiting for Apple for more new stuffs. :)

 

10.12.4 also added firmware updates (which contain the ApfsJumpstart driver). 

 

Yup. We've discussed it before!  :yes:

 Share
Go to topic listing
×
×
  • Create New...