Is mine functional from the files you got already?EmuVariable only optional if you know your native NVRAM is functional.
Requires testing native NVRAM...
So? Remember, I'm not a coder. (thank you for the explanations though, I'm doing my best to understand them as a designer Does it mean 100% or anything else? At least we can continue what the problem is with my backlight level. If it's 100%, then whatever I set is not registering. If it's 30-40% then system is not reading that config file or plist on the next boot or resets it on boot. If it's anything than the 2 I just said, then the data it gets not connected to what I set or what system sets (100%).It corresponds to backlight level 0x00f7 (it is byte reversed in the data, aka Intel byte order).
I didn't set DropOem=true through Clover, Do you think this might be the issue? Also Should I place all SSDTs to patched folder even the ones I haven't patched or just the patched ones are enough like I did? (I have all of them in Clover/ACPI/Original folder anyway)Finally, keep in mind you cannot provide patched SSDTs without dropping the OEM SSDTs that they replace. The easiest way is to use DropSSDT=Yes (Chameleon) or ACPI/SSDT/DropOem=true (Clover) to drop all the SSDTs, then provide the patched (and unpatched) files for loading by the bootloader.
Is mine functional from the files you got already?
So? Remember, I'm not a coder. (thank you for the explanations though, I'm doing my best to understand them as a designer Does it mean 100% or anything else?
In that case, what should we do next?
I didn't set DropOem=true through Clover, Do you think this might be the issue? Also Should I place all SSDTs to patched folder even the ones I haven't patched or just the patched ones are enough like I did? (I have all of them in Clover/ACPI/Original folder anyway)
Finally brightness is working, but i didn't change DropOEM from "false" to "true". When i do that (DropOem=true), after loading screen, i see a black screen and there is nothing i can do.
I'll post my files here, if you wanna take a look. Is everything ok?
I've just learned how to rename GFX0 to IGPU using Clover hotpatch. Didn't know that is only a patch for DSDT. To patch SSDT i have to use Maciasl patching option?
First you should verify NVRAM is working.
Then troubleshoot from there.
If you haven't looked at your native NVRAM contents (use the UEFI shell), then it is probably time to do that also...
UEFI Shell:
Mapping table:
FS0: Alias(s): HD0a65535a:;BLK1:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,...
FS4: Alias(s): HD0a65535a:;BLK6:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,...
FS1: Alias(s): HD0a65535a:;BLK2:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,...
FS2: Alias(s): HD0a65535a:;BLK3:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,...
FS3: Alias(s): HD0a65535a:;BLK4:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,...
BLK0: Alias(s): HD0a65535a:;BLK1:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)
BLK5: Alias(s): HD0a65535a:;BLK1:
PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)
Seems like NVRAM is working. nvram.plist back-light value changes on everyboot.
I don't know if they mean anything to you but neither "sudo nvram -p" nor "nvram -p" commands work in Shell UEFI.Code:UEFI Shell: Mapping table: FS0: Alias(s): HD0a65535a:;BLK1: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,... FS4: Alias(s): HD0a65535a:;BLK6: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,... FS1: Alias(s): HD0a65535a:;BLK2: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,... FS2: Alias(s): HD0a65535a:;BLK3: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,... FS3: Alias(s): HD0a65535a:;BLK4: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1.GPT,... BLK0: Alias(s): HD0a65535a:;BLK1: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0) BLK5: Alias(s): HD0a65535a:;BLK1: PCIRoot (0x0)/PCi(0xF1,0x2)/Sata(0x0,0xFFFF,0x0)
You know what I realized? It's native NVRAM! Because whenever I restarted or turn on the laptop, backlight screams, ASUS logo bright as hell, then Clover boot screen and Apple Loading logo are the same. And you know what? I can change the brightness level in Shell UEFI screen with Fn+F5 and F6 (default Asus brightness keys).
What is your suggestion at this level? I already deleted EmuVariableUefi-64.efi and tried, rebuilt cache, upgrade Clover with the same settings (to install EmuVariableUefi-64.efi and RC Scripts) nothing happened.