Jump to content

Question about Clover

Bootloader Clover

  • Please log in to reply
3 replies to this topic

#1
Noodle07

Noodle07

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

Hi Forum,

 

Just switch to Clover recently, and really like it. Especially I can keep original OSX install untouched, and patch kexts dynamically.

 

But I have two questions about clover.

 

I'm running a pretty old PC. ASUS P5E-VM HDMI motherboard and QX9650 CPU, it has ALC883 audio chip and running latest Mavericks (10.9.4). And my questions are:

 

1. My CPU shows only two steps: x6 2.0G and x9 3.0G. Not sure if this CPU will only use this two steps or my configuration issue? I didn't change anything relate to CPU in config.plist yet.

2. ALC883 is pretty old audio chip, fortunately, I found a Mavericks AppleHDA.kext for it, and it works fine. However I read somewhere said I need to put this patched kext under /S/L/E, if I keep it in both /S/L/E and /EFI/CLOVER/kexts/10.9, I will get KP, so I just replace the one under /S/L/E with patched.

But this make me feel like I'm not really using Clover. So I searched again, and find ForceKextsToLoad. The document and example is not very clear. Is this option means: if I have two version (original and patched) AppleHDA.kext under /S/L/E and /EFI/CLOVER/kexts/10.9, I can force system use the one from /EFI/CLOVER/kexts/10.9 and keep /S/L/E untouched?

Also, example shows "\Extra\Extensions", but how about EFI partition? how to specify the kexts from EFI partition?

 

Thanks

 

Noodle



#2
Slice

Slice

    InsanelyMacaholic

  • Local Moderators
  • 2,973 posts
  • Gender:Male
  • Location:Moscow

For the question 1.

You seems may use all steps from 6 to 9. Just configure.

But the question that I can't still get any answer. "For a what?". If CPU working then high state (9), if idle then low state (6).

Do you want to work on lower state then highest?

Do you want to rest on higher state then minimum?

 

For question #2. I have ALC883 and it works fine with VoodooHDA+AppleHDADisabler.



#3
Noodle07

Noodle07

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

Thanks for you reply, Slice.

 

For question 1, I mean I'm not seeing steps between 2.0G to 3.0G, but only 2.0G and 3.0G. Maybe that's how QX9650 work? 

 

For question #2. I tried to completely remove AppleHDA.ext form /S/L/E, and keep patched AppleHDA in EFI partition, but it still not working. Had to put patch AppleHDA under /S/L/E.

It's ok to me. Just wondering if this is known issue?

 

Thanks

 

Noodle

 

For the question 1.

You seems may use all steps from 6 to 9. Just configure.

But the question that I can't still get any answer. "For a what?". If CPU working then high state (9), if idle then low state (6).

Do you want to work on lower state then highest?

Do you want to rest on higher state then minimum?

 

For question #2. I have ALC883 and it works fine with VoodooHDA+AppleHDADisabler.



#4
jamiethemorris

jamiethemorris

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 510 posts
  • Gender:Male
  • Location:San Rafael, CA

I think that might be just how it works, I have a Q6600 and it only does x6 and x9. However IIRC verdant said he gets more than 2 p-states on his. You may want to try at least enabling generate C states and Generate P states in the config.plist and see if that helps. If not, it may be possible to get it working by editing your SSDT, I never bothered with that because it's kind of tedious and I wasn't sure if it would even work on this CPU.

 

AppleHDA is typically not used in the EFI partition and I don't think it ever works due to dependencies. Also when you update I believe any kexts in s/l/e will override what's in the EFI partition. it is possible to patch AppleHDA on the fly with this method, but your codec is not supported so you would have to figure out how to apply that method to your codec. I couldn't tell you how to do that, perhaps toleda can. As Slice said, VoodooHDA + AppleHDADisabler works and doesn't break with every update, but in my experience audio quality can sometimes be glitchy depending on the codec.

 

ForceKextsToLoad is for when you have a kext that doesn't load by default on your computer, but you need it to load so that Clover can patch it and make it functional. I don't know if that would help or not. You could try using AppleHDADisabler to disable the stock AppleHDA and then ForceKextsToLoad for your patched one. I don't know how to load it from the EFI partition but you could load it from your user directory or something. However I would imagine AppleHDADisabler might override ForceKextsToLoad.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy