todesto Posted November 28, 2013 Share Posted November 28, 2013 Maybe some USB device is misbehaving? But first, could you upload your DSDT/config so I can compare it to mine? And can you check what version of the Z68AP-D3 you've got? Is it rev1 or 2? Here is my config.plist. i have rev 2 and tried UEFI but it really sucks. Can't change much in Bios and I didn't see any improvement so I reverted it back to regular bios. I am using DSDT that I was using for my Chameleon. I booted with Chameleon and I find sleep/wakes works fine with it. I'd like to use Clover as it has kext to patch so I don't have to mess with S/L/E kexts but I just might have to switch it back...... config copy.plist.zip Link to comment Share on other sites More sharing options...
pokenguyen Posted November 28, 2013 Share Posted November 28, 2013 Here is my config.plist. i have rev 2 and tried UEFI but it really sucks. Can't change much in Bios and I didn't see any improvement so I reverted it back to regular bios. I am using DSDT that I was using for my Chameleon. I booted with Chameleon and I find sleep/wakes works fine with it. I'd like to use Clover as it has kext to patch so I don't have to mess with S/L/E kexts but I just might have to switch it back...... What UEFI drivers are you using? Link to comment Share on other sites More sharing options...
todesto Posted November 28, 2013 Share Posted November 28, 2013 i am not using any UEFI drivers. only X64 drivers. I thought you dont use UEFI driver if you are on bios board? Link to comment Share on other sites More sharing options...
Maniac10 Posted November 28, 2013 Share Posted November 28, 2013 Upload your DSDT too. Do you have a SSDT? Try with the iMac12,1/12,2 profile, mine works better with them. And you can actually boot UEFI with your regular bios (I do with mine), they're "hybrid" bios. Just delete the boot file from the MBR (no idea how, I started with a clean drive) and install Clover to the EFI FAT32 partition, then the bios should find Clover UEFI and boot it. In that case you'll need a couple of UEFI drivers, like VBoxHfs-64.efi and FSInject-64.efi. The rest are not required. Link to comment Share on other sites More sharing options...
toleda Posted November 28, 2013 Share Posted November 28, 2013 But sorry, IGPU and HDAU are ACPI names and written in DSDT/SSDT. As you are not using DSDT patch by Clover so it is not Clover mistake. Check if your DSDT is the same in both cases. Yes, it was the change in Clover. "If there is a drop a one table then DropOEM set to false" I will propose you to check once more, what tables you want to drop. Slice, thanks for the reply. Clover_2236 is a USB, Clover 2330 on another. 10.9 install, dsdt, 3 ssdts and config.plist are the same in this experiment. The difference in the logs is a change in the way Clover processes the same information. I tried setting DropOEM/True, no difference. Device GFX0 is not in the dsdt, it is in OEM/SSDT-3. I am trying to add Device IGPU and ignore GFX0. Clover_2236 works correctly, Clover_2330 does not. Obviously editing the dsdt solves the problem with 2330. What do I need to drop in Clover_2330 to enable ssdt HD4600 video and audio? New debug logs with the same working config.plist, no change. 2236-2330_files_v2.zip Link to comment Share on other sites More sharing options...
todesto Posted November 28, 2013 Share Posted November 28, 2013 Upload your DSDT too. Do you have a SSDT? Try with the iMac12,1/12,2 profile, mine works better with them. And you can actually boot UEFI with your regular bios (I do with mine), they're "hybrid" bios. Just delete the boot file from the MBR (no idea how, I started with a clean drive) and install Clover to the EFI FAT32 partition, then the bios should find Clover UEFI and boot it. In that case you'll need a couple of UEFI drivers, like VBoxHfs-64.efi and FSInject-64.efi. The rest are not required. Here is my DSDT. BTW, how would you boot UEFI on bios? I don't have boot installed on my fusion drive. I am only using USB stick to boot. What option do you choose on clover installer? do i select uefi board which is the very first option? DSDT.aml.zip Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 For that Clover needs to be installed on the EFI partition and the MBR boot sector should be clean. So when the system checks the drive, if it doesn't find a loader in the MBR it checks for one in the EFI partition to boot in UEFI mode. And yes, you need to select the first option to make sure nothing is added to the MBR, but before that format the EFI partition as FAT32 (it is detailed in the installer), and then find out how to wipe the MBR boot sector, else it will always boot in legacy mode. Also your DSDT contains specific code for an external USB device UTHC in PEX3. Are you sure that device isn't to blame for your sleep issue? Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 I never thought of that. I don't need USB 3.0 expansion thing in my DSDT but don't know how to remove that. It was patched by friend. Can you remove that for me? but I booted without DSDT using DSDT fix and had same issue. Maybe I will try that again. I only need HPET fix to boot. I am still testing it with clover and it sleep/wakes fine on first try, but second time, it will still reboot. I didn't have this problem with ML....so Maverick is doing something different? I use SAME DSDT with chameleon and have no problem wake/sleep. Thanks so much for your help. Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 Then try booting in UEFI mode as I told you, mine works flawlessly that way. Well, except for the resolution at boot but that's no problem. Here's your DSDT without the code for USB3 (and some tweak here and there) and just in case I'll recommend these 2 drivers for USB3 and LAN. DSDT.aml.zip EDIT: your config have lots of unnecessary keys. And your serial number may be wrong, why does it starts with C07? config-simple.plist.zip And as I told you before, try an iMac12,1/12,2 profile. Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 Thank. Went through the installer, but don't see VBoxHfs-64.efi and FSInject-64.efi in UEFI driver? Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 Those are included by default, but make sure they're in the "drivers64UEFI" folder. Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 I must be doing something wrong. Here is what I chose: Install Clover in the ESP Bootloader: Don't update MBR and PBR sectors Clover EFI: SATA CP SSDT and DSDT (yours) in ACPI/patched I rebooted with it, but stuck at loading operating system.... Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 If you want to boot UEFI then you've got to wipe the MBR boot sector first. And select the first option in the installer, it will gray out unneeded things. EDIT: and try the config I posted before. Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 Can you give me a link on how to wipe out MBR boot sector? Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 This should do it: sudo fdisk -u /dev/diskXBut before, you need to make sure your system is not using the MBR table but the GPT, else you'll lose all your partitions. Link to comment Share on other sites More sharing options...
Slice Posted November 29, 2013 Share Posted November 29, 2013 Slice, thanks for the reply. Clover_2236 is a USB, Clover 2330 on another. 10.9 install, dsdt, 3 ssdts and config.plist are the same in this experiment. The difference in the logs is a change in the way Clover processes the same information. I tried setting DropOEM/True, no difference. Device GFX0 is not in the dsdt, it is in OEM/SSDT-3. I am trying to add Device IGPU and ignore GFX0. Clover_2236 works correctly, Clover_2330 does not. Obviously editing the dsdt solves the problem with 2330. What do I need to drop in Clover_2330 to enable ssdt HD4600 video and audio? New debug logs with the same working config.plist, no change. See tables you have 1:318 0:006 Get Acpi Tables List from RSDT: 1:332 0:013 Found table: FACP A M I len=132 1:339 0:006 Found table: APIC A M I len=146 1:345 0:006 Found table: FPDT A M I len=68 1:352 0:006 Found table: SSDT Cpu0Ist len=1337 1:359 0:006 Found table: SSDT CpuPm len=2776 1:366 0:006 Found table: MCFG A M I len=60 1:373 0:006 Found table: HPET A M I len=56 1:379 0:006 Found table: SSDT SataTabl len=877 1:391 0:012 Found table: SSDT SaSsdt len=12958 You already dropped "SSDT CpuPm" but what about others? If you want same behavior as 2236 then just set <key>SSDT</key> <dict> <key>DropOem</key> <true/> And exclude other drops. Link to comment Share on other sites More sharing options...
toleda Posted November 29, 2013 Share Posted November 29, 2013 If you want same behavior as 2236 then just set <key>SSDT</key> <dict> <key>DropOem</key> <true/> And exclude other drops. Working, thanks. 10:189 0:006 Drop tables from Xsdt, SIGN=SSDT TableID= Length=0 10:196 0:006 Xsdt has tables count=9 10:203 0:006 Table: SSDT Cpu0Ist 1337 dropped 10:215 0:012 Table: SSDT CpuPm 2776 dropped 10:222 0:006 Table: SSDT SataTabl 877 dropped 10:228 0:006 Table: SSDT SaSsdt 12958 dropped 10:235 0:006 corrected XSDT length=76 10:242 0:006 Inserting SSDT.aml from EFI\CLOVER\ACPI\patched ... Success 10:258 0:015 Inserting SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success 10:273 0:015 Inserting SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success 2330_working.zip Link to comment Share on other sites More sharing options...
frankiee Posted November 29, 2013 Share Posted November 29, 2013 Hey there, so I tried clover the first time, bc the other methods don't work right (kill my USB ports). While the clover installation fixed that (thanks to "FIX_IPIC") I get other problems I hadn't before with Chameleon: - major problems with sleep / shutdown: The machine cannot properly sleep - it looks like so at a first glance, but the power light is not blinking (like it should), and the machine does not react to keybvoard or mouse in this state. If I try to wake using the power key, the machine comes up (but no screen, still all black), then immediatly goes down, comes up again, then shuts down again etc, until I manually shut down the machine completely. Also hangs at shutdown, and also seems to generate a KP each time. At least I have some crashlogs. - I like to use a custom SSDT, and placed it in the appropriate location, but it seems not to be loaded. Seems like a noob thing, but how do I actually use a custom SSDT with clover? - Cannot boot into windows anymore. The partition is detected, but I only get a blinking cursor, and nothing else. Same when I try from my Win7 installtion stick. Yeah, might all be noob things, so please do not shoot me for asking stupid questions But I tried for hours now, so I am stuck and simply have to ask. TIA! Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 This should do it: sudo fdisk -u /dev/diskXBut before, you need to make sure your system is not using the MBR table but the GPT, else you'll lose all your partitions. I have my SSD+HDD as fusion drive. Does that mean it is using GPT? So if my SSD is disk0 and HDD is disk1, sudo fdisk -u /dev/disk0 sudo fdisk -u /dev/disk1 then I format my USB stick with GUID partition, intall clover: select install for UEFI motherboard. Copy paste config.plist to the USB then reboot with Clover USB stick. Is this right procedure? Hey there, so I tried clover the first time, bc the other methods don't work right (kill my USB ports). While the clover installation fixed that (thanks to "FIX_IPIC") I get other problems I hadn't before with Chameleon: - major problems with sleep / shutdown: The machine cannot properly sleep - it looks like so at a first glance, but the power light is not blinking (like it should), and the machine does not react to keybvoard or mouse in this state. If I try to wake using the power key, the machine comes up (but no screen, still all black), then immediatly goes down, comes up again, then shuts down again etc, until I manually shut down the machine completely. Also hangs at shutdown, and also seems to generate a KP each time. At least I have some crashlogs. - I like to use a custom SSDT, and placed it in the appropriate location, but it seems not to be loaded. Seems like a noob thing, but how do I actually use a custom SSDT with clover? - Cannot boot into windows anymore. The partition is detected, but I only get a blinking cursor, and nothing else. Same when I try from my Win7 installtion stick. Yeah, might all be noob things, so please do not shoot me for asking stupid questions But I tried for hours now, so I am stuck and simply have to ask. TIA! shutdown issue: Are you using DSDT or DSDT patch by clover. You need to give little more detail how you are booting. SSDT should be ACPI/patched folder if you don't use OEM folder. just delete OEM folder and place it in ACPI/patched UEFI will not boot legacy windows. I know you can boot Windows but not sure how it can be done. Link to comment Share on other sites More sharing options...
frankiee Posted November 29, 2013 Share Posted November 29, 2013 SSDT should be ACPI/patched folder if you don't use OEM folder. just delete OEM folder and place it in ACPI/patched Yeah, I just placed the SSDT.aml in this location, but nothing seems to happen. And by OEM folder you mean /EFI/CLOVER/OEM? Just seems to be empty, apart from two extra config.plists UEFI will not boot legacy windows. I know you can boot Windows but not sure how it can be done. Actually I have a Win7 64 bit install. That should be able to boot via EFI, right? So yes, I'd like to boot both OS with EFI. shutdown issue: Are you using DSDT or DSDT patch by clover. You need to give little more detail how you are booting. I installed Clover for UEFI motherboards, the other two options I ticked were "OsxAptioFixDrv.efi" and "Install RC scripts on target volume". Booting via UEFI. And this is my current config.plist: <?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>SMBIOS</key> <dict> <key>BoardType</key> <integer>11</integer> <key>ChassisType</key> <integer>6</integer> <key>BiosReleaseDate</key> <string>10/07/10</string> <key>Version</key> <string>1.0</string> <key>SerialNumber</key> <string>CK227BRMEUH</string> <key>Manufacturer</key> <string>Apple Computer, Inc.</string> <key>BoardManufacturer</key> <string>Apple Computer, Inc.</string> <key>ChassisAssetTag</key> <string>Pro-Enclosure</string> <key>BiosVendor</key> <string>Apple Computer, Inc.</string> <key>ChassisManufacturer</key> <string>Apple Computer, Inc.</string> <key>BiosVersion</key> <string>MP51.88Z.007F.B03.1010071432</string> <key>Board-ID</key> <string>Mac-F221BEC8</string> <key>Family</key> <string>Mac Pro</string> <key>ProductName</key> <string>MacPro5,1</string> </dict> <key>GUI</key> <dict> <key>Language</key> <string>de:0</string> <key>ScreenResolution</key> <string>1920x1200</string> <key>Theme</key> <string>bootcamp</string> <key>Mouse</key> <dict> <key>Enabled</key> <true/> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Tool</key> <true/> <key>Legacy</key> <string>First</string> </dict> <key>Hide</key> <array> <string>Windows</string> <string>\EFI\BOOT\BOOTX64.EFI</string> </array> </dict> <key>DisableDrivers</key> <array> <string>Nothing</string> </array> <key>Boot</key> <dict> <key>Arguments</key> <string>npci=0x2000</string> <key>DefaultVolume</key> <string>OS X</string> <key>Legacy</key> <string>PBR</string> <key>Log</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>No</string> <key>WhiteList</key> <array/> <key>BlackList</key> <array/> <key>Secure</key> <false/> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>Intel</key> <true/> <key>ATI</key> <false/> <key>NVidia</key> <false/> </dict> </dict> <key>Devices</key> <dict> <key>USB</key> <dict> <key>Inject</key> <true/> <key>FixOwnership</key> <true/> <key>AddClockID</key> <true/> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> </dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>ReuseFFFF</key> <false/> <key>SlpSmiAtWake</key> <true/> <key>Name</key> <string>DSDT.aml</string> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>AddMCHC_0008</key> <false/> <key>FakeLPC_0020</key> <false/> <key>FixAirport_4000</key> <false/> <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>FixIDE_0200</key> <false/> <key>FixIPIC_0040</key> <true/> <key>FixLAN_2000</key> <true/> <key>FixSATA_0400</key> <false/> <key>FixSBUS_0080</key> <true/> <key>FixShutdown_0004</key> <false/> <key>FixUSB_1000</key> <true/> </dict> <key>DropOEM_DSM</key> <false/> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> </array> <key>SSDT</key> <dict> <key>MinMultiplier</key> <integer>8</integer> <key>PLimitDict</key> <integer>0</integer> <key>UnderVoltStep</key> <integer>0</integer> </dict> </dict> <key>RtVariables</key> <dict> <key>LogEveryBoot</key> <string>10</string> <key>LogLineCount</key> <integer>3000</integer> <key>MountEFI</key> <string>Yes</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>AsusAICPUPM</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>Replace</key> <data> SW50ZXJuYWw= </data> <key>Comment</key> <string>External icons patch</string> </dict> </array> </dict> <key>SystemParameters</key> <dict> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> and this is the SSDT: DefinitionBlock ("SSDT.aml", "SSDT", 1, "Test", "amitest", 0x00008000) { External (SMB_, DeviceObj) External (GBE_, DeviceObj) External (NPE3, DeviceObj) External (PCI0, DeviceObj) Scope (\_SB) { Device (VSND) { Name (_HID, EisaId ("APP0007")) Name (_CID, "virtual-sound") Name (_STA, 0x0B) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "hda-gfx", Buffer (0x0A) { "onboard-4" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Scope (PCI0) { Device (FWHD) { Name (_HID, EisaId ("INT0800")) Name (_CRS, ResourceTemplate () { Memory32Fixed (ReadOnly, 0xFF000000, // Address Base 0x01000000, // Address Length ) }) } Device (HDEF) { Name (_ADR, 0x001B0000) Method (_DSM, 4, NotSerialized) { Store (Package (0x06) { "hda-gfx", Buffer (0x0A) { "onboard-3" }, "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "PinConfigurations", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Scope (NPE3) { Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x0C) { "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "@0,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@1,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@2,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "@3,connector-type", Buffer (0x04) { 0x00, 0x08, 0x00, 0x00 }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Device (HDAU) { Name (_ADR, One) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } Scope (GBE) { OperationRegion (GPIO, SystemIO, 0x0800, 0x06) Field (GPIO, ByteAcc, NoLock, Preserve) { GO01, 8, GO02, 8, GO03, 8, GO04, 8, GO05, 8, GP45, 1, GP9, 1 } Method (EWOL, 1, NotSerialized) { If (LEqual (Arg0, One)) { Or (GP9, One, GP9) } Else { And (GP9, Zero, GP9) } If (LEqual (Arg0, GP9)) { Return (Zero) } Else { Return (One) } } Method (_DSM, 4, NotSerialized) { Store (Package (0x0A) { "AAPL,slot-name", Buffer (0x09) { "Internal" }, "built-in", Buffer (One) { 0x01 }, "device_type", Buffer (0x14) { "Ethernet Controller" }, "model", Buffer (0x1E) { "Intel(R) 82579V PCI-E Gigabit" }, "name", Buffer (0x14) { "Ethernet Controller" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Scope (SMB) { Device (BUS0) { Name (_CID, "smbus") Name (_ADR, Zero) Device (DVL0) { Name (_ADR, 0x57) Name (_CID, "diagsvault") Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "address", 0x57 }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } } } } Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, Buffer (0x10) { /* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, /* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B })) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } } Hope that helps! Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 I have my SSD+HDD as fusion drive. Does that mean it is using GPT? So if my SSD is disk0 and HDD is disk1, sudo fdisk -u /dev/disk0 sudo fdisk -u /dev/disk1 then I format my USB stick with GUID partition, intall clover: select install for UEFI motherboard. Copy paste config.plist to the USB then reboot with Clover USB stick. Yeah, it must be GPT to be turned into a fusion drive. But, install Clover UEFI in your hard drive(s), not the USB stick. Link to comment Share on other sites More sharing options...
todesto Posted November 29, 2013 Share Posted November 29, 2013 Yeah, it must be GPT to be turned into a fusion drive. But, install Clover UEFI in your hard drive(s), not the USB stick. this is what I get, sudo fdisk -u /dev/disk0 Password: fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory ----------------------------------------------------- ------ ATTENTION - UPDATING MASTER BOOT RECORD ------ ----------------------------------------------------- Do you wish to write new MBR? [n] n MBR is unchanged so I don't have anything in there, but I find the clover installer is not going to be installed in EFI of fusion volume. Looks like I have CP the files over. will update soon. Thanks for your help. Link to comment Share on other sites More sharing options...
Maniac10 Posted November 29, 2013 Share Posted November 29, 2013 Just say yes there. And Clover must be installed in the EFI partition, but I have no idea how that works on a fusion drive. Link to comment Share on other sites More sharing options...
JahStories Posted November 30, 2013 Share Posted November 30, 2013 Hi there, thanks to ermac and all the guys working on clover, it simply rocks! i'm sorry if the question is been already asked, i'm using clover to dual boot osx 10.9 and androidx86 i've 4 entries now on boot internal uefi (efi) linux internal uefi (android) osx i'd like to hide internal uefi (efi) linux can someone help me editing the config.plist to hide them? Thx a lot Another question, since i'm using clover on a touch device, and the market of such machine is growing, i'd like to know if clover is going to support touch input, it's the only process that require to use a keyboard or a mouse... thanks again. Link to comment Share on other sites More sharing options...
Slice Posted November 30, 2013 Share Posted November 30, 2013 Another question, since i'm using clover on a touch device, and the market of such machine is growing, i'd like to know if clover is going to support touch input, it's the only process that require to use a keyboard or a mouse... thanks again. Yes, is going. If I'll get full information what to do. Link to comment Share on other sites More sharing options...
Recommended Posts