Lenovo IdeaPad U310

[XMYUKON]

So far, so good, i make everything function and now with Ivy Power Management (from x12 to x18, not bad). I finally apply the (not so elegant) patch for Cx 20590.

The sleep issues disappear as soon as i delete the GenericUSCXHCI and AppleUSBXHCI, and USBs still function. The U310 works great with just the patches from Rehabman's repository. The patches are listed in post #202 but ill paste here what i have applied and my actual DSDT.

- IRQ FIX
- RTC FIX
- Brightness fix
- 7 Series USB (Curiosly when you apply the 7 or 6 there is no difference)
- SMBus fix
- IGPU Rename
- HD4000 Low Resolution
- Battery Fix Ux10-Z580
- Insert DTGP (Sourceforge)
- Apple HDA patch (October 2012, Cx 20590, sounds good on earphones, not so good with speakers)

Im only using 3 Kext at this time, AppleHDA, AppleACPIBatteryManager and Multibeast AppleIntelCPUPowerManagement 10.8.5.

Everything runs fine.

Lots of thanks for your patience Rehabman.

You also need rehabman's trackpad kext to make it work and the keyboard.

You got sleep and usb 3.0 to work though? Where did you get the patch for audio?

What patch is this? Cx 20590

- - - Updated - - -

At Terminal, type 'man diskutil' and study the result. You can also do 'man diskutil >~/Desktop/diskutil_manual.txt', then open it in TextEdit. Looks like 'diskutil partitionDisk' can create multiple partitions.

OK. I will try this

 

[RehabMan]

So far, so good, i make everything function and now with Ivy Power Management (from x12 to x18, not bad). I finally apply the (not so elegant) patch for Cx 20590.

You can probably get x8, but first you must be sure that your CPU supports it. See this post: http://www.tonymacx86.com/ssdt/91551-appleintelcpupowermanagementinfo-kext-msrdumper-successor.html

Once you discover if your CPU can support it, see here: http://www.tonymacx86.com/ssdt/86906-ssdt-generation-script-ivybridge-pm.html. Download the script then modify it so the LFM is 800.

The sleep issues disappear as soon as i delete the GenericUSCXHCI and AppleUSBXHCI, and USBs still function.

That's a nice work around for now. What it does is disable USB3 and all are treated as USB2.

- Insert DTGP (Sourceforge)
- Apple HDA patch (October 2012, Cx 20590, sounds good on earphones, not so good with speakers)

You can do without the Insert DTGP if you use my version of the audio patch (modify it for your audio data).

Im only using 3 Kext at this time, AppleHDA, AppleACPIBatteryManager and Multibeast AppleIntelCPUPowerManagement 10.8.5.

Everything runs fine.

That's great and very good to have a clean system running with your own DSDT. One thing... you could use my latest battery manager instead: https://github.com/RehabMan/OS-X-ACPI-Battery-Driver. The one you're using is a bit old.

Nice work!

 

[RehabMan]

You also need rehabman's trackpad kext to make it work and the keyboard.

+1 Especially if you have a Synaptics trackpad...

 

[XMYUKON]

You can probably get x8, but first you must be sure that your CPU supports it. See this post: http://www.tonymacx86.com/ssdt/91551-appleintelcpupowermanagementinfo-kext-msrdumper-successor.html

Once you discover if your CPU can support it, see here: http://www.tonymacx86.com/ssdt/86906-ssdt-generation-script-ivybridge-pm.html. Download the script then modify it so the LFM is 800.



That's a nice work around for now. What it does is disable USB3 and all are treated as USB2.



You can do without the Insert DTGP if you use my version of the audio patch (modify it for your audio data).



That's great and very good to have a clean system running with your own DSDT. One thing... you could use my latest battery manager instead: https://github.com/RehabMan/OS-X-ACPI-Battery-Driver. The one you're using is a bit old.

Nice work!

I think I am going to give it another go. I have gotten this far so I want to use a clean DSDT. Three questions:

If I find out that my CPU supports "x8" (not sure what that means" do I just run that script?

You say to modify your patch for my audio data. What does this entail? Can I see something g inside ikkoku's DSDT for this data? My audio works with his dsdt but like I said earlier the slider won't move if I use keyboard buttons (level changes though, if I go to mute only then do you see the change with the slider from the hardware sound buttons)

Which of your patches will enable sleep do you believe?

 

[XMYUKON]

Also, I wonder if fusion drive works on the U310 touch. If so I will not even install windows.

 

[RehabMan]

I think I am going to give it another go. I have gotten this far so I want to use a clean DSDT. Three questions:

If I find out that my CPU supports "x8" (not sure what that means" do I just run that script?

The SSDT is generated by a shell script. If you find out your CPU supports LFM at x8 (you need to follow the instructions for using AppleIntelCPUPowerManagementInfo.kext first), then you can modify the script to support 800 as LFM for your CPU (if you open the code for the script, and search for your own CPU, you'll discover the table that contains data for each known CPU).

Note: the script copies the result to /Extra/ssdt_pr.aml. To use it, you will need to rename it to /Extra/ssdt.aml.

You say to modify your patch for my audio data. What does this entail? Can I see something g inside ikkoku's DSDT for this data? My audio works with his dsdt but like I said earlier the slider won't move if I use keyboard buttons (level changes though, if I go to mute only then do you see the change with the slider from the hardware sound buttons)

I added "Audio Layout 12 (advanced)" to the patch repo. Hopefully that helps...

Which of your patches will enable sleep do you believe?

I'm not sure. Sleep has a lot of moving parts...

 

[Jos1984]

Hi again, Thx for everything Rehabman, i used the new kext that you brought to me and everything looks fine, except that now the USB can be used for a mouse but not for Pendrives formatted in FAT, HFS+ its ok. The Pendrive it's being detected in Disk Utility, but it cannot be mounted. I think this is a problem with my Unibeast USB instalation.

You can probably get x8, but first you must be sure that your CPU supports it. See this post:AppleIntelCPUPowerManagementInfo.kext (MSRDumper successor)

Once you discover if your CPU can support it, see here: SSDT generation script (Ivybridge PM). Download the script then modify it so the LFM is 800.

Here it's what AppleIntelCPUPowerManagementInfo.kext, dump into system.log

Oct 11 18:20:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 18:20:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 18:20:20 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 18:20:23 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 18:20:36 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 16 17 18 ]
Oct 11 18:20:36 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 18:29:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 18:29:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 18:30:03 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 ]
Oct 11 18:30:03 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 18:30:31 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 17 18 ]
Oct 11 19:04:24 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 19:04:26 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 19:04:29 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 19:04:29 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 16 17 18 ]
Oct 11 19:04:30 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 21:29:05 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:29:07 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 21:29:09 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 21:29:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 17 18 ]
Oct 11 21:29:32 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 21:49:06 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 21:49:06 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:53:19 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 21:53:19 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:53:26 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 9 17 ]

I understand that the i3-3217U it's capable to down to 8x, but when i changes the values in the SSD generator from this...

i3-3217U,17,0,1800,0,2,4

to this...

i3-3217U,17,800,1800,0,2,4

I suffer a KP... why? Any idea? Try another smbios or values?

I'll send you my SSDT. Maybe you can see something strange?

Thx.

I'll try to configure your Sound Patch

 

[RehabMan]

Hi again, Thx for everything Rehabman, i used the new kext that you brought to me and everything looks fine, except that now the USB can be used for a mouse but not for Pendrives formatted in FAT, HFS+ its ok. The Pendrive it's being detected in Disk Utility, but it cannot be mounted. I think this is a problem with my Unibeast USB instalation.



Here it's what AppleIntelCPUPowerManagementInfo.kext, dump into system.log

Oct 11 18:20:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 18:20:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 18:20:20 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 18:20:23 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 18:20:36 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 16 17 18 ]
Oct 11 18:20:36 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 18:29:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 18:29:58 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 18:30:03 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 ]
Oct 11 18:30:03 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 18:30:31 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 17 18 ]
Oct 11 19:04:24 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 19:04:26 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 19:04:29 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 19:04:29 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 16 17 18 ]
Oct 11 19:04:30 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 21:29:05 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:29:07 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 18 ]
Oct 11 21:29:09 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 17 18 ]
Oct 11 21:29:14 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 17 18 ]
Oct 11 21:29:32 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 12 13 16 17 18 ]
Oct 11 21:49:06 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 21:49:06 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:53:19 localhost kernel[0]: AICPUPMI: CPU P-States [ 17 ]
Oct 11 21:53:19 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 17 ]
Oct 11 21:53:26 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 9 17 ]

That wasn't really what you were looking for. You were looking for the startup output from the kext where it prints various information about your CPU. But...

You're already getting x8 (you said previously you were only getting x12), so no need to do anything...

Or maybe you were not getting x86platformplugin loading before, so were not getting Ivy PM???

What was the SSDT you were using before? Can you post it as well?

FYI: There seems to be an issue with this script and i3 CPUs (or, more generally, CPUs without any turbo states).

 

[Jos1984]

That wasn't really what you were looking for. You were looking for the startup output from the kext where it prints various information about your CPU. But...

You're already getting x8 (you said previously you were only getting x12), so no need to do anything...

Or maybe you were not getting x86platformplugin loading before, so were not getting Ivy PM???

What was the SSDT you were using before? Can you post it as well?

FYI: There seems to be an issue with this script and i3 CPUs (or, more generally, CPUs without any turbo states).

Of course, ill give you the x12 SSDT and a IOregister log. I see that X86 platform is loaded, but i repeat that with this SSDT i can only go down to x12, but i3 is x8 capable.

EDIT: the SSDT Script says that i3 have 10 p-states, but i only see [8 12 13 16 17 18], those are 6 p-states, or im missing something??

Any work around for this problem?

 

[RehabMan]

Of course, ill give you the x12 SSDT and a IOregister log. I see that X86 platform is loaded, but i repeat that with this SSDT i can only go down to x12, but i3 is x8 capable.

According to the log above, you're getting x8. (I assume with the SSDT generated from the ProBook Installer?)

EDIT: the SSDT Script says that i3 have 10 p-states, but i only see [8 12 13 16 17 18], those are 6 p-states, or im missing something??

That is normal. You won't necessarily hit all the states in between. It depends on what OS X decides to use.

FYI: Your ioreg dump is corrupt. Please be sure you're using the correct version of IORegistryExplorer.