Jump to content
30960 posts in this topic

Recommended Posts

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.

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 by Guest

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 

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$ 

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$ 

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 by Guest

 

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.

@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. 

  • Like 2

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

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

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

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!

 

attachicon.gifmemmap.txt

attachicon.gifbootlog.log.txt

 

 

I was you, I might try slide of 257 -> targets this area:

available  0000000020200000-000000003FFFFFFF  000000000001FE00 000000000000000F

 

 

$ cat foo |grep avail

available  0000000000008000-000000000006EFFF  0000000000000067 000000000000000F

available  0000000000100000-0000000000FFFFFF  0000000000000F00 000000000000000F

available  0000000003236000-0000000003236FFF  0000000000000001 000000000000000F

available  0000000003252000-0000000003252FFF  0000000000000001 000000000000000F

available  0000000003267000-0000000003267FFF  0000000000000001 000000000000000F

available  0000000003316000-0000000003332FFF  000000000000001D 000000000000000F

available  0000000003449000-0000000003DFEFFF  00000000000009B6 000000000000000F

available  0000000004DA0000-000000001FFFFFFF  000000000001B260 000000000000000F

available  0000000020200000-000000003FFFFFFF  000000000001FE00 000000000000000F

available  0000000040200000-00000000B7A03FFF  0000000000077804 000000000000000F

available  00000000B7B04000-00000000BA30FFFF  000000000000280C 000000000000000F

available  00000000BA9F7000-00000000BA9F7FFF  0000000000000001 000000000000000F

available  00000000BA9FF000-00000000BABCCFFF  00000000000001CE 000000000000000F

available  00000000BACF4000-00000000BACF5FFF  0000000000000002 000000000000000F

available  00000000BADE8000-00000000BAF25FFF  000000000000013E 000000000000000F

available  00000000BAFE8000-00000000BAFFCFFF  0000000000000015 000000000000000F

available  0000000100000000-000000023FDFFFFF  000000000013FE00 000000000000000F

  • Like 1

I was you, I might try slide of 257 -> targets this area:

available  0000000020200000-000000003FFFFFFF  000000000001FE00 000000000000000F

 

 

$ cat foo |grep avail

available  0000000000008000-000000000006EFFF  0000000000000067 000000000000000F

available  0000000000100000-0000000000FFFFFF  0000000000000F00 000000000000000F

available  0000000003236000-0000000003236FFF  0000000000000001 000000000000000F

available  0000000003252000-0000000003252FFF  0000000000000001 000000000000000F

available  0000000003267000-0000000003267FFF  0000000000000001 000000000000000F

available  0000000003316000-0000000003332FFF  000000000000001D 000000000000000F

available  0000000003449000-0000000003DFEFFF  00000000000009B6 000000000000000F

available  0000000004DA0000-000000001FFFFFFF  000000000001B260 000000000000000F

available  0000000020200000-000000003FFFFFFF  000000000001FE00 000000000000000F

available  0000000040200000-00000000B7A03FFF  0000000000077804 000000000000000F

available  00000000B7B04000-00000000BA30FFFF  000000000000280C 000000000000000F

available  00000000BA9F7000-00000000BA9F7FFF  0000000000000001 000000000000000F

available  00000000BA9FF000-00000000BABCCFFF  00000000000001CE 000000000000000F

available  00000000BACF4000-00000000BACF5FFF  0000000000000002 000000000000000F

available  00000000BADE8000-00000000BAF25FFF  000000000000013E 000000000000000F

available  00000000BAFE8000-00000000BAFFCFFF  0000000000000015 000000000000000F

available  0000000100000000-000000023FDFFFFF  000000000013FE00 000000000000000F

 

Thanks, I also tried that. Went with 513 because the region 0x40200000 has more pages available. Anyway without slide or with slide=257 or slide=513 I still can't reboot properly. I have to shutdown and then turn on the laptop. Otherwise I get the prohibited sign or "does printf work?" on -v.

 

I was hoping that by using AptioFix2 I would get rid of the annoying graphic glitches of my HD3000.

 

Cheers!

 

EDIT: well, using 257 allows me to rebooth this time! I found some glitches but so far, so good. Thanks!

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$

 

So you have working NVRAM but the firmware that has the whitelist restriction as you were able to write to one of the whitelisted global variables. I am unsure how to solve this.

 


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 

 

 

Yes, I understand it used to work. After r4369, AptioFix can no longer work reliably, so if you are using that don't use it. Use AptioFix2. I know currently sleep/hibernate is probably broken because of the method of preserving runtime regions changing. I am unsure the best way to solve as there are a few possibilities. There's no need to use slide=0 if you are getting a good boot without using it.

 

 

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$ 

 

Yeah, I think this is confirmation that ASUS X99 also apparently have the whitelist issue. I guess you guys will have to continue to use EmuVar for now until a solution is found to bypass the whitelist.

 

I want to said we can use sip=0 or other value to boot into macOS.

 

Because there are patches by clover to allow this and work.

 

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.

 

Don't conflate injecting and loading kexts. Unsigned kexts will not be loaded by the kernel or the cache if bit 0 is unset in csr config. Injection is patched. No injected kext is added to a rebuilt cache. With AptioFix2 from at least r4369 you must set csr config to 0x40?

 

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!

 

Try slide=39. You must have miscalculated as there is it must be in range 0 to 255.

 

What about slide=2048 (0x800), so targeting address space 0x100000000 ? Or is such a value too big?

 

Only the range 0 to 255 are acceptable values.

 

The entire kernel range must reside below that area.

 

Haha, yeah.

 

I was you, I might try slide of 257 -> targets this area:

available  0000000020200000-000000003FFFFFFF  000000000001FE00 000000000000000F

 

No, that is not acceptable position. It is higher in memory than the slide regions.

 

Thanks, I also tried that. Went with 513 because the region 0x40200000 has more pages available. Anyway without slide or with slide=257 or slide=513 I still can't reboot properly. I have to shutdown and then turn on the laptop. Otherwise I get the prohibited sign or "does printf work?" on -v.

 

I was hoping that by using AptioFix2 I would get rid of the annoying graphic glitches of my HD3000.

 

Cheers!

 

EDIT: well, using 257 allows me to rebooth this time! I found some glitches but so far, so good. Thanks!

 

Don't see how using 257 (that's not a valid value) didn't just disable KASLR and put you at slide=0, where there is a region that can probably load the kernel.

available  0000000000100000-0000000000FFFFFF  0000000000000F00 000000000000000F

EDIT: Actually it looks as though passing an invalid valid just lets it choose, so it's just like not setting slide.

 

Please try slide=39, you have a perfectly acceptable region there at 0x4F00000.

available  0000000004DA0000-000000001FFFFFFF  000000000001B260 000000000000000F

Thanks!

 

Now simply plugged in a usb stick, which FS# was more obvious.

 

 

Here: 

 

Ok, here also is boot.log:

 

I actually think you need to remove the key for your CPU bus speed from config.plist.

0:100  0:000  BrandString = Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
...
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:100  0:000  MaxDiv/MinDiv: 34.0/8
0:100  0:000  Turbo: 37/38/39/39
0:100  0:000  Features: 0xBFEBFBFF
0:100  0:000  Threads: 8
0:100  0:000  Cores: 4
0:100  0:000  FSB: 100 MHz
0:100  0:000  CPU: 3400 MHz
0:100  0:000  TSC: 3400 MHz
0:100  0:000  PIS: 100 MHz
0:100  0:000  ExternalClock: 25 MHz
...
164:674  0:000  Finally: ExternalClock=24MHz BusSpeed=99768kHz CPUFreq=3392MHz PIS: hw.busfrequency=96000000Hz

That's a pretty significant clock difference.

  • Like 1

So you have working NVRAM but the firmware that has the whitelist restriction as you were able to write to one of the whitelisted global variables. I am unsure how to solve this.

what about this ?

sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout

Password:

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %01%00

 

 

 

Try slide=39. You must have miscalculated as there is it must be in range 0 to 255.

 

 

 

 

Don't see how using 257 (that's not a valid value) didn't just disable KASLR and put you at slide=0, where there is a region that can probably load the kernel.

available  0000000000100000-0000000000FFFFFF  0000000000000F00 000000000000000F

Please try slide=39, you have a perfectly acceptable region there at 0x4F00000.


 

Nope, slide=39 gives me the message "does printf work?" or prohibited sign if -v is not set.

what about this ?

sudo nvram 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout

8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout %01%00

 

I'm not sure what you're asking? Did you do the other steps? Did you try setting a test variable, restart and check if it was there? Did you try setting to 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Timeout=%05%00 before this and restart?

 

 

Nope, slide=39 gives me the message "does printf work?" or prohibited sign if -v is not set.

 

Please try the AptioFix2 driver attached to this post.

×
×
  • Create New...