Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

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$

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

  • Like 1
el_charlie
el_charlie
Posted
Posted

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

 

Hello Slice,

 

I know that an HD3000 system is an old equipment, but that's the one I have. Do you have any insight on how to get rid of the graphics glitches?

 

I already have 8GB of RAM and don't know the DVMT size or how to increase it.

 

I was booting in legacy mode but I discovered I can do UEFI and now I'm using Aptio2Fix without a slide parameter. My calculated slide=39 doesn't work.

cecekpawon
cecekpawon
Posted
Posted

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)

 

I wondering how can you show boot.efi messages like that?

* it must be after entering OS entry, but you said before?

kgp
kgp
Posted
Posted

@fabiosun ,

 

CsmVideoDxe-64.efi seems apfs.efi related... 

 

If I don't use it I get these messages before entering the clover boot menu (see attachment).

 

 

Back to the topic... 

 

 

The remaining question is why my system is not recognised by the Appstore as iMac Pro and if this issue is Clover_v2.4k_r4369 related.. 

 

Update:

 

I wondering how can you show boot.efi messages like that?

* it must be after entering OS entry, but you said before?

 

Yes.... Same behaviour with my system disk if I omit CsmVideoDxe-64.efi (in fact I formerly also did not implement CsmVideoDxe-64.efi in the EFI-Folder of my MacOS USB Flash Drive Installer). 

 

With CsmVideoDxe-64.efi, also some messages appear before entering the clover boot menu.. but for a millisecond.. thus, I am not able to see or trace the content.. 

post-1362934-0-78869700-1515510375_thumb.png

  • Like 1
Guest
Guest
Posted
Posted (edited)

Many people stated this thing about output of apfs.efi

but using that driver is useful for display resolution and in some case it delay video output and people does not see apfs.efi lines

 

if you search in this forum you can find a simple patch from PMHeart and a more simple script from ErmaC to patch apfs.efi to disappear that log output.

 

            #81            

 

link verbose apfs boot added

@fabiosun ,

 

CsmVideoDxe-64.efi seems apfs.efi related... 

 

If I don't use it I get these messages before entering the clover boot menu (see attachment).

 

 

Back to the topic... 

 

 

The remaining question is why my system is not recognised by the Appstore as iMac Pro and if this issue is Clover_v2.4k_r4369 related.. 

 

Update:

 

 

Yes.... Same behaviour with my system disk if I omit CsmVideoDxe-64.efi (in fact I formerly also did not implement CsmVideoDxe-64.efi in the EFI-Folder of my MacOS USB Flash Drive Installer). 

 

With CsmVideoDxe-64.efi, also some messages appear before entering the clover boot menu.. but for a millisecond.. thus, I am not able to see or trace the content.. 

Edited by Guest
Slice
Slice
Posted
Posted

Hello Slice,

 

I know that an HD3000 system is an old equipment, but that's the one I have. Do you have any insight on how to get rid of the graphics glitches?

 

I already have 8GB of RAM and don't know the DVMT size or how to increase it.

 

I was booting in legacy mode but I discovered I can do UEFI and now I'm using Aptio2Fix without a slide parameter. My calculated slide=39 doesn't work.

Once upon a time I heard about slide=0 may help to artefact problem on Intel HD3000. I can't confirm or comment this because I have no such video.

My HD4000 depends on BIOS version (comp #2 in sig). Version A12 good while version A23 is full of artefacts. Did you checked different BIOSes?

  • Like 1
el_charlie
el_charlie
Posted
Posted

Once upon a time I heard about slide=0 may help to artefact problem on Intel HD3000. I can't confirm or comment this because I have no such video.

My HD4000 depends on BIOS version (comp #2 in sig). Version A12 good while version A23 is full of artefacts. Did you checked different BIOSes?

 

For that model, ASUS didn't release many BIOSes, the one I'm using is the latest and that's the one that boots Win8 and Win10.

 

In fact, on the download site there's no previous version. I'm even afraid to downgrade because I bricked the same laptop by flashing a bad BIOS. Had to replace the motherboard.

 

The slide=0 I think was a placebo. Currently, I can't boot with slide=0 on AptioFix2. With AptioFix1 slide=0 allows me to boot but the artifacts are there. They appear later when the computer has a more time on.

kgp
kgp
Posted
Posted

Many people stated this thing about output of apfs.efi

but using that driver is useful for display resolution and in some case it delay video output and people does not see apfs.efi lines

 

if you search in this forum you can find a simple patch from PMHeart and a more simple script from ErmaC to patch apfs.efi to disappear that log output.

 

            #81            

 

link verbose apfs boot added

 

perfect... apsf.efi issue resolved... thanks! 

 

BTW.. apparently I do not need the CsmVideoDxe-64.efi on my system.. also thanks for all related info

 

 

Now back to my original question:

 

Can it be that the incorrect recognition of my system in the Appstore can be due to the current Clover_v2.4k_r4369 iMacPro implementation?

 

The same question states for the apparent issue with the MacOS 10.13.2 (17C2120) USB Flash Drive Installer partition, which currently is not visible in the Clover Boot Menu. 

 

BTW.. the native NVRAM implementation also concludes that the MSR in the ASUS Prime X299 Deluxe v1014 BIOS is in fact unlocked? 

Guest
Guest
Posted
Posted

no. sorry not related to Nvram...

maybe you can check with pikeralpha tool to see but i think it is locked.

Maybe you can try with uefipatch

I see in the latest Patches.txt some lines related to skylake CPU

 

.....

 

 

 

BTW.. the native NVRAM implementation also concludes that the MSR in the ASUS Prime X299 Deluxe v1014 BIOS is in fact unlocked? 

kgp
kgp
Posted
Posted

no. sorry not related to Nvram...

maybe you can check with pikeralpha tool to see but i think it is locked.

Maybe you can try with uefipatch

I see in the latest Patches.txt some lines related to skylake CPU

 

I did previously check the MSR with AppleIntelInfo.kext (still using a  i7-7800X) and within earlier ASUS Prime X299 Deluxe BIOS versions the MSR was always locked.

 

Now with the i9-7980XE, my system immediately reboots on kextload of AppleIntelInfo.kext. The kext is not compatible with the latter CPU, see https://github.com/Piker-Alpha/AppleIntelInfo/issues/22.

 

The UEFI patch apparently works fine with the ASUS X299 Prime-A and ASUS X299 Strix BIOS, however with the ASUS Prime X299 Deluxe BIOS it fails apparently due to a different BIOS file system.. See https://github.com/LongSoft/UEFITool/issues/91.

Guest
Guest
Posted
Posted

offtopic

 

If you are sure uefipatch is working with ASUS X299 Prime-A

output message is the same also for your motherboard after patching..

Last login: Tue Jan  9 17:40:28 on console
fabios-Mac-Pro:~ fabio$ cd desktop
fabios-Mac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch PRIME-X299-A-ASUS-1004.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
Image patched
fabios-Mac-Pro:desktop fabio$ 

 

I did previously check the MSR with AppleIntelInfo.kext (still using a  i7-7800X) and within earlier ASUS Prime X299 Deluxe BIOS versions the MSR was always locked.

 

Now with the i9-7980XE, my system immediately reboots on kextload of AppleIntelInfo.kext. The kext is not compatible with the latter CPU, see https://github.com/Piker-Alpha/AppleIntelInfo/issues/22.

 

The UEFI patch apparently works fine with the ASUS X299 Prime-A and ASUS X299 Strix BIOS, however with the ASUS Prime X299 Deluxe BIOS it fails apparently due to a different BIOS file system.. See https://github.com/LongSoft/UEFITool/issues/91.

kgp
kgp
Posted
Posted

 

offtopic

 

If you are sure uefipatch is working with ASUS X299 Prime-A

output message is the same also for your motherboard after patching..

Last login: Tue Jan  9 17:40:28 on console
fabios-Mac-Pro:~ fabio$ cd desktop
fabios-Mac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch PRIME-X299-A-ASUS-1004.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
Image patched
fabios-Mac-Pro:desktop fabio$ 

 

Off topic request: can you please attach your patches.txt? I will give it a try... 

Sherlocks
Sherlocks
Posted
Posted

i tested my hp 4230s sandy laptop

now, i can use native NVRAM with OsxAptioFix2Drv.efi.

 

i always used slide=0 before. but if i use new OsxAptioFix2Drv.efi, i can't use slide=0. i have to remove slide=0 bootarg.

as result, only use OsxAptioFix2Drv.efi

 

thank you so much again.

 

EDIT1.

i will check Snow leopard booting.

  • Like 3
el_charlie
el_charlie
Posted
Posted

i tested my hp 4230s sandy laptop

now, i can use native NVRAM with OsxAptioFix2Drv.efi.

 

i always used slide=0 before. but if i use new OsxAptioFix2Drv.efi, i can't use slide=0. i have to remove slide=0 bootarg.

as result, only use OsxAptioFix2Drv.efi

 

thank you so much again.

I'm in the same boat. Using slide=0 gives me the prohibited sign. I even calculated my slide value (well, it was calculated for me by apianti) and I can't boot with that value either.

 

However, I did have native NVRAM without emuvariable.efi.

 

How are you doing with the graphical glitches of the HD3000? do you have any??

  • Like 1
apianti
apianti
Posted
Posted

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

 

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?

 

Yeah it should 100MHz, unless you overclocked the base clock.

 

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:

 

Yeah it uses either base64 or hexadecimal encoded data, it's not a string because it's meant to replace data not just strings.

 

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

 

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

 

Does no one read what I say? DO NOT USE AptioFix after r4369!!!!!!! Only AptioFix2. There is a bug that will allow the relocated kernel to overwrite the previously reserved runtime regions that were just protected from being moved into the kernel. Remove AptioFix and use AptioFix2.

 

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.

 

Can't anymore, AptioFix is more broken than AptioFix2. Unless you use an older version. You firmware has more reserved regions than I have ever seen before and only some are marked for runtime, it's hard to say if those other regions also need to be protected because they are indeed runtime or not but 

 

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

 

There is no such thing. Unless you mean disabling individual kext injection.

 

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

 

There should be no issues except with Z97 and X99 systems, the rest should be working with a few caveats.

 

 

it kinda seems that way....

  • Like 1
Guest
Guest
Posted
Posted

Hi apianti

if I don't remember bad you talk about to mod nvram section in x99 bios.

Can you point me in right direction if it is there some guide to execute this firmware patch?

 

I would like to ask also, in my condition I see many useful variable stored I think by clover and my system is fully working

For x99 users is there a really needs to have a working Nvram?

thank you

 

 

----

 

 

There should be no issues except with Z97 and X99 systems, the rest should be working with a few caveats.

 

 

it kinda seems that way....

apianti
apianti
Posted
Posted

 

Ambiguous output redirect

other weird behaviour... 

 

Even with 10.13.2 (17C2120) and SMBIOS iMacPro1,1, the Appstore does not recognise my system as iMac pro and just provides standard MacOS Installers instead of the iMac Pro specific ones. 

 

If I intent to download e.g. the 10.13.2 Full Package installer, I get the following error message (see attachment)

 

If I just update to 10.13.2 SA, again the standard installer is taken... 

 

I don't know if this issue is Clover_v2.4k_r4369 or build related.. I have a i9-7980XE which is not natively implemented yet by OSX (in contrary to the i9-7900X) and I use a Nvidia GPU instead of a Vega 64. 

 

Surprisingly, for user DSM2 with an ASUS Prime X299 Deluxe, a  i9-7900X  and 2x Vega 64 but Clover _v2.4k_4318, everything works as expected.. His system is fully recognised by the Appstore as iMacPro and he receives the correct iMac Pro specific macOS installer packages. 

 

 

You probably need to do some patching.

 

But if I remove EmuVariableUefi-64.efi, my SMBIOS iMacPro1,1 serial number, board serial number and UUID will not be correctly transmitted and I will face issues with iCloud, iMessage and Facetime, isn't it? 

 

No, those are from your configuration....

 

what about CsmVideoDxe-64.efi? Can I skip that too?

 

No, that is to allow full resolutions over the CSM module. You could possibly try disabling CSM, removing it, and then you may get full resolution with the UEFI drivers. You can no longer boot legacy though.... Don't see why you would need to though.

 

This is legacy Clover BDS menu timeout. I am not sure if it used anywhere.

 

That's why I chose that variable to test the writing. They have a whitelist in which only certain variables can be written, that is one. They can write to it, but not another test variable. So, they have working NVRAM just that the actual NVRAM modules have a bug that restricts what can be written at runtime.

 

Hello Slice,

 

I know that an HD3000 system is an old equipment, but that's the one I have. Do you have any insight on how to get rid of the graphics glitches?

 

I already have 8GB of RAM and don't know the DVMT size or how to increase it.

 

I was booting in legacy mode but I discovered I can do UEFI and now I'm using Aptio2Fix without a slide parameter. My calculated slide=39 doesn't work.

 

I also have an HD3000. I'm trying to figure it out.... 

 

Once upon a time I heard about slide=0 may help to artefact problem on Intel HD3000. I can't confirm or comment this because I have no such video.

My HD4000 depends on BIOS version (comp #2 in sig). Version A12 good while version A23 is full of artefacts. Did you checked different BIOSes?

 

I have heard this too and I don't think it's actually related to the solution. Because it does nothing for me. I think that the slide was just overwriting some region it needed and disabling KASLR didn't put the kernel overwriting these regions. The fact that two versions of the same firmware act differently tells me that most likely it has to do with a memory region that in windows and linux is ok but in macOS it determines the wrong mapping or no mapping for it.

  • Like 2
apianti
apianti
Posted
Posted

For that model, ASUS didn't release many BIOSes, the one I'm using is the latest and that's the one that boots Win8 and Win10.

 

In fact, on the download site there's no previous version. I'm even afraid to downgrade because I bricked the same laptop by flashing a bad BIOS. Had to replace the motherboard.

 

The slide=0 I think was a placebo. Currently, I can't boot with slide=0 on AptioFix2. With AptioFix1 slide=0 allows me to boot but the artifacts are there. They appear later when the computer has a more time on.

 

It most certainly is, I think it was just a matter of luck, as sleep/hibernation seemed to be.

 

i tested my hp 4230s sandy laptop

now, i can use native NVRAM with OsxAptioFix2Drv.efi.

 

i always used slide=0 before. but if i use new OsxAptioFix2Drv.efi, i can't use slide=0. i have to remove slide=0 bootarg.

as result, only use OsxAptioFix2Drv.efi

 

thank you so much again.

 

EDIT1.

i will check Snow leopard booting.

 

slide=0 just disables KASLR.

 

I'm in the same boat. Using slide=0 gives me the prohibited sign. I even calculated my slide value (well, it was calculated for me by apianti) and I can't boot with that value either.

 

However, I did have native NVRAM without emuvariable.efi.

 

How are you doing with the graphical glitches of the HD3000? do you have any??

 

I don't get why it's failing when you set the slide, there must be some other side effect, but your firmware is nuts with the allocations. Jeez.

 

Hi apianti

if I don't remember bad you talk about to mod nvram section in x99 bios.

Can you point me in right direction if it is there some guide to execute this firmware patch?

 

I would like to ask also, in my condition I see many useful variable stored I think by clover and my system is fully working

For x99 users is there a really needs to have a working Nvram?

thank you

 

fabio, don't you have working NVRAM? It is just whitelisted. And yes you probably want fully functioning NVRAM to actually be able to write stuff, like when you use an upgrade or an installer or want to set startup disk, or any number of things stored in NVRAM. sleep/hibernation....

 

can someone help me calculate the slide value needed. ive attached my memmap.

 

 

Thanks in advanced!

 

Use any slide you want.

Available  0000000000100000-00000000312F9FFF 00000000000311FA 000000000000000F

Is clover ready for 17C205 security update?

 

No idea. Yes?

  • Like 1
el_charlie
el_charlie
Posted
Posted

Is clover ready for 17C205 security update?

 

If it wasn't, I wouldn't be writing this on my hack... ;)

 

I have updated my both hacks and no problems, just testing the correct slide value to see if it minimizes the glitches on my HD3000.

 

Cheers!

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...