Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About Sfairat

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  1. Hello, Well, if you take a closer look at this ssdt, it consists of \_SB.PCI0.PEG0.PEGP._DSM (Buffer (0x10) { /* 0000 */ 0xF8, 0xD8, 0x86, 0xA4, 0xDA, 0x0B, 0x1B, 0x47, /* 0008 */ 0xA7, 0x2B, 0x60, 0x42, 0xA6, 0xB5, 0xBE, 0xE0 }, 0x0100, 0x1A, Buffer (0x04) { 0x01, 0x00, 0x00, 0x03 }) If (One) { \_SB.PCI0.PEG0.PEGP._PS3 () } If you look at _SB.PCI0.PEG0.PEGP._PS3 method in ssdt5, you'll find this If (LEqual (\_SB.PCI0.PEG0.PEGP.OMPR, 0x03)) { \_SB.PCI0.PEG0.PEGP._OFF () Store (One, DGOS) Store (0x02, \_SB.PCI0.PEG0.PEGP.OMPR) } so, it calls _OFF method if OMPR is set to 3. And, if you look at what _DSM does with the parameters provided in the call, you'll notice that one of the side-effects will be setting OMPR to 3. Looks like _DSM with these parameters makes some preparations needed to turn GPU off safely/in a proper way. Also, in your guide you recommend to inject string into AirPortBrcm4360 > info.plist > IONameMatch. There's a bit more update-safe way. You can do Toleda's DSDT patch from here http://www.insanelymac.com/forum/topic/292542-airport-pcie-half-mini/ , there's only one difference: in the original patch, properties are injected into RP04. In our DSDT, RP04 is wired LAN, and wireless LAN is RP05, so you have to inject PXSX into it, or you'll break both LAN and WLAN. This is highly unlikely. In windows, NVidia reports that display is connected to GPU#0, which is not ultrabay GPU. Maybe I'll have more time to get it working on the weekend. I think that this is related to DSDT patching, though the only patch I have is FixRegions. I'm gonna try Clover's debugLog/have a closer look at my dsdts.
  2. Hello, everyone, Ahmed Salah AIS, that is a great guide you've written. I've updated to 10.10 a week or so ago (didn't have enough free time to try it earlier), and was able to fix everything quite fast. I only have one problem (had it with previous 10.9 installation), in 75% of boots clover hangs on "+++++" right before starting loading the OS, and I have to reboot to windows and then try launching OS X once again. Didn't you have such a problem? I'm gonna take a look at clover debug logs sometime later. Also, how did you manage to boot into os x with both NVidia GPUs? Do you boot it in safe mode? I'm interested in it 'cause I'm a bit tired of taking off the ultrabay gpu and putting it back.. When I try to boot with both GPUs, verbose log is fine, though it reboots just before showing the login screen. What are the downsides of it? Also, if you want to disable nvidia GPU whatsoever, you can use the SSDT I've once provided in the previous topic.
  3. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Yes, I've edited the kext inside /s/l/e. Our dsdts should be compatible, I'll have a look at your ones a bit later. DSDT is "Differentiated system description table", and SSDT is "secondary system description table". You may say that DSDT is "main" table, and SSDT's are "additional" tables. About where to read - well, just google it, there's a lot of info. Our original DSDTs are completely identical, by the way.
  4. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    SSDT-3 in my DSDT's disables Nvidia GPU. About FakeSMC - you may try the latest version, I don't think it will make things worse. About VoodooHDA - in my case, it couldn't autoswitch between internal speakers and headphones. If you have the same problem, you may have a look at my VoodooHDA's config.plist (it lies inside VoodooHDA kext) IOKitPersonalities/NodesToPatch. By the way, I'm now trying to get sleep on lid close to work. Rehabman, I've read your solution to this with ACPIPoller and though it works, I can't understand why GPE's _L1F method in DSDT isn't being triggered :/ ACPIDebug shows me that of all GPE events, only L1E is being triggered, and it looks like L1f is responsible for lid, because it calls Notify on Lid device. Am I right that GPE's methods should be called by the "hardware"?
  5. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    That's really strange, our DSDTs should be compatible. There are some actions which may help. 1. Please check that you have DSDT & SSDTs in ACPI/patched folder in clover. 2. Try to boot without my dsdts and without ACPI/SSDT/DropOEM key in clover, if this gets stuck on the same line as before, then it's probably not DSDT problem. 3. Provide me your native unpatched DSDT and SSDT tables, I'll have a look at them. 4. Also, try to make a vanilla installation usb drive & put my files on it and check whether it will boot - I've just made this procedure and everything worked for me.
  6. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Ok, try to boot into chameleon, then remove the NullCPUPM kext from /e/e (if you need to put it back to /e/e to boot with cham) and run kext utility. Looks like it's stuck in caches for some reason, kext utility will probably get it out of there. Don't really understand why clover loads the cache when told not to do so, will investigate it tomorrow.
  7. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    It still loads NullCPUPM, or it doesn't work even without it?
  8. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Looks like you have it somewhere.
  9. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Your third screenshot looks like normal boot. Try to remove NullCPUPM from /S/L/E, select "boot without caches" in clover. Also, remove KernelAndKextPatches/KernelPM flag from clover's config.plist, if you have already patched kernel. Clover sometimes hangs at that "+++++"'s, it looks like it has problems with hibernated windows (that bug doesn't appear when I shut down by rebooting).
  10. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Whitelist checks not these FRU numbers, but hardware & subsystem IDs, which are the same for that card on ebay and for that listed in lenovo maintenance manual. Actually, these two FRUs and the hardware ID correspond to BCM 4352 manufactured by LiteOn.
  11. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    I bought this one, was in the whitelist. What are the errors with clover? Can you provide a screenshot? Do you put FakeSMC and other kexts to Clover/Kexts/10.9 or to /S/L/E, or did you forget to copy it from /Extra ? Here's my full EFI folder, all my additional kexts I've provided above lie in /S/L/E.
  12. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    1. You can take a look at my kexts/clover config. 2. System preferences -> displays -> color, try to change your color profile to another one. You can then calibrate the working profile, it will somewhat improve the color quality. 3. Try BCM4352, works perfectly with OS X and is 802.11 AC compatible. 4. If you reboot into windows, there is a way which can help you - press fn+f1, it will put your laptop to sleep, then wake it - the display will be properly reinitialized If you reboot into OS X, dunno how to fix that. 5. Try GenericUsbXHCI - native OS X usb kexts prevented my laptop from sleeping. Even with these kexts, I have two (minor IMO) sleep problems - laptop doesn't recognize that lid is closed, and it doesn't sleep with AC connected (it wakes up immediately, to be precise). 6. By the way, how did you make it work?
  13. Laptop - Lenovo IdeaPad Y510p - 10.9 - Mavericks

    Hello, I use this laptop as a primary working machine for iOS/Mac development, and it's surprisingly stable (I had no KPs/freezes/reboots for ~2 months); I even don't need to use my real mac any more (early 2013 MBP 15" with retina, it used to freeze several times a week for no reason ). OK, about my system: I use clover bootloader, slightly patched DSDTs and kexts. DSDTs have: 1) Patched P-states 2) Patched battery section 3) Disabled GT-755m, so it won't draw energy 4) Some other patches Kexts have: 1) Patched IO80211Family for BCM 4352 support 2) Patched IONetworkingFamily (with ALXEthernet) for ethernet support 3) GenericUSBXHCI (With native usb kexts sleep doesn't work properly/usb doesn't wake after sleep). 4) VoodooHDA was patched a bit, so it can auto-switch between speakers and headphones automatically (You should install VoodooHDA by installer, and then replace the kext with my ver.) 5) Other kexts for backlight/battery management/etc. I use RehabMan's VoodooPS2Controller for touchpad (you should also download it from RehabMan's repository on github and follow the installation instructions there), it works great for me (I have synaptics touchpad). Clover's config.plist doesn't contain serial numbers for obvious reasons, so you need to generate new ones (using clover configurator, for example). For installation, you should follow vanilla installation guide. With the files provided there should be no problems with it; you don't need to delete any nvidia kexts. You also should take out the second nvidia GPU, if you have one. Y510Hack.zip
  14. First of all, thanks a lot, your kext is the only one which enables usb3.0 on my lenovo y570 with upd720200a nec/renesas usb3.0 chipset. But, now I, among some other people, have problem with wake up from sleep both on 1.1 and 1.1.4 version. It doesn't matter if any device is connected to usb3.0 port, system doesn't wake up in any case. Anyway, I value +2 usb3.0 ports more than sleep, so thanx) caps.txt running.txt