clover efi yosemite language screen messed up

#Clover efi yosemite language screen messed up install#
#Clover efi yosemite language screen messed up generator#
#Clover efi yosemite language screen messed up drivers#
#Clover efi yosemite language screen messed up update#
#Clover efi yosemite language screen messed up Bluetooth#

I had the Bluetooth working previously with patched IOBluetooth and IOFamily kexts but for some reason now it won't work. Now the issue I have is that Bluetooth is not working.

It's running so native, that even Boot Camp Assistant runs without issue. Sleep mode and sleep with lid due to XCPM and Rehabman's patchīCM4360 up to 5GHz and Wifi LED Indicator After updating to 10.9.3, I noticed the slider was there. Not really sure, when I first used the new EFI String I was on 10.9.2 and there was no slider. Ohh, great, you have now an almost all working setup. Check what patches are you using for your kernel.Īre you using some DSDT patched for disable Nvidia card?

Usually this is caused by kernel not patched for XCPM, maybe you are using a kernel build by someone instead patching your own kernel. Any suggestions on using Ioreg or DSDT patches or anything else to get this working would be very much appreciated, and a help to any other JM owners. I'm thinking the problem is related to the Maxwell 860M Optimus card. In verbose boot it boots normally but does not start graphics. The problem I'm having is that I can only get the SSD to boot in safe mode.

#Clover efi yosemite language screen messed up install#

Using this patch I'm able to boot the installer and install to my SSD. I've produced a Unibeast Mavericks 10.9.1 install USB and extracted my DSDT and SSDT files using RWeverything. I've a fair amount of experience with MacOS on PC, with two previous laptop installs and numerous desktop installs. I don't want to hijack the thread but I'm having problems with a G70JM install. Hello everyone, kudos to Bozzified, Areosjc, gazzacbr and everyone else for the progress being made. I hope I had explain myself ( sorry for my bad english)

#Clover efi yosemite language screen messed up generator#

One of this info is the UnderScan feature (this feature now should also work using my EFI string, is used to customize screen size presentation to fit on a HDMI screen).Īnswering your question, you can have a brightness control using just DSDT, but you will lose other features.ģ.-The SSDT-1 and SSDT-2 are just for complete DSDT info, remember some methods inside DSDT are declared as a external objects, in this case SATA values, if you like to have just one SSDT for CPU PM just integrate this info inside main DSDT.Ĥ.-You are correct in your appreciation I´m using Pike´s SSDT generator (Sorry if I did´t mention this before all credits goes to him for his script), I use it without any parameter, but I correct the file generated because his script give me 12 Turbo PStates (for 4700HQ this is wrong, it only has 10 Turbo PStates, still happens on his last version) This will lead you to have some info injected via DSDT and some info injected via EFI string, that´s why I choose to inject all the info using EFI string. I have more questions, but those would be all for now!ġ.- I can do the individual patches, I just need some timeĢ.- I also like to have all in DSDT but some info injected in the EFI string does´t work if you inject it using DSDT. I have more questions, but those would be all for : awesome work you got here, looks impressive to me by the amount of work you did to make it compatible. Can you tell me what command line parameters you used to do that if you can recall? Or no parameters at all?Īlso, why the other 2 SSDT? What are those for? I've seen in the original zip you uploaded for Bozzified that you had 2 SSDT files:ĭefinitionBlock ('SSDT.aml', 'SSDT', 1, 'APPLE ', 'CpuPm', 0x00012700)ĭefinitionBlock ('SSDT-1.aml', 'SSDT', 1, 'Intel', 'zpodd', 0x00001000)ĭefinitionBlock ('SSDT-2.aml', 'SSDT', 1, 'SataRe', 'SataTabl', 0x00001000)įor the first SSDT (CpuPm), I can see clearly that you used pikeralpha utility (I think he has a 13.x version now, btw) to generate it. Is it possible first for you to make the patches for DSDT so everyone else with different G750 laptops could apply on their own?Īlso, would be possible to skip that efi injector and use brightness via DSDT fix? I'm at version 331 at the : awesome work you got here, looks impressive to me by the amount of work you did to make it compatible.Īdded you on skype so I could ask you a couple of questions but either the request went bad or I don't know.

#Clover efi yosemite language screen messed up update#

Updated to 10.9.3, Bluetooth and sound stopped working but I'm assuming all i have to do is reinstall kexts.ĮDIT: It's not letting update to the Nvidia Web Driver to 334, it's saying it's incompatible. Yup! Thanks a lot for the help :) Didn't even realize the Wifi Indicator, haha

#Clover efi yosemite language screen messed up drivers#

If you can update to 10.9.3 use the new nvidia Web Drivers they fix the OpenCL issue witch was causing bad GPU power management. Keyboard with backlight working including auto off feature (your last state is remembered) (Dinesh credits for his kext) Touchpad with Gestures working (you can customize your own setting refer to OSXlatitude forum) Sound with AppleHDA with soobwoofer working Your PNLF Device does´t get the AppleBacklight kext attached. You old AsusNBFnKeys had a parameter for Brightness but is for intel based laptops.