Contribute
Register

OSX El Capitan 10.11.6 on Samsung Galaxy Book 12

Status
Not open for further replies.
axel9546 said:
Okay i just tried that and Brightness is working, also no internet connection (cause i think i need driver for that)
Audio and brightness was working.
I have installed ACPIDebug kext as u can see in the later Report.zip, so i have just to apply
Code: 
To use it you must install the two components that make up the software.  First of all, you must patch your DSDT to add the RMDT (RehabMan Debug Trace) device.  The presence of this device allows the kext to load.  Apply the debug.txt patch via MaciASL.  You can also add this repo as a MaciASL "source" in MaciASL preferences: http://raw.github.com/RehabMan/OS-X-ACPI-Debug/master.
This patch, but i cannot find the patch when i go in MaciAsl, patch section, cant find this one

PS: Would this be that we need to create a new Kext for OLED screens (hackintosh), for the future XD ??
Click to expand...

You have to add the ACPIDebug repo to MaciASL->Preferences->Sources.
Keep in mind using ACPIDebug involves coding.
 
RehabMan said:
You have to add the ACPIDebug repo to MaciASL->Preferences->Sources.
Keep in mind using ACPIDebug involves coding.
Click to expand...
Added the repo but i cannot find the patch
I dont ever coded nothing in my lifw, but i would like to solve this problems
 
axel9546 said:
Added the repo but i cannot find the patch
I dont ever coded nothing in my lifw, but i would like to solve this problems
Click to expand...

It sounds like you didn't add the correct URL.
Impossible to help unless you post some screen shots to show what you're doing.
 

Attachments

  • Screen Shot 2017-10-20 at 18.38.04.png
    Screen Shot 2017-10-20 at 18.38.04.png
    814.7 KB · Views: 192
RehabMan said:
You should see this in Patch:
View attachment 287130
Click to expand...
Attached a screen
Also would like to know, why when i save the SSDT-XOSI and reboot, i got this
Code: 
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20161210-64(RM)
* Copyright (c) 2000 - 2016 Intel Corporation
*
* Disassembling to non-symbolic legacy ASL operators
*
* Disassembly of iASLK8ZaIY.aml, Fri Oct 20 18:48:12 2017
*
* Original Table Header:
*     Signature        "SSDT"
*     Length           0x000000BE (190)
*     Revision         0x02
*     Checksum         0xC9
*     OEM ID           "hack"
*     OEM Table ID     "XOSI"
*     OEM Revision     0x00000000 (0)
*     Compiler ID      "INTL"
*     Compiler Version 0x20161210 (538317328)
*/
DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    Method (XOSI, 1, NotSerialized)
    {
        Store (Package (0x09)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }, Local0)
        Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}
Still the code good? Why it changes alone??
 

Attachments

  • Screen Shot 2017-10-20 at 18.49.16.png
    Screen Shot 2017-10-20 at 18.49.16.png
    464.1 KB · Views: 106
axel9546 said:
Attached a screen
Click to expand...

It is not showing.
Probably you have a trailing space in the URL.

axel9546 said:
Also would like to know, why when i save the SSDT-XOSI and reboot, i got this
Code: 
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20161210-64(RM)
* Copyright (c) 2000 - 2016 Intel Corporation
*
* Disassembling to non-symbolic legacy ASL operators
*
* Disassembly of iASLK8ZaIY.aml, Fri Oct 20 18:48:12 2017
*
* Original Table Header:
*     Signature        "SSDT"
*     Length           0x000000BE (190)
*     Revision         0x02
*     Checksum         0xC9
*     OEM ID           "hack"
*     OEM Table ID     "XOSI"
*     OEM Revision     0x00000000 (0)
*     Compiler ID      "INTL"
*     Compiler Version 0x20161210 (538317328)
*/
DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    Method (XOSI, 1, NotSerialized)
    {
        Store (Package (0x09)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }, Local0)
        Return (LNotEqual (Ones, Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}
Still the code good? Why it changes alone??
Click to expand...

You should not expect compiled+disassembled code to be the same as the source code.
If you look at both the source and the the disassembled version, you will find they are equivalent logic.
 
RehabMan said:
It is not showing.
Probably you have a trailing space in the URL.



You should not expect compiled+disassembled code to be the same as the source code.
If you look at both the source and the the disassembled version, you will find they are equivalent logic.
Click to expand...
Okay sorry but i would like to understand thoose things like whn i read a book and there are words that i can understand xD!
How could be hard write a kext for OLED hackintoshes, for the future?
I saw another hackintsh with OLED screen (Alienware 13 something), and he also have no brightness adjustment
https://www.******.com/r/hackintosh/comments/5rty98/my_alienware_13_r3_with_sierra_10122/
 
axel9546 said:
Okay sorry but i would like to understand thoose things like whn i read a book and there are words that i can understand xD!
How could be hard write a kext for OLED hackintoshes, for the future?
I saw another hackintsh with OLED screen (Alienware 13 something), and he also have no brightness adjustment
https://www.******.com/r/hackintosh/comments/5rty98/my_alienware_13_r3_with_sierra_10122/
Click to expand...

You would need to get some information on how the brightness is controlled.
Then you could write code that manipulates the hardware directly just as I did with IntelBacklight.kext.
Unfortunately, the IntelBacklight.kext and ACPIBacklight.kext mechanisms are not working in 10.12.4+.
But that doesn't stop them being used on up to 10.12.3
Of course, if you knew how to manipulate the backlight hardware directly, you could also do so from ACPI via ACPIBacklight.kext.
 
RehabMan said:
You would need to get some information on how the brightness is controlled.
Then you could write code that manipulates the hardware directly just as I did with IntelBacklight.kext.
Unfortunately, the IntelBacklight.kext and ACPIBacklight.kext mechanisms are not working in 10.12.4+.
But that doesn't stop them being used on up to 10.12.3
Of course, if you knew how to manipulate the backlight hardware directly, you could also do so from ACPI via ACPIBacklight.kext.
Click to expand...
Sorry but i dont know how to do that
Funny fact : i calibrated the screen with a colorimeter with the software 1display pro.
At the end when i had to save it and apply, my brightness was set to 120 (pleasure for my eyes) and all colors now are also calibrated.
Still i cant change brightness.
Why the software could apply Brightness and other utility as Brightness by berg dont work?
 
Last edited:
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top