Contribute
Register

[Guide] ASUS K501UQ - High Sierra

Status
Not open for further replies.
Stop and think carefully what you're doing.

Graphics patching are for model with dual GPU. You have only Intel GPU.
I thought that it was also a patch for the random wake reboots, I guess not. Would you know if any other solution? It seems that whenever I close the loo in sleep the laptop restarts on wake
 
I thought that it was also a patch for the random wake reboots, I guess not. Would you know if any other solution? It seems that whenever I close the loo in sleep the laptop restarts on wake

You disabled PluginType=1 and removed SSDT.aml. In doing that you disabled native power management. Set ACPI/SSDT/Generate/PluginType back to Yes or put back generated.
At least that is what I see in your latest report files.

If that doesn't help, try what I said above, about 'pmset -g log'. Start again with clean DSDT and write down what patches are you using (don't forget to backup, obviously). Finally, start another thread in support forum.

Also you didn't answer my question about EDID.

Some additional things. They won't solve your problem, just some optmizations.
Remove dart and kext-dev-mode from boot options. They do nothing. (of course, assuming you disabled Vt-d in bios, which you should have)
For the sake of clean config remove Devices/AddProperties entries, they disable Nvidia drivers, which you have no need to. Also you can check Clover boot log and remove DSDT patches that don't do anything.
Did you actually fill out SMBIOS data? You should use MBPro13,1 as it has closest CPU to yours; RehabMan's defaults in your config are a bit out of date.
 
Alright, I was messing around and sleep seems to be working now. Now I've got another issue. When I try to wake from sleep, sometimes the laptop just reboots itself. I tried following 'patching - graphics' instructions but they were too complicated for me. Can you explain what I have to do?

Your ioreg shows CPU PM not implemented.
See guide:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

Hint: config.plist/ACPI/SSDT/Generate/PluginType=true
 
You disabled PluginType=1 and removed SSDT.aml. In doing that you disabled native power management. Set ACPI/SSDT/Generate/PluginType back to Yes or put back generated.
At least that is what I see in your latest report files.

If that doesn't help, try what I said above, about 'pmset -g log'. Start again with clean DSDT and write down what patches are you using (don't forget to backup, obviously). Finally, start another thread in support forum.

Also you didn't answer my question about EDID.

Some additional things. They won't solve your problem, just some optmizations.
Remove dart and kext-dev-mode from boot options. They do nothing. (of course, assuming you disabled Vt-d in bios, which you should have)
For the sake of clean config remove Devices/AddProperties entries, they disable Nvidia drivers, which you have no need to. Also you can check Clover boot log and remove DSDT patches that don't do anything.
Did you actually fill out SMBIOS data? You should use MBPro13,1 as it has closest CPU to yours; RehabMan's defaults in your config are a bit out of date.


Your ioreg shows CPU PM not implemented.
See guide:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

Hint: config.plist/ACPI/SSDT/Generate/PluginType=true

Alright, so now I was able to successfully wake form sleep once, but sleep only seems to work 50/50. I don't know what's happening, if it works sometimes then is it an fixable error?
 

Attachments

  • debug_6553.zip
    1.8 MB · Views: 104
First, that patch is for my specific model. It can be modified for similar models, but obviously won't work without modification.

Second, you have different EC0 and ATKD in corresponding parts. Weirdly empty SLKB method, for one — it seems keyboard backlight is controlled by some other method. Can't help, sorry.

Try asking in dev thread for AsusNBFnKeys. I vaguely remember there were reports of problems with some ROG and/or newer models, so there might be no solution yet.

Also you can try and reverse engineer DSDT a bit. First you'll need to find out which _Q## method corresponds to keyboard backlight switch key — look at this guide for example. Then follow execution chain that's called from there. You'll end in some method that actually writes in EC0 registers (or whatever they're called). Copy those write commands into custom SKBL.

Also I'm not sure if kext will work at all, as Fn keys on my model call methods _Q09-_Q0F, and your uses _Q59-_Q74. Do other Fn keys work?
 
Yes my keyboard backlight is multicolored.
so, the link you gave might not be appropriate for me, right? Not sure if I can make the patch myself. I’m just an enthusiast. But thanks for your help, I’ll just to wait for a fix then.
That link contains instructions that will allow to see which DSDT methods correspond to Fn-keys. That's something only owner of your specific model could do.

Knowing which method gets called when you press Fn-↑ or Fn-↓ will allow to follow its execution chain down to writing commands into EC registers, i.e. actual commands that change keyboard backlight. That might be possible with just DSDT file (and probably some willing guinea pig). Unfortunately I a) can't promise I'd have ehough free time for you and b) am not the dev of this kext, which mean I could get into a dead end.

Still, if you could find some time and get those DSDT methods mapped, you can give that information to dev (google it) and hopefully he'll make compatible patch.
 
Thanks for this guide! Deciding to do hack or not)
How it works with battery after hackintoshing? How many hours on full charge?
And what about fan noise? Do you hear it often?
 
Thanks for this guide! Deciding to do hack or not)
How it works with battery after hackintoshing? How many hours on full charge?
And what about fan noise? Do you hear it often?
I didn't run any tests, and mostly work from AC power, but overall feeling is that battery drain is comparable to Windows.

Yeah, fan is a minor problem. Default EC controls switch it as soon as temperature passes 40°, so main problem isn't that it's loud (nVidia GPU is disabled, and CPU is quite cool, I managed to get it only to 52°), but that it keeps switching on and off. This could be solved by overriding default controls. Check this thread. I'll add it to the guide in a few days.
 
Status
Not open for further replies.
Back
Top