AptioMemoryFix

[vit9696]

This is not unexpected and comparably obvious from the AptioMemoryFix code. Modern boards need AptioMemoryFix primarily to preserve RT areas from relocation during boot.efi start, as they are not relocatable on APTIO, and break NVRAM support. Failing to do so will break NVRAM and Hibernation at the very least, and cause random memory corruptions in worse cases with successful boots.

 

In my opinion, little theorisation is needed here, and more actual research with a proper understanding of APTIO firmware and AptioMemoryFix logic.

[Pene]

I understand. I was actually surprised that it works consistently, so I thought it might be worth mentioning.

 

Speaking of random memory corruption, I'll mention a strange issue which I had several times on both my previous (Z370) and current (Z390) boards, when at some point both my NVMe SSDs (not even the same manufacturer) start to develop data corruption on all partitions (APFS/NTFS). Strangely, this corruption appears at some point together on both NVMe SSDs (SATA not affected), and on all partitions. Probably unrelated to AptioMemoryFix (I suspect AppleNVMe) but I'm mentioning it in case you consider it might somehow be.

 

Anyway, enough with theorisation... I'll gladly put the time needed in the research, when you have the time to help with the necessary code needed

Edited January 29, 2019 by Pene

[mhaeuser]

@Pene Does the drive happen to be a Samsung OEM model?

[Pene]

22 minutes ago, Download-Fritz said:

@Pene Does the drive happen to be a Samsung OEM model?

Nope.

I know about the PM981/PM961 problems, and it's not one of these.

Happened to me on two different motherboards (my prev Z370 and current Z390) and 3 different drives:

- Retail Samsung 970 Evo 1TB

- Plextor M8Pe 1TB

- Plextor M9Pe 1TB

Happens about every 2-3 months :/

Edited January 30, 2019 by Pene

[joevt]

I have come across a situation where adding dart=0 to config.plist boot args or disabling VT-d in BIOS or dropping DMAR tables causes a driver for an audio device using the VT1712 PCI Multi-Channel Audio Controller to fail. The data sheet for the VT1712 explains that some DMA addresses are limited to 28 bits (the first 256 MB of memory).

 

The driver kext is unable to use IOBufferMemoryDescriptor::inTaskWithPhysicalMask to allocate 192K (48 pages) of physically contiguous memory in the first 256 MB of RAM unless dart is not disabled, VT-d is enabled, and DMAR tables are not dropped, but this causes problems with some Hackintoshes (USB not working, no boot, etc.).

 

I am wondering if there is no space for any size of memory allocation (such as one 4K page) in the first 256 MB, or if the problem is fragmentation where there is no contiguous range of memory containing 48 free pages. I also wonder if AptioMemoryFix can help with this situation with some modification.

 

The driver works with VT-d (through the AppleVTD driver I guess) because the IOMMU can create a range of contiguous I/O addresses for the DMA operation that map to discontiguous physical pages.

 

I have started to look into this situation by writing a test kext to test different memory allocations. I'll probably have to look at MemoryMap in boot_args, building my own kernel for debugging, etc.

 

Has anyone come across this problem before or know if a solution is possible or not?

 

        if ((membuf[0] = IOBufferMemoryDescriptor::inTaskWithPhysicalMask(kernel_task, kIOMemoryPhysicallyContiguous, 192*1024, 0x0ffff000)))
        {
            IOLog("Hack: Got 192K at %llx\n", membuf[0]->getPhysicalAddress());
        }
        else
        {
            IOLog("Hack: Failed to get 192K\n");
        }

 

Edited March 6, 2019 by joevt

[apianti]

Write a patch to change the maximum location for the allocation of the buffer and see if that solves the issue, with all that still disabled.

 

EDIT: Oh, I should read more closely. There's only 28 bits, so yeah you need a fix I've been talking about for a while. You need everything in the UEFI environment to be allocated in as high of memory as possible to leave the low memory free for usage by stuff like this that causes problems.

Edited February 20, 2019 by apianti

[joevt]

2 hours ago, apianti said:

Write a patch to change the maximum location for the allocation of the buffer and see if that solves the issue, with all that still disabled.

 

EDIT: Oh, I should read more closely. There's only 28 bits, so yeah you need a fix I've been talking about for a while. You need everything in the UEFI environment to be allocated in as high of memory as possible to leave the low memory free for usage by stuff like this that causes problems.

I can allocate 192K using a full 32 bits, but I can't allocate anything greater than 4K with 28 bits (and doing 4K returns a physical address > 28 bits for some reason!?).

 

memmap from EFI Shell shows 231579 pages at 0x100000 available (65280 pages available in the 28 bit range) which seems like it should be plenty of room for 48 pages to be reserved. Doesn't this mean the UEFI environment is messed up later by boot.efi or the kernel? I guess I need to use a debug version of AptioMemoryFix to see what's going on.

 

[apianti]

2 hours ago, joevt said:

I can allocate 192K using a full 32 bits, but I can't allocate anything greater than 4K with 28 bits (and doing 4K returns a physical address > 28 bits for some reason!?).

 

memmap from EFI Shell shows 231579 pages at 0x100000 available (65280 pages available in the 28 bit range) which seems like it should be plenty of room for 48 pages to be reserved. Doesn't this mean the UEFI environment is messed up later by boot.efi or the kernel? I guess I need to use a debug version of AptioMemoryFix to see what's going on.

 

 

When did you use the shell? Because it's impossible to say something wasn't allocated there afterwards but before exit boot services (technically it could be the kernel) and almost certainly there was allocations but leaving no regions of more than one consecutive page seems weird. Also, yeah I think there is way to make aptiomemoryfix print out the memory map at certain places during boot.

[joevt]

On 2/20/2019 at 3:27 PM, apianti said:

When did you use the shell? Because it's impossible to say something wasn't allocated there afterwards but before exit boot services (technically it could be the kernel) and almost certainly there was allocations but leaving no regions of more than one consecutive page seems weird. Also, yeah I think there is way to make aptiomemoryfix print out the memory map at certain places during boot.

I used the EFI Shell from Clover.

 

The KDK from Apple (downloaded using Xcode) includes a debug script that includes many helpful lldb commands including one to print the boot args memory map. That should be the final memory map after AptioMemoryFix does its thing?

 

Yeah, it seems weird that there wouldn't be any consecutive pages - maybe the kernel just doesn't want to allocate anything in the 28 bit address range. When macOS boots, there is a message like "Available physical space from 0x1a422000 to 0x89efff000". The address 0x1a422000 is outside the 28 bit range. I need to do some debugging to find out if that address relates to the allocation my kext needs to do, and if so, how that address was calculated, and how it can be modified (maybe with a modification to aptiomemoryfix, or to the kernel).

 

I was trying to get two-machine debugging using FireWire to work, but only got fwkpfv to function. fwkdp gave errors so I couldn't connect in lldb. My host computer is running Mojave, and the target Hackintosh is running High Sierra.

 

Now I can't seem to boot my Hackintosh into High Sierra, so I'll try reinstalling that. I want to get away from using an apfs partition anyway.

 

I was doing tests with the debug kernel included with the KDK. Is this safe to use on a Hackintosh or does Clover require a release kernel?

 

[vit9696]

Clover patches are incompatible with debug kernel in most cases, including the CpuPm patch and kext injection. Otherwise it should work fine.

[maxb2000]

Hi guys !

 

I have a problem with an HP EliteBook 810 G1 which has 7 series CPU (Intel Core i5 3417U) and 1366 x 768 resolution:

 

a) When I try to boot with with CSM enabled I get an error allocating pages at 0x260 or something like that. If you need a picture just tell me and I will upload it here. So I need to calculate the slide. The problem is that HP doesn't implement all the functions of the UEFI so I can't launch any shell. (Clover's shell doesn't launch, it's stuck on the underscore sign)

 

b) If I boot without CSM, it boots fine but I get artifacts all over the place I can't see what's going on so native UEFI is the solution I tink

 

c) If I boot with Osxaptio (old driver) it works fine but I get EFIRuntime timeout because of the inexistent NVRAM support.

 

d) If I boot with Osxaption + EmuVariableEFI, Clover won't load at alll (I can't see the boot menu screen and it's stuck on black screen)

 

So, how can I troubleshoot this ?

 

I am trying to boot macOS 10.13 because with Mojave I got different results and I was stuck on something USB related for some reason.

[Modmike]

Hello all,

 

I am running an Asus Z390 with 8700K, and Saphhire Pulse RX-580.  Everything works well for me but some of the people using my guide have had issues with using audio layout 1 (recommended by Toleda) as well as other odd video issues.  I read that aptiomemoryfix had to be used during install and then changed OsxAptiofixdrv3 after install to get sleep, shutdown, and restart working.

 

After deleting OSXAptioFix3drv, RC Scripts (in /etc/rc.boot.d/), and my nvram.plist, I rebooted.  Everything booted fine but Sleep, wake, and shutdown were completely broken.  I noticed that the nvram.plist had a last modified date 5 hours in the future.

 

I suspect that the system is unable to update the file when sleeping, restarting or shutting down it thinks it is trying to write an older file. This seems to be borne out by the system not displaying the customary wait icon as it shut down.

 

After further reading, I re-enabled emuvariable and lo and behold, everything worked again.  I know that we are told not to use it, but I will keep testing to make sure the system is stable.  I did not have to use slide=0.

 

I think the key to making AptioMemeoryfix-64.efi work is to fix the future dated nvram.plist it writes.

 

Hope I was helpful.

Edited March 18, 2019 by Modmike

[mhaeuser]

44 minutes ago, Modmike said:

I read that aptiomemoryfix had to be used during install and then changed OsxAptiofixdrv3 after install to get sleep, shutdown, and restart working.

This is nonsense, use AptioMemoryFix with EmuVariable.

 

44 minutes ago, Modmike said:

I noticed that the nvram.plist had a last modified date 5 hours in the future.

Didn't you just say you deleted it? It will not be re-created without RC scripts.

 

44 minutes ago, Modmike said:

I suspect that the system is unable to update the file when sleeping, restarting or shutting down it thinks it is trying to write an older file.

This has nothing to do with AMF and doesn't matter for the problem.

 

44 minutes ago, Modmike said:

I think the key to making AptioMemeoryfix-64.efi work is to fix the future dated nvram.plist it writes.

Nope

[maxim_cin]

I have 10.14.3 on Lenovo x260 with 16GB RAM installed. Aptio works flawlessly. 

Recently I bought 32GB RAM module (Samsung DDR4 2666 MHz SO-DIMM 260 M471A4G43MB1-CTD https://www.samsung.com/semiconductor/dram/module/M471A4G43MB1-CTD/)

And now kernel cannot start. I see something like

"End RandomSeed

+++++++++++++++++++++++"

And then (I think) kernel panic and restart.

I've got memmap dumps from 16GB and 32GB to check differences.

 

16 GB:

Spoiler

??Type       Start            End              # Pages          Attributes
BS_Code    0000000000000000-0000000000000FFF 0000000000000001 000000000000000F
BS_Data    0000000000001000-0000000000001FFF 0000000000000001 000000000000000F
BS_Code    0000000000002000-000000000000BFFF 000000000000000A 000000000000000F
Available  000000000000C000-0000000000057FFF 000000000000004C 000000000000000F
Reserved   0000000000058000-0000000000058FFF 0000000000000001 000000000000000F
Available  0000000000059000-0000000000069FFF 0000000000000011 000000000000000F
BS_Data    000000000006A000-000000000006AFFF 0000000000000001 000000000000000F
BS_Code    000000000006B000-000000000008BFFF 0000000000000021 000000000000000F
Reserved   000000000008C000-000000000009FFFF 0000000000000014 000000000000000F
BS_Code    0000000000100000-000000000010FFFF 0000000000000010 000000000000000F
Available  0000000000110000-0000000096D7BFFF 0000000000096C6C 000000000000000F
BS_Data    0000000096D7C000-0000000096D9BFFF 0000000000000020 000000000000000F
Available  0000000096D9C000-00000000A7DBAFFF 000000000001101F 000000000000000F
LoaderCode 00000000A7DBB000-00000000A7F87FFF 00000000000001CD 000000000000000F
BS_Data    00000000A7F88000-00000000A9C49FFF 0000000000001CC2 000000000000000F
ACPI_NVS   00000000A9C4A000-00000000A9C4AFFF 0000000000000001 000000000000000F
RT_Data    00000000A9C4B000-00000000A9C74FFF 000000000000002A 800000000000000F
BS_Data    00000000A9C75000-00000000A9D6AFFF 00000000000000F6 000000000000000F
BS_Code    00000000A9D6B000-00000000A9D6BFFF 0000000000000001 000000000000000F
Available  00000000A9D6C000-00000000AC0D0FFF 0000000000002365 000000000000000F
BS_Data    00000000AC0D1000-00000000ADB5AFFF 0000000000001A8A 000000000000000F
Available  00000000ADB5B000-00000000AE3D8FFF 000000000000087E 000000000000000F
BS_Data    00000000AE3D9000-00000000AEBE2FFF 000000000000080A 000000000000000F
Available  00000000AEBE3000-00000000AED71FFF 000000000000018F 000000000000000F
BS_Data    00000000AED72000-00000000AED72FFF 0000000000000001 000000000000000F
Available  00000000AED73000-00000000AEDC1FFF 000000000000004F 000000000000000F
BS_Data    00000000AEDC2000-00000000AEDF3FFF 0000000000000032 000000000000000F
Available  00000000AEDF4000-00000000AEDF7FFF 0000000000000004 000000000000000F
BS_Data    00000000AEDF8000-00000000AEE1EFFF 0000000000000027 000000000000000F
Available  00000000AEE1F000-00000000AEE24FFF 0000000000000006 000000000000000F
BS_Data    00000000AEE25000-00000000AFD9FFFF 0000000000000F7B 000000000000000F
Available  00000000AFDA0000-00000000AFDA7FFF 0000000000000008 000000000000000F
BS_Data    00000000AFDA8000-00000000AFF5AFFF 00000000000001B3 000000000000000F
Available  00000000AFF5B000-00000000AFF5BFFF 0000000000000001 000000000000000F
BS_Data    00000000AFF5C000-00000000B1DDEFFF 0000000000001E83 000000000000000F
Available  00000000B1DDF000-00000000B45B8FFF 00000000000027DA 000000000000000F
BS_Code    00000000B45B9000-00000000B465DFFF 00000000000000A5 000000000000000F
RT_Code    00000000B465E000-00000000B465EFFF 0000000000000001 800000000000000F
BS_Data    00000000B465F000-00000000B485EFFF 0000000000000200 000000000000000F
BS_Code    00000000B485F000-00000000B55DEFFF 0000000000000D80 000000000000000F
RT_Code    00000000B55DF000-00000000B562FFFF 0000000000000051 800000000000000F
RT_Data    00000000B5630000-00000000B6E2FFFF 0000000000001800 800000000000000F
Reserved   00000000B6E30000-00000000B7D4AFFF 0000000000000F1B 000000000000000F
ACPI_NVS   00000000B7D4B000-00000000B7F78FFF 000000000000022E 000000000000000F
Reserved   00000000B7F79000-00000000B7F79FFF 0000000000000001 000000000000000F
ACPI_NVS   00000000B7F7A000-00000000B7FCEFFF 0000000000000055 000000000000000F
ACPI_Recl  00000000B7FCF000-00000000B7FFEFFF 0000000000000030 000000000000000F
BS_Data    00000000B7FFF000-00000000B7FFFFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000004417FFFFF 0000000000341800 000000000000000F
Reserved   00000000000A0000-00000000000FFFFF 0000000000000060 0000000000000000
Reserved   00000000B8000000-00000000B80FFFFF 0000000000000100 0000000000000000
Reserved   00000000B8600000-00000000BC7FFFFF 0000000000004200 0000000000000000
MMIO       00000000F80FA000-00000000F80FAFFF 0000000000000001 8000000000000001
MMIO       00000000F80FD000-00000000F80FDFFF 0000000000000001 8000000000000001
MMIO       00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001
 
  Reserved  :         21,137 Pages (86,577,152 Bytes)
  LoaderCode:            461 Pages (1,888,256 Bytes)
  LoaderData:              0 Pages (0 Bytes)
  BS_Code   :          3,682 Pages (15,081,472 Bytes)
  BS_Data   :         29,306 Pages (120,037,376 Bytes)
  RT_Code   :             82 Pages (335,872 Bytes)
  RT_Data   :          6,186 Pages (25,337,856 Bytes)
  ACPI_Recl :             48 Pages (196,608 Bytes)
  ACPI_NVS  :            644 Pages (2,637,824 Bytes)
  MMIO      :             19 Pages (77,824 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      4,123,286 Pages (16,888,979,456 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         16,264 MB (17,054,494,720 Bytes)
 

  

32GB

Spoiler

??Type       Start            End              # Pages          Attributes
BS_Code    0000000000000000-0000000000000FFF 0000000000000001 000000000000000F
BS_Data    0000000000001000-0000000000001FFF 0000000000000001 000000000000000F
BS_Code    0000000000002000-000000000000BFFF 000000000000000A 000000000000000F
Available  000000000000C000-0000000000057FFF 000000000000004C 000000000000000F
Reserved   0000000000058000-0000000000058FFF 0000000000000001 000000000000000F
Available  0000000000059000-0000000000069FFF 0000000000000011 000000000000000F
BS_Data    000000000006A000-000000000006AFFF 0000000000000001 000000000000000F
BS_Code    000000000006B000-000000000008BFFF 0000000000000021 000000000000000F
Reserved   000000000008C000-000000000009FFFF 0000000000000014 000000000000000F
BS_Code    0000000000100000-000000000010FFFF 0000000000000010 000000000000000F
Available  0000000000110000-0000000096D7BFFF 0000000000096C6C 000000000000000F
BS_Data    0000000096D7C000-0000000096D9BFFF 0000000000000020 000000000000000F
Available  0000000096D9C000-00000000A7DBBFFF 0000000000011020 000000000000000F
LoaderCode 00000000A7DBC000-00000000A7F87FFF 00000000000001CC 000000000000000F
BS_Data    00000000A7F88000-00000000A9C49FFF 0000000000001CC2 000000000000000F
ACPI_NVS   00000000A9C4A000-00000000A9C4AFFF 0000000000000001 000000000000000F
RT_Data    00000000A9C4B000-00000000A9C74FFF 000000000000002A 800000000000000F
BS_Data    00000000A9C75000-00000000A9D6AFFF 00000000000000F6 000000000000000F
BS_Code    00000000A9D6B000-00000000A9D6BFFF 0000000000000001 000000000000000F
Available  00000000A9D6C000-00000000AC551FFF 00000000000027E6 000000000000000F
BS_Data    00000000AC552000-00000000ADB5AFFF 0000000000001609 000000000000000F
Available  00000000ADB5B000-00000000AE69AFFF 0000000000000B40 000000000000000F
BS_Data    00000000AE69B000-00000000AF0E1FFF 0000000000000A47 000000000000000F
Available  00000000AF0E2000-00000000AF285FFF 00000000000001A4 000000000000000F
BS_Data    00000000AF286000-00000000AF2AFFFF 000000000000002A 000000000000000F
Available  00000000AF2B0000-00000000AF2B1FFF 0000000000000002 000000000000000F
BS_Data    00000000AF2B2000-00000000AFD92FFF 0000000000000AE1 000000000000000F
Available  00000000AFD93000-00000000AFE04FFF 0000000000000072 000000000000000F
BS_Data    00000000AFE05000-00000000AFE40FFF 000000000000003C 000000000000000F
Available  00000000AFE41000-00000000AFE44FFF 0000000000000004 000000000000000F
BS_Data    00000000AFE45000-00000000AFE6BFFF 0000000000000027 000000000000000F
Available  00000000AFE6C000-00000000AFE72FFF 0000000000000007 000000000000000F
BS_Data    00000000AFE73000-00000000AFE95FFF 0000000000000023 000000000000000F
Available  00000000AFE96000-00000000AFE97FFF 0000000000000002 000000000000000F
BS_Data    00000000AFE98000-00000000AFEA0FFF 0000000000000009 000000000000000F
Available  00000000AFEA1000-00000000AFEA1FFF 0000000000000001 000000000000000F
BS_Data    00000000AFEA2000-00000000AFEA5FFF 0000000000000004 000000000000000F
Available  00000000AFEA6000-00000000AFEA6FFF 0000000000000001 000000000000000F
BS_Data    00000000AFEA7000-00000000AFFEAFFF 0000000000000144 000000000000000F
Available  00000000AFFEB000-00000000AFFEFFFF 0000000000000005 000000000000000F
BS_Data    00000000AFFF0000-00000000B0005FFF 0000000000000016 000000000000000F
Available  00000000B0006000-00000000B000AFFF 0000000000000005 000000000000000F
BS_Data    00000000B000B000-00000000B0077FFF 000000000000006D 000000000000000F
Available  00000000B0078000-00000000B007CFFF 0000000000000005 000000000000000F
BS_Data    00000000B007D000-00000000B0081FFF 0000000000000005 000000000000000F
Available  00000000B0082000-00000000B0084FFF 0000000000000003 000000000000000F
BS_Data    00000000B0085000-00000000B009AFFF 0000000000000016 000000000000000F
Available  00000000B009B000-00000000B009BFFF 0000000000000001 000000000000000F
BS_Data    00000000B009C000-00000000B1DDEFFF 0000000000001D43 000000000000000F
Available  00000000B1DDF000-00000000B4598FFF 00000000000027BA 000000000000000F
BS_Code    00000000B4599000-00000000B45ACFFF 0000000000000014 000000000000000F
RT_Code    00000000B45AD000-00000000B45ADFFF 0000000000000001 800000000000000F
BS_Data    00000000B45AE000-00000000B47ADFFF 0000000000000200 000000000000000F
BS_Code    00000000B47AE000-00000000B55DEFFF 0000000000000E31 000000000000000F
RT_Code    00000000B55DF000-00000000B562FFFF 0000000000000051 800000000000000F
RT_Data    00000000B5630000-00000000B6E2FFFF 0000000000001800 800000000000000F
Reserved   00000000B6E30000-00000000B7D4AFFF 0000000000000F1B 000000000000000F
ACPI_NVS   00000000B7D4B000-00000000B7F78FFF 000000000000022E 000000000000000F
Reserved   00000000B7F79000-00000000B7F79FFF 0000000000000001 000000000000000F
ACPI_NVS   00000000B7F7A000-00000000B7FCEFFF 0000000000000055 000000000000000F
ACPI_Recl  00000000B7FCF000-00000000B7FFEFFF 0000000000000030 000000000000000F
BS_Data    00000000B7FFF000-00000000B7FFFFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000008417FFFFF 0000000000741800 000000000000000F
Reserved   00000000000A0000-00000000000FFFFF 0000000000000060 0000000000000000
Reserved   00000000B8000000-00000000B80FFFFF 0000000000000100 0000000000000000
Reserved   00000000B8600000-00000000BC7FFFFF 0000000000004200 0000000000000000
MMIO       00000000F80FA000-00000000F80FAFFF 0000000000000001 8000000000000001
MMIO       00000000F80FD000-00000000F80FDFFF 0000000000000001 8000000000000001
MMIO       00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001
 
  Reserved  :         21,137 Pages (86,577,152 Bytes)
  LoaderCode:            460 Pages (1,884,160 Bytes)
  LoaderData:              0 Pages (0 Bytes)
  BS_Code   :          3,714 Pages (15,212,544 Bytes)
  BS_Data   :         27,374 Pages (112,123,904 Bytes)
  RT_Code   :             82 Pages (335,872 Bytes)
  RT_Data   :          6,186 Pages (25,337,856 Bytes)
  ACPI_Recl :             48 Pages (196,608 Bytes)
  ACPI_NVS  :            644 Pages (2,637,824 Bytes)
  MMIO      :             19 Pages (77,824 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      8,319,491 Pages (34,076,635,136 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         32,648 MB (34,234,363,904 Bytes)
 

 

Could someone please help me check difference between memmaps and calculate correct slide.

 

[Modmike]

4 hours ago, Download-Fritz said:

Didn't you just say you deleted it? It will not be re-created without RC scripts.

 

Possibly but I did uninstall rc-scripts and the nvram.plist increments on every boot.  So where is RC Scripts residing?

 

 

 

[mhaeuser]

14 hours ago, maxim_cin said:

Could someone please help me check difference between memmaps and calculate correct slide.

Your error is not related to slide and very unlikely to AptioMemoryFix at all.

13 hours ago, Modmike said:

So where is RC Scripts residing?

Sorry, haven't used them in like five years, I don't remember

[maxim_cin]

9 hours ago, Download-Fritz said:

Your error is not related to slide and very unlikely to AptioMemoryFix at all.

Do you know is there way to check what was wrong? Verbose or debug mode or how to get kernel backtrace in this case?

 

[apianti]

Disable automatic restarting on a kernel panic.

[maxim_cin]

11 hours ago, apianti said:

Disable automatic restarting on a kernel panic.

Here is screenshot of the KP:

 

Spoiler

 

Spoiler

 

zalloc: zone map exhausted while allocating from zone. Could it be related to AptioMemoriFix?

[mhaeuser]

4 hours ago, maxim_cin said:

Could it be related to AptioMemoriFix?

More than unlikely. Is it an ASUS board? Might be the memory information in SMBIOS is incorrect.

[maxim_cin]

8 hours ago, Download-Fritz said:

More than unlikely. Is it an ASUS board? Might be the memory information in SMBIOS is incorrect.

No, it's Lenovo x260 laptop. It has only one memory slot.  When I've installed 8 or 16GB it worked perfect. But 32GB does not work.

I already tried add RAM config on the config.plist. Did not help :(

I'm sure that memory is ok, I've checked it. Moreover Linux works without problem.

Edited March 20, 2019 by maxim_cin

[Modmike]

On 3/19/2019 at 6:12 AM, Download-Fritz said:

Your error is not related to slide and very unlikely to AptioMemoryFix at all.

Sorry, haven't used them in like five years, I don't remember

 

Actually there was no error by Aptiomemoryfix. Turns out that even though I did the registry time fix for Windows to align with the Mac, my SYSTEM time was still 8 hours  ahead and can’t be changed.

 

The issue is emuvariable reading the system time thereby setting a future creation date.  Doesn’t seem to matter because it runs fine now.

 

Last question, I read that aptiomemoryfix is supposed to support emulated nvram but that the feature does not work. Is this true?  Are there plans to fix it?

 

Thanks!

 

 

[Slice]

7 hours ago, Modmike said:

 

Last question, I read that aptiomemoryfix is supposed to support emulated nvram but that the feature does not work. Is this true?  Are there plans to fix it?

 

Thanks!

 

 

What is the feature? Emulated NVRAM supported by EmuVariableDxe.efi no matter what AptioFix used.

[Modmike]

On 3/21/2019 at 6:05 AM, Slice said:

What is the feature? Emulated NVRAM supported by EmuVariableDxe.efi no matter what AptioFix used.

1

 

Sorry if I wasn't clear.  I believe I read that AptioMemoryFix could emulate NVRAM but had a bug.  Is this correct?  I would love to eliminate EmuVariableDxe.efi for no other reason than to have fewer kexts.

 

Thank you

 

 

[apianti]

It allows you to use your native nvram. However, as the way the nvram implementation in firmware behaves changes over time, there develop different issues. Apparently some newer firmwares now present some other issue that forces using emulated nvram again. You have to reconcile the native nvram with the emulated nvram if you switch back as they will have different variables and values.