Clover General discussion

mhaeuser · January 8, 2018

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

The entire kernel range must reside below that area.

tluck · January 9, 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

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

el_charlie · January 9, 2018

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!

apianti · January 9, 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$

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.

Regi Yassin · January 9, 2018

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

el_charlie · January 9, 2018

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.

apianti · January 9, 2018

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.

Regi Yassin · January 9, 2018

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?

test var wasnt success,

still have no working nvram.

never set anything before for nvream

apianti · January 9, 2018

test var wasnt success,

still have no working nvram.

never set anything before for nvream

Those are tests to see if you have working native NVRAM. Are you sure that you couldn't write to the global Timeout variable? You restarted? It seems to me that ASUS Z97 and X99 both have the whitelist issue, where your NVRAM is actually working but you can only write a small subset of non consequential variables because they are whitelisted by the firmware.

EDIT: Anyone with these platforms that can't replace or patch the modules will have to use EmuVar still for now.

el_charlie · January 9, 2018

Please try the AptioFix2 driver attached to this post.

The same message. Removing the slide=39 boots just fine.

TL;DR: slide=0 , slide=39 results in printf message. slide=257 or slide=513 boots fine but apparently it does nothing.

apianti · January 9, 2018

The same message. Removing the slide=39 boots just fine.

TL;DR: slide=0 , slide=39 results in printf message. slide=257 or slide=513 boots fine but apparently it does nothing.

What about no slide at all? Please try this driver:

OsxAptioFix2Drv-64.efi

Regi Yassin · January 9, 2018

Those are tests to see if you have working native NVRAM. Are you sure that you couldn't write to the global Timeout variable? You restarted? It seems to me that ASUS Z97 and X99 both have the whitelist issue, where your NVRAM is actually working but you can only write a small subset of non consequential variables because they are whitelisted by the firmware.

EDIT: Anyone with these platforms that can't replace or patch the modules will have to use EmuVar still for now.

after running this

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

and restarted

it still the same, not back to 1

i tried all bioses from asus, all of them cant write to nvram, so i presume i have no modules that writeable, am i right?

but i dont need emuvar and/or rc script,

all working as expected. volume level is preserved after restart. (i dont know what that means)

apianti · January 9, 2018

after running this

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

and restarted

it still the same, not back to 1

i tried all bioses from asus, all of them cant write to nvram, so i presume i have no modules that writeable, am i right?

but i dont need emuvar and/or rc script,

all working as expected. volume level is preserved after restart. (i dont know what that means)

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

el_charlie · January 9, 2018

What about no slide at all? Please try this driver:

It boots fine(*) with no slide at all. slide=39 results in printf message (no boot).

(*) sometimes I get prohibited sign after a reboot, sometimes after a cold boot. Most of the times it boots.

Regi Yassin · January 9, 2018

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

correct, nvram test="value", restart, nvram test >> nvram: Error getting variable - 'test': (iokit/common) data was not found

can i test timeout to another value ?

EDIT : change time out back to 1

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

restart, and its stayed 1.

January 9, 2018

Hi apianti

variable below are achieved in this way

osx 10.13.2

no RC Script and no emuvariable installed

on clover boot menu Nvram cleaned with f11 key

all these variable are set by OSX/Clover R.4369

Last login: Tue Jan  9 07:18:43 on consolefabios-Mac-Pro:~ fabio$ sudo nvram -pPassword:fakesmc-key-MSWr-ui8	%00flagstate	%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%00fakesmc-key-RBr -ch8*	j90%00%00%00%00%00fakesmc-key-EPCI-ui32	%06%f0%f0%00fakesmc-key-MSAc-ui16	%00%00efi-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	(%00fakesmc-key-NATi-ui16	%00%1eLocationServicesEnabled	%01fakesmc-key-NTOK-ui8	%01fakesmc-key-BATP-flag	%00fakesmc-key-$Num-ui8	%01fakesmc-key-REV -ch8*	%02 %0f%00%00%18bluetoothActiveControllerInfo	%0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3fakesmc-key-HI0N-ui8	%10fmm-computer-name	fabio%e2%80%99s Mac Profakesmc-key-MSTc-ui8	%00fakesmc-key-MSPS-ui16	%00%03fakesmc-key-RMde-char	Acsr-active-config	g%00%00%00fakesmc-key-RPlt-ch8*	j90%00%00%00%00%00fakesmc-key-BEMB-flag	%00fakesmc-key-#KEY-ui32	%00%00%00%10SystemAudioVolume	Afakesmc-key-MSFW-ui8	%01%00specialbootdevice	%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%00security-mode	nonefakesmc-key-LsBA-ui8	%90fakesmc-key-$Adr-ui32	%00%00%03%00nvda_drv	1%00EFILoginHiDPI	%00%00%00%00fakesmc-key-CLKT-ui32	%00%00f%d8fakesmc-key-BNum-ui8	%00SystemAudioVolumeDB	%f0fakesmc-key-NATJ-ui8	%02efi-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%00fabios-Mac-Pro:~ fabio$

And it seems a common situation with x99 users (maybe only Asus users?)

So you are no able to write sudo nvram test="value", restart, and see sudo nvram test, print out it is "value"? But you can write to the global Timeout if it stayed at 5, and if you can write to other variables and you are not using EmuVar are you sure you couldn't write the test variable??

apianti · January 9, 2018

correct, nvram test="value", restart, nvram test >> nvram: Error getting variable - 'test': (iokit/common) data was not found

can i test timeout to another value ?

EDIT : change time out back to 1

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

restart, and its stayed 1.

Hi apianti

variable below are achieved in this way

osx 10.13.2

no RC Script and no emuvariable installed

on clover boot menu Nvram cleaned with f11 key

all these variable are set by OSX/Clover R.4369

Last login: Tue Jan  9 07:18:43 on consolefabios-Mac-Pro:~ fabio$ sudo nvram -pPassword:fakesmc-key-MSWr-ui8	%00flagstate	%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%00fakesmc-key-RBr -ch8*	j90%00%00%00%00%00fakesmc-key-EPCI-ui32	%06%f0%f0%00fakesmc-key-MSAc-ui16	%00%00efi-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	(%00fakesmc-key-NATi-ui16	%00%1eLocationServicesEnabled	%01fakesmc-key-NTOK-ui8	%01fakesmc-key-BATP-flag	%00fakesmc-key-$Num-ui8	%01fakesmc-key-REV -ch8*	%02 %0f%00%00%18bluetoothActiveControllerInfo	%0a%18%05%0b%00%00%00%00`%14%f0%03%8c<%b5%a3fakesmc-key-HI0N-ui8	%10fmm-computer-name	fabio%e2%80%99s Mac Profakesmc-key-MSTc-ui8	%00fakesmc-key-MSPS-ui16	%00%03fakesmc-key-RMde-char	Acsr-active-config	g%00%00%00fakesmc-key-RPlt-ch8*	j90%00%00%00%00%00fakesmc-key-BEMB-flag	%00fakesmc-key-#KEY-ui32	%00%00%00%10SystemAudioVolume	Afakesmc-key-MSFW-ui8	%01%00specialbootdevice	%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%00security-mode	nonefakesmc-key-LsBA-ui8	%90fakesmc-key-$Adr-ui32	%00%00%03%00nvda_drv	1%00EFILoginHiDPI	%00%00%00%00fakesmc-key-CLKT-ui32	%00%00f%d8fakesmc-key-BNum-ui8	%00SystemAudioVolumeDB	%f0fakesmc-key-NATJ-ui8	%02efi-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%00fabios-Mac-Pro:~ fabio$

And it seems a common situation with x99 users (maybe only Asus users?)

Yes, ASUS Z97 and X99 users will have to continue to use EmuVar if setting the test variable does not work, as they still don't have fully working NVRAM because the firmware itself has a very stupid bug....

It boots fine(*) with no slide at all. slide=39 results in printf message (no boot).

(*) sometimes I get prohibited sign after a reboot, sometimes after a cold boot. Most of the times it boots.

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

OsxAptioFix2Drv-64.efi

Funky frank · January 9, 2018

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.

Hi, I do not set the bus speed in config.plist. Please have a look at it:

config.plist.zip

How can I fix that? Btw. my bios is in "turbo" mode, so maybe overclock everything a bit. Should I then set the busspeed?

Do you mean that it is too slow? Because I am fine with it, if it was too fast

EDIT: So the busspeed should be 100MHz / 100000kHz? I now actually set the busspeed to 100000, and it is reporting now:

Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=3400MHz PIS: hw.busfrequency=100000000Hz

Does that look correct to you?

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

This one still crashes in FCPX while using opencl hd4600+nvidia. Do you really think that it crashes because of memory corruption? The area in my memory map at 0x10000 looks quite big to me....?

btw. the Info.plist kext patching in clover is quite retarded: You cannot use strings for search/replace, it seems:

0:114 0:000 - [06]: AppleGraphicsPowerManagement (disable GFX0 pm)[ERROR] bin2hex 'GFX0' syntax error

0:114 0:000 [ERROR] bin2hex 'GFXX' syntax error

0:114 0:000 - invalid Find/Replace data - skipping!

Needy · January 9, 2018

Remove EmuVar driver and use AptioFix2 driver from at least r4369, have native NVRAM.

Disregard my previous messages.

I can confirm that it works with the latest AptioFix2 driver. Ty

KGP-iMacPro · January 9, 2018

News from the Skylake-X/X299 SMBIOS iMacPro1,1 front

System boots flawless with OsxAptioFixDrv-64.efi from Clover_v2.4k_r4369. No memory allocation errors and no slide boot flag necessary (see attachment IMG_5991.png)

Nevertheless, problems with the macOS 10.13.2 17C2120 USB Flash Drive Installer.

USB MacOS Installer partition does not appear in the Clover Boot Menu.

I don't know if the problem is Clover or macOS USB Flash Drive Installer related.

When booting with the EFI on the USB Drive, I get the following message before entering the clover boot menu (see attachment 2 IMG-9550.png)

el_charlie · January 9, 2018

So neither of those two other drivers gives different results? Hmmmmm... Please try this one then

The same results

I think I might go with Aptio1. With Aptio 2, sometimes I get the prohibited sign. Mostly when I turn off the computer for more than a minute.

When I get the prohibted sign, I turn it off (just press the power button, no need to press and hold) and turn it on right away and it boots fine.

Thanks anyway you've been very helpful. I have to live with those graphics glitches.

marcozardi · January 9, 2018

where i find kext disabling menu on last clover (4369) ?

Matthew82 · January 9, 2018

News from the Skylake-X/X299 SMBIOS iMacPro1,1 front

System boots flawless with OsxAptioFixDrv-64.efi from Clover_v2.4k_r4369. No memory allocation errors and no slide boot flag necessary (see attachment IMG_5991.png)

Nevertheless, problems with the macOS 10.13.2 17C2120 USB Flash Drive Installer.

USB MacOS Installer partition does not appear in the Clover Boot Menu.

I don't know if the problem is Clover or macOS USB Flash Drive Installer related.

When booting with the EFI on the USB Drive, I get the following message before entering the clover boot menu (see attachment 2 IMG-9550.png)

You have asus x299? Your NVRAM working natively? Your MSR is unlocked?

KGP-iMacPro · January 9, 2018

You have asus x299? Your NVRAM working natively? Your MSR is unlocked?

Yes... i9-7980XE with ASUS Prime X299 Deluxe... MSR is locked.. no way so far to unlock..

How to check if NVRAM works natively?

Regi Yassin · January 9, 2018

Yes ASUS Prime X299 Deluxe... MSR is locked.. no way so far to unlock..

How to check if NVRAM works natively?

sudo nvram Test="Value" > reboot > nvram Test

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites