Lenovo G500 10.9.1: Almost done, just a little bit of help needed...

[chumdoggin]

Hi all. I have decided that since there is no input codec yet for that cx20757 I am switching back to voodoohda. Using 2.8.5 and it works for input. Just kept the capri inject and the hdmi works good. better after going into the audio midi setup and fixing the wrong bit rates. I got to play with an osx version of siri named sinus... kind of amusing.

Anyway, found out that I had been searching in the plist for numlock instead of num lock so I was able to fix my issue there. For now, using the brightness slider app if I want key commands for brightness.

Funny thing I found out was I had been loading ps2controller for quite some time along with the élan trackpad. Its pretty surprising that the machine had functioned as well as it did despite that. Booted in safe mode and saw that was causing a crash!

 

[chumdoggin]

Good guide and using the dsdt edits etc. brings everything working pretty good.

issues are the system uses a lot of memory in mavericks. Maybe thats normal, maybe the reason system crashes fairly often.

I get different battery readings of remaining time on a full charge. There is full brightness on boot. Though not sure it's going to be an issue, once out of beta, XX gives the opposite effect. Low brightness. But also on wake besides boot.

As for the lid, and sleep its not been bad at all. the lid does initiate sleep but does not wake it. But no problems besides that on wake/sleep.

 

[chumdoggin]

Solved full brightness on boot by deleting the nvram file from root and also the power management plist in library prefs.
This also solved mount efi yes however now efi no does not work. Seems system used more ram before i changed clover to detect xmp yes.

System boot seems a bit slow, spends some time on fsck. sys log showed crashes from dock mostly.

 

[chumdoggin]

Hello, hadn't figured the rc script part of the efi when doing a reinstall. From the last post about all works.

Boot seems to be a little long on fsck_hfs 15-20 secs. Not sure what it is but when the efi is mounted, disk utility finds it to have problems when checking disk. But not on the drive if the efi ejected. If its allowed to repair it, it deletes the data. As soon as there is data back on it, it finds problems again.

I found this patch but not sure how to apply it as the apply button is greyed out. https://github.com/RehabMan/OS-X-ACPI-Backlight/issues/7

 

[RehabMan]

Hello, hadn't figured the rc script part of the efi when doing a reinstall. From the last post about all works.

Boot seems to be a little long on fsck_hfs 15-20 secs. Not sure what it is but when the efi is mounted, disk utility finds it to have problems when checking disk. But not on the drive if the efi ejected. If its allowed to repair it, it deletes the data. As soon as there is data back on it, it finds problems again.

I'm not sure under what conditions the system does fsck... but not all the time. If you have a clean startup (not safe mode, not verbose) and have a clean shutdown, then you should boot without a fsck.

Disk Utility will find issues with the EFI partition if it is not in the first position, if it is too small, and perhaps a few other issues...

I found this patch but not sure how to apply it as the apply button is greyed out. https://github.com/RehabMan/OS-X-ACPI-Backlight/issues/7

That is a diff for the code in ACPIBacklight.kext. You don't need it for Mavericks.

 

[chumdoggin]

Thanks again. Added the install to the win drive pretty easily. Though kind of silly using an sata II drive on sata III.

 

[RehabMan]

Thanks again. Added the install to the win drive pretty easily. Though kind of silly using an sata II drive on sata III.

A single HDD doesn't come even remotely close to saturating a SATA 3GB/s connection. SATA2 is more than adequate for spinning platters.

 

[chumdoggin]

Ok..

Saw negotiated link speed on former install was 1.5mbs. Wondered if the original windows drive was going to be sata III since I saw it was supported. It is seeming a little faster on the now negotiated speed of 3gbs. It really is plenty fast.

Going to try an ssd anyway. I have yet to try ssd on anything. They have been out for quite some time now. Was reluctant when they were newer. Still costs a third of the price paid for the machine.

This will work in clover kext to patch ok for any machine?

<key>X</key>
<dict>
<key>Name</key>
<string>IOAHCIBlockStorage</string>
<key>Find</key>
<data>QVBQTEUgU1NE</data>
<key>Replace</key>
<data>AAAAAAAAAAAA</data>
</dict>

 

[RehabMan]

Ok..

Saw negotiated link speed on former install was 1.5mbs. Wondered if the original windows drive was going to be sata III since I saw it was supported. It is seeming a little faster on the now negotiated speed of 3gbs. It really is plenty fast.

Going to try an ssd anyway. I have yet to try ssd on anything. They have been out for quite some time now. Was reluctant when they were newer. Still costs a third of the price paid for the machine.

This will work in clover kext to patch ok for any machine?

<key>X</key>
<dict>
<key>Name</key>
<string>IOAHCIBlockStorage</string>
<key>Find</key>
<data>QVBQTEUgU1NE</data>
<key>Replace</key>
<data>AAAAAAAAAAAA</data>
</dict>

YMMV.

On my laptops, I've had no trouble patching for non-Apple SSDs (Crucial M4, Samsung EVO). But on my desktop (Mushkin Chonos Deluxe), enabling TRIM actually slows the boot time significantly. As a result I run without TRIM on my desktop.

 

[moonhack]

As of 10.9.4 everything is still working perfectly, save for one thing: now the battery status menu indicates "Service Battery". I know this is not true because this machine has been barely used and Windows, before and after battery calibration, indicates healthy battery status. Does anyone know what could be the cause? Maybe a Clover bug? Maybe 10.9.4 needs some new DSDT patch?

Thanks