Jump to content
vit9696

AptioMemoryFix

561 posts in this topic

Recommended Posts

9 hours ago, Pene said:

Hi Slice,

 

I already wrote previously on this thread that situation on my Z390 board is the same. I also posted my full memory map some time ago also, if you wish to see it.

But for getting proper console output, HandleProtocol override is still needed, as EfiGraphicsOutputProtocol continues not to be present on ConOutHandle.

 

P.S. I am writing this solely for educational purposes, and by no means for getting into a debate whether to use it or not.

Is it possible to override only HandleProtocol? Or rewrite ConsoleSplitter?

I see, you made override HandleProtocol so this is possible. What is wrong in this way?

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
2 hours ago, Slice said:

Is it possible to override only HandleProtocol? Or rewrite ConsoleSplitter?

I see, you made override HandleProtocol so this is possible. What is wrong in this way?

a gBS->HandleProtocol override is one of the fixes included in all *Aptio*Fix* drivers:

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/OsxAptioFixDrv/OsxAptioFixDrv.c#l219

Edited by Pene

Share this post


Link to post
Share on other sites
Posted (edited)

I'll ask one more time to not mislead users into believing booting without relocation prevention is acceptable, because it is not.

Edited by Download-Fritz

Share this post


Link to post
Share on other sites

@Slice If you refer to Z390's NVRAM issues, our research shows that reading (usually?) works fine and writing causes a deadlock for unknown reasons. If you have research revealing memory corruption and a plausible explaination for such, I'm excited to hear of it.

Share this post


Link to post
Share on other sites

Hey guys, im currently running into a "Couldn't allocate runtime area" problem on my new Lenovo Yoga S740 (i7-1065g7, 16gb, 512 SSD, Ice Lake).

I've read a few posts and guides and figured I should just follow this guide and set a custom slide parameter to get it to boot.

 

This is the exact message that I get:

Error allocating 0x8e368 pages at 0x000000000cccf000 alloc type 2
Couldn't allocate runtime area

 

So I follow the guide and run memmap, I end up with the following available sectors:

Available xxx-xxx 000000000000009F 000000000000000F
Available xxx-xxx 0000000000020F8A 000000000000000F
Available xxx-xxx 0000000000000001 000000000000000F
Available xxx-xxx 00000000000011C4 000000000000000F
Available 0000000100000000-00000004BABFFFFF 00000000003BAC00 000000000000000F

As you can see only the last Sector is big enough, so I chose that one even though it is really huge.

 

I use the formular found in the guide like this:

0x100000000 - 0x100000 = 0xFFF00000
0xFFF00000 / 0x200000 = 0x7FF

0x7FF converted to dec = 2047

 

So now if I use the bootargument "slide=2047" I still end up with the same error but other parameters:

Error allocating 0x8e368 pages at 0x00000000124d3000 alloc type 2
Couldn't allocate runtime area

 

Can anyone help me through this? I am kinda lost here, I tried all different aptiofix drivers.

Share this post


Link to post
Share on other sites

@Killuminati91 The kernel can never be allocated over 4 GB, which is what you are trying to do, iirc the slide value is capped to 255. Without OpenCore's DevirtualiseMMIO quirk, you'll probably not get very far, possibly not even with it.

 

You could try this with DevirtualiseMMIO=true, but we do not actively support the usage of that driver

Share this post


Link to post
Share on other sites
8 hours ago, Download-Fritz said:

@Killuminati91 The kernel can never be allocated over 4 GB, which is what you are trying to do, iirc the slide value is capped to 255. Without OpenCore's DevirtualiseMMIO quirk, you'll probably not get very far, possibly not even with it.

 

You could try this with DevirtualiseMMIO=true, but we do not actively support the usage of that driver

 

Thanks for the headsup! Sadly this doesnt work either as it stalls at End RandomSeed ++++++. Ill try to educate my self on OpenCore.

Does this mean in conclusion that this laptop model simply is not compatible?

 

Full memmap attached, unless I'm blind there is really no available sector except the one that is way too large.

 

Type       Start            End              # Pages          Attributes
Available  0000000000000000-000000000009EFFF 000000000000009F 000000000000000F
Reserved   000000000009F000-000000000009FFFF 0000000000000001 000000000000000F
Available  0000000000100000-000000002252EFFF 000000000002242F 000000000000000F
LoaderCode 000000002252F000-0000000022617FFF 00000000000000E9 000000000000000F
Available  0000000022618000-000000002261EFFF 0000000000000007 000000000000000F
BS_Data    000000002261F000-000000002267DFFF 000000000000005F 000000000000000F
Available  000000002267E000-000000002267EFFF 0000000000000001 000000000000000F
BS_Data    000000002267F000-00000000226ABFFF 000000000000002D 000000000000000F
Available  00000000226AC000-00000000226ACFFF 0000000000000001 000000000000000F
BS_Data    00000000226AD000-0000000022F25FFF 0000000000000879 000000000000000F
Available  0000000022F26000-0000000022F27FFF 0000000000000002 000000000000000F
BS_Data    0000000022F28000-0000000023103FFF 00000000000001DC 000000000000000F
Available  0000000023104000-0000000023104FFF 0000000000000001 000000000000000F
BS_Data    0000000023105000-0000000023198FFF 0000000000000094 000000000000000F
LoaderCode 0000000023199000-000000002327EFFF 00000000000000E6 000000000000000F
BS_Data    000000002327F000-00000000260ADFFF 0000000000002E2F 000000000000000F
BS_Code    00000000260AE000-00000000260C8FFF 000000000000001B 000000000000000F
BS_Data    00000000260C9000-00000000260D9FFF 0000000000000011 000000000000000F
BS_Code    00000000260DA000-00000000260DAFFF 0000000000000001 000000000000000F
BS_Data    00000000260DB000-00000000260EBFFF 0000000000000011 000000000000000F
BS_Code    00000000260EC000-00000000260F9FFF 000000000000000E 000000000000000F
BS_Data    00000000260FA000-0000000027474FFF 000000000000137B 000000000000000F
BS_Code    0000000027475000-0000000027491FFF 000000000000001D 000000000000000F
BS_Data    0000000027492000-00000000274C2FFF 0000000000000031 000000000000000F
BS_Code    00000000274C3000-00000000274CCFFF 000000000000000A 000000000000000F
BS_Data    00000000274CD000-00000000274DEFFF 0000000000000012 000000000000000F
BS_Code    00000000274DF000-00000000274FFFFF 0000000000000021 000000000000000F
BS_Data    0000000027500000-0000000027987FFF 0000000000000488 000000000000000F
Reserved   0000000027988000-0000000028287FFF 0000000000000900 000000000000000F
BS_Code    0000000028288000-000000002828FFFF 0000000000000008 000000000000000F
BS_Data    0000000028290000-000000002829EFFF 000000000000000F 000000000000000F
Available  000000002829F000-0000000029668FFF 00000000000013CA 000000000000000F
BS_Code    0000000029669000-000000002A09EFFF 0000000000000A36 000000000000000F
RT_Code    000000002A09F000-000000002A46EFFF 00000000000003D0 800000000000000F
RT_Data    000000002A46F000-000000002ADEEFFF 0000000000000980 800000000000000F
Reserved   000000002ADEF000-000000002B4DEFFF 00000000000006F0 000000000000000F
ACPI_NVS   000000002B4DF000-000000002BBCEFFF 00000000000006F0 000000000000000F
ACPI_Recl  000000002BBCF000-000000002BC4EFFF 0000000000000080 000000000000000F
BS_Data    000000002BC4F000-000000002BC4FFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000004BABFFFFF 00000000003BAC00 000000000000000F
Reserved   00000000000A0000-00000000000FFFFF 0000000000000060 0000000000000000
Reserved   000000002BC50000-000000003FFFFFFF 00000000000143B0 000000000000000F
Reserved   0000000040000000-0000000040FFFFFF 0000000000001000 0000000000000009
Reserved   0000000041000000-00000000453FFFFF 0000000000004400 0000000000000000
MMIO       0000000045400000-00000000CFFFFFFF 000000000008AC00 8000000000000001
MMIO       00000000FC800000-00000000FE7FFFFF 0000000000002000 8000000000000001
MMIO       00000000FED00000-00000000FED00FFF 0000000000000001 8000000000000001
MMIO       00000000FED10000-00000000FED17FFF 0000000000000008 8000000000000001
Reserved   00000000FED20000-00000000FED7FFFF 0000000000000060 0000000000000000
MMIO       00000000FEDA0000-00000000FEDA1FFF 0000000000000002 8000000000000001
MMIO       00000000FEE00000-00000000FEE00FFF 0000000000000001 8000000000000001
MMIO       00000000FF600000-00000000FFFFFFFF 0000000000000A00 8000000000000001
 
  Reserved  :        108,641 Pages (444,993,536 Bytes)
  LoaderCode:            463 Pages (1,896,448 Bytes)
  LoaderData:              0 Pages (0 Bytes)
  BS_Code   :          2,736 Pages (11,206,656 Bytes)
  BS_Data   :         21,020 Pages (86,097,920 Bytes)
  RT_Code   :            976 Pages (3,997,696 Bytes)
  RT_Data   :          2,432 Pages (9,961,472 Bytes)
  ACPI_Recl :            128 Pages (524,288 Bytes)
  ACPI_NVS  :          1,776 Pages (7,274,496 Bytes)
  MMIO      :        579,084 Pages (2,371,928,064 Bytes)
  MMIO_Port :              0 Pages (0 Bytes)
  PalCode   :              0 Pages (0 Bytes)
  Available :      4,056,228 Pages (16,614,309,888 Bytes)
  Persistent:              0 Pages (0 Bytes)
              -------------- 
Total Memory:         15,959 MB (16,735,268,864 Bytes)

 

Edited by Killuminati91

Share this post


Link to post
Share on other sites

Hi, I have weird issue since final release of catalina. My Nvram works with osxaptio 1, 3, osxaptio2-wtf and aptioinput aswell but after catalina if I boot even once with these drivers, I cant access bios. When I try it hang out in black screen. If I use osxaptio2 all the time I can access bios but mlb and rom values becaming 0. Also if I get blackscreen once only way to revert that reflashing nvram with amibios tool. I have also tried OpenCore it has same issue as well. I ve tried QcQuirks as well it has same issue too.

I have never experianced that kind of issue before on mojave. 

Device: Asus FX553VD i-7700hq.

Edit: I modified QcQuirks also but only way to keep bios alive disabling mac's access to nvram in that way nvram becoming meaningless.

Edited by valinor61

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.

×