Jump to content

Unable to calculate slide for Z390

4 posts in this topic

Recommended Posts

Trying out OpenCore following @dracoflar excellent guide. Everything is going well except trying to calculate the slide value. 


First just to clarify ProvideCustomSlide should be set to true? From the OpenCore documentation, it could be interpreted as false is appropriate when supplying a slide boot argument (for the kernel?): 


This also ensures that slide= argument is never passed to the operating system for security reasons.

But by trial and error it does look that when ProvideCustomSlide=true the slide value is provided, judging from the error message, see below. 


Motherboard: https://www.gigabyte.com/us/Motherboard/Z390-AORUS-PRO-rev-10#kf


memory map after disabling iGPU as well (using iMacPro1,1 SMBios it's not used anyways):

??Type       Start            End              # Pages          Attributes
Available  0000000000000000-000000000009EFFF 000000000000009F 000000000000000F
Reserved   000000000009F000-000000000009FFFF 0000000000000001 000000000000000F
Available  0000000000100000-000000001A12DFFF 000000000001A02E 000000000000000F
BS_Data    000000001A12E000-000000001A16DFFF 0000000000000040 000000000000000F
Available  000000001A16E000-00000000301D9FFF 000000000001606C 000000000000000F
LoaderCode 00000000301DA000-00000000302ECFFF 0000000000000113 000000000000000F
BS_Data    00000000302ED000-000000003200FFFF 0000000000001D23 000000000000000F
ACPI_NVS   0000000032010000-0000000032010FFF 0000000000000001 000000000000000F
RT_Data    0000000032011000-0000000032011FFF 0000000000000001 800000000000000F
BS_Data    0000000032012000-000000003211DFFF 000000000000010C 000000000000000F
Available  000000003211E000-0000000032129FFF 000000000000000C 000000000000000F
LoaderCode 000000003212A000-000000003212CFFF 0000000000000003 000000000000000F
BS_Data    000000003212D000-000000003D0FEFFF 000000000000AFD2 000000000000000F
Available  000000003D0FF000-000000003D22CFFF 000000000000012E 000000000000000F
BS_Code    000000003D22D000-000000003DB53FFF 0000000000000927 000000000000000F
Reserved   000000003DB54000-000000003DFC9FFF 0000000000000476 000000000000000F
Available  000000003DFCA000-000000003E1D9FFF 0000000000000210 000000000000000F
BS_Data    000000003E1DA000-000000003E3D9FFF 0000000000000200 000000000000000F
ACPI_NVS   000000003E3DA000-000000003E529FFF 0000000000000150 000000000000000F
RT_Data    000000003E52A000-000000003EE4FFFF 0000000000000926 800000000000000F
RT_Code    000000003EE50000-000000003EEFEFFF 00000000000000AF 800000000000000F
BS_Data    000000003EEFF000-000000003EEFFFFF 0000000000000001 000000000000000F
Available  0000000100000000-00000010BDFFFFFF 0000000000FBE000 000000000000000F
Reserved   00000000000A0000-00000000000FFFFF 0000000000000060 0000000000000000
Reserved   000000003EF00000-000000003EFFFFFF 0000000000000100 000000000000000F
Reserved   000000003F000000-000000003FFFFFFF 0000000000001000 0000000000000000
MMIO       00000000E0000000-00000000EFFFFFFF 0000000000010000 800000000000100D
MMIO       00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001
MMIO       00000000FEC00000-00000000FEC00FFF 0000000000000001 8000000000000001
MMIO       00000000FEE00000-00000000FEE00FFF 0000000000000001 8000000000000001
MMIO       00000000FF000000-00000000FFFFFFFF 0000000000001000 800000000000100D

000000001A16E000 looks like the candidate, yields 208, doing the reverse ends up a little short at 0x1A100000, so 209 yields 0x1A300000, so that should still give us (00000000301D9FFF - 0x1A300000)/4k 0x15ED9 pages, should be more than enough given error message. 


Trying to boot with slide=209 I still see:

ERROR allocating 0x119f5 pages at 0x0000000021597000 alloc type 2
Couldn't allocate runtime area


so fewer pages than we have available but by is the offset/index so much further than the anticipated 0x1A300000 or am I completely misunderstanding how this works? Using that offset it looks like only 0xEC42 pages are available, which IS a problem. 


config.list attached but I think these are the salient bits:


          <string>-v keepsyms=1 debug=0x100 slide=209</string>


Any input appreciated! 


Edited by nefilim

Share this post

Link to post
Share on other sites
On 11/25/2019 at 3:50 PM, BiggestCookie said:

Can you explain what a "slide" is for a Newbie?


It is a workaround for fragmented memory.

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.