Jump to content
ErmaC

Clover General discussion

22,503 posts in this topic

Recommended Posts

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

Share this post


Link to post
Share on other sites
Advertisement

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

 

 

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

 

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.

Share this post


Link to post
Share on other sites

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)

Share this post


Link to post
Share on other sites

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??

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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??

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

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!

Share this post


Link to post
Share on other sites

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)

 

  

 

 

post-1362934-0-80970600-1515499298_thumb.png

post-1362934-0-65950100-1515499634_thumb.png

Share this post


Link to post
Share on other sites

 

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.

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

Announcements

  • Similar Content

    • By surfermax
      buon giorno 
      spero tu mi possa aiutare ,perche' non riesco piu' a far partire i miei 2 ssd 850 samsung sui quali highsierra funzionava perfettamente da 1 anno e non ce' maniera di farlo ripartire .unica cosa e' che riesco ad arrivare alla console dell'istaller e ho tentato varie volte di ripristinare da una time machine che ho salvato su un altro disco usb .
      il mio sistema e' un asus p5qd turbo ed e7500 dual core . grafica gtx1050 chr funzionava con accelerazione e webdriver nvidia .audio voodoo 282. e boot clover che e' sempre stato il 5103 che poi  ho aggiornato a 5120 proprio il giorno prima che succedesse il fattaccio .quel giorno ho aggiornato dal sito apple la comboupdate 10.13 .6 da 10.13.4 .e qui al riavvio boom niente diski in clover nn li visualizzava piu .ora sciacciando f3 visualizzo il preboot e lssd con highsierra aggiornato ma arrivato alla console andava in reset loop .
      a questo punto riesco a ripartire togliendo l'accelerazione .e installando i nuovi webdriver di nvidia aggiornati all 10.13.6 .
      al riavvio non parte piu' con accelerazione e sempre problema in clover dei diski ma riuscivo a partire con f3 e preboot .
      ora decido di installare da time machine e tornare alla versione 10.13.4 del giorno prima ..e al riavvio niente piu dischi ne preboot .sono fermo a questo punto ..riesco solo a far partire installer ma nn so i comandi da dare in terminal per aggiustare le cose . ho anche linux su un altro notebook. ti ringrazio anticipatamente per l'aiuto .
    • By pink101
      So, here's what i think clover do when it patch ati framebuffer, first it read a cached kext, then it search the original hex value of the connector, then it changed the value with the new one. Is it correct? now, here's what i find confusing... let's say that i want to patch AMD7000Controller.kext, in that kext, i want to patch "AJI" framebuffer with a new value, so clover try to find the hex value of "AJI" connector then replace it with the new one, simple right? but when i search the AMD7000Controller binary file for other framebuffer, some of them didn't exist in the binary, for example, i tried to patch "Ramen" framebuffer, from various source, it said that:
      Ramen (6) @ 0xeba70 LVDS, HDMI, DP, DP, DP, DP 020000000001000039050108000000002001050600000000 000800000402000000010200000000001000030500000000 000400000403000000010343000000001102010100000000 000400000001000000010431000000002103040300000000 000400000403000000010563000000001204020200000000 000400000001000000010651000000002205040300000000 So i open a hex editor and search for:
      020000000001000039050108000000002001050600000000000800000402000000010200000000001000030500000000000400000403000000010343000000001102010100000000000400000001000000010431000000002103040300000000000400000403000000010563000000001204020200000000000400000001000000010651000000002205040300000000 but, it turns out that hex editor couldnt find that hex value in AMD7000Controller,

       
      most of the framebuffer exist in the AMD7000Controller, but some doesnt, If this is the case, then, where does clover find the original framebuffer to be patched? am i missing something?
       
       
    • By tluck
      Lenovo T460 macOS with Clover Guide
      Latest Release on GitHub (July 2020) Updated to Clover r5120 Updated Lilu based kexts - Lilu, ALC, WEG Added AirportBrcmFixup.kext
        Various Tweaks over Last months The main branch in my github repo is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle seems to work on Sierra, HighSierra, Mojave and Catalina. There is an OpenCore branch in the repo as an alternative to Clover. This guide was developed for a Clover implementation. But the thread has evolved to include discussion of both Clover and Opencore for these systems: T460 and T470 family of ThinkPads.
       
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (the old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • By tlefko
      News
      In light of the recent WWDC, we will begin testing the functionality of our EFI on macOS 11 for this device with the latest developer preview Version Info
      Features and Overview
      Now Compatible with 10.15.6 Please leave feedback with issues or w/o Comitted to Updating up to OS 11 Multitouch Trackpad Support 4K @60 Hz Fixed Bluetooth and Wifi Stability Issues Preformance and Power Management Additional Patches for 4K Display updated for 15.6 rev 1 Sleep Wake is functional for some models ----if screen glitches on wake or reopen lid. If this is a bother just disable sleep. This is issue is resolved in Big Sur Bugs
      Some models may experience screen split in half. If so disable. USB devices eject (external) No Internal Mic What Works
      Everything minus sleep issue above, internal microphone. (audio is fine, headphones / usb mic fine, just not laptop mic) POST
      run sudo pmset -a hibernatemode 0
      Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. You can easily view all the DSDT patches along with configuration files for the bootloader as they are all documented clearly in the files. This does include a copy of Clover, which of course I do not contribute to and am only responsible for the provided files, patches, and kext placements This guide provides a working setup with little knowledge of the topic and without "optimization" (because often they can break things). But, it is fully functional and preforms properly and is stable.
      Unsupported Wifi
      Make sure you are using DW1560 or 1820a for wifi or else there is a risk of KP. If not using remove BRCM kexts from CLOVER>kexts>other Styling
      This guide is designed to be literally as thorough as possible to appeal all types of users. It does not cover complex topics like undervolting etc etc only to provide a completely functional system
      Notes
      Never tested USB C except for charging, USB, works great (not sure about DispOut) 4K model has sleep wake issues occasionally, 1080P is fully functional BIOS
      Disable Secure Boot Disable Vt-d Recommended: Clean Install (Preinstall steps)
      Format a USB (16GB) as Journaled and then proceed to download the latest Catalina Installer Patcher Application. Download the latest Catalina installer from within the Patcher App, and select to download a new copy and install to your USB device Download the clover configurator application and mount the EFI of the USB partition, then copy the contents of the Files linked above to A new EFI Folder (that you create) within the EFI partition. ** This is because the App Store installers will often not download a full installer, just an truncated version that downloads the installer files from the interent while installing. Thus, they're not bootable from a USB as they're not complete. That is why you should use this method to make sure the installer is usable for bootable media.
      Boot From USB
      Use f9, copy EFI folder to efi partition of your usb. after installation complete copy EFI to your ssd. Boot Entry Setup
      Reccomend using windows to find a tool to add a UEFI bios entry to boot EFI/Boot/bootx64 Credits
      @MaLd0n for DSDT Patches and support (HUGE SHOUTOUT) Original Kexts Authors Clover Headphones and Audio
      All audio from speakers should work perfectly along with Bluetooth and USB audio Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions.
      Donations
      Send me a coffee lefkotyler@gmail.com
      EFI Catalina.zip
       
      **for latest releases and faster replies please refer to GitHub https://github.com/tlefko/HP-ENVY-13-2020-Catalina
    • By geheim19
      I’m new here and hope a lot of answers to my questions to find.
       
×