Contribute
Register

MSI GF62VR 7RF with Sierra 10.12.6

Status
Not open for further replies.
goldenegg said:
I followed the laptop backlight control guide and until I reached to customization. I don't know where and how to modify the PWMMax.
https://www.tonymacx86.com/threads/...rol-using-applebacklightinjector-kext.218222/

Attache files.
Click to expand...

No customization of PWMMax (LMAX) needed.
The defaults in SSDT-PNLF.aml are already correct for your ig-platform-id choice.

Your config.plist does not have the required AppleBacklight patch (you have it in KernelToPatch instead of KextsToPatch... it is not a patch for the kernel).
And you don't want to use that config.plist anyway (it is for Skylake spoof, not KabyLake native).
 
Thanks. Brightness is working.

RehabMan said:
And you don't want to use that config.plist anyway (it is for Skylake spoof, not KabyLake native).
Click to expand...
I don't know which one you mean? If you mean the config.plist in efi that I used (config_HD615_620_630_640_650_spoof.plist) That one only worked for me instead of (config_HD615_620_630_640_650.plist).

Another thing is How can I configure the FN button keyboard to control the brightness? or Is it from keyboard type in Mac?
 
goldenegg said:
Thanks. Brightness is working.


I don't know which one you mean? If you mean the config.plist in efi that I used (config_HD615_620_630_640_650_spoof.plist) That one only worked for me instead of (config_HD615_620_630_640_650.plist).
Click to expand...

Sierra 10.12.6 (and later) has native support for KabyLake graphics/CPU, so Skylake spoofing is not needed.

Another thing is How can I configure the FN button keyboard to control the brightness? or Is it from keyboard type in Mac?
Click to expand...

Read brightness guide linked from the FAQ (it covers mapping the brightness keys from ACPI):
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
 
RehabMan said:
Sierra 10.12.6 (and later) has native support for KabyLake graphics/CPU, so Skylake spoofing is not needed.
Click to expand...
Maybe you are right. I was trying to install 10.12.2 in this thread
https://www.tonymacx86.com/threads/...ng-overrides-for-iabootfiles-boot-efi.236154/


Here what I did for brightness control:
- downloaded ioio and copied it to usr/bin
- install ACPIDebug.kext: https://github.com/RehabMan/OS-X-ACPI-Debug
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot
The question is how can I determine if they are handled by PS2 or ACPI?
Where can I find monitor system.log with Console.app?
 
goldenegg said:
Maybe you are right. I was trying to install 10.12.2 in this thread
https://www.tonymacx86.com/threads/...ng-overrides-for-iabootfiles-boot-efi.236154/


Here what I did for brightness control:
- downloaded ioio and copied it to usr/bin
- install ACPIDebug.kext: https://github.com/RehabMan/OS-X-ACPI-Debug
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot
The question is how can I determine if they are handled by PS2 or ACPI?
Where can I find monitor system.log with Console.app?
Click to expand...

Why 10.12.2? Current version is 10.12.6. Or 10.13.2.
No KabyLake native support in 10.12.2.

Most new computers use ACPI for brightness controls (the ProBook/EliteBook/Zbook from HP seem to be an exception).
In Sierra, kernel logs are not in system.log.
Read here:
https://www.tonymacx86.com/threads/readme-common-some-unsolved-problems-in-10-12-sierra.202316/
 
RehabMan said:
Why 10.12.2? Current version is 10.12.6. Or 10.13.2.
No KabyLake native support in 10.12.2.

Most new computers use ACPI for brightness controls (the ProBook/EliteBook/Zbook from HP seem to be an exception).
In Sierra, kernel logs are not in system.log.
Read here:
https://www.tonymacx86.com/threads/readme-common-some-unsolved-problems-in-10-12-sierra.202316/
Click to expand...
I meant I was trying in the thread given with 10.12.2 and I got no success reaching the installer. and the current version is 10.12.6.


I will determine it as ACPI because mine in new laptop.
 
After typing this command:-
log show --predicate "processID == 0" --debug
it shows long log
here is part of it
2017-12-16 01:54:30.827647+0300 0x2b10 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 exit"

2017-12-16 01:54:30.827764+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e077=80 down

2017-12-16 01:54:31.633811+0300 0x2b10 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB8 enter"

2017-12-16 01:54:31.634527+0300 0x18c Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB8 exit"

2017-12-16 01:54:31.634672+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e078=80 down

2017-12-16 01:54:32.033627+0300 0x2bf2 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 enter"

2017-12-16 01:54:32.034164+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e077=80 down

2017-12-16 01:54:32.034416+0300 0x18c Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 exit"
Does it mean that they are handled by P2S?



Also attached files I am not if I have to go walk through creating ssdt for usbInjectall.kext. Ioreg shows that I have HSO03,HSO4,HS08 working and when I plug usb in HSO3 it says usb accessory needs power.
 

Attachments

  • test2.zip
    2.3 MB · Views: 75
goldenegg said:
After typing this command:-
log show --predicate "processID == 0" --debug
it shows long log
here is part of it
2017-12-16 01:54:30.827647+0300 0x2b10 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 exit"

2017-12-16 01:54:30.827764+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e077=80 down

2017-12-16 01:54:31.633811+0300 0x2b10 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB8 enter"

2017-12-16 01:54:31.634527+0300 0x18c Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB8 exit"

2017-12-16 01:54:31.634672+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e078=80 down

2017-12-16 01:54:32.033627+0300 0x2bf2 Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 enter"

2017-12-16 01:54:32.034164+0300 0x18e Default 0x0 0 kernel: (kernel) ApplePS2Keyboard: sending key e077=80 down

2017-12-16 01:54:32.034416+0300 0x18c Default 0x0 0 kernel: (ACPIDebug) ACPIDebug: "EC _QB7 exit"
Does it mean that they are handled by P2S?
Click to expand...

Possibly both ACPI and PS2.
e077 and e078 are standard brightness down/up for LG laptops.
As noted in ApplePS2ToADBMap.h:
Code: 
#ifndef PROBOOK
    BRIGHTNESS_DOWN,    // e0 77 lg down
    BRIGHTNESS_UP,      // e0 78 lg up
#else
    DEADKEY,// e0 77
    DEADKEY,// e0 78 WiFi on/off button on HP ProBook
#endif

But your logs also show EC query methods being called.
You should pay attention to which logs happen as you're pressing the keys.

Also attached files I am not if I have to go walk through creating ssdt for usbInjectall.kext. Ioreg shows that I have HSO03,HSO4,HS08 working and when I plug usb in HSO3 it says usb accessory needs power.
Click to expand...

USB guide:
https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/
 
Ok.
here what happens I hit these buttons:-
Up button e048=7e
Down button e050=7d
fn+up= Ec _QB8 enter e078=80
fn+down= EC _QB7 exit e077=80
Fn = 75=80
-------------
Where should I do the patching now ? The guide not explaining where to do the patch. (in the Q10 and Q11 example)
Also do I have to do the editing through info.plist?
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top