Jump to content
216 posts in this topic

Recommended Posts

Hi all,

 

After realizing that Clover doesn't work on AMD Ryzen systems and the only solution is to use a closed-source fork, I set out to implement Ryzen support in Clover myself and share the results.

The source can be found at https://github.com/shawnanastasio/Clover-Ryzen and I've attached a build to this post.

 

I have confirmed that it boots on my Ryzen 7 1800X system, but I have not tried booting macOS yet. If anybody has a Ryzen hackintosh set up, I'd love to hear if it works for you. To try it out, just replace your current BOOT/BOOTX64.efi and CLOVER/CLOVERX64.efi with the attached build.

 

Feedback is welcome!

 

============

Update 7/1/17: Add support for fractional multipliers (like 39.5). Link to download.

============

 

Old Downloads:

Update 6/30/17: Fix max/min ratio detection as well as FSB detection. Link to download.

Update 6/29/17: Add automatic CPU max/min ratio detection. Should resolve clock speed issues. Link to download.

CLOVERX64.efi

  • Like 8

I can confirm this works, however i do get a lot of [MSR-64] unknown location 0x00000000c0010071 when booting.

 

Took 2 attempts to boot, but the 2nd went fine.

 

Just tested Cinebench opengl with this clover, 26fps... Ugh

did you try your nvidia card yet? any performance boost?

what card you using?

I got 26fps in Cinebench, this makes me believe it is something to do with clover and not the kernel. It seems the nvidia drivers are not being injected properly at boot.

I did notice this error when i was booting up though: 

 

GeForceSensors: GeforceSensors by kozlek © 2012

GeForceSensors: found 1b81 Nvidia chip

 

GeForceSensors (0): [Error] unknown chipset, 0x134000a1

 

Edit: I removed the Geforce Sensor kext.

 

But it is very interesting why this clover variant is providing far less performance 

I did notice this error when i was booting up though:

 

GeForceSensors: GeforceSensors by kozlek © 2012

GeForceSensors: found 1b81 Nvidia chip

 

GeForceSensors (0): [Error] unknown chipset, 0x134000a1

 

Edit: I removed the Geforce Sensor kext.

 

But it is very interesting why this clover variant is providing far less performance

that is maybe this is why our cards are having bad performance

Hi all,

 

After realizing that Clover doesn't work on AMD Ryzen systems and the only solution is to use a closed-source fork, I set out to implement Ryzen support in Clover myself and share the results.

The source can be found at https://github.com/shawnanastasio/Clover-Ryzen and I've attached a build to this post.

 

I have confirmed that it boots on my Ryzen 7 1800X system, but I have not tried booting macOS yet. If anybody has a Ryzen hackintosh set up, I'd love to hear if it works for you. To try it out, just replace your current BOOT/BOOTX64.efi and CLOVER/CLOVERX64.efi with the attached build.

 

Feedback is welcome!

 

Could you please attach the BOOTX64.efi as well? Thanks

Come on be nice there is no need to keep everything cealed, you did a good work, so share it as easily as possible or do you need a crown?

Sharing is caring!

Come on be nice there is no need to keep everything cealed, you did a good work, so share it as easily as possible or do you need a crown?

Sharing is caring!

Just create a copy of BOOTX64.efi and rename it to CLOVERX64.efi, they're the same file with a different name. It's always the case.

 

:)

  • Like 1

Glad to hear it is working!

 

As for the CPU clock issues, I'll be sure to take a look at that. For those of you who are having CPU clock issues, could you please post the clockspeed that you're getting in macOS and a copy of your clover debug.log?

To enable debug.log, find the `Debug` section in your clover.plist under `Boot` and set it to true. The next time you boot, clover will produce a debug log in EFI/CLOVER/misc/debug.log.

 

Have you shared this with Slice to have it added to the official source?

I'm not sure it's at a stage where its ready to be upstreamed but once it is ill definitely contact the clover guys.

 

Sent from my Nexus 5X using Tapatalk

  • Like 3

Is it possible for the original Clover project to implement ryzen and have duality with Intel? I'm not technically saavy to this deep level therefore the question. I just though that it will get much more support that way.

 Absolutely - my fork should work just fine on Intel. I was careful not to break anything relating to Intel CPU support.

  • Like 1
Hi ! 
Try this boot for Clover ! 
Fixed for all Cpu's ! 

 

But i need know that how shows Multiplier in Ryzen in menu Clover  !  Because i added Min and Max Ratio from manuals fam_17h ! And i added Cores / 2 !
For source , need wait ... 
 
  • Like 2

 

Hi ! 
Try this boot for Clover ! 
Fixed for all Cpu's ! 

 

But i need know that how shows Multiplier in Ryzen in menu Clover  !  Because i added Min and Max Ratio from manuals fam_17h ! And i added Cores / 2 !
For source , need wait ... 
 

 

 

wooh !!

 

8/16 !! :thumbsup_anim:

 

0:100  0:000  Running on: 'System Product Name' with board 'PRIME B350M-A'

0:100  0:000  === [ GetCPUProperties ] ==================================

0:100  0:000  CPU Vendor = 68747541 Model=800F11

0:100  0:000   The CPU supported SSE4.1

0:100  0:000      Looking to disable C1E if is already enabled by the BIOS:

0:100  0:000  BrandString = AMD Ryzen 7 1700 Eight-Core Processor          

0:100  0:000  CurrentSpeed: 3650

0:100  0:000  FSBFrequency = 25 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz

0:100  0:000  MaxDiv/MinDiv: 0.5/34

0:100  0:000  Turbo: 0/0/0/0

0:100  0:000  Features: 0x178BFBFF

0:100  0:000  Threads: 16

0:100  0:000  Cores: 8

0:100  0:000  FSB: 25 MHz

0:100  0:000  CPU: 0 MHz

0:100  0:000  TSC: 3650 MHz

0:100  0:000  PIS: 100 MHz

 

but problem speed kernel cinebench 15 1650 => 1403  (1647 Win10)

post-2087795-0-22578900-1498769870_thumb.png

  • Like 1
×
×
  • Create New...