a1k0n Posted October 8, 2013 Share Posted October 8, 2013 Hi I was install Mavericks GM with Clover v2 USB Drive on Fusion Drive "Macintosh HD" All works great. If i want install Clover_v2k_r2211.pkg on "Macitosh HD" there is an error. I know Fusion Drive is the problem. Also i manually copy EFI Folder to EFI Drive. Now my little problem is Clover stops every time at Clover Gui. In config.plist i set the option: <key>Timeout</key> <integer>0</integer> <key>DefaultVolume</key> <string>Macintosh HD</string> <key>Fast</key> <false/> but it s always stops at Clover Gui. i don't need the Gui. OSX is the only OS on my PC. Her is my complete config.plist i hope anyone can help my <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>FixAirport_4000</key> <true/> <key>FixDarwin_0002</key> <true/> <key>FixDisplay_0100</key> <true/> <key>FixFirewire_0800</key> <true/> <key>FixHDA_8000</key> <true/> <key>FixHPET_0010</key> <true/> <key>FixIPIC_0040</key> <true/> <key>FixLAN_2000</key> <true/> <key>FixSBUS_0080</key> <true/> <key>FixShutdown_0004</key> <true/> <key>FixUSB_1000</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> </dict> <key>DropOemSSDT</key> <string>Yes</string> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> <key>MinMultiplier</key> <integer>8</integer> <key>PLimitDict</key> <integer>0</integer> <key>UnderVoltStep</key> <integer>0</integer> </dict> </dict> <key>GUI</key> <dict> <key>DefaultVolume</key> <string>Macintosh HD</string> <key>Fast</key> <false/> <key>ScreenResolution</key> <string>1650x1050</string> <key>Theme</key> <string>bootcamp</string> <key>Timeout</key> <integer>0</integer> <key>XMPDetection</key> <string>Yes</string> </dict> <key>Graphics</key> <dict> <key>CustomEDID</key> <data> AP///////wAEcgkAcD9RgQ8SAQNoLx54KscgpFVJmScTUFS/74BxT4GAlQ+V AKlAswABAQEBITmQMGIaJ0AYsDZA2SgRAAAcAAAA/wBMQVAwODAwMzQyMTEK AAAA/QA4TB5TEQAKICAgICAgAAAA/ABBY2VyIFgyMjNXCiAgABw= </data> <key>Inject</key> <dict> <key>NVidia</key> <true/> </dict> <key>InjectEDID</key> <string>Yes</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Find</key> <data> QVBQTEUgU1NEAA== </data> <key>Name</key> <string>IOAHCIBlockStorage</string> <key>Replace</key> <data> AAAAAAAAAAAAAA== </data> </dict> <key>PCI</key> <dict> <key>InjectClockID</key> <string>Yes</string> <key>USBFixOwnership</key> <true/> <key>USBInjection</key> <false/> </dict> <key>RtVariables</key> <dict> <key>MLB</key> <string>C02JY164DHJT234567</string> <key>ROM</key> <string>50:e5:49:bd:57:63</string> </dict> <key>SMBIOS</key> <dict> <key>BiosVersion</key> <string>IM121.88Z.0047.B1D.1110171110</string> <key>Board-ID</key> <string>Mac-942B59F58194171B</string> <key>Family</key> <string>iMac</string> <key>ProductName</key> <string>iMac12,2</string> <key>SerialNumber</key> <string>C02JY164DHJT</string> </dict> <key>SystemParameters</key> <dict> <key>InjectSystemID</key> <string>Yes</string> <key>boot-args</key> <string></string> <key>prev-lang:kbd</key> <string>de:0</string> </dict> <key>Volumes</key> <dict> <key>Hide</key> <array> <string>VOLUME_NAME</string> <string>VOLUME_UUID</string> <string>TODO_HIDE_VOLUME_BY_TYPE/GROUP</string> </array> <key>Legacy</key> <string>No</string> </dict> </dict> </plist> Second ask is there anyway to install rc.scripts from Clover_v2k_r2211.pkg manually? Sry for my bad english iam german nativ. thx for reading Link to comment Share on other sites More sharing options...
rr7 Posted October 8, 2013 Share Posted October 8, 2013 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 Link to comment Share on other sites More sharing options...
blackosx Posted October 8, 2013 Share Posted October 8, 2013 1. Gray images are always 256 so the metal dragon is not a proof. 2. The icon that I downloaded from you post show me planar image with 32bit only plane. May be there is another format? 3. 256pxl is not a problem for decoders. My background is larger. The problem is menu layout with custom entries. Hi Slice. 1 - Yes you are right. A full colour photo would suffer from the compression but a large percentage of images used in themes are small similarly styled icons which would benefit from the compression, especially any animation PNG files (black_green Anim_1_Logo_IntroOutro 1.5Mb vs 647Kb). So the majority of the PNG files in the themespkg dir COULD be compressed without any issue, if desired by the theme author. While any other PNG which requires full detail could remain without further compression. 2 - That's different terminology to what I'm used to so I had to look up the difference between a planar and interleaved image and now know what they are. I see load_icns.c supports both so that's good. However, I'm not sure what you mean by 32bit plane. What procedure do you use to determine that as the .png file used in that .icns file is 256 colour 8 bit per pixel? Maybe the iconutil app is converting it? 3 - I should have said .icns decoder only. While on this topic, I know rEFIt used .icns so I guess that's why Clover also uses them, but in Clover's case, the .icns file is used only as a container for a 32x32 and 128x128 PNG image. Could Clover maybe not use .icns for the os images and instead just use .PNG like the other graphic files? -------------------- @a1k0n 1 - Can you help identify the package installer error with the installer log? You can check by clicking the Window menu -> Installer Log. 2 - Try setting the Fast=True option. <key>Fast</key> <true/> 3 - Yes, the rc.scripts can be installed manually. You can download them directly from the repo http://sourceforge.net/p/cloverefiboot/code/HEAD/tree/CloverPackage/CloverV2/etc/ EDIT: I think you will have to set the ownership/permissions of the scripts to root:wheel and 755. Link to comment Share on other sites More sharing options...
a1k0n Posted October 8, 2013 Share Posted October 8, 2013 @blackosx Thx for help. Which files i have to download? And where must i install this? (i think /etc right?) <key>Fast</key> <true/> is set in config.plist If i use an older Version from CLOVERX64.efi Timeout works but i can use FixAirport_4000 in config.plist and other options Link to comment Share on other sites More sharing options...
blackosx Posted October 8, 2013 Share Posted October 8, 2013 Yes. They go in to /etc I suggested setting Fast=True because the config.plist you posted above has it set to false <key>GUI</key> <dict> <key>DefaultVolume</key> <string>Macintosh HD</string> <key>Fast</key> <false/> <key>ScreenResolution</key> <string>1650x1050</string> What is the version number of CLOVERX64.efi that works for you? There have been many changes to Clover so maybe something else needs setting/changing. Link to comment Share on other sites More sharing options...
a1k0n Posted October 8, 2013 Share Posted October 8, 2013 @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 Link to comment Share on other sites More sharing options...
artur_pt Posted October 8, 2013 Share Posted October 8, 2013 hello Slice u advice do the trick maybe a problem in export key to clover thanks Link to comment Share on other sites More sharing options...
alexanderq Posted October 8, 2013 Share Posted October 8, 2013 @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 Link to comment Share on other sites More sharing options...
a1k0n Posted October 8, 2013 Share Posted October 8, 2013 You are my hero. It works ^^ Many thx to all who was helping Link to comment Share on other sites More sharing options...
oswaldini Posted October 8, 2013 Share Posted October 8, 2013 Yep, same here, rev 2216 2:104 0:000 Volume 'Recovery HD', OS '', Icon(s) '<null string>', GUID = 6ADC85EA-3817-47B7-86DA-4C762262A7EB Link to comment Share on other sites More sharing options...
tonydickinson Posted October 9, 2013 Share Posted October 9, 2013 @devs What is the latest news in using Mavericks GM with CloverGrowerPro. Are there any known fixes available? Link to comment Share on other sites More sharing options...
Pene Posted October 9, 2013 Share Posted October 9, 2013 @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. Link to comment Share on other sites More sharing options...
Pene Posted October 9, 2013 Share Posted October 9, 2013 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. 2 Link to comment Share on other sites More sharing options...
AsusFreak Posted October 9, 2013 Share Posted October 9, 2013 @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.'. Link to comment Share on other sites More sharing options...
Pene Posted October 9, 2013 Share Posted October 9, 2013 @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 1 Link to comment Share on other sites More sharing options...
AsusFreak Posted October 9, 2013 Share Posted October 9, 2013 OK, thanks... boot.log.zip Link to comment Share on other sites More sharing options...
tonydickinson Posted October 9, 2013 Share Posted October 9, 2013 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! Link to comment Share on other sites More sharing options...
wishywashy Posted October 9, 2013 Share Posted October 9, 2013 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) Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 9, 2013 Share Posted October 9, 2013 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: 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: 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! Link to comment Share on other sites More sharing options...
Slice Posted October 9, 2013 Share Posted October 9, 2013 Hi blackosx, See Link to comment Share on other sites More sharing options...
SoThOr Posted October 9, 2013 Share Posted October 9, 2013 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: 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: 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 . Link to comment Share on other sites More sharing options...
Fab1Man Posted October 9, 2013 Share Posted October 9, 2013 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: 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: 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. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 9, 2013 Share Posted October 9, 2013 What theme are you using? mlcamp Link to comment Share on other sites More sharing options...
Pene Posted October 9, 2013 Share Posted October 9, 2013 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. 1 Link to comment Share on other sites More sharing options...
tonydickinson Posted October 9, 2013 Share Posted October 9, 2013 @ 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. Link to comment Share on other sites More sharing options...
Recommended Posts