Jump to content
vit9696

AptioMemoryFix

495 posts in this topic

Recommended Posts

Advertisement

No issue here in my both rigs AptioMemoryFix R9 works well like R8

Compilling by me inside edk2/Clover

Thank you all

Share this post


Link to post
Share on other sites

No sorry and no inconvenience

Thank you for your great effort and free work for us

I will test by now and report (if I will be able to compile it)

 

The latest version from git (marked as R10) should have it fixed. Sorry for inconvenience.

Edited by fabiosun

Share this post


Link to post
Share on other sites

@vit9696 

cold boot is working now

I have a non working Nvram (as always) but I don't use any script or emu variable to have Nvidia dev set to 1

now (system starts fine but with osx default Nvidia driver as you can see)

try by now to reselect it and reboot..

 

post-468967-0-29054700-1517762437_thumb.png

Share this post


Link to post
Share on other sites

@vit9696 

cold boot is working now

I have a non working Nvram (as always) but I don't use any script or emu variable to have Nvidia dev set to 1

now (system starts fine but with osx default Nvidia driver as you can see)

try by now to reselect it and reboot..

Nice, thx for the report. For nvram I cannot say much, there still are appear to exist motherboards where it does not work. Generally the case is ASUS whitelist, which requires flashing an older nvram driver, but honestly there may be other issues too. All of them are almost certainly our of the scope of AptioMemoryFix, however.

Share this post


Link to post
Share on other sites

I know about your efi scope and I was reporting it because for me from RC5 it helped so much in automatic way

By the way I have also CSM enabled which is adviced to disable in read.me

For me now is working well and after a reboot Nvidia driver is set fine again to Webdriver option

 

Thank you again

 

Nice, thx for the report. For nvram I cannot say much, there still are appear to exist motherboards where it does not work. Generally the case is ASUS whitelist, which requires flashing an older nvram driver, but honestly there may be other issues too. All of them are almost certainly our of the scope of AptioMemoryFix, however.

Share this post


Link to post
Share on other sites

On all my systems in signature AptioMemoryFix working perfect except two systems both Gigabyte Z77X i7-3770K and Gigabyte Z68X i7-2600K.  Occasionally I get the "Does PrintF work?".   The fix for me is to power off, pull the power cord wait a few seconds for all caps to discharge then power up.  The version I am using was installed from Clover 4392.

 

What is AptioInputFix used for?

 

Thanks!

 

Edited 2-5-18

 

Github explained my other questions.  I believe the only time I get the Aptio "Does Printf Work?" is after a kernel panic.  After reading more on github I have to look into a boot.efi patch in order to get the specifics of that error.  The kernel panic was because of the table id "MATS", which I have now dropped in Clover Drop Table ID.

Share this post


Link to post
Share on other sites

The current driver revision are always here. It may appear very fast on your screen, hope your loader can do log that for you.

* Please ignore my current format (0.0.8), it should be (R8).

 

My bootlog doesn't show current version. Only "load success". I don't know why?

0:225  0:000  === [ LoadDrivers ] =======================================
0:244  0:019  Loading APFS.EFI  status=Success
0:258  0:013   - driver needs connecting
0:258  0:000  Loading AppleImageCodec-64.efi  status=Success
0:259  0:000  Loading AppleKeyAggregator-64.efi  status=Success
0:259  0:000  Loading AppleUITheme-64.efi  status=Success
0:260  0:000  Loading AptioMemoryFix.efi  status=Success
0:261  0:001  Loading CsmVideoDxe-64.efi  status=Success
0:262  0:000   - driver needs connecting
0:262  0:000  Loading DataHubDxe-64.efi  status=Success
0:292  0:030  Loading Fat-64.efi  status=Success
0:300  0:007   - driver needs connecting
0:300  0:000  Loading FirmwareVolume-64.efi  status=Success
0:302  0:002  Loading FSInject-64.efi  status=Success
0:303  0:001  Loading HFSPlus.efi  status=Success
0:304  0:000   - driver needs connecting

Share this post


Link to post
Share on other sites

 

My bootlog doesn't show current version. Only "load success". I don't know why?

0:225  0:000  === [ LoadDrivers ] =======================================
0:244  0:019  Loading APFS.EFI  status=Success
0:258  0:013   - driver needs connecting
0:258  0:000  Loading AppleImageCodec-64.efi  status=Success
0:259  0:000  Loading AppleKeyAggregator-64.efi  status=Success
0:259  0:000  Loading AppleUITheme-64.efi  status=Success
0:260  0:000  Loading AptioMemoryFix.efi  status=Success
0:261  0:001  Loading CsmVideoDxe-64.efi  status=Success
0:262  0:000   - driver needs connecting
0:262  0:000  Loading DataHubDxe-64.efi  status=Success
0:292  0:030  Loading Fat-64.efi  status=Success
0:300  0:007   - driver needs connecting
0:300  0:000  Loading FirmwareVolume-64.efi  status=Success
0:302  0:002  Loading FSInject-64.efi  status=Success
0:303  0:001  Loading HFSPlus.efi  status=Success
0:304  0:000   - driver needs connecting

Hi Matgen84

He explains here

 

http://www.insanelymac.com/forum/topic/331381-aptiomemoryfix/page-10?do=findComment&comment=2583761

Share this post


Link to post
Share on other sites

— Are you sure you follow the guidelines regarding recommended bios preferences? Particularly fast boot must be off.

 

 

Where can I find these recommended BIOS settings? I did not see in post #1?

Share this post


Link to post
Share on other sites

Hi, I'm struggling with my mobo which has always been awful regarding memory issues.

So far, only the 1st OSXAptiofix version got it to boot, from time to time.
It was broken with 10.13.1, ok with 10.13.2, then broken again with 10.13.3.
 
I tried to use the version 2 and calculate a slide value. Here's what I did :
 
Located this area that seemed to be sufficient :
available  000000000CF06000-00000000AD737FFF  00000000000A0832 000000000000000F
 
Calculated :
CF06000 - 100000 = CE06000
CE06000 / 200000 = 67
 
Did it backward to verify and noticed I had to increase it to 68.
 
Used slide=104
 
Problem is stil the same (error allocating blah page blah…)
Is there something I miss ? 

Share this post


Link to post
Share on other sites

Try increasing it one by one until it works. Or let the automatic choose for you.

 

EDIT: Also make sure that you are checking the memory map after you are in clover.

EDIT2: Use the AptioFix from here or AptioFix3 from the package.

Share this post


Link to post
Share on other sites

Hi Apianti, I already tried all the aptio fixes with no succes. I also tried with 105 but I'll try again increasing it more.

 

Try only using either of those two drivers, try every single slide if you have to, it may take a while but just to rule it out. There might be something else going on there. Does it tell you where it failed to allocate the memory? Like the address and how many pages? Did you try the AptioFix from here with no slide value, letting it choose one?

Share this post


Link to post
Share on other sites

Are you sure the memory is free at 0xd200000? Did you check the memory map after you entered clover GUI from EFI shell? Is it consistent? Also use AptioFix from this topic or AptioFix3 from the installer (they both may be in the installer?). Fix1 and Fix2 are inherently broken...

 

EDIT: Post your memmap from EFI shell after clover GUI.

Share this post


Link to post
Share on other sites

No I launched the shell from Bios because its the only way I can reach it. It crashes when launched from Clover, since a while the option is not even present anymore.

I already tried v3 and aptiofix r10

Share this post


Link to post
Share on other sites

There are several versions of the EFI shell you can try but I don't see why it would crash from clover but not the firmware, are there drivers being loaded that are causing problems? You need to put it in the tools folder and name it specific names to be found. Also make sure that GUI/Scan/Tool=true in config.plist. You need the memory map from after clover has reached the GUI, it's useless otherwise. Have you tried AptioMemoryFix without a slide letting it calculate one for you?

Share this post


Link to post
Share on other sites

The shell stopped working years ago, somewhere before builds 2000 of clover.

Ok, gonna check all that.

Edit : ok the scan option brought it back but it still crashes. I get a fix cursor on the upper left corner. I think it's again a memory issue because it does launch fine from clover in legacy mode.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×