Jump to content
intruder16

DSDT/SSDT Auto-Patcher for Lenovo Y510p Ideapad

43 posts in this topic

Recommended Posts

Compatible with Sierra!

 

 

Hey guys, 

 

I have created a script to auto-patch DSDT/SSDT's automatically with the given patches. Never use DSDT/SSDT's from another PC.

 

Some details:

 

Rest assured, this script will NOT in any way make any kind of change to your system! You do NOT need to run this script with "sudo"!

 

At first i created this script for my purposes only, that is, patching tables extracted from linux. I use a modded BIOS and due to increased settings it was troublesome to patch tables again and again after changing "major" settings. This script is created for the fact that if you change some BIOS settings you will have to re-extract and re-patch the ACPI tables (a headache for modded BIOS users) so that you will have a patched DSDT specifically for your BIOS settings. What happens is for some settings you change in BIOS (like DVMT pre-alloc etc.) the result is reflected in your ACPI tables. So if you use someone else's DSDT there "may" be unexplained behaviours on your end coz both of your systems  having different BIOS settings (not usually but with modded BIOS chances are significantly higher).

 

Since clover can extract tables using "F4"  at boot menu all you have to do is re-patch your extracted tables with necessary patches and this script will do that within seconds. So you have your system ready in 2 mins max.

 

Now i am releasing this script to the public. I've changed many things now for public use.

 

How to use it?

 

Very simple! Clone my git repository with the following command:

git clone https://github.com/intruder16/Y510p-OS-X.git
                                                  OR
 
if you do not have a working internet connection, go to
 
 
download the repo as zip (option in down-right corner). Extract the zip.
 
This will create a "Y510p-OS-X" folder with all the patches and autopatcher script (Y510p.sh).
 
In a terminal navigate to the unpacked Y510p git data and execute the following:
 
Make the script executable:
chmod +x Y510p.sh
Run the script
./Y510p.sh -t "target dir"
By default it will patch all SSDT's BUT it will keep the bare minimum (only 3 SSDT's - Custom CPU, iGPU & dGPU) required for a working OS X.
 
There's a new feature/option if you want to keep all SSDT's (OEM CPU related etc.). Add/pass an argument "-k" to the script to use it.
 
Note : You can pass arguments (-t, -u, -k, etc) in any order you like ! For Example :
./Y510p.sh -k -t "target dir"
or
./Y510p.sh -t "target_dir" -k

or 

./Y510p.sh -kt "target_dir"

etc.

 
To update to latest version :
./Y510p.sh -u
For more options
./Y510p.sh -h
The script will guide you through the process.
 
NOTE-1: You must specify (--target/-t ) a target folder (containing extracted DSDT/SSDT's)
 
NOTE-2: I'll highly advice you to check logs in "tmp/" after running the script.
 
Watch the script in action here:
 
 
Change-log:
 
v1.1 : Initial Release (Stable - No errors) (17 Mar 2015)
  • Internet check - the script will check for internet conn. if its available it will download all up-to-date patches required else it will use patches from "patches/" folder (i'll keep them up-to-date)
  • Multiple runs - if you run the script more than once, you won't have to worry about previous leftovers they won't be overwritten simply copied to new folder inside "tmp/" like "tmp-1", "tmp-2" etc.
  • Added "logging system"
  • Added "patches check"
  • Added choice for both Synaptics & ELAN Touchpad users (needed for brightness keys to work)
  • Added choice for debug methods (DSDT, _WAK/_PTC, Qxx)
  • Intelligent SSDT patching, that is, no matter how you extract acpi tables they will be patched always right. 
          For ex. Every method has unique naming of ssdt's.
             If extracted from linux then ssdt1,ssd2,etc and ssdt6, ssdt7 & ssdt8 inside dynamic folder.
             If extracted using clover then ssdt-0, ssdt-1, ssd-2, ssdt3x, ssdt-4x etc.
             Now the script will look at the contents of SSDT and patch it with required patches. 
  • Added brief description at the start of script about what it is going to do.
v1.2 (28 Mar 2015) : 
  • Cleanup -Removed Bogus SSDT's

  •                -Using "OS Check Windows 12" patch now (might help with native usb drivers)

  • Added choice for "LID Sleep"

  • Added choice for "Wake On USB"

  • Added an option to use native CPU PM SSDT, but that's experimental and that's why disabled in script.

v1.3 (12 Apr 2015) : 
  • Added "MCHC" patch (forgotten)

  • patches updated for offline mode.

v1.4 (21 Apr 2015) : 
  • Added new option (-k) to keep all SSDT's

  • using only 2 OEM SSDT's (iGPU & dGPU) by default

  • minor improvements/optimizations

  • using "getops" now

  • added new CPU SSDT for 10.10.3 & SMBIOS MacBookPro 11,2

v1.5 (06 Dec 2015) : 
  • Added support for El Caiptan 10.11 & above

  • Added support for SmartTouchpad users for both Synaptic & ELAN touchpads

  • minor improvements/optimizations

v1.6 (08 Dec 2015) : 
  • Fixed USB patches for El Caiptan 10.11 & above

  • Fixed a bug where DSDT won't compile if you did not chose to add "DSDT Debug Methods" but chose "WAK/PTS" or "EC Queries"

  • Raised "tmp-1", "tmp-2" folder limit to "tmp-100" (previously upto "tmp-10")

v1.7 (28 Sep 2016) : 

  • Fixed for Sierra 10.12.x

  • Using IntelBacklight (faster) instead of ACPIBacklight patches. Use IntelBacklight.kext with it.

  • minor improvements/optimizations

  • Added optional clover hotpatch.

IMP: (Only for El Capitan 10.11+ usersDon't forget to install FakePCIID.kext & FakePCIID_XHCIMux.kext (included in FakePCID zip) from here.

 

NEW: A new clover hotpatch method is also added here

 

Credits:
 
Pike R Alpha : https://github.com/Piker-Alpha/ssdtPRGen.sh (For CPUSpeedStep SSDT patch)
 
 
 
If you would like to modify this script for your own purposes feel free to modify it, but if sharing publicly give credits!
 
Any feedback and suggestions are appreciated.
 
Enjoy.

Share this post


Link to post
Share on other sites
Advertisement

This is an awesome work. I have an idea if you have the time and will to implement it. Currently this work is dedicated for Y510P only but why not expand it? Something like:

  1. Preparing a list of patches (those available in your repository)
  2. The user picks from them all the relevant to his PC
  3. The selection is saved to an XML file (can be edited away from your program) in a special location to the program
  4. The program patch the ACPI files according to the selection from the XML file
  5. Next time if the program found the XML in place, it asks the user to directly patch using that XML file
  6. The program offers an ability to add/remove/rearrange patches and update the XML accordingly
  7. Since some patches needs to be edited for certain hardware, the program can offer this functionality:
    • Save a copy from the repository patch in the XML file
    • The user edit the patch inside the XML file according to his hardware
    • The program check some flags while using the XML in patching so it knows the most up-to-date version to use (online or XML)
      • If online version is updated (for whatever reason), the user is notified to fetch the new patch and edit it to match his hardware
      • if XML version is still up-to-date then the program use it right away
  8. A GUI as a front end to the script? would be awesome for newbies !

I think this would be a hit, thought it would need much work from you to put it in the perfect shape ...

Share this post


Link to post
Share on other sites

That is a nice idea. I remember a program like that, made in '11 i think but never updated. It would take a long time. But i'm really sorry i really don't have that much time.

 

The only problem i think it should never be implemented is that it defeats the whole purpose of learning. Creating an ideal patcher is something very tiresome. Someone always will have some problem with it.

 

Its like this old adage :

 

"Give a man a fish and he can eat for a day, teach a man how to fish and he'll eat for a lifetime."

 

Also it is very straightforward to patch using patchmatic (if you already have your patches). You won't believe the first version of this script (for my own use) was something like this :

#!/bin/sh
 
cd working_dir
 
patchmatic DSDT.dsl some_patch1.txt DSDT.dsl
patchmatic DSDT.dsl some_patch2.txt DSDT.dsl
patchmatic DSDT.dsl some_patch3.txt DSDT.dsl
patchmatic DSDT.dsl some_patch4.txt DSDT.dsl
 
exit

Then i saw someone made a script for auto-post-config of OS X (including DSDT, clover config etc) and i changed my script to what it is today.

 

But i very much appreciate your suggestion and it would be great if someone could do that. Thanks.  :angel:

Share this post


Link to post
Share on other sites

That is a nice idea. I remember a program like that, made in '11 i think but never updated. It would take a long time. But i'm really sorry i really don't have that much time.

 

I agree, I'm not sure anybody would have that much time! 

 

The only problem i think it should never be implemented is that it defeats the whole purpose of learning. Creating an ideal patcher is something very tiresome. Someone always will have some problem with it.

 

Its like this old adage :

 

"Give a man a fish and he can eat for a day, teach a man how to fish and he'll eat for a lifetime."

 

That's true which is why I did not include a downloads section in my guide for long time. People should learn to Google for the right tools and do their stuff by their own hand to learn. However, I have found that most people don't have the will to learn as much as having the thing working. They would agree to try by themselves but they rarely read and almost always ask and its always the same mistakes and questions which makes the more experienced ones wants to get rid all this by providing pre-made solutions! 

 

 

 

Share this post


Link to post
Share on other sites

DSDT Auto-Patcher for Y510p Updated.

 

Changelog:

 

v1.4 (21 Apr 2015) : 
  • Added new option (-k) to keep all SSDT's

  • using only 2 OEM SSDT's (iGPU & dGPU) by default

  • minor improvements/optimizations

  • using "getops" now

  • added new CPU SSDT for 10.10.3 & SMBIOS MacBookPro 11,2

A new argument (-k) has been added. Use it if you want to keep all the SSDT's.

./Y510p.sh -k -t "target_dir"

or

./Y510p.sh -t "target_dir" -k

or 

./Y510p.sh -kt "target_dir"

etc.

Share this post


Link to post
Share on other sites

I just tried this method for the first time. Yep, great work but unfortunately it didn't help me!!

It's not a problem with your work but something is wrong with the BIOS (v3.08), the disassembled native tables do not compile without errors. Do you know anything about this??

 

 

Edit:

Never mind, it was a weird problem with MaciASL. I used Rehabman's version and all is fine now.

Share this post


Link to post
Share on other sites

Sorry for being away for so long. I was very busy.

 

Glad you got it working. I really don't remember, but i think i did try it with new BIOS (v3.08) and it worked alright.

 

If you find any issues feel free to give a feedback here.

Share this post


Link to post
Share on other sites

Hello, I have extracted my tables using CLOVER f4 method and I have already patched those files using your git repo method. Now I copied these into patched folder but I don't see any difference. I tried  ahmed_ais config.plist file but if I use this .plist file I can't access to OS X. It restarts after apple logo. What should I do?

Share this post


Link to post
Share on other sites

Hello, I have extracted my tables using CLOVER f4 method and I have already patched those files using your git repo method. Now I copied these into patched folder but I don't see any difference. I tried  ahmed_ais config.plist file but if I use this .plist file I can't access to OS X. It restarts after apple logo. What should I do?

 

Hi. Please state what's the problem you are having clearly. You say you did not see any difference, to what?

 

Patching the tables is necessary and the method here works brilliantly. Also having properly configured config.plist is necessary and the one I uploaded on the other topic is working fine AFAIK. I am not sure why your hack reboots as you say but try to:

  • Boot in verbose mode so you can see any logs that could help. (post a screenshot if possible)
  • Boot without dropping any tables (from Clover interface) so if it does booted then you may have a problem with one or more of your tables.
  • Boot using the USB installer so it would boot without patched tables and without my config.plist
  • Post your EFI folder here so one could investigate

Share this post


Link to post
Share on other sites

 

Hi. Please state what's the problem you are having clearly. You say you did not see any difference, to what?

 

Patching the tables is necessary and the method here works brilliantly. Also having properly configured config.plist is necessary and the one I uploaded on the other topic is working fine AFAIK. I am not sure why your hack reboots as you say but try to:

  • Boot in verbose mode so you can see any logs that could help. (post a screenshot if possible)
  • Boot without dropping any tables (from Clover interface) so if it does booted then you may have a problem with one or more of your tables.
  • Boot using the USB installer so it would boot without patched tables and without my config.plist
  • Post your EFI folder here so one could investigate

 

Hello, by I don't see difference I meant I don't fixed any problems. If I use original config.plist then it will boot to the OS X but it won't detect my dsdt files and with your config.plist it won't boot into OS X. So I don't know what to do.  

 

This is my CLOVER folder: https://mega.co.nz/#!7NUSRJIb!eY_iQjjOI6ofeG-C0ekjB3FMX_FtssvTO3tT1u9IwHY

In this Folder I have standard CLOVER config.plist

 

This is verbose mode using your config.plist  http://www.upload.ee/image/4772071/IMG_0026.JPG

 

I hope someone can help me out.

Share this post


Link to post
Share on other sites

Hello, by I don't see difference I meant I don't fixed any problems. If I use original config.plist then it will boot to the OS X but it won't detect my dsdt files and with your config.plist it won't boot into OS X. So I don't know what to do.  

 

This is my CLOVER folder: https://mega.co.nz/#!7NUSRJIb!eY_iQjjOI6ofeG-C0ekjB3FMX_FtssvTO3tT1u9IwHY

In this Folder I have standard CLOVER config.plist

 

This is verbose mode using your config.plist  http://www.upload.ee/image/4772071/IMG_0026.JPG

 

I hope someone can help me out.

 

Still you did not define what are these problems you are trying to fix unless you mean that the problem is OS X does not load your patched ACPI tables. Am I correct?

 

I toke a quick look at your Clover folder and found things I am not used to:

  • Some drivers are missing (EmuVariableUefi-64.efi and PartitionDxe-64.efi) and one weird driver is there (HPFanReset.efi)
  • I cannot find any need for the kext: RealtekRTL8111.kext. I will also assume that you installed the remaining necessary kexts in /S/L/E.
  • Many files are absent from the folder: tools 
  • Some folders are missing: drivers32UEFI, OEM, doc

While Clover may not complain about the missing items as some of them are actually not needed for x64 system, I believe this installation is corrupt. I advice you to backup this Clover folder, remove it from EFI, and install a recent version of Clover following the steps in the guide

 

Regarding config.plist, the one included with your Clover folder has many things to be removed as it is too generic. One advice about config.plist: only include the options you need. Finally about my config.plist (after seeing the picture you uploaded), I think you used it as is without modification right? If so, edit it to include a valid SMBIOS as I do not include one inside a public config.plist (for serial number concerns) and also do not copy it from your other config.plist. Try to use Clover Configurator to generate the SMBIOS then look at the code inside the file to learn more about the structure of this tag.

 

A general advice: follow the guide literally and you should be totally fine. If you still have problems, post back in the guide as your problems seems not related to this one and may confuse other people of thinking there are problems with the Auto-Patcher.

Share this post


Link to post
Share on other sites

Ooh, it is so difficult to express myself because english is not my native language. I now try to explain everything from 0 to where I am.

What I have done:

1. Installed OS X Yosemite following these guides 

2. After install I dropped my tables using Clover f4 method.

3. After table dropping I patched my files using "Intruder 16" repo.

4. Copied all files like said.

 

Problem:

If I use the those original CLOVER files, I can boot to OS X but I have problems like picture is flicering etc.

If I use your config.plist I can't boot into OS X anymore.

 

 

Now answers for your questions.

I havent installed any drivers only one kext to get network.

 

One more problem is that I don't understand this Clover Configurator. It is very hard to follow because I don't see the code behind it. In tonymacx86 forum one guy said, I am not allowed to edit config.plist in text editor because it will corrupt my config.plist file.

 

My questions.

How can I modify your config.plist with clover configurator if I can't boot with it?

How can i "say" to clover configurator that I use these DSDT and SSDT files?

 

Maybe you have a little time to add me on Skype; tarvomaesepp and help me using team viewer.

 

Best wishes!

Share this post


Link to post
Share on other sites

Ooh, it is so difficult to express myself because english is not my native language....

No worries. Try your best to describe the problem, and I will try my best to understand. After all, English is not my native language too.

 

... I now try to explain everything from 0 to where I am.

What I have done:

1. Installed OS X Yosemite following these guides

2. After install I dropped my tables using Clover f4 method.

3. After table dropping I patched my files using "Intruder 16" repo.

4. Copied all files like said.

Not bad. I would say you have succeeded to install OS X on your machine. But remains to fix it so you have a better experience. By the way, please confirm you have Y510p!

 

Problem:

If I use the those original CLOVER files, I can boot to OS X but I have problems like picture is flicering etc.

This is not related to the original Clover files. This is because graphics have to be fixed as described in detail within the guide.

 

If I use your config.plist I can't boot into OS X anymore.

I already said it is un-complete file as it lacks SMBIOS section which is mandatory. But it is still preferred over the default one as it only contains what we need for Y510p and proven to work. By the way, even when you complete my config.plist you will still have bad graphics because they have to be fixed away from Clover as I said above.

 

Now answers for your questions.

I havent installed any drivers only one kext to get network.

Regarding kexts, we need a handful number of them to fix our setup. There is one for ethernet (LAN), two for graphics, one for brightness, one for battery, one for keyboard & touchpad, one or two for audio, and you might also need one for WiFi. Links for all this and description of what they do and other important details are covered thoroughly in the guide.

 

One more problem is that I don't understand this Clover Configurator. It is very hard to follow because I don't see the code behind it. In tonymacx86 forum one guy said, I am not allowed to edit config.plist in text editor because it will corrupt my config.plist file.

 

 

My questions.

How can I modify your config.plist with clover configurator if I can't boot with it?

How can i "say" to clover configurator that I use these DSDT and SSDT files?

Clover configurator is just a front-end / GUI to edit config.plist. It is useful for newbies to get a picture of what's going on though it have some hiccups and all advanced users end up editing the code directly within config.plist. It is correct that normal text editors can destroy a .plist file and render it unusable. However, there are other special editors that can edit .plist files efficiently like Xcode and PlistEditPro.

 

To edit the config.plist I supplied, boot with the USB installer and use PlistEditPro from within OS X to edit the file then save it in the correct location. And to tell Clover to use your tables, you have to tell it not to use default/native tables (OEM). This is done by checking "Drop OEM" in ACPI section and of course your tables must be in the proper location.

 

One more thing, make sure the structure in EFI partition is correct. This means, EFI partition > EFI folder > Clover folder > (ACPI, Kexts, .... ) folders.

 

Kindly invest half an hour to read the guide because all your questions are answered there and you will find more to learn about. It is not appropriate to keep writing the same things while they are already in the guide with details. Me and others spent a lot of time to gather all the required information for the pleasure of Y510p users so why don't you read and benefit? And again, try to post in the right topic to get the best response and keep other topics clean and organized. Follow the guide and post back there if you still have issue (I am not going to reply about this here anymore).

 

 

Share this post


Link to post
Share on other sites

...1. Installed OS X Yosemite following these guides https://www.youtube.com/watch?v=xb0qraapHtE....

 

Do you have Y50 or Y510p? Keep in mind, this thread is for Y510p only.

 

If you have Y510p refer the guide here.

 

If you have Y50-70 refer the guide here

 

Read it thoroughly, follow it, you'll have OSX running in your laptop in no time.

Share this post


Link to post
Share on other sites

I now start all over. I have already created my USB with 2 partitions, one is YOSEMITE and the second partition is CLOVER.

 
May I ask you for your EFI folder since the most hardest thing to understand is the CLOVER. Thank you for your time guys and I promise not to waste your time anymore.
 
Cheers ;) 

Share this post


Link to post
Share on other sites

 

I now start all over. I have already created my USB with 2 partitions, one is YOSEMITE and the second partition is CLOVER.....

 

Which laptop do you have?

 

....Thank you for your time guys and I promise not to waste your time anymore.

 

No need. Keep your questions coming. Happy to help.

Share this post


Link to post
Share on other sites

Hello, I am back here because I don't think this is about me :D If I patch my files I have error in patch.log

Error "patchmatic: unable to open input file 'tmp/DSDT/Decompiled/SSDT-1.dsl'" What is this and how to be able to open this file? 

 

I tried patched files, pretty much everything works perfectly but I don't have sound and no battery management.

Share this post


Link to post
Share on other sites

Did you extract DSDT/SSDT's? If you did, point the script to that folder using "-t" argument. Refer OP for more details. See "Watch the script in action" part.

Share this post


Link to post
Share on other sites

Yeah, I know, I extracted my DSDT/SSDT's from clover with f4 method, I think it is right way to do this? Or it is not? 

 

Correct. Now use the commands in OP (or those i gave you in PM before. They worked, right?).

 

If it didn't work, post screenshots of extracted DSDT location and script location.

Share this post


Link to post
Share on other sites

Yes, your commands work like a charm. But look at this.

This is terminal, everything went successfully and patch.log error: http://www.upload.ee/files/4776748/IMG_0033.jpg.html

and this is (extracted tables(I copied them from clover to desktop)): http://www.upload.ee/files/4776752/IMG_0034.jpg.html

 

Upload "clover/origin" and the "tmp-3" folder.

 

Which BIOS version are you using?

 

EDIT: No need. You are missing one SSDT (one with dedicate GPU - Nvidia info). There should be a total of 8 SSDTS (including dynamic ones). Re-extract tables in clover.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?f=45&t=9172
       
      ---USB---
      https://pikeralpha.wordpress.com/2016/07/13/simple-skylake-usb-fix-no-kexts-required/
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By AppleBytes
      Hello,
      I'm working on a re-install of OSX on a dell inspiron 9400. I was finally able to get a copy of SL on it. But it still needs MUCH work, as the graphics (NVIDIA Geforce Go 7800) isn't properly recognized -- either by model, or installed VRAM.
      It has 512Mb, but only initializes 256Mb VESA.
      Anyway, as a start, I thought it best to use a valid dsdt.dsl for compilation, and start there. I've managed to remove all the warnings, and errors save 2
      OUTPUT:
      # sudo iasl -ta ./dsdt.dslll Intel ACPI Component Architecture ASL Optimizing Compiler version 20110527-64 [May 27 2011] Copyright (c) 2000 - 2011 Intel Corporation ./dsdt.dslll   3519:                                 Return (0x00) Error    4080 -           Invalid object type for reserved name ^  (found INTEGER, requires Buffer) ./dsdt.dslll   3956:                     Return (Package (0x00) {}) Remark   5072 -         Effective AML package length is zero ^ ASL Input:  ./dsdt.dslll - 4997 lines, 158533 bytes, 1633 keywords Compilation complete. 1 Errors, 0 Warnings, 1 Remarks, 577 Optimizations I'm attaching a copy of the above output, and the dsdt.dsl file in a tarball to this post in hopes someone with the required knowledge can help me fix it.
      FWIW
      SMBIOS I'm using indicates this is a MBP 3,1
      cpu: cd2 (T7400 @2.16Ghz)
      graphics: NVIDIA Geforce Go 7800 ( G70M? )
      ram: 4Gb
      dell inspiron 9400 (Laptop)
       
      Thank you for all your time, and consideration!
       
      --Chris
       
      DSDT-DSL.tar
    • By penghubingzhou
      URL:https://github.com/penghubingzhou/VoodooI2C-DSDT
       
      VoodooI2C-DSDT is a repository that is aiming at collecting various successful DSDTs for Voodoo I2C.
      Purpose
      The purpose of this repository is to provide some useful code examples for people who haven't yet make Voodoo I2C work. Maybe It don't have your model of laptop, but code in this repository may have some help and references for you.
      Note that the code in this repository is ONLY FOR REFERENCES and it can‘t replace your own work!
      For Submission
      This repository welcomes everyone to submit DSDT code examples that have successfully made VoodooI2C work by PR. To submit your example, please put the DSDT file (or Hotpatch SSDT file), an ioreg without Voodoo I2C installed, and Info.txt in a folder named by your laptop model. Info.txt should include:
      Your CPU model (better for including CPU platform)
      Your touchpad Device ID
      The mode you use (GPIO interrupt or polling)
      Satellite Driver You Use
      Then, fork this repository and clone it, put your file in and commit it to your repository. After checking the conflicts, you can send your commit as a PR to me.
      An example for submitting can be found in Lenovo Xiaoxin Chao 7000-14.
      Credits
      @Alexandred for VoodooI2C @daggeryu for the idea in this repository @penghubingzhou and @williambj1 for maintaining
    • By Gorec
      Hi.
      I apologize in advance if I didn't post in the right category and if my title and description aren't specific enough :c
       
      My config in a nutshell:
      CPU: i7 5820k GPU: MSI GTX 1060 3GB RAM: 16 GB MOBO: MSI X99 SLI PLUS I attached RunMe output with all the details of my built.
       
      Some background:
      I have my Hackintosh for about half a year. That time I managed to make it works and fix major issues, but some of them left unresolved since then and I ignored them until now.
      I use my Hackintosh for Adobe projects (PR, AE, PS, IL, AU and a lot more) - most of them connected with video editing of course browsing with Chrome and other small tasks.
       
      Problems:
      Random restarts - this is the biggest one. I'm starting to work on bigger and bigger projects and at this time I think I can't allow this to happen that often. In the past, they happened like once a day or a couple of times a week. However, now it's just frustrating when it happens even 5 or more times a day. I've tried to observe and find out what can be the cause but I haven't managed to find any connections. I thought it happens when Premiere or another app is using GPU, but I haven't seen increased usage when it restarts. I think that it can be connected with GPU, memory or PSU or... meh, anything else. I don't have resources to check if it'll work with other components. There should be some fix for this. I will really appreciate any help with this :c Restart instead of shutdown & sleep doesn't work. I've tried to look through some Google results for this and tried many solutions (as you can see in attached Clover folder), but I think the right one for many of these issues is to make my own DSDT. Glitches, freezes and other things while encoding a video. It happens very often when I try to do this. Maybe it is an issue with GPU or (hopefully) only with GPU drivers which can be fixed with some patch. Today my headphones stopped working. I have a multi-output device configured in the Audio MIDI Setup app which includes my headphones (HyperX Cloud via USB) and Soundflowerbed virtual audio device for capturing system audio. Today while I was trying (like 15 times) to encode a video in Media Encoder in the background and watch video on YouTube I stopped hearing anything from my system. Of course, it restarted a couple of times as always, but even this didn't solve this. If I plug them directly with mini jack (not via USB Soundcard which was in the box and which I always used) in the front IO or the back I only hear some loud noise It takes EX-Fat formatted volumes a few minutes to mount after each restart. I found a workaround to format it with NTFS since I have Tuxera installed and I will reformat these volumes when I will find time for this, but maybe there is some fix for this. GPU is a little bit hot. HW Monitor shows it is only 45-55 degrees, but for my hand is a little bit hot, idk. Also related to GPU - glitch after POST but before entering Clover boot menu. It is a black screen with little white squared glitches for a few seconds. Maybe it indicates the GPU drivers are loading, but maybe it shouldn't be like this. And if I can ask about that - I can't make all applications hide on startup. I, obviously, have "Hide" checkbox checked on every login item in settings, but it doesn't work, none of the apps is hidden in the dock. Is there a way to fix this? Also a small but annoying problem - I can't turn off permanently Mojave update notification (since I tried to install it, and I had to reverse to High Sierra because I had a black screen and I didn't have time for repairing all of them. Tags are not working in Finder - every time I tag a file or folder and make a change in it (for example save a text file) the tag disappears.  
      So, with knowing all of that, is there a way to make a proper DSDT file for my Hackintosh? I tried to look through some guides on how to make it but I think I reached my abilities to understand how Mac OS works and what all of these things are, so I'm asking you guys politely, would someone like to help me? At least with these random restarts? :/
      I really begin to think that I'm a newbie in configuring all of that Clover things - even after what I managed to do with my PC. Help me, pleease... :c
       
      If you have any questions post it below, I will really appreciate any help <3
      Send me MBP-Gorec.home.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
×