Jump to content
ErmaC

Clover General discussion

18,084 posts in this topic

Recommended Posts

@backosx

 

Sry i was playing arround with config.plist and set to test Fast - false. 

When i use CLOVERX64.efi from Clover_v2_r1995.pkg its works great but it can't Inject wlancard to Airport :(

 

 

Edit://

 

I was found something between boot.log from Clover_v2k_r2211 and boot.log Clover_v2k_r1995

 

 

boot.log Clover_v2k_r1995

0:100  0:000  Clover revision: 1995  running on To be filled by O.E.M.
0:100  0:000  ... with board Z68X-UD3H-B3
0:104  0:003  Found theme BOOTCAMP
0:108  0:004  Found theme MRENGLES
0:111  0:002  ConfigPlistPath: EFI\CLOVER\config.plist
0:112  0:001  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:112  0:000  Loading early settings
0:112  0:000  timeout set to 0
0:112  0:000  Default theme: bootcamp

boot.log from Clover_v2k_r2211

0:100  0:000  Clover revision: 2211  running on To be filled by O.E.M.
0:100  0:000  ... with board Z68X-UD3H-B3
0:100  0:000  Clover load options size = 0 bytes
0:103  0:002  ConfigPlistPath: EFI\CLOVER\config.plist
0:104  0:001  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:105  0:000  EFI\CLOVER\config.plist loaded: Success
0:106  0:001  Found theme BOOTCAMP
0:110  0:004  Found theme MRENGLES
0:113  0:002  Loading early settings
0:113  0:000  Default theme: bootcamp

I think thats the problem but i don't know how to fix :(

In newer versions many things have changed and one of thes is your problem so you must change your config to this

<dict>

    <key>Boot</key>

    <dict>

        <key>Timeout</key>

        <integer>5</integer>

        <key>Arguments</key>

        <string>-v arch=i386 slide=0</string>

        <key>DefaultVolume</key>

        <string>MacHDD</string>

        <key>Log</key>

        <false/>

        <key>Fast</key>

        <true/>

    </dict>

but the best thing is to read the wiki

 

http://clover-wiki.zetam.org/Home

Share this post


Link to post
Share on other sites
Advertisement

Yep, same here, rev 2216

2:104  0:000    Volume 'Recovery HD', OS '', Icon(s) '<null string>', GUID = 6ADC85EA-3817-47B7-86DA-4C762262A7EB

Share this post


Link to post
Share on other sites

@devs

What is the latest news in using Mavericks GM with CloverGrowerPro.

 

Are there any known fixes available?

No fix is needed, as CGP was already updated to support 10.9.

 

If it doesn't work for you on Mav GM, then you are probably using the wrong Xcode...

Mav GM needs Xcode 5.0.1 GM (!) - even Xcode 5.0 does not have the 10.9 SDK.

 

After installing Xcode 5.0.1, rebuild the toolchain (erase toolchain directory from CGP, it will result in rebuilding it).

Then it should work.

Share this post


Link to post
Share on other sites

Is this specific for me? Under r2218, I lost recovery icon at GUI. Should I add something in config?

 

r2184

1:115  0:000    Volume 'Recovery HD', OS 'ML', Icon(s) 'cougar,mac', GUID = B1CB8FFD-A38C-49ED-A6C6-B1696A2310EA

 

r2218

0:954  0:000    Volume 'Recovery HD', OS '', Icon(s) '<null string>', GUID = B1CB8FFD-A38C-49ED-A6C6-B1696A2310EA

 

Thanks,

 

Yep, same here, rev 2216

2:104  0:000    Volume 'Recovery HD', OS '', Icon(s) '<null string>', GUID = 6ADC85EA-3817-47B7-86DA-4C762262A7EB

 

Seems to me like this is not because of change in Clover, but because 10.9 recovery partition has a different layout. You guys probably installed 10.9, and your Recovery partition got updated. Didn't you?

 

Anyway, I added icon support for 10.9 recovery with r2220, so please check if it solves it for you.

 

And on a different note, the log lines you posted show in recent revisions icons only for Legacy. So I renamed now the debug at that place to LegacyIcon(s) to be clearer that nothing should appear there anymore for OSX.

The relevant debug to post if it doesn't work (as of r2220) would be the one looking like this:

4:461  0:001  20: 'Recovery HD'
4:462  0:000      Added 'Boot Recovery from Recovery HD': OSType='10', OSVersion='10.9'

Edit: Please check later revisions, as it includes further icon fixed.

Share this post


Link to post
Share on other sites

@Pene 

 

Your attached Cloverx64.efi doesn't fix the lost Recovery partition in the GUI, but thanks for the effort.

 

Additionally I can now build in 10.9 with CloverGrowerPro but installation still fails...  Any thoughts, install log below.

 

Thanks

Oct  8 23:33:45 Hack.local installd[386]: PackageKit: ----- Begin install -----
Oct  8 23:33:47 Hack.local installd[386]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Clover_v2k_r2220.pkg”." UserInfo=0x7ffde8025070 {NSFilePath=./preinstall, NSURL=file://localhost/Users/ken/CloverGrowerPro/builtPKG/Clover_v2k_r2220.pkg#EFIFolder.pkg, PKInstallPackageIdentifier=org.clover.efifolder, NSLocalizedDescription=An error occurred while running scripts from the package “Clover_v2k_r2220.pkg”.} {
	    NSFilePath = "./preinstall";
	    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cClover_v2k_r2220.pkg\U201d.";
	    NSURL = "file://localhost/Users/ken/CloverGrowerPro/builtPKG/Clover_v2k_r2220.pkg#EFIFolder.pkg";
	    PKInstallPackageIdentifier = "org.clover.efifolder";
	}
Oct  8 23:33:47 Hack.local Installer[423]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Oct  8 23:33:47 Hack.local Installer[423]: Displaying 'Install Failed' UI.
Oct  8 23:33:47 Hack.local Installer[423]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.

Share this post


Link to post
Share on other sites

 

@Pene

 

Your attached Cloverx64.efi doesn't fix the lost Recovery partition in the GUI, but thanks for the effort.

 

Additionally I can now build in 10.9 with CloverGrowerPro but installation still fails... Any thoughts, install log below.

 

Thanks

Oct  8 23:33:45 Hack.local installd[386]: PackageKit: ----- Begin install -----
Oct  8 23:33:47 Hack.local installd[386]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Clover_v2k_r2220.pkg”." UserInfo=0x7ffde8025070 {NSFilePath=./preinstall, NSURL=file://localhost/Users/ken/CloverGrowerPro/builtPKG/Clover_v2k_r2220.pkg#EFIFolder.pkg, PKInstallPackageIdentifier=org.clover.efifolder, NSLocalizedDescription=An error occurred while running scripts from the package “Clover_v2k_r2220.pkg”.} {
	    NSFilePath = "./preinstall";
	    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cClover_v2k_r2220.pkg\U201d.";
	    NSURL = "file://localhost/Users/ken/CloverGrowerPro/builtPKG/Clover_v2k_r2220.pkg#EFIFolder.pkg";
	    PKInstallPackageIdentifier = "org.clover.efifolder";
	}
Oct  8 23:33:47 Hack.local Installer[423]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
Oct  8 23:33:47 Hack.local Installer[423]: Displaying 'Install Failed' UI.
Oct  8 23:33:47 Hack.local Installer[423]: 'Install Failed' UI displayed message:'The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.'.

I have no idea about the installer, I don't use it, so perhaps someone else will help.

 

But I will appreciate if you attach your boot.log with r2220 where recovery icon does't show

Share this post


Link to post
Share on other sites

No fix is needed, as CGP was already updated to support 10.9.

 

If it doesn't work for you on Mav GM, then you are probably using the wrong Xcode...

Mav GM needs Xcode 5.0.1 GM (!) - even Xcode 5.0 does not have the 10.9 SDK.

 

After installing Xcode 5.0.1, rebuild the toolchain (erase toolchain directory from CGP, it will result in rebuilding it).

Then it should work.

Thanks Pene - much appreciated thank you, r2220 compiled fine and installed fine.

 

10.9 Gm is a great improvement, managed to fix the long standing iTunes errors in diskutilities by removing 8400 ACL files, plus "PowerNap" also works well here. Impressed!

Share this post


Link to post
Share on other sites

I'm having trouble getting custom entries to show up at all on r2217 (or any revision for that matter). I followed the wiki. Here's that part of my config.plist. (Ignore the empty volume UUID)

 

DMaCpyJ.png

Share this post


Link to post
Share on other sites

Type detection is horribly broken as of 2220.. the last revision I had compiled was 2194 and all of the type detection worked flawlessly.

Here's an image with 2194:

4Ls8U.png

Left to right: Recovery HD 10.9, Windows 7 Professional bootmgfw.efi, Macintosh HD 10.8.5, Recovery HD 10.8.5, Macintosh SSD 10.9

 

Now, with 2219 and 2220:

4Lscy.png

Recovery HD from 10.9 seems to be the only partition that has it's type detected properly because it has custom entry defined for it. The other ones are just generic. 

 

UPD:

Fixed as of r2222!

Share this post


Link to post
Share on other sites

Type detection is horribly broken as of 2220.. the last revision I had compiled was 2194 and all of the type detection worked flawlessly.

Here's an image with 2194:

4Ls8U.png

Left to right: Recovery HD 10.9, Windows 7 Professional bootmgfw.efi, Macintosh HD 10.8.5, Recovery HD 10.8.5, Macintosh SSD 10.9

 

Now, with 2219 and 2220:

4Lscy.png

Recovery HD from 10.9 seems to be the only partition that has it's type detected properly because it has custom entry defined for it. The other ones are just generic. 

 

r2220






0:491  0:000  found 9 volumes with blockIO
0:491  0:000   0. Volume:
0:491  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0)
0:491  0:000    Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid>
0:491  0:000   1. Volume:
0:491  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0x0)
0:491  0:000    found optical drive
0:491  0:000    Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid>
0:491  0:000   2. Volume:
0:491  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0)
0:492  0:000    Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid>
0:492  0:000   3. Volume:
0:492  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0)/HD(1,GPT,14BA7FEC-3957-410C-A6F4-5BB115712747,0x22,0x64000)
0:493  0:000    Result of bootcode detection: bootable Legacy (legacy)
0:539  0:046    Volume 'EFI', LegacyOS 'Legacy', LegacyIcon(s) 'legacy', GUID = 14BA7FEC-3957-410C-A6F4-5BB115712747
0:539  0:000    This is SelfVolume !!
0:539  0:000   4. Volume:
0:539  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0)/HD(2,GPT,F1E83FCF-0B7B-41F5-BB83-27F659A16540,0x64028,0x3A1EC0C0)
0:539  0:000    Volume 'Macintosh HD', LegacyOS '', LegacyIcon(s) '<null string>', GUID = F1E83FCF-0B7B-41F5-BB83-27F659A16540
0:539  0:000   5. Volume:
0:539  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0)/HD(3,GPT,4D4AC37C-5E28-48D5-BEC3-F215CBA5176F,0x3A2500E8,0x135F20)
0:540  0:000    Volume 'Recovery HD', LegacyOS '', LegacyIcon(s) '<null string>', GUID = 4D4AC37C-5E28-48D5-BEC3-F215CBA5176F
0:540  0:000   6. Volume:
0:540  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0)/HD(1,GPT,5CF68E22-ADD1-46EF-93E8-2A05DC8587BF,0x28,0x64000)
0:541  0:000    Result of bootcode detection: bootable Legacy (legacy)
0:545  0:004    Volume 'EFI', LegacyOS 'Legacy', LegacyIcon(s) 'legacy', GUID = 5CF68E22-ADD1-46EF-93E8-2A05DC8587BF
0:545  0:000   7. Volume:
0:545  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0)/HD(2,GPT,56A99F34-37A2-4C19-A96B-FFF5EB7EF595,0x64028,0xECE2340)
0:546  0:000    Volume 'Macintosh SSD', LegacyOS '', LegacyIcon(s) '<null string>', GUID = 56A99F34-37A2-4C19-A96B-FFF5EB7EF595
0:546  0:000   8. Volume:
0:546  0:000    PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0)/HD(3,GPT,DFFF3AAF-F9E6-4452-ACEB-B2D72856EBFD,0xED46368,0x135F20)
0:547  0:000    Volume 'Recovery HD', LegacyOS '', LegacyIcon(s) '<null string>', GUID = DFFF3AAF-F9E6-4452-ACEB-B2D72856EBFD
0:547  0:000  Invalidating BuiltinIcons...
0:548  0:001  Using theme 'mlcamp' (EFI\CLOVER\themes\mlcamp)
0:558  0:010  font mpr.png loaded from themedir
0:558  0:000  Font loaded: ImageWidth=176 ImageHeight=288 Ptr=B6F17018
0:558  0:000  Font 2 prepared WxH=11x18 CharWidth=10
0:558  0:000  Custom entries start
0:558  0:000  Custom entry 0 "Recovery" "\com.apple.recovery.boot\boot.efi" "" (10) 0x2 matching "Recovery HD" ...
0:558  0:000     Checking volume "EFI" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0)\HD(1,GPT,14BA7FEC-3957-410C-A6F4-5BB115712747,0x22,0x64000)) ... skipped
0:558  0:000     Checking volume "Macintosh HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0)\HD(2,GPT,F1E83FCF-0B7B-41F5-BB83-27F659A16540,0x64028,0x3A1EC0C0)) ... skipped
0:558  0:000     Checking volume "Recovery HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0)\HD(3,GPT,4D4AC37C-5E28-48D5-BEC3-F215CBA5176F,0x3A2500E8,0x135F20)) ... match!
0:628  0:070      Added 'Boot Recovery from Recovery HD': OSType='10', OSVersion='10.8'
0:628  0:000     Checking volume "EFI" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0)\HD(1,GPT,5CF68E22-ADD1-46EF-93E8-2A05DC8587BF,0x28,0x64000)) ... skipped
0:628  0:000     Checking volume "Macintosh SSD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0)\HD(2,GPT,56A99F34-37A2-4C19-A96B-FFF5EB7EF595,0x64028,0xECE2340)) ... skipped
0:628  0:000     Checking volume "Recovery HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0)\HD(3,GPT,DFFF3AAF-F9E6-4452-ACEB-B2D72856EBFD,0xED46368,0x135F20)) ... match!
0:631  0:002      Added 'Boot Recovery from Recovery HD': OSType='10', OSVersion='10.9'
0:631  0:000  Custom entries finish
0:631  0:000  Scanning loaders...
0:631  0:000   0: 'Whole Disc Boot' no file system
0:631  0:000   1: 'Whole Disc Boot' no file system
0:631  0:000   2: 'Whole Disc Boot' no file system
0:631  0:000   3: 'EFI'
0:693  0:061      Added 'Boot Microsoft EFI boot menu from EFI': OSType='6', OSVersion='<null string>'
0:693  0:000   4: 'Macintosh HD'
0:824  0:131      Added 'Boot Mac OS X from Macintosh HD': OSType='1', OSVersion='10.8.5'
0:826  0:002   5: 'Recovery HD'
0:827  0:001      Added 'Boot Recovery from Recovery HD': OSType='10', OSVersion='10.8'
0:827  0:000   6: 'EFI'
0:827  0:000   7: 'Macintosh SSD'
0:843  0:015      Added 'Boot Mac OS X from Macintosh SSD': OSType='1', OSVersion='10.9'
0:845  0:001   8: 'Recovery HD'
0:845  0:000  skipped because path `PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0)\HD(3,GPT,DFFF3AAF-F9E6-4452-ACEB-B2D72856EBFD,0xED46368,0x135F20)\\com.apple.recovery.boot\boot.efi` already exists for another entry!
0:845  0:000  Custom legacy start
0:845  0:000  Custom legacy end
0:845  0:000  Custom tool start
0:845  0:000  Custom tool end

Yes this was due to me separating legacy and uefi loader types. Should be fixed in r2222. 

 

@Pene I'm not sure I like r2220. It assumes too much about the case where SystemVersion.plist is not found and com.apple.recovery.boot\boot.efi is found. It might have been the issue I just fixed(r2222) that was the problem?

Maybe if we can't find the the SystemVersion.plist we should use the detection code from main.c:StartLoader(...)?(which you wrote right?) I think we would need to pass LOADER_ENTRY instead of REFIT_VOLUME though. That way we don't have to check all the different paths we can just use Entry->LoaderPath as the boot file to scan for version.

It would also reduce the number of places we look for OSversion :)

Share this post


Link to post
Share on other sites

Type detection is horribly broken as of 2220.. the last revision I had compiled was 2194 and all of the type detection worked flawlessly.

Here's an image with 2194:

4Ls8U.png

Left to right: Recovery HD 10.9, Windows 7 Professional bootmgfw.efi, Macintosh HD 10.8.5, Recovery HD 10.8.5, Macintosh SSD 10.9

 

Now, with 2219 and 2220:

4Lscy.png

Recovery HD from 10.9 seems to be the only partition that has it's type detected properly because it has custom entry defined for it. The other ones are just generic. 

 

UPD:

Fixed as of r2222!

What theme are you using?

 

 

Tonight I'll reinstall my rig. Currently it's using Ozmosis as a bootloader, but I like Clover better. First it looks sleeker, has more options to configure and can be finetuned.

For one, I like the option to graphically switch OS'es. One thing I didn't manage to get working in Clover is the StartupDiskPreferencePane. I would like to be able to go into the settings, choose my desired startup volume (for example, I'm in OS X and I want to switch to Windows) and reboot into this. Why? I'm very mobile oriented and therefore I want to have full control over my PC at any distance. So with the PrefPane it would actually be possible to reboot into a different OS remotely. In the first post this is also stated as a feature.

Share this post


Link to post
Share on other sites

Yes this was due to me separating legacy and uefi loader types. Should be fixed in r2222. 

 

@Pene I'm not sure I like r2220. It assumes too much about the case where SystemVersion.plist is not found and com.apple.recovery.boot\boot.efi is found. It might have been the issue I just fixed(r2222) that was the problem?

Maybe if we can't find the the SystemVersion.plist we should use the detection code from main.c:StartLoader(...)?(which you wrote right?) I think we would need to pass LOADER_ENTRY instead of REFIT_VOLUME though. That way we don't have to check all the different paths we can just use Entry->LoaderPath as the boot file to scan for version.

It would also reduce the number of places we look for OSversion :)

Hi SoThor!

 

What you just fixed and this are actually two different issues...

 

Yes, I wrote the boot.efi version reading. But he reason I don't do it for all cases is because I prefer to avoid reading larger files (boot.efi is about 0.5 meg) during scan.

We could do all the OS X detection using boot.efi, as it's the most reliable, but it does add an overhead, and I don't think it's worth it.

 

Regarding Recovery - you can check yourself - com.apple.recovery.boot\SystemVersion.plist was removed from recovery partition as of 10.9.

We always got version for Recovery partitions using this file, it existed before, and we could successfully retrieve version using it.

I confirmed on multiple systems that SystemVersion.plist exists for 10.7 and 10.8 recovery partitions (and contains the proper version) but doesn't exist at all for 10.9 recovery. If you know of a case where this is not true, please do let me know. Additionally Clover completely relies on this file for detecting versions for all OSX (regular+server+recovery), and this currently seems the only case where it's not there.

 

Honestly, I don't like these kinds of heuristics either, and I added it without liking it :) Actually Clover contained similar assumptions about Installer, all of which I removed when I added boot.efi version detection.

For Installer I think it's OK to just use the "mac" icon type in menu (as it's a one-time boot which disappears after). But for Recovery - as it stays there - I think it's better to actually have the OS version so it is displayed properly in menu.

 

And regarding assuming too much - what's the risk? Worst case scenario is ending up with the wrong icon for Recovery (which shouldn't happen anyway). So I think that overall this is currently the best solution for this. And I will keep an eye open to see if anything changes in this regard. ;)

Share this post


Link to post
Share on other sites

@ Devs.

 

Still issues with CGP using Mavericks. The first build since a rebuild of CGP in 10.9 worked fie revision 222o,

 

But I am una to build 2223 it fails with and error

make[1]: *** [/Users/tonydickinson/CloverGrowerPro/edk2/Clover/CloverPackage/sym/clover-genconfig/clover-genconfig] Error 65
make: *** [all-recursive] Error 1
I have deleted and rebuilt it but always same error. Searching around it appears to be a mismatch with the new and current builds(?),

 

any ideas?.

 

If it of any note I still have 10.8.5 loaded on another disk with CGP loaded there as well and whoa the same error there as well.

 

Edit: R2224 compiled ok. Tks.

Share this post


Link to post
Share on other sites

Hi SoThor!

 

What you just fixed and this are actually two different issues...

 

The reason I don't do boot.efi reading during scan is because I prefer to avoid reading larger files (boot.efi is about 0.5 meg) during scan.

We could do all the OS X detection using boot.efi, as it's the most reliable, but it does add an overhead, and I don't think it's worth it.

 

Regarding Recovery - you can check yourself - com.apple.recovery.boot\SystemVersion.plist was removed from recovery partition as of 10.9.

We always got version for Recovery partitions using this file, it existed before, and we could successfully retrieve version using it.

I confirmed on multiple systems that SystemVersion.plist exists for 10.7 and 10.8 recovery partitions (and contains the proper version) but doesn't at all for 10.9 recovery. If you know of a case where this is not true, please do let me know. Additionally Clover completely relies on this file for detecting versions for all OSX, and this currently seems the only case where it's not there.

 

Honestly, I don't like these kinds of heuristics either, and actually Clover contained similar assumptions about Installer, which I removed when I added boot.efi version detection.

For Installer I think it's OK to just use the "mac" icon type in menu (as it's a one-time boot which disappears after). But for Recovery - as it stays there - I think it's better to actually have the OS version so it is displayed properly in menu.

 

And regarding assuming too much - what's the risk? Worst case scenario is ending up with the wrong icon for Recovery (which shouldn't happen anyway). So I think that overall this is currently the best solution for this. And I will keep an eye open to see if anything changes in this regard. ;)

Okay, I just wasn't sure if it was just an attempt to fix the issue with the wrong Volume icon or not. So was just making sure. You have checked everything out so all is good :)

 

You are right there isn't much harm in doing it like that. I'm just a bit of a perfectionist and don't want to make any assumptions we don't have to.

Share this post


Link to post
Share on other sites

I think clover has done something to my bios.

 

I used the option to add clover to EFI when booting from UEFI and then the option to boot this device has gone.

 

I didn't realise this was what happened until I booted another usb key with different version of clover and it was available for UEFI boot, but when adding to efi it again disappeared.

 

also, my bios now reports 8gb ram where 12gb was installed. the board and ram are fine. it seems that maybe clover changes something in nvram?

 

how can I boot into uefi clover and revert the changes?

 

I did not know where else to post this message :(

okay I've solved the missing UEFI boot options, looks like lenovo hides any efi boot option in nvram that isn't 'windows boot loader' or 'red hat linux' or a couple of other 'supported' bootloaders. I used an Ubuntu to remove the entries and it's all good.

 

but the memory limit thing is still an issue. I think it may be the aptiofix/ aptiolowmem driver overwriting something in the NVRAM. its related to the dim slots rather than the physical ram, I can get 12 or 16gb by using 8gb modules. but it seems to limit the banks in concurrent use from 4 to 2.

 

booting into bios or windows shows 8gb ram, booting into os x shows the correct 12gb, but it wont boot without aptiofix / aptiolowmem.

 

is there somewhere else I need to discuss this? i'm new to clover. are the aptiofix drivers maintained by someone else? is there source code?

 

thanks!

Share this post


Link to post
Share on other sites

I'm having trouble getting custom entries to show up at all on r2217 (or any revision for that matter). I followed the wiki. Here's that part of my config.plist. (Ignore the empty volume UUID)

 

DMaCpyJ.png

Any chance you could share a boot.log (or preboot.log)? It is difficult to know what the problem is otherwise.

Share this post


Link to post
Share on other sites

okay I've solved the missing UEFI boot options, looks like lenovo hides any efi boot option in nvram that isn't 'windows boot loader' or 'red hat linux' or a couple of other 'supported' bootloaders. I used an Ubuntu to remove the entries and it's all good.

 

but the memory limit thing is still an issue. I think it may be the aptiofix/ aptiolowmem driver overwriting something in the NVRAM. its related to the dim slots rather than the physical ram, I can get 12 or 16gb by using 8gb modules. but it seems to limit the banks in concurrent use from 4 to 2.

 

booting into bios or windows shows 8gb ram, booting into os x shows the correct 12gb, but it wont boot without aptiofix / aptiolowmem.

 

is there somewhere else I need to discuss this? i'm new to clover. are the aptiofix drivers maintained by someone else? is there source code?

 

thanks!

?

AptioFixDrv is essential part of Clover. It created by dmazar and supported by rest developers.

Here is the sources

                      OsxAptioFixDrv         

Share this post


Link to post
Share on other sites

Great news for Asus x79 ,

I tested on my x 79, removing the null cpu I have no more kernel panics obviously with original ACPM
 
PS; But i see only one pstate , maybe i need a SSDT table for cpu

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 thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By Teress
      I get a lot of questions about HOW TO BACKUP A HACKINTOSH. So I decided to create Complete Guide with 5 methods described in detail, how to easily make bootable clones of Hackintosh system disks, or backup your data. Full step by step tutorial is here:
       
       
    • By STLVNUB
      Reviving my old INSTAHackintosh, it's been a while....
      Purpose:
      Create User Custom Install iso/dmg with bootloader, apps and user-settings.
      Create Live iso/usb.
      What Versions:
      Tiger-Current ( bit ambitious but hey I like a challenge ).
      Why:
      Because I can!
      I'm not too impressed with the way Apple and others handle their installs.
      Support for 4 Bootloaders:
      Chameleon
      Clover Legacy
      Refit Ozmosis
      Clover UEFI
      Keep you informed as I progress from scratch.
      This could take a while, it's NOT my priority.
      Will probably release in Os versions, starting at Mojave and working backwards.
    • By FernandoCoverdale
      Buenas!
      recuerdo que cuando empece a instalar el clover para hacer mi hackintosh el boot de clover tenia una cuenta atrás en la que pasado “no se si eran 5 o 6 segundos”se iniciaba la opcion de arranque de high sierra del disco duro que es la que se marca por defecto, seguramente habré instalado un theme que me lo deja fijo y no recuerdo como volver activarlo.
      gracias de antemano!!!
      adjunto foto

×