Jump to content
ErmaC

Clover General discussion

19,684 posts in this topic

Recommended Posts

6 hours ago, Sherlocks said:

thanks. i didn't notice it.

나의 SM-N960N 의 Tapatalk에서 보냄
 

 

Does Clover affect the processor type under the About This Mac? If it is, that's why all 9900K users seeing own processor type as an i7 then.

Share this post


Link to post
Share on other sites
Advertisement
 
Does Clover affect the processor type under the About This Mac? If it is, that's why all 9900K users seeing own processor type as an i7 then.
not at all. it'not affect the about this mac.
it is just record for check of smbios model

나의 SM-N960N 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
21 hours ago, Sherlocks said:

@Slice

long time no see.

can we consider smcverision 1/2/3? smcversion3 doesn't have REV/EPCI/RBR. 

FakeSMC force inject REV value right? can we just control datahub part to not relate FakeSMC rev?

Hi,

May be you are right but older computers need REV. Can you propose a way to distinct when used or not?

I just can propose that injecting redundant value does not influence at all.

 

Share this post


Link to post
Share on other sites
1 hour ago, Slice said:

Hi,

May be you are right but older computers need REV. Can you propose a way to distinct when used or not?

I just can propose that injecting redundant value does not influence at all.

 

 

here is smc version 3

 

no key list 
MacBookPro15,1 : REV rBR EPCI
MacBookPro15,2 : REV rBR EPCI
MacBookAir8,1  : REV rBR EPCI
Macmini8,1     : REV rBR EPCI
iMacPro1,1     : REV rBR EPCI

2 hours ago, telepati said:

 

Does Clover affect the processor type under the About This Mac? If it is, that's why all 9900K users seeing own processor type as an i7 then.

 

try this cputype "0x1009"

Share this post


Link to post
Share on other sites
1 hour ago, telepati said:

 

Thank you. But correct value is 0x1005. This is from real iMac 19,1.

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

Share this post


Link to post
Share on other sites
52 minutes ago, Matgen84 said:

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

 

Since it's an i7, I'm guessing (and this is just me guessing, based on what I read online so far): 0x0705 (?)

 

Also, I think maybe iMac19,2 might be closer...? The iMac19,2 seems to be an i7 8700k. iMac19,1 seems to be an i9. So..since this is an i7, I'm guessing iMac19,2 might be closer.

 

However, Clover is already pretty good at getting the correct value for your CPU, so you might not need to enter anything there. And it's only cosmetic anyway.

 

 

Share this post


Link to post
Share on other sites
2 hours ago, telepati said:

 

Thank you. But correct value is 0x1005. This is from real iMac 19,1.

I looked to dumps of real iMac19,1 and found cpu type = 0x0709

Share this post


Link to post
Share on other sites
Posted (edited)
5 hours ago, Slice said:

I looked to dumps of real iMac19,1 and found cpu type = 0x0709

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

ioreg.png.a84d620305fcc28cbd5f2d57bd6ca914.png

 

Credits; DexterOX

 

6 hours ago, Matgen84 said:

 

Hi

Where I can find cputype for core i7 9700k? What smbios is recommanded: Imac19,1! Thanks

 

I've to build a new hackintosh next week (Asus Prime z390-A, Core i7 9700K, MSI Radeon RX580)

4

 

I think i7 9700K will be recognized by automatically in 10.14.5.

Edited by telepati

Share this post


Link to post
Share on other sites
5 hours ago, telepati said:

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

 

 

Credits; DexterOX

 

 

I think i7 9700K will be recognized by automatically in 10.14.5.

We should tell about CPU not MacModel.

I saw iMac19,1 with i7-8700.

Share this post


Link to post
Share on other sites
6 hours ago, telepati said:

 

This also dumps from real iMac19,1. You probably know better than me :wink_anim:

 

ioreg.png.a84d620305fcc28cbd5f2d57bd6ca914.png

 

Credits; DexterOX

 

 

I think i7 9700K will be recognized by automatically in 10.14.5.

 

Thanks.

 

As @Slice, I saw Imac19,2 with i7-8700 in everyman.com site. But there is also IMac19,1 for i5-9600K. So what SMBIOS is good for i7-9700K in config.plist?

https://everymac.com/systems/apple/imac/specs/imac-core-i7-3.2-21-inch-aluminum-retina-4k-early-2019-specs.html

 

Everymac.com:

"The iMac "Core i9" 3.6 27-Inch Aluminum (Retina 5K, 2019/Coffee Lake) technically is a "configure-to-order" configuration of the iMac "Core i5" 3.1 27-Inch (5K, 2019) or iMac "Core i5" 3.7 27-Inch (5K, 2019)"

 

Share this post


Link to post
Share on other sites

I need to see DMI dumps from models with other CPU

iMac "Core i3" 3.6 21.5-Inch (4K, Early 2019) or iMac "Core i5" 3.0 21.5-Inch (4K, Early 2019), 

 

Share this post


Link to post
Share on other sites
On 4/23/2019 at 10:03 AM, Badruzeus said:

Well, I have few questions:

1. Why after writing boot1f32 my EFI partition (/dev/disk0s1) becomes "Unknown"..?

 

Screenshot 7.png

 

 

Which software is this?

Share this post


Link to post
Share on other sites
On 5/11/2019 at 7:45 AM, apianti said:

Siiiiiiiiiiiiiiiiiiiiiiiiiiiiigggggggggggggggggghhhhhhhhhhhhhhhh...................... You missed my point, it is not reading the EFI entries. It is reading the BCD from the registry, which was populated with firmware entries by bootmgfw.efi on boot. If I go into the registry and look at the BCD I have firmware entries there, yet none of them are displayed in bcdedit /enum all. Also as I said it can create one entry {bootmgr}, I'm pretty sure what you describe in the other topic is a bug (just like the enumeration one I am saying there is) not to mention that yes it includes the option data which can cause undefined behavior in whatever you created when launched... If it was able to create actual entries then you would be able to add an entry that is simply a firmware application, you cannot do this. The only way to edit EFI entries is to use the windows API. Windows applications and drivers can't even read or write nvram variables without a special certificate from microsoft (that you must request and provide reasons why you need to use nvram), and additionally being signed, having two special attributes, being run as an administrator or the system and that user has to have a special privilege. What you have described is actually an easy way for a rootkit to be installed, which completely defeats the purpose of all their restrictions on nvram access.

I use EasyBCD to edit/add/reorder Windows boot entries and EasyEFI to edit/add/reorder NVRAM boot entries. I try not to mess with the windows boot entry because either the firmware or Windows wants it to exist a certain way but I can change the order of the entries at least.

 

Share this post


Link to post
Share on other sites
22 hours ago, Funky frank said:

 

Which software is this?

That image is from DarwinDumper.

 

And to answer Badruzeus' question, DarwinDumper adds the name of the Loader to the dump by identifying known bytes in the MBR. If you see Unknown then that just simply means the code is not known by DarwinDumper rather than there being anything necessarily wrong with your MBR. 

 

DarwinDumper is old now and mostly out of date, better to see newer program's like headkaze's Hackintool and the Acidanthera repo for newer code for various tools

Share this post


Link to post
Share on other sites
Posted (edited)
11 minutes ago, blackosx said:

That image is from DarwinDumper.

 

Which is also your "baby". :)

 

Quote

DarwinDumper is old now and mostly out of date

 

It's also one of the best tools I've ever used. You should be proud of it. :) 

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)

smc v3.

i have to remove rev and commented rev key in datahub.

fakesmc write rev key and clover overwrite rev key from platformdata.

136462451_2019-05-319_55_09.png.71ee36629b5dac174afcfa522f501ecf.png

 

we need to think idea.. i think if we can control with non-touched fakesmc, will be better

Edited by Sherlocks

Share this post


Link to post
Share on other sites

REV key is model specific. As we can change model in Clover then Clover should set the key and override previous defined key.

Share this post


Link to post
Share on other sites
REV key is model specific. As we can change model in Clover then Clover should set the key and override previous defined key.

yes. can clover remove previous defined rev key if i use mbp15,1?

we just disable rev in datahub, still alive rev. because fakesmc write rev 1.33f?.

so we override disable key or remove 1.33f?

 

나의 SM-N960N 의 Tapatalk에서 보냄

 

 

 

Share this post


Link to post
Share on other sites

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?  

 

 

Share this post


Link to post
Share on other sites

Hi

 

I can't restart or shutdown on my new Hack (Asus Prime Z390-A, i7 9700K) with Clover r4937. Does anybody know why?

 

Sorry if this issue is Off-Topic

Share this post


Link to post
Share on other sites
17 hours ago, Sherlocks said:

yes. can clover remove previous defined rev key if i use mbp15,1?

we just disable rev in datahub, still alive rev. because fakesmc write rev 1.33f?.

so we override disable key or remove 1.33f?

 

나의 SM-N960N 의 Tapatalk에서 보냄

 

 

 

We should erase the key from FakeSMC. Let it be always from Clover present or not to be depend on Model.

 

14 hours ago, telepati said:

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?  

 

 

Looks like your ACPI has some difficulties for Clover. Provide, please, debug.log to see the moment of the stop.

 

11 minutes ago, Matgen84 said:

Hi

 

I can't restart or shutdown on my new Hack (Asus Prime Z390-A, i7 9700K) with Clover r4937. Does anybody know why?

 

Sorry if this issue is Off-Topic

It is surely on-topic.

There was several changes in Clover concerning CoffeeLake CPU. You should search what is the key.

First I will propose to set manually

CPU->Type = 0x0705

Share this post


Link to post
Share on other sites
Posted (edited)
14 hours ago, telepati said:

On clover boot screen I am pressing F4 and boot screen freezes. I can't make a boot, I must force reset from the case. I am using v4934. Does anybody know why this happening?

Running 4934 here. Aaand..no issues getting the ACPI tables on my side. So, as Slice mentioned, it's most likely something specific for your case. :)

 

Just wanted to share my own results, so you don't think it's a general issue with this version. Cause it doesn't look like it.

Edited by arsradu

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Slice said:

We should erase the key from FakeSMC. Let it be always from Clover present or not to be depend on Model.

 

Looks like your ACPI has some difficulties for Clover. Provide, please, debug.log to see the moment of the stop.

 

It is surely on-topic.

There was several changes in Clover concerning CoffeeLake CPU. You should search what is the key.

First I will propose to set manually

CPU->Type = 0x0705

 

Thanks @Slice

 

Where should I set CPU>Type in config.plist

 

PS: I remove kexts one by one, and now I can reboot or shutdown correctly. If issue remains again, I post debug.log

Edited by Matgen84

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   0 members

    No registered users viewing this page.

  • 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.
×