Jump to content

Clover issue with r2758 and onwards


smolderas
 Share

5 posts in this topic

Recommended Posts

Dear Clover developers and community,

 

first of all please let me thank you for that huge project and the maintenance you guys are providing for the community.
I’m a long time lurker and wanted to report an issue with my system. I didn’t first want to open a ticket on sourceforge.net, because I wanted to be sure, that my issue is actually a bug and not a configuration error on my side, but since I'm 99% sure, that it has to do with some changes in the source code between releases r2721 and r2758.

 

(please skip to my issue)

I have my hackintosh running now from the version 10.7 up until 10.9.4 with the “legacy” bootloader chameleon (actually I have some modification for my own on the source code (like CPU speed detection etc…), which is not a branch on the svn). I wanted to “upgrade” my bootloader to a more vanilla experience and gave a shot to Clover. First of all, it is amazing. I want to participate to it in some manners (like (re-)organize the source code, or even write a tutorial or translate it to my native language (tr or de)).

 

Now to my issue:

 

My system is:
- ga-z68x-ud5-b3 (F10) BIOS (not UEFI)
- i7-2600k
- 2*gtx 570
- patched DSDT.aml and SSDT.aml
- HFSPlus.efi instead of VBoxHfs-64.efi in drivers64UEFI
- in the kexts/10.10 I have:
. GenericUSBXHCI.kext
. FakeSMC.kext (most updated) with plug-ins
. realtekALC.kext
. RealtekRTL81xx.kext

 

I have a fully functioning Yosemite public beta 1 installation (and 10.9.4) with the clover revision 2721 (see boot.log in the attachment), with the following config.plist (see attachment).

 

After I’ve updated to a newer version (r2795) I couldn’t boot up the system. While booting I get a somekind of restriction symbol instead of apple symbol and the system won’t continue to boot (see pictures in the attachment). I get the same restriction symbol in the verbose mode too.
Since the system won’t boot, I don’t have the boot.log of the failing boot up. I have the same error after creating a new OS X installation USB and booting from it.
I could narrow it down to the revision r2758, so the problem exists with the versions:
- r2758
- r2774
- r2795

 

I can’t compile from the source, because of my Xcode version, so I can’t /couldn’t test the newer versions. I’m happy to test, if you provide me the files though.

Since the Clover project is evolving and getting more perfect, I don’t want to use an old revision and would like to use newest revisions with newer features or fixes.

I would be glad, if you could help me out.

 

Thanks in advance.

 

Attachments are in the Clover.zip, and are separately here as well:
boot.log - https://db.tt/D1l6IT7E
config.plist - https://db.tt/TzgLlUJ3
Clover installer setup - https://db.tt/H9ihbbw9
failed boot up foto0 - https://db.tt/X4DHpzvC
failed boot up foto1 - https://db.tt/7mW0jZmg
failed boot up foto2 - https://db.tt/yaHFGR9o

See ticket #67:  https://sourceforge.net/p/cloverefiboot/tickets/67/

Clover.zip

Link to comment
Share on other sites

your system and configs seem correctly configured, I found that after the aforementioned revision if the fakeSMC.kext was not in /S/L/E I got the same lock/Crash you are experiencing. I ditched the chameleon a long time around r800 days of clover and haven't looked back. for the most part, I try to keep my system as close to vanilla as possible incase I have to swap the drive with my real mac for something, but the one Kext that seems to have to be in /S/L/E without fail is fakeSMC...

 

 

HBP

  • Like 1
Link to comment
Share on other sites

Remover GforceSenrors kext.

How to delete kexts for enable video.

Sorry, but there isn't any issue with that extension...

 

your system and configs seem correctly configured, I found that after the aforementioned revision if the fakeSMC.kext was not in /S/L/E I got the same lock/Crash you are experiencing. I ditched the chameleon a long time around r800 days of clover and haven't looked back. for the most part, I try to keep my system as close to vanilla as possible incase I have to swap the drive with my real mac for something, but the one Kext that seems to have to be in /S/L/E without fail is fakeSMC...

 

 

HBP

That was it. Thank you very much. I did put a copy of the FakeSMC.kext in the /S/L/E and the system booted up with the newest revision R2795.

Clearly it is a bug and I will update the ticket 67# accordingly. Thank you very much.

  • Like 1
Link to comment
Share on other sites

your welcome, I almost reformatted and reinstalled my 10.10 system after that bug hit until I began looking back at what the differences were... dropped the kext in and saved myself a load of time ;)

 

HBP

Link to comment
Share on other sites

 Share

×
×
  • Create New...