gujiangjiang Posted February 23, 2017 Share Posted February 23, 2017 My xps 15 9550 have suffered from OSXAptioFixDrv2 and i tried many ways but no use. Type Start End # Pages AttributesRT_Data 0000000000000000-0000000000000FFF 0000000000000001 800000000000000FAvailable 0000000000001000-0000000000057FFF 0000000000000057 000000000000000FReserved 0000000000058000-0000000000058FFF 0000000000000001 000000000000000F Available 0000000000059000-000000000009CFFF 0000000000000044 000000000000000FReserved 000000000009D000-000000000009EFFF 0000000000000002 000000000000000FRT_Data 000000000009F000-000000000009FFFF 0000000000000001 800000000000000FAvailable 0000000000100000-000000000421BFFF 000000000000411C 000000000000000F BS_Data 000000000421C000-000000000425BFFF 0000000000000040 000000000000000FAvailable 000000000425C000-0000000021D53FFF 000000000001DAF8 000000000000000F 32 270LoaderCode 0000000021D54000-0000000021EEAFFF 0000000000000197 000000000000000FACPI_Recl 0000000021EEB000-0000000021F1CFFF 0000000000000032 000000000000000FBS_Data 0000000021F1D000-0000000023970FFF 0000000000001A54 000000000000000FACPI_NVS 0000000023971000-0000000023971FFF 0000000000000001 000000000000000FRT_Data 0000000023972000-00000000239BBFFF 000000000000004A 800000000000000FBS_Data 00000000239BC000-0000000023A12FFF 0000000000000057 000000000000000FRT_Data 0000000023A13000-0000000024203FFF 00000000000007F1 800000000000000FBS_Data 0000000024204000-000000002420BFFF 0000000000000008 000000000000000FAvailable 000000002420C000-000000003128AFFF 000000000000D07F 000000000000000F 288 392BS_Data 000000003128B000-0000000036A89FFF 00000000000057FF 000000000000000FAvailable 0000000036A8A000-0000000036C2FFFF 00000000000001A6 000000000000000F 436 437BS_Code 0000000036C30000-0000000037298FFF 0000000000000669 000000000000000FReserved 0000000037299000-0000000037645FFF 00000000000003AD 000000000000000FACPI_Recl 0000000037646000-0000000037667FFF 0000000000000022 000000000000000FAvailable 0000000037668000-0000000037CB9FFF 0000000000000652 000000000000000F 442 445ACPI_NVS 0000000037CBA000-000000003800EFFF 0000000000000355 000000000000000FRT_Data 000000003800F000-000000003A48BFFF 000000000000247D 800000000000000FRT_Code 000000003A48C000-000000003A4FEFFF 0000000000000073 800000000000000FBS_Data 000000003A4FF000-000000003A4FFFFF 0000000000000001 000000000000000FAvailable 0000000100000000-00000004BDFFFFFF 00000000003BE000 000000000000000F 2047 9711Reserved 000000003A500000-000000003A5FFFFF 0000000000000100 0000000000000000MMIO 00000000E0000000-00000000EFFFFFFF 0000000000010000 8000000000000001MMIO 00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001MMIO 00000000FEC00000-00000000FEC00FFF 0000000000000001 8000000000000001MMIO 00000000FEE00000-00000000FEE00FFF 0000000000000001 8000000000000001MMIO 00000000FF000000-00000000FFFFFFFF 0000000000001000 8000000000000001 Reserved : 1,200 Pages (4,915,200 Bytes) LoaderCode: 407 Pages (1,667,072 Bytes) LoaderData: 0 Pages (0 Bytes) BS_Code : 1,641 Pages (6,721,536 Bytes) BS_Data : 29,427 Pages (120,532,992 Bytes) RT_Code : 115 Pages (471,040 Bytes) RT_Data : 11,450 Pages (46,899,200 Bytes) ACPI_Recl : 84 Pages (344,064 Bytes) ACPI_NVS : 854 Pages (3,497,984 Bytes) MMIO : 69,651 Pages (285,290,496 Bytes) MMIO_Port : 0 Pages (0 Bytes) PalCode : 0 Pages (0 Bytes) Available : 4,117,798 Pages (16,866,500,608 Bytes) Persistent: 0 Pages (0 Bytes) -------------- Total Memory: 16,256 MB (17,046,634,496 Bytes)Here is my memmap from uefishell command "memmap > mem.txt" and i have get all the Available slide data such as 32,270 and so on, I have tried all this data "32 270 288 392 436 437 442 445 2047 9711"but still can't boot into the osx and saying "Error allocating xxxx pages at xxxxx". I have also tried to delete all the kext expect fakesmc.kext but still same error. Then i tried to delete the addtional efi drivers such as DataHub.efi but still same error. I want to know does any other problem can cause this allocating error happen? Edit1:I have tried this files with slide=0 and can boot into the osx fine. https://sourceforge.net/p/cloverefiboot/tickets/125/#fd2c/6d91/539a I noticed the h4x said "I merged test2.efi into OsxAptioFix2Drv.efi. You can delete ALL aptio fixes, test2.efi, and even LowMemFix and place this binary in your driverUEFI64 folder and have a try." So does this problem can be sloved by this way? Edit2:I found a solution here with edited OsxLowMemFixDrv-64.efi together with OSXAptioFixDrv2 and add "slide=32"and boot fine with no error. https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/ What I needed to do was recompile Clover from source with an edited OsxLowMemFixDrv-64.efi memory allocation file. I then included that file along with the regular OsxAptioFixDrv2-64.efi file in the /EFI/ClOVER/drivers64UEFIfolder. Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000. The way it works is that it loads the edited OsxLowMemFixDrv-64.efi file first and wipes out the entire memory allocation table up to 0x20000000. I renamed the recompiled version to Test2.efi to avoid the confusion. So i use OsxAptioFixDrv2-64.efi from clover4012 and modified Test2.efi together and use "slide=32"and boot fine with no error. But i use OsxAptioFixDrv2-64.efi and OsxLowMemFixDrv-64.efi together from clover4012 and use "slide=32" and boot with error. I think this can be commit to clover or just commit to OsxLowMemFixDrv-64.efi with 0x40000000 or higher instead of 0x10000000 just like the Test2.efi because the 0x10000000 or 0x20000000 is small with the latest macOS. Thanks slice. 1 Link to comment Share on other sites More sharing options...
JahStories Posted February 23, 2017 Share Posted February 23, 2017 Hi there folks, just wanted to report a problem with patching on Clover, while some patches works right away, some others don't.... Here the description of the issue happening for me on two kexts on two different systems: The AGDP Patch that "don't disable GFX0" when using MacPro Smbios, this one: AppleGraphicsDevicePolicy Find: 626F6172642D6964 Replace:626F6172642D6978 Does not apply, but after editing the binary manually and installing the kexts doing a reboot and reinstalling the original, the patch works! The same thing happens when using the Disable minStolenSize less or equal fStolenMemorySize assertion 10.12 patch: AppleIntelSKLGraphicsFramebuffer Find: 8945C839C67651 Replace: 8945C839C6EB51 Why is this happening? I understand is a cache problem but is there a solution? Hoping to be helpful somehow! THX Link to comment Share on other sites More sharing options...
cecekpawon Posted February 23, 2017 Share Posted February 23, 2017 @Zenith Did you get any other error like: 'error 3000: Global macro ARCH is not permitted' since that commit? @randombrain You can try this wrapper & discuss there, or by following this steps? 1 Link to comment Share on other sites More sharing options...
Zenith432 Posted February 23, 2017 Share Posted February 23, 2017 @Zenith Did you get any other error like: 'error 3000: Global macro ARCH is not permitted' since that commit Yes. There were 2 problems with edk2 commit dc4c77 Get error "global macro arch is not permitted' in refit.inf. This is result of change in MetaFileParser.py. Can fix this by either using reversion checked in by Slice, or as Fritz suggested - edit refit.inf and change CLOVER$(ARCH) to just CLOVER. The change in WorkspaceDatabase.py caused unfixable breakdown - a regression in edk2 build process. It was fixed by edk2 commit 1d8ceb. So after 1d8ceb, it is possible to use WorkspaceDatabase.py from edk2 tree or the reversion checked in by Slice. Hope this clarifies. Link to comment Share on other sites More sharing options...
frankiee Posted February 23, 2017 Share Posted February 23, 2017 My xps 15 9550 have suffered from OSXAptioFixDrv2 and i tried many ways but no use. Reminds me of a similar problem I had. I always had KPs after wake and reboot (with type 14 page fault errors). At first I thought it was bad RAM, but that wasn't the case. My solution back then was to use a recompiled AptioFixDrv (not "2") with increased memory allocation. Curiously, with my current clover version (3961) the problem has apparently vanished - but I also changed my GPU in the meantime so I am not 100% sure what exactly fixed that problem. But it seems that maybe PCI configuration (i.e. how many and which cards you have installed and maybe also in which slots they reside) might play a role here. 1 Link to comment Share on other sites More sharing options...
cecekpawon Posted February 24, 2017 Share Posted February 24, 2017 Thanks @Zenith, what I need to do is just hardcoded that BASE_NAME since I never built other but X64, and problem solved. In fact they not only reject global macros to be used in INF, but also all of our defined variables / passed from commandline. Link to comment Share on other sites More sharing options...
Slice Posted February 24, 2017 Share Posted February 24, 2017 Hi Slice. Sorry really short time now, but with a quick look at the source I've lost where Clover handles the separator ':', can be this the problem? I will look about GUID:Name records in nvram.plist interpretation by Clover. Anyway there is no value for boot0082 and no decryption key at all. Looks like this application didn't do the main work, it can't save new variables during sleep event. Link to comment Share on other sites More sharing options...
Sherlocks Posted February 24, 2017 Share Posted February 24, 2017 @Slice i have a question. I used Clover Configurator and Cloud Clover Editor I'm not trying to compare the two apps. I want to know which one is correct and want to report it to the creator. CC use this <key>Memory</key> <dict> <key>Channels</key> <integer>2</integer> <key>Modules</key> <array> <dict> <key>Frequency</key> <string>1066</string> <key>Size</key> <string>8192</string> <key>Slot</key> <string>1</string> <key>Type</key> <string>DDR4</string> <key>Vendor</key> <string>Samsung</string> </dict> </array> <key>SlotCount</key> <integer>4</integer> </dict> CCE use <key>Memory</key> <dict> <key>Channels</key> <integer>2</integer> <key>Modules</key> <array> <dict> <key>Frequency</key> <integer>1066</integer> <key>Size</key> <integer>8192</integer> <key>Slot</key> <integer>1</integer> <key>Type</key> <string>DDR4</string> <key>Vendor</key> <string>Samsung</string> </dict> </array> <key>SlotCount</key> <integer>4</integer> </dict> What is correct? additionally report it http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2369526 Do you have this problem? thanks in advance Link to comment Share on other sites More sharing options...
PMheart Posted February 24, 2017 Share Posted February 24, 2017 @Slice i have a question. I used Clover Configurator and Cloud Clover Editor I'm not trying to compare the two apps. I want to know which one is correct and want to report it to the creator. CC use this CCE use What is correct? additionally report it http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2369526 Do you have this problem? thanks in advance I think they should be 'integer'. Please check the latest (currently r4017) Settings.c in src/edk2/Clover/rEFIt_UEFI/Platform/Settings.c at the start of LINE 5008. (Sorry the code is too much !) Link to comment Share on other sites More sharing options...
JahStories Posted February 24, 2017 Share Posted February 24, 2017 Any idea about the patching problem I reported here? Link to comment Share on other sites More sharing options...
Slice Posted February 24, 2017 Share Posted February 24, 2017 I think they should be 'integer'. Please check the latest (currently r4017) Settings.c in src/edk2/Clover/rEFIt_UEFI/Platform/Settings.c at the start of LINE 5008. (Sorry the code is too much !) Line206 is the explanation. GetPropertyInteger allows both "Integer" or "String" including HexString. Any idea about the patching problem I reported here? No ideas. 2 Link to comment Share on other sites More sharing options...
JahStories Posted February 24, 2017 Share Posted February 24, 2017 Link to comment Share on other sites More sharing options...
tluck Posted February 24, 2017 Share Posted February 24, 2017 @sherlocks , philip_petev Good report. I also reported other issue.1.5 still has issues. Spin wait and metadata never index can't help failure case in my case and your case.I will report it to syscl.Now, he is busy. Because he has exams.Thank you나의 LG-F410S 의 Tapatalk에서 보냄 syscl and I had a brief chat about this issue and why there could be nvram.plist in / some times. Note: we did not have a such an occurrence (file in /) However, the difference is likely because we are NOT running the nvram_script as part of the standard CloverDaemon shutdown process. we suspect this is the reason for random failure: why not? Running the nvram save script as a result of shutdown kill (in the standard CloverDaemon), is not going to be 100% reliable as there is a race to kill all processes and unmount all filesystems to shutdown gracefully. So sometimes it will work (mount ESP and complete the write) and every now and then it will not. A more reliable method (and endorsed by apple) has proven to be: use a LogoutHook. So I split CloverDaemon into 2 scripts - first one runs all startup scripts in /etc/rc.boot.d invoked by launchd - the 2nd one does NOT sit in a spin wait loop - BUT is ONLY run as a LogoutHook - which then runs all scripts in /etc/rc.shutdown.d 1 Link to comment Share on other sites More sharing options...
Micky1979 Posted February 24, 2017 Share Posted February 24, 2017 CC use this CCE use Pandora's Box do that: --> for me CCE is right I will look about GUID:Name records in nvram.plist interpretation by Clover. Anyway there is no value for boot0082 and no decryption key at all. Looks like this application didn't do the main work, it can't save new variables during sleep event. Tomorrow will do extensive tests. As I said there is a bug typing values with "String" tag 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted February 24, 2017 Share Posted February 24, 2017 @sherlocks , philip_petev syscl and I had a brief chat about this issue and why there could be nvram.plist in / some times. Note: we did not have a such an occurrence (file in /) However, the difference is likely because we are NOT running the nvram_script as part of the standard CloverDaemon shutdown process. we suspect this is the reason for random failure: why not? Running the nvram save script as a result of shutdown kill (in the standard CloverDaemon), is not going to be 100% reliable as there is a race to kill all processes and unmount all filesystems to shutdown gracefully. So sometimes it will work (mount ESP and complete the write) and every now and then it will not. A more reliable method (and endorsed by apple) has proven to be: use a LogoutHook. So I split CloverDaemon into 2 scripts - first one runs all startup scripts in /etc/rc.boot.d invoked by launchd - the 2nd one does NOT sit in a spin wait loop - BUT is ONLY run as a LogoutHook - which then runs all scripts in /etc/rc.shutdown.d okay. i understand it If there is a way to improve the problem, I am ready to test it. thank you Pandora's Box do that: gui.png -->txtmode.png for me CCE is right Tomorrow will do extensive tests. As I said there is a bug typing values with "String" tag thanks micky 1 Link to comment Share on other sites More sharing options...
D-an-W Posted February 24, 2017 Share Posted February 24, 2017 Hi folks, would anyone know if I can use Clover in any way to select the default audio device (Mine recently started reverting back to Headphone after a reboot)? If not, would anyone know where I might start to look? Sherlocks did mention trying Clover version r3974 but I don't think that had the fix to allow the latest Sierra betas to boot? Link to comment Share on other sites More sharing options...
tluck Posted February 24, 2017 Share Posted February 24, 2017 @sherlocks (and others) - nvram save via logouthook only - here is a zip with a script to convert to the "dual script" CloverDaemon with LogoutHook. it is essentially using the same /etc/rc.shutdown.d script - but will be initiated by LogoutHook - unzip and run nvram_save_patch.command script - reboot nvram-logouthook.zip 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted February 24, 2017 Share Posted February 24, 2017 @sherlocks (and others) - nvram save via logouthook only - here is a zip with a script to convert to the "dual script" CloverDaemon with LogoutHook. it is essentially using the same /etc/rc.shutdown.d script - but will be initiated by LogoutHook - unzip and run nvram_save_patch.command script - reboot I will test your script for weeks Thank you 나의 LG-F410S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
PMheart Posted February 25, 2017 Share Posted February 25, 2017 Line206 is the explanation. GetPropertyInteger allows both "Integer" or "String" including HexString. thx Slice. Link to comment Share on other sites More sharing options...
pico joe Posted February 25, 2017 Share Posted February 25, 2017 Hi folks, would anyone know if I can use Clover in any way to select the default audio device (Mine recently started reverting back to Headphone after a reboot)? If not, would anyone know where I might start to look? Sherlocks did mention trying Clover version r3974 but I don't think that had the fix to allow the latest Sierra betas to boot? me too in Sierra, but in Yosemite no problem (output @ internal speaker) 1 Link to comment Share on other sites More sharing options...
D-an-W Posted February 25, 2017 Share Posted February 25, 2017 Hopefully then it might get resolved with future Sierra updates Link to comment Share on other sites More sharing options...
PMheart Posted February 25, 2017 Share Posted February 25, 2017 Same here on ALC887. In most cases the default output device is HP instead of Speaker. Finally I resolved it by changing the patches for AppleHDA. (In the past I used 8419d411 -> 8708ec10, now using 8b19d411 -> 8708ec10 && 8a19d411 -> 00000000) And the problem got almost resolved after that. But I shall still seldom get HP as the default output device. Sent from my iPhone 7 using Tapatalk 2 Link to comment Share on other sites More sharing options...
D-an-W Posted February 25, 2017 Share Posted February 25, 2017 I would seriously run out of talent before I could figure out what was needed to fix that here! Good to know it isn't just something I did wrong however, thanks for the info. 1 Link to comment Share on other sites More sharing options...
telepati Posted February 25, 2017 Share Posted February 25, 2017 Hi Guys I made stupid thing. Broke my working system. Here is what I do; I changed Legacy Boot PBR to NONE You can ask me why doing do that? I just playing on Clover Configurator. I am a big fan of @Slice thread I am trying to new staff even I do not know what they do Anyway I shutdown my machine and restart again. Everything works I can't see any problem. Here is the problem when I turn NONE to PBR again my shutdown doesn't work anymore. Computer making restart after shutdown. I can shutdown with FixShutdown on ACPI fix. Questions; WHY this settings break my Shutdown? Should I need the PBR or can I use it as NONE? Link to comment Share on other sites More sharing options...
PMheart Posted February 26, 2017 Share Posted February 26, 2017 @Slice Hi. I found a new updated platform data of MacPro6,1 and here it is. [EDIT] CONFUSING CONTENTS REMOVED 1 Link to comment Share on other sites More sharing options...
Recommended Posts