Contribute
Register

Lenovo G510 - Mostly working, help needed

Status
Not open for further replies.
Joined
Mar 26, 2013
Messages
142
Motherboard
Lenovo G510 (Clover)
CPU
i7-4700MQ
Graphics
HD 4600, 1366 x 768
Mobile Phone
  1. iOS
EDIT:

For anyone else looking to get this working, I wrote up some quick notes on it here: https://gist.github.com/matt-curtis/59b9e40a6919d16d572a

--------

Hello everyone!

I've gotten my Lenovo G510 with the following specs to run Yosemite, using this guide:

CPU: 4th Generation Intel Core i7-4700MQ (2.4 GHz 1600MHz 6MB)
Graphics: Intel HD 4600 Graphics
Memory: 8GB

Everything is working well, except Wifi (using Ethernet for now, but I have a fix for this I'm working on by flashing the BIOS/inserting the Wifi Card after POST-Boot). Issues with Graphics were resolved with this guide and brightness control gained with this one.

What remains (and what this post is about) is getting Sleep working. Right now, whenever I try to sleep the computer appears visibly to go to sleep (with the screen turning off, etc.) but very shortly after the whole machine reboots. I'm not sure where to start with fixing this. I've tried disabling Safe Sleep and Hibernate mode (as I did with my former G500) but that doesn't appear to have worked.

Any ideas?
 
Hello everyone!

I've gotten my Lenovo G510 with the following specs to run Yosemite, using this guide:



Everything is working well, except Wifi (using Ethernet for now, but I have a fix for this I'm working on by flashing the BIOS/inserting the Wifi Card after POST-Boot). Issues with Graphics were resolved with this guide and brightness control gained with this one.

What remains (and what this post is about) is getting Sleep working. Right now, whenever I try to sleep the computer appears visibly to go to sleep (with the screen turning off, etc.) but very shortly after the whole machine reboots. I'm not sure where to start with fixing this. I've tried disabling Safe Sleep and Hibernate mode (as I did with my former G500) but that doesn't appear to have worked.

Any ideas?

http://www.tonymacx86.com/yosemite-laptop-support/146870-guide-native-power-management-laptops.html

http://www.tonymacx86.com/yosemite-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html
 

OK. It seems like most of what is on those checklists I've done (probably incorrectly). Here's my questions:


  • After acquiring my DDST and SSDT .dsl files via Linux, I was left with 1 DDST and 4 SSDTs. In Clover's /patched/ folder I only included the compiled .aml files for the DDST and 4th SSDT (the one containing GFX0, which was patched for brightness control). What I'm wondering is if it's necessary that I compile all 4 SSDTs...? (For some reason, the 1st SSDT wouldn't compile without errors)
  • My plist configuration:
    <key>SSDT</key> <dict>
    <key>DropOem</key>
    <true/>
    <key>Generate</key>
    <dict>
    <key>CStates</key>
    <false/>
    <key>PStates</key>
    <false/>
    </dict>
    </dict>
  • Upon verbose boot I see this: https://i.imgur.com/aIKsWlB.jpg
 
...
[*]After acquiring my DDST and SSDT .dsl files via Linux, I was left with 1 DDST and 4 SSDTs. In Clover's /patched/ folder I only included the compiled .aml files for the DDST and 4th SSDT (the one containing GFX0, which was patched for brightness control). What I'm wondering is if it's necessary that I compile all 4 SSDTs...? (For some reason, the 1st SSDT wouldn't compile without errors)
[*]My plist configuration:

I prefer to include all SSDTs.

[*]Upon verbose boot I see this: https://i.imgur.com/aIKsWlB.jpg

"Waiting for DSMOS" without a corresponding "DSMOS has arrived" implies that FakeSMC is missing or not loading.
 
I prefer to include all SSDTs.

"Waiting for DSMOS" without a corresponding "DSMOS has arrived" implies that FakeSMC is missing or not loading.

Do you think including all SSDTs will help, or does it matter?

As for the verbose log screenshot, I was specifically worried about "power management may be incomplete or unsupported" DSMOS arrives without issue, I have FakeSMC.
 
Do you think including all SSDTs will help, or does it matter?

As for the verbose log screenshot, I was specifically worried about "power management may be incomplete or unsupported" DSMOS arrives without issue, I have FakeSMC.

If you want me to check power management setup...

Download patchmatic: https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-patchmatic-2015-0107.zip
Extract the 'patchmatic' binary from the ZIP. Copy it to /usr/bin, such that you have the binary at /usr/bin/patchmatic.

In terminal,
Code:
rm -R ~/Downloads/RehabMan
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

Post contents of Downloads/RehabMan directory (as ZIP).

Also, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

And output from:
Code:
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
 
If you want me to check power management setup...

Download patchmatic: https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/RehabMan-patchmatic-2015-0107.zip
Extract the 'patchmatic' binary from the ZIP. Copy it to /usr/bin, such that you have the binary at /usr/bin/patchmatic.

In terminal,
Code:
rm -R ~/Downloads/RehabMan
mkdir ~/Downloads/RehabMan
cd ~/Downloads/RehabMan
patchmatic -extract

Post contents of Downloads/RehabMan directory (as ZIP).

Also, post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

And output from:
Code:
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu

kextstat|grep -y acpiplat output:

13 2 0xffffff7f81edc000 0x65000 0x65000 com.apple.driver.AppleACPIPlatform (3.1) <12 11 7 6 5 4 3 1>

kextstat|grep -y appleintelcpu: Empty.

ioreg & patchmatic extract:

View attachment Results.zip

Thank you!
 
How will I need to configure things so that my patched SSDT (with the brightness fix) doesn't conflict with the one generated from ssdtPRgen.sh? Or is that even a problem...?

You can have more than one SSDT in ACPI/patched. SSDT.AML, SSDT-0.aml, SSDT-1.aml, etc.

It is best to keep the original numbers on your patched SSDTs in order to reduce confusion.

Make sure the order is specified in config.plist/ACPI/SortedOrder.
 
Status
Not open for further replies.
Back
Top