Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

apianti
apianti
Posted
Posted

@Slice,
 
Can you please build a new package for sf.net because of new AptioFix?
 

I loaded apfs.efi using efi_disk_io_protocol.  But what about FV2 encrypted system partition? 
I have no idea how Apple load apfs.efi from FV2 encrypted partition using block io..

How are you savvas.. Any progress of this? :)

 
He seemed to have figured out that the APFS container itself holds a record to where the driver is on disk and loads it.

 

I remember that you PM me about this question.
Of course it is possible, but there is no need to do this, because we already use refit volume handler inside Clover. I'm working on own implementation of APFS jump start driver. Just wait a bit. I have a lot of work and all of my contribution in Clover just a hobby.
Currently, I am not satisfied with my algorithm for searching and reading "JSDR" block via EFI_DISK_IO_PROTOCOL, I'll need to do it much more accurate.
For now, I'm working on generating
"NXSB - > apfs offset id -> blockmap"
"blockmap -> apfs offsetid -> block number"
"block number -> APSB -> root"
structure to find JSDR faster inside apfs partition superblocks (apsb).
If someone interesting in this, I can post my full research with descriptions how APFS works, and how Apple loads driver from APFS_EFI_Boot_Record in UEFI.

 

Also just for your knowledge, EFI_DISK_IO_PROTOCOL is just a wrapper around EFI_BLOCK_IO_PROTOCOL to allow reading random sizes at random disk offsets. If you want to just use EFI_BLOCK_IO_PROTOCOL then you need to figure out which block the offset for the driver starts, then read as many device blocks as the size of the driver (accounting for that it may not be aligned to the beginning of the block). You then need to trim the parts off the beginning and end that do not actually belong to the driver. I have a feeling however that the driver is probably perfectly aligned on a block and even though it says some exact byte size, if you round that up to the next multiple of the block size then it's probably zeroed out and you can just load the blocks start from the offset. I think probably everyone is interested in the research BTW.

  • Like 1
vandroiy2012
vandroiy2012
Posted
Posted

@Slice,

 

Can you please build a new package for sf.net because of new AptioFix?

 

Hi. 

 

I think this new AptoFix should be separate file (ex. OsxAptioFix3Drv.efi) because several users on applelife already reported problems with hibernation with new version. 

  • Like 2
cecekpawon
cecekpawon
Posted
Posted

He seemed to have figured out that the APFS container itself holds a record to where the driver is on disk and loads it.

Also just for your knowledge, EFI_DISK_IO_PROTOCOL is just a wrapper around EFI_BLOCK_IO_PROTOCOL ..

 

Yes, I believe so, but he just gone. Thanks apianti, but my brainfart cant handle all of those parts..

 

Hi. 

 

I think this new AptoFix should be separate file (ex. OsxAptioFix3Drv.efi) because several users on applelife already reported problems with hibernation with new version. 

 

Sorry to interrupt, did you managed to safe-boot with OsxAptioFix2/3? Any special sip values to be used for this purpose?

PMheart
PMheart
Posted
Posted

Sorry to interrupt, did you managed to safe-boot with OsxAptioFix2/3? Any special sip values to be used for this purpose?

Hi, so far I have never managed to boot -x with AptioFix v2/v3... Only OsxAptioFix2Drv-free2000.efi did the trick. Also, CsrActiveConfig is not specified.

mhaeuser
mhaeuser
Posted
Posted

Hi.

 

I think this new AptoFix should be separate file (ex. OsxAptioFix3Drv.efi) because several users on applelife already reported problems with hibernation with new version.

I never understood why dmazar drops the MemoryMapHandoff... The comments suggest it was for the same reason as removing RT flags, but latter code was removed. Might have been a fix to ghost issues caused by the RT drivers writing into Nirvana. Did anyone test an AF2 without that drop?

Also, I don't remember now if I called the restore code on hibernate image entry, can somebody verify (phone...)?

 

EDIT: whoops, not calling the protection code on hibernate wake. Can you fix that, apianti?

 

Also, will somebody with an A5 bother to test hibernation after that, with and without dropping the MemoryMap handoff?

cecekpawon
cecekpawon
Posted
Posted

Hi, so far I have never managed to boot -x with AptioFix v2/v3... Only OsxAptioFix2Drv-free2000.efi did the trick. Also, CsrActiveConfig is not specified.

 

Hey where have you been? Thanks.. I thought it was just me. AptiofixV1 had no problem to boot with -x here :)

PMheart
PMheart
Posted
Posted

Hey where have you been? Thanks.. I thought it was just me. AptiofixV1 had no problem to boot with -x here :)

The life of pre-university is kind of busy so I hardly get an appropriate time to visit IM... Fortunately it's now about to be the vacation. :)

Oh yes, but you have to disable SIP NVRAM Protection/Restriction (CsrActiveConfig = 0x40) with AptioFix v1.

  • Like 1
apianti
apianti
Posted
Posted

Nah, hibernation just wasn't fixed with the changes though I'm not sure it's exactly fixed correctly now. There is not going to be MORE AptioFix that's for sure, trying to get rid of them all but one. Stop trying to make more. Stop it. Stop. Please. Stop. I beg of you.

 

 

OK, but I not sure that all correct because I am not at home.

 

Ah yes, it has issues but no more than it already did. Just different ones. It should be cool now though, except the hibernation memory handoff. I'm pretty sure that there's still a problem there....

maleorderbride
maleorderbride
Posted
Posted

Can anyone help with this panic on a 10.13.2 install? First startup (I cloned a working install to it). I tried dropping MATS and some other tables, but no luck.

Is there a way I can check my tables to see which one is causing this problem? Or is it something else entirely?

FakeSMC is 6.25.

 

Also, does Inject EDID work in Clover if you do not have AMD/Nvidia/Intel injection set to True?

 

Thanks!

 

post-358090-0-34355300-1515270682_thumb.jpg

maleorderbride
maleorderbride
Posted
Posted

Looks like the same problem, try adding config.plist/DSDT/Fixes/FixHeaders=true.

 

Thanks. I should have tried that earlier.

That gets me past it. Now to figure out my bizarre EDID issue, or whatever it is.

 

When I run ioreg -l | grep "IODisplayEDID" , I get no output.

 

I have the below in my config. What I am doing wrong that the OS is not seeing that EDID?

<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<true/>
		</dict>
		<key>EDID</key>
		<dict>
			<key>Inject</key>
			<true/>
			<key>Custom</key>
			<data>AP///////wBMo08xAAAAAwAZAQS1Hyp4Cg+VrlJDsCYPUFQAAAABAQEBAQEBAQEBAQEBAQEB+anKZIC4VrAYEFUAKo0RAAAYAAAAAQAAAAAAAAAAAAAAAAAAAAAA/gBTQU1TVU5HICAgICAgAAAA/gBMVE0yODJSTDAxICAgAEg=</data>
			<key>VendorID</key>
			<string></string>
			<key>ProductID</key>
			<string></string>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
	</dict>
kgp
kgp
Posted
Posted

I assume you're using AptioFix1... to use AptioFix1, update to r4369 or switch to using AptioFix2.

 

Yes, I use OsxAptioFixDrv-64.efi + Test2-2016.efi..

 

Switched now to Clover r4369... 

 

Everything works again as expected.. Many thanks for the extremely useful hint. 

 

However, like in Clover r4366, I am not able to boot the 10.13.2 USB Flash Drive Installer with SMBIOS iMacPro1,1. 

 

Guess the problem is however not Clover.. The problem might be that the iMacPro BoardID and iMacPro1,1 ModelProperties are not part of the PlatfromSupport.plist of the macOS 10.13.2 Installer Package. 

apianti
apianti
Posted
Posted

Yes, I use OsxAptioFixDrv-64.efi + Test2-2016.efi..

 

Switched now to Clover r4369... 

 

Everything works again as expected.. Many thanks for the extremely useful hint. 

 

However, like in Clover r4366, I am not able to boot the 10.13.2 USB Flash Drive Installer with SMBIOS iMacPro1,1. 

 

Guess the problem is however not Clover.. The problem might be that the iMacPro BoardID and iMacPro1,1 ModelProperties are not part of the PlatfromSupport.plist of the macOS 10.13.2 Installer Package. 

 

They are not supported fully yet. But you should not be using those two drivers together, ever. Please remove those two drivers and use only the newest revisions AptioFix2. You may need to add a slide=N argument if it doesn't find a region to place the kernel.

  • Like 2
kgp
kgp
Posted
Posted

They are not supported fully yet. But you should not be using those two drivers together, ever. Please remove those two drivers and use only the newest revisions AptioFix2. You may need to add a slide=N argument if it doesn't find a region to place the kernel.

 

Is there any reason why I should not use these two drivers together with Skylake-X/X299? They work absolutely flawless, while AptioFix2 still leads to occasional memory allocation errors at early boot... 

apianti
apianti
Posted
Posted

Is there any reason why I should not use these two drivers together with Skylake-X/X299? They work absolutely flawless, while AptioFix2 still leads to occasional memory allocation errors at early boot... 

 

You should try using just AptioFix2 with r4369. It should work. The memory allocation error is another issue, it should not happen as often now as not as much will be needed without relocating runtime. That's due to firmware memory fragmentation. The reason not to use the two drivers is because first they are meant to only be used alone. Second, the one not named AptioFix just deletes random memory below a certain address with no idea what the memory is used for...

  • Like 2
kgp
kgp
Posted
Posted

You should try using just AptioFix2 with r4639. It should work. The memory allocation error is another issue, it should not happen as often now as not as much will be needed without relocating runtime. That's due to firmware memory fragmentation. The reason not to use the two drivers is because first they are meant to only be used alone. Second, the one not named AptioFix just deletes random memory below a certain address with no idea what the memory is used for...

 

O.k. thanks for the details.. I will try to use AptioFix2 with the slide boot flag.. Without this boot flag I get a print,f error at early boot... slide=0 is fine or do I really have to use slide=N?   

apianti
apianti
Posted
Posted

O.k. thanks for the details.. I will try to use AptioFix2 with the slide boot flag.. Without this boot flag I get a print,f error at early boot... slide=0 is fine or do I really have to use slide=N?

 

Once you get into the clover GUI, you need to go into the EFI shell and use the memmap command find the available region that has the largest space and calculate the slide value. You do that by taking the address of the region you found, subtract 0x100000 then divide by 0x200000. Now you have the slide value, you must make sure it is good. Do the calculation 0x100000 + (slide * 0x200000). That should give you the same address of the free area, if not add one to the slide or find another region and repeat.

 

EDIT: It's also ok if address calculated with the slide just offsets slightly into the region as long as there is still enough space for the kernel to load, usually around 0x12000 pages is good enough.

where do I get r4639?

I guess that's just a typo.. I guess it should properly read r4369...

 

Yes it's a typo, I fixed it, meant r4369.

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