Guest Posted January 8, 2018 Share Posted January 8, 2018 Attached files requested Thank you memmap > FS#:\memmap.txt Where # is a number of a writable filesystem to save memmap. Thankyou_Apianti.zip Link to comment Share on other sites More sharing options...
Balamut Posted January 8, 2018 Share Posted January 8, 2018 Available 0000000000100000-00000000657F9FFF 00000000000656FA 000000000000000FOh, come on, man! You can literally pick any slide, that is not encouraging. Did you try not setting it at all or slide=0? What slide values did you use? What other stuff are you using drivers/injection/etc? What is your board and CPU? Dude I might look like a simpleton but I’m not I promise you Off course I did, the only difference between booting and not was aptiofix update, with the old one the system loads fine. Yes I did every single possible combination with and without slide. I’ll be back in couple of hours and will post the clover folder. It’s Asus z10pe-d16, dual cpu board. Link to comment Share on other sites More sharing options...
apianti Posted January 8, 2018 Share Posted January 8, 2018 Thanks for posing a real world example of calculating slide. I understand that now. However, won't the slide memmap (and hence optimal slide value) change everytime I add/remove a PCI-e device? I change those around quite frequently for work, and often have 5+ PCI-e slots occupied. I was actually slightly off, you should follow this. It depends on how your firmware allocates the necessary regions and which slide you choose. Maybe? Dude I might look like a simpleton but I’m not I promise you Off course I did, the only difference between booting and not was aptiofix update, with the old one the system loads fine. Yes I did every single possible combination with and without slide. I’ll be back in couple of hours and will post the clover folder. It’s Asus z10pe-d16, dual cpu board. Just trying to figure out what you did already, to know where to go. You mean AptioFix2 right? You should be using AptioFix2. And you literally did slide=0 through slide=255? Are you using the official package r4369 driver? Attached files requested Thank you Remove all those boot args and try only slide=128, slide=129, or slide=0. 1 Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 Remove all those boot args and try only slide=128, slide=129, or slide=0. now I have -v darkwake=8 npci=0x2000 slide=128 without npci=0x2000 system should not start..I am trying by now :-) Link to comment Share on other sites More sharing options...
artur_pt Posted January 8, 2018 Share Posted January 8, 2018 hello apianti can check if I need any slide value all is working .. only problem is hibernation it stuck just before video .. it show the right desktop but is freeze FirmwareMemoryMap.txt.zip thanks Link to comment Share on other sites More sharing options...
Balamut Posted January 8, 2018 Share Posted January 8, 2018 I was actually slightly off, you should follow this. It depends on how your firmware allocates the necessary regions and which slide you choose. Maybe? Just trying to figure out what you did already, to know where to go. You mean AptioFix2 right? You should be using AptioFix2. And you literally did slide=0 through slide=255? Are you using the official package r4369 driver? Remove all those boot args and try only slide=128, slide=129, or slide=0. Yes sir, compiled myself from the source. I’ll test more in a couple of hours and will shoot you the clover folder just in case. Also will enable debug in the clover, maybe dual cpu systems are a bit off on the aptio v Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 (edited) yep without ncpi=0x2000 system hangs on pic configuration begin stage.. now I have -v darkwake=8 npci=0x2000 slide=128 without npci=0x2000 system should not start..I am trying by now :-) slide=0 printf error slide 128 ok but Nvram is not working slide 129 ok but Nvram is not working Edited January 8, 2018 by Guest Link to comment Share on other sites More sharing options...
apianti Posted January 8, 2018 Share Posted January 8, 2018 now I have -v darkwake=8 npci=0x2000 slide=128 without npci=0x2000 system should not start..I am trying by now :-) yep without ncpi=0x2000 system hangs on pic configuration begin stage.. Well use npci=0x2000 then and try slide=128, slide=129, and slide=0. If you still don't have working NVRAM, then try to write to a global variable that's in the whitelist. sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00 hello apianti can check if I need any slide value all is working .. only problem is hibernation it stuck just before video .. it show the right desktop but is freeze thanks You can try slide=0, but if it's working without then that's fine. There is probably a sleep/hibernation problem as we weren't sure if the regions needed fixed again or handed-off. EDIT: It could possibly be related to ACPI, I saw in your log that it says you have too many CPU APIC ids so it doesn't look like it does anything with it.... Have you completely fixed up your ACPI tables? Yes sir, compiled myself from the source. I’ll test more in a couple of hours and will shoot you the clover folder just in case. Also will enable debug in the clover, maybe dual cpu systems are a bit off on the aptio v I'm not sure about dual CPUs. I don't know how that's supposed to work at all. You using MacPro5,1? The debug.log might help maybe? EDIT: Somehow the comments got messed up. Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 (edited) before reboot Well use npci=0x2000 then and try slide=128, slide=129, and slide=0. If you still don't have working NVRAM, then try to write to a global variable that's in the whitelist. sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00 Last login: Mon Jan 8 18:52:35 on ttys000 fabios-Mac-Pro:~ fabio$ sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00 Password: fabios-Mac-Pro:~ fabio$ sudo nvram -p fakesmc-key-MSWr-ui8 %00 flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 fakesmc-key-RBr -ch8* j90%00%00%00%00%00 fakesmc-key-EPCI-ui32 %06%f0%f0%00 fakesmc-key-MSAc-ui16 %00%00 efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3A55787E-1275-45BE-87EB-0ACF96BC0343</string></dict></dict></dict></array> fakesmc-key-CLKH-{clh %00%00p%80%00%01%19@ bootercfg (%00 fakesmc-key-NATi-ui16 %00%1e LocationServicesEnabled %01 fakesmc-key-NTOK-ui8 %01 fakesmc-key-BATP-flag %00 fakesmc-key-$Num-ui8 %01 fakesmc-key-REV -ch8* %02 %0f%00%00%18 bluetoothActiveControllerInfo %0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3 fakesmc-key-HI0N-ui8 %10 fmm-computer-name fabio%e2%80%99s Mac Pro fakesmc-key-MSTc-ui8 %00 fakesmc-key-MSPS-ui16 %00%03 fakesmc-key-RMde-char A csr-active-config g%00%00%00 fakesmc-key-RPlt-ch8* j90%00%00%00%00%00 fakesmc-key-BEMB-flag %00 fakesmc-key-#KEY-ui32 %00%00%00%10 SystemAudioVolume A fakesmc-key-MSFW-ui8 %01%00 specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00 security-mode none fakesmc-key-LsBA-ui8 %90 fakesmc-key-$Adr-ui32 %00%00%03%00 nvda_drv 1%00 EFILoginHiDPI %00%00%00%00 fakesmc-key-CLKT-ui32 %00%01%09u fakesmc-key-MSDW-ui8 %01 fakesmc-key-BNum-ui8 %00 SystemAudioVolumeDB %f0 fakesmc-key-NATJ-ui8 %02 efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00 fabios-Mac-Pro:~ fabio$ after Last login: Mon Jan 8 19:11:45 on console fabios-Mac-Pro:~ fabio$ sudo nvram -p Password: fakesmc-key-MSWr-ui8 %00 flagstate %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00 fakesmc-key-RBr -ch8* j90%00%00%00%00%00 fakesmc-key-EPCI-ui32 %06%f0%f0%00 fakesmc-key-MSAc-ui16 %00%00 efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3A55787E-1275-45BE-87EB-0ACF96BC0343</string></dict></dict></dict></array> fakesmc-key-CLKH-{clh %00%00p%80%00%01%19@ bootercfg (%00 fakesmc-key-NATi-ui16 %00%1e LocationServicesEnabled %01 fakesmc-key-NTOK-ui8 %01 fakesmc-key-BATP-flag %00 fakesmc-key-$Num-ui8 %01 fakesmc-key-REV -ch8* %02 %0f%00%00%18 bluetoothActiveControllerInfo %0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3 fakesmc-key-HI0N-ui8 %10 fmm-computer-name fabio%e2%80%99s Mac Pro fakesmc-key-MSTc-ui8 %00 fakesmc-key-MSPS-ui16 %00%03 fakesmc-key-RMde-char A csr-active-config g%00%00%00 fakesmc-key-RPlt-ch8* j90%00%00%00%00%00 fakesmc-key-BEMB-flag %00 fakesmc-key-#KEY-ui32 %00%00%00%10 SystemAudioVolume A fakesmc-key-MSFW-ui8 %01%00 specialbootdevice %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00 security-mode none fakesmc-key-LsBA-ui8 %90 fakesmc-key-$Adr-ui32 %00%00%03%00 nvda_drv 1%00 EFILoginHiDPI %00%00%00%00 fakesmc-key-CLKT-ui32 %00%01%0d%f5 fakesmc-key-MSDW-ui8 %01 fakesmc-key-BNum-ui8 %00 SystemAudioVolumeDB %f0 fakesmc-key-NATJ-ui8 %02 efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%03%00%00%00%00H%0a%00%00%00%00%00%88%ca%93;%00%00%00%00~xU:u%12%beE%87%eb%0a%cf%96%bc%03C%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%ea%00%1f.%994-E%bd%9e%da%ff%12}%c4%a6%7f%ff%04%00 fabios-Mac-Pro:~ fabio$ Edited January 8, 2018 by Guest Link to comment Share on other sites More sharing options...
apianti Posted January 8, 2018 Share Posted January 8, 2018 after You didn't print the value of the variable sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 ops fabios-Mac-Pro:~ fabio$ sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout Password: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %05%00 fabios-Mac-Pro:~ fabio$ Link to comment Share on other sites More sharing options...
artur_pt Posted January 8, 2018 Share Posted January 8, 2018 You can try slide=0, but if it's working without then that's fine. There is probably a sleep/hibernation problem as we weren't sure if the regions needed fixed again or handed-off. hello apianti hibernation works .. I think in 10.9 with dazmar efi driver fix2 , pmsethibernationmode=57 after that the pmset change and not accept that value i will try the slide=0 all the best thanks Link to comment Share on other sites More sharing options...
Matthew82 Posted January 8, 2018 Share Posted January 8, 2018 On asus x99 the same. Working good with slide=128 and OsxAptioFix2Drv-64.efi. Mateuszs-Pro:~ mateuszjachym$ sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout Password: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %05%00 Mateuszs-Pro:~ mateuszjachym$ Link to comment Share on other sites More sharing options...
Funky frank Posted January 8, 2018 Share Posted January 8, 2018 How do I generate such a print of the Firmware memory map? Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 Hi Matthew82 what do you mean? have you a working Nvram which resist to a reboot? On asus x99 the same. Working good with slide=128 AP2. Mateuszs-Pro:~ mateuszjachym$ sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout Password: 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %05%00 Mateuszs-Pro:~ mateuszjachym$ Link to comment Share on other sites More sharing options...
Matthew82 Posted January 8, 2018 Share Posted January 8, 2018 Hi Matthew82 what do you mean? have you a working Nvram which resist to a reboot? I don't know. Just giving the info of the nvram result Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 (edited) I don't know. Just giving the info of the nvram result ok try this if you can without emuvariabledriver64 uefi and rc script sudo nvram test="value" then reboot and put output from sudo nvram -p and see if test variable is there after reboot.. in my case no #16151 How do I generate such a print of the Firmware memory map? Edited January 8, 2018 by Guest Link to comment Share on other sites More sharing options...
Funky frank Posted January 8, 2018 Share Posted January 8, 2018 Please give me memmap from EFI shell after clover GUI and boot.log (or debug.log) when using AptioFix2 from at least r4369. Please try this AptioFix2 and let me know results. Could be a disaster... Could work. Thanks! How do I make a memmap? Your provided AptioFix2 has same result: Crash in FCPX with activated connector-full hd4600. Link to comment Share on other sites More sharing options...
Guest Posted January 8, 2018 Share Posted January 8, 2018 read here as I said before #16151 Thanks! How do I make a memmap? Your provided AptioFix2 has same result: Crash in FCPX with activated connector-full hd4600. Link to comment Share on other sites More sharing options...
Funky frank Posted January 8, 2018 Share Posted January 8, 2018 in my case no #16151 And how do I know which FS number is a writable FS? memmap > FS#:\memmap.txt Where # is a number of a writable filesystem to save memmap. Link to comment Share on other sites More sharing options...
tluck Posted January 8, 2018 Share Posted January 8, 2018 @Funky frank Thanks! How do I make a memmap? Your provided AptioFix2 has same result: Crash in FCPX with activated connector-full hd4600. i did it like this: 1) boot to clover and use the tools to go into shell. 2) run command to "mount ESP": map fs0 3) type this to enter this mount filesystem: fs0: 4) go to misc folder: cd EFI/CLOVER/misc 5) run the command: memmap > memmap.txt then startup macOS - mount ESP - cd to misc folder - read (cat) memmap.txt file. 2 Link to comment Share on other sites More sharing options...
gujiangjiang Posted January 8, 2018 Share Posted January 8, 2018 I want to said we can use sip=0 or other value to boot into macOS. On my old laptop using Clover Legacy it can be set sop csr to 0x00 and can inject all the 3-rd part kexts and with no problem. On my new XPS15 I just set sip csr to 0x40 to disable nvram district and still works well with all 3-rd part kexts. I don’t know why many people think I’d set csr=0x00 it will not load 3-rd part kexts?Does you test it by your self or it just you think it? I have test 0x00 from installing to finishing and with no problem with my old laptop and 0x40 with my new laptop.Both can inject all the kexts very well and can rebuild the kernel cache by KCPM. I want set csr=0x00 with my new laptop but can’t. With aptiov2 I must set 0x40 to avoid memory allocation error but with no affect with 3-rd part kexts injection. Thanks. 从我的 iPhone 发送，使用 Tapatalk Link to comment Share on other sites More sharing options...
Funky frank Posted January 8, 2018 Share Posted January 8, 2018 Thanks! Now simply plugged in a usb stick, which FS# was more obvious. Please give me memmap from EFI shell after clover GUI and boot.log (or debug.log) when using AptioFix2 from at least r4369. Here: memmap.txt Where do I find boot.log? Ok, here also is boot.log: bootlog.txt Link to comment Share on other sites More sharing options...
el_charlie Posted January 8, 2018 Share Posted January 8, 2018 Guys, I need some assistance with my laptop ASUS U46E (Intel HD 3000): I'm now using Clover r4369 with AptioFix2 and calculated my slide and found the value of 0x201 (513). I can even boot without a slide value or with that slide=513 but I can't reboot. As soon as I reboot I get the prohibited sign or the print-f work message. Attached are my memmap and boot.log. My nvram was already working without any help in UEFI mode. I still can't get rid of some graphic artifacts like lines on the screen that appear when I'm starting using programs. Thanks in advance! memmap.txt bootlog.log.txt Link to comment Share on other sites More sharing options...
Funky frank Posted January 8, 2018 Share Posted January 8, 2018 What about slide=2048 (0x800), so targeting address space 0x100000000 ? Or is such a value too big? Link to comment Share on other sites More sharing options...
Recommended Posts