Jump to content
ErmaC

Clover General discussion

19,684 posts in this topic

Recommended Posts

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$ 

Share this post


Link to post
Share on other sites
Advertisement

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 

Share this post


Link to post
Share on other sites

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 fabiosun

Share this post


Link to post
Share on other sites

 

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

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

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

  • Recently Browsing   1 member

  • Similar Content

    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×