Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

About Maniac10

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That SSD looks so good with that big X. Count me in!
  2. Hi Mackie, lately?when I open CC it says it can’t find my EFI partition and fails to list my plists, but when I go to “Mount EFI?? and press “Open Partition?? it does find it. I’ve restored revision after revision and the last working one is 4.16. ? EDIT: it works again if I have a config.plist in /EFI/EFI/CLOVER, but mine are in the OEM folder. It seems to be the same issue I had a while ago that you already had fixed. ? EDIT 2: working again in 4.18.1, thanks for the quick fix.
  3. Love the new interface for custom entries, it makes the setup a lot easier. Thanks Mackie!
  4. Problem solved in 4.12.1. Once again, thank you for the quick fix mackie!
  5. I think "Arguments" is the key responsible for the problem. Take the config-sample.plist that comes with Clover for example, change anything but arguments and the export fails. Then go to arguments and add any key and it's exported successfully but it adds a "(null)" to the string. ? Here's the config-sample: http://cl.ly/0G1k1S453u0f
  6. Mackie, Clover Configurator 4.12.0 can't save some plist files and I can't figure out why. Here's the error shown in the Console: 20/08/14 00:35:32,623 Clover Configurator[13165]: An uncaught exception was raised20/08/14 00:35:32,623 Clover Configurator[13165]: -[__NSCFString appendString:]: nil argument20/08/14 00:35:32,625 Clover Configurator[13165]: ( 0 CoreFoundation 0x00007fff97b0125c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff8a5c3e75 objc_exception_throw + 43 2 CoreFoundation 0x00007fff97b0110c +[NSException raise:format:] + 204 3 CoreFoundation 0x00007fff97ad0def mutateError + 159 4 Clover Configurator 0x0000000101e5bdbf -[bootController saveDocument:] + 3658 5 Clover Configurator 0x0000000101e68086 -[Document saveData:] + 677 6 AppKit 0x00007fff8b30d260 -[NSApplication sendAction:to:from:] + 327 7 AppKit 0x00007fff8b3281c8 -[NSMenuItem _corePerformAction] + 394 8 AppKit 0x00007fff8b327f04 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 117 9 AppKit 0x00007fff8b37740d -[NSMenu _internalPerformActionForItemAtIndex:] + 35 10 AppKit 0x00007fff8b377289 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 104 11 AppKit 0x00007fff8b31dff6 NSSLMMenuEventHandler + 716 12 HIToolbox 0x00007fff964e51d4 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 892 13 HIToolbox 0x00007fff964e4787 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 385 14 HIToolbox 0x00007fff964f8880 SendEventToEventTarget + 40 15 HIToolbox 0x00007fff9652e640 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 420 16 HIToolbox 0x00007fff96561228 SendMenuCommandWithContextAndModifiers + 59 17 HIToolbox 0x00007fff965611d0 SendMenuItemSelectedEvent + 178 18 HIToolbox 0x00007fff965610af _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 94 19 HIToolbox 0x00007fff9653f19e _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttjS4_S4_PK10__CFStringPP13OpaqueMenuRefPt + 1726 20 HIToolbox 0x00007fff9653e2f6 _HandlePopUpMenuSelection7 + 596 21 AppKit 0x00007fff8b376161 _NSSLMPopUpCarbonMenu3 + 4153 22 AppKit 0x00007fff8b4e0db5 -[NSCarbonMenuImpl _popUpContextMenu:withEvent:forView:withFont:] + 192 23 AppKit 0x00007fff8b66b926 -[NSMenu _popUpContextMenu:withEvent:forView:withFont:] + 200 24 Clover Configurator 0x0000000101e91165 -[CNSplitViewToolbarButton mouseDown:] + 323 25 AppKit 0x00007fff8b2f3a58 -[NSWindow sendEvent:] + 11296 26 AppKit 0x00007fff8b2925d4 -[NSApplication sendEvent:] + 2021 27 AppKit 0x00007fff8b0e29f9 -[NSApplication run] + 646 28 AppKit 0x00007fff8b0cd783 NSApplicationMain + 940 29 libdyld.dylib 0x00007fff94d975fd start + 1 30 ??? 0x0000000000000001 0x0 + 1)
  7. How about doing a more "visual" approach to the custom entries section, with icons and labels like the Clover GUI? I think it will be much more intuitive for the user and can help you hide each entry's options in a sliding popup (like the SMBIOS Mac model assistant). Would you be interested in seeing a?draft? ? As a workaround for now, could you make it so Clover Configurator ignores unknown entries and keep them in the plist instead of deleting them?
  8. @Mackie, Apianti recently added the possibility to add the whole?KernelAndKextPatches section in a custom entry, so now it should be possible to selectively apply patches to each custom entry. More info in the wiki. <key>Entries</key><array> <dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <false/> <key>KextsToPatch</key> <array> ... </dict> </dict> ...</array>It doesn't look easy to add such a thing to Clover Configurator…
  9. The thing is, you won't find the ACPI path of the bluetooth device, only the one for the USB port it's connected to, so I don't think it'll work. At least I don't know a way to do so. ?Try with the kext instead and forget the string for now. ? And I extracted that EFI string for the audio device with Darwin Dumper's "Device Properties" dump.
  10. For both methods you'll need the device's path. For example this would be the converted EFI string for my audio device: <key>PciRoot(0x0)/Pci(0x1b,0x0)</key> > ACPI path ??<dict>????<key>layout-id</key>????<data>AwAAAA==</data>??</dict>You can do the same with a DSDT patch, but you need to place the DSM method under the "HDEF@1B" device like this: Device (HDEF) { Method (_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) } Return (Package() { "layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 }, }) }}Anyway, if your Bluetooth adapter is USB, then it doesn't have a fixed address, so I don't think these methods will work. At least I don't know how to do it with DSDT or EFI strings. So for now I'd advice you to try the dummy kext first, just placing it in Clover's kext folders should work.? The "developer mode" (I guess you're talking about the kernel argument) is not tied to a paying account, it's a workaround implemented by Apple to allow loading unsigned kexts (Yosemite still ships with some unsigned kexts after all). And even if this argument is removed from the final release, we just need to use Clover's injector or look for a signed kext (Andy has been uploading signed kexts like VoodooHDA and others).
  11. To simplify things, let's say there are 2 ways of enabling the device: ? 1- Masking the real device id as a similar and compatible one, so OSX will see it, think it's compatible and load the appropriate kexts. This can be achieved through DSDT editing or EFI string (not sure this actually works with this device). 2- Force the system into believing your real device id is compatible. This can be achieved by manually adding your id into the kext's info.plist, or by using an injector like Andy's kext. ? If you want to use the injector then you have to convert your hexadecimal device model and vendor shown in System Profiler to decimal and use those to replace the existing values called idProduct and idVendor in the kext's info.plist. If you need help with this method just ask and I'll walk you through it. ? What's your device's real model? Is it a USB dongle or PCI card?
  12. Sadly Clover doesn't provide native ways to inject bluetooth ids but you can try to fake it with an EFI string or DSDT, though I'm not sure it will work. If you want to try the EFI string method then you need to add the string into?Properties?and enable?Inject. As described in the wiki, this works exactly the same way than adding a DSM method in your DSDT, so this won't override the info.plist with your id but on the contrary it will mask your bluetooth as a compatible model. So you should try to identify a compatible device id similar to yours first and then inject that model with the EFI string. ? Still, I'd recommend you to first try this kext injector developed by Andy. In this case you need to convert your device vendor and id (from System Profiler->Bluetooth) to decimal and add them in the kext's info.plist. Read that thread carefully to fully understand how it works.
  13. @osxfr33k: this chat is getting too long, why don't you create a topic in the forum with all this information so we can discuss it with ease?
  14. Mackie, if I don't have a config.plist in /CLOVER then the app won't detect my OEM plists. It's like it stops looking if there's no CLOVER/config.plist.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.