stonevil / Razer_Blade_Advanced_early_2019_Hackintosh

Razer Blade Advanced early 2019 Hackintosh. Guide and EFI
126 stars 16 forks source link

Can't get brightness level to persist after reboot #20

Open ghost opened 5 years ago

ghost commented 5 years ago

Followed the instructions to replace this:

Device (ALSD)
{
    Name (_HID, "ACPI0008")  // _HID: Hardware ID
    Method (_STA, 0, NotSerialized)  // _STA: Status
    {
        If (LEqual (ALSE, 0x02))
        {
            Return (0x0B)
        }

        Return (Zero)
    }

    Method (_ALI, 0, NotSerialized)  // _ALI: Ambient Light Illuminance
    {
        Return (Or (ShiftLeft (LHIH, 0x08), LLOW))
    }

    Name (_ALR, Package (0x05)  // _ALR: Ambient Light Response
    {
        Package (0x02)
        {
            0x46, 
            Zero
        }, 

        Package (0x02)
        {
            0x49, 
            0x0A
        }, 

        Package (0x02)
        {
            0x55, 
            0x50
        }, 

        Package (0x02)
        {
            0x64, 
            0x012C
        }, 

        Package (0x02)
        {
            0x96, 
            0x03E8
        }
    })
}

With this:

Device (_SB.ALS0)
{
    Name (_HID, "ACPI0008")  // _HID: Hardware ID
    Name (_CID, "smc-als")  // _STA: Status
    Name (_ALI, 300)  // _ALI: Ambient Light Illuminance
    Name (_ALR, Package ()  // _ALR: Ambient Light Response
    {
        Package () { 100, 300 },
    })
}

Compiled without issues. Saved DSDT.aml and put in the /E/C/A/P. Restarted several times and brightness level resets every time to max.

Anyone have this working?

k-sym commented 5 years ago

Ditto. Thinking its an NVRAM issue, but tested that to death too, to no avail... NVRAM persists and checking it (along with other key value pairs) is definitely setting the brightness setting, however afer reboot, the setting is back to max (backlight-level {%ff)

ghost commented 5 years ago

Ok, thanks for confirming. It isn't a huge issue, but would be nice if it persisted.

soerenkampschroer commented 4 years ago

Update your kexts, I'm not sure which one it was but it persists for me after updating everything today. You can use Kext Updater to check and download the latest versions.

If you update the BrcmPatchRam kexts and use the DW1560 you'll now have to install these three kexts: BrcmBluetoothInjector.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext. Make sure to uninstall all other Brcm* kexts you have.

Cheers!

stonevil commented 4 years ago

Sorry, have no access to RBA to test any staff. I will try to update remotely RBA to Catalina this weekend and will update documentation regarding new finding.