Contribute
Register

Asus Zenbook UX330UA

Status
Not open for further replies.
Here it is in the attachment. this is the correct way, using Clover F4 ACPI to extract the dsl.

You don't even have the correct set of files in ACPI/patched.
Based on ACPI/origin there should be in ACPI/patched:
DSDT.aml
SSDT.aml (ssdtPRgen.sh)
SSDT-0.aml
SSDT-1.aml
SSDT-2.aml
SSDT-3.aml
SSDT-11.aml
SSDT-12.aml
 
You don't even have the correct set of files in ACPI/patched.
Based on ACPI/origin there should be in ACPI/patched:
DSDT.aml
SSDT.aml (ssdtPRgen.sh)
SSDT-0.aml
SSDT-1.aml
SSDT-2.aml
SSDT-3.aml
SSDT-11.aml
SSDT-12.aml

because i had renamed all the SSDT in ACPI/patched, i´ve attached the zip file again with the corrected names.

I tested the disassembly with your list of SSDTs...
with SSDT-2.aml it gives me that error:
ACPI Error: [_UPC] Namespace lookup failure, AE_ALREADY_EXISTS (20161117/dswload-462)
ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20161117/psobject-310)

so i removed SSDT-2.aml from disassembly? but why should be in the ACPI/patched according to your list?

what about SSDT-13.aml? should be in disassembly? why you did not include SSDT-13.aml in your ACPI/patched list?
 

Attachments

  • AML to DSL.zip
    262.7 KB · Views: 105
  • ASUS UX330 2.zip
    2.5 MB · Views: 105
Last edited:
because i had renamed all the SSDT in ACPI/patched, i´ve attached the zip file again with the corrected names.

I tested the disassembly with your list of SSDTs...
with SSDT-2.aml it gives me that error:
ACPI Error: [_UPC] Namespace lookup failure, AE_ALREADY_EXISTS (20161117/dswload-462)
ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20161117/psobject-310)

so i removed SSDT-2.aml from disassembly? but why should be in the ACPI/patched according to your list?

what about SSDT-13.aml? should be in disassembly? why you did not include SSDT-13.aml in your ACPI/patched list?

I missed SSDT-13 when I did the copy/paste. Of course it should be included.
SSDT-2.aml is optional. You can try with/without (it requires no patches).
The ioreg shows WiFi working.
Your battery method BAT0._STA is reporting "no battery present" (_STA shows as 0x0f, should be 0x1f for battery present).
If you look at the code, you see it depends on the value of BATP in a SystemMemory region, GNVS.
And if you look at that SystemMemory region address, you find that you ACPI/patched is different from ACPI/origin:
ACPI/origin/DSDT.aml
Code:
    OperationRegion (GNVS, SystemMemory, 0x9AD97000, 0x06B3)

ACPI/patched/DSDT.aml
Code:
    OperationRegion (GNVS, SystemMemory, 0x9AD98000, 0x06B3)

So, your issues probably stem from your ACPI/patched not being in sync with ACPI/origin.
 
I missed SSDT-13 when I did the copy/paste. Of course it should be included.
SSDT-2.aml is optional. You can try with/without (it requires no patches).
The ioreg shows WiFi working.
Your battery method BAT0._STA is reporting "no battery present" (_STA shows as 0x0f, should be 0x1f for battery present).
If you look at the code, you see it depends on the value of BATP in a SystemMemory region, GNVS.
And if you look at that SystemMemory region address, you find that you ACPI/patched is different from ACPI/origin:
ACPI/origin/DSDT.aml
Code:
    OperationRegion (GNVS, SystemMemory, 0x9AD97000, 0x06B3)

ACPI/patched/DSDT.aml
Code:
    OperationRegion (GNVS, SystemMemory, 0x9AD98000, 0x06B3)

So, your issues probably stem from your ACPI/patched not being in sync with ACPI/origin.

ok thank you for that.
so i will correct the BAT0._STA to 0x1f.

and should i correct the OperationRegion like the ACPI/origin/DSDT.aml?
 
ok thank you for that.
so i will correct the BAT0._STA to 0x1f.

No need to correct any code in BAT0._STA.
The code there is correct.

and should i correct the OperationRegion like the ACPI/origin/DSDT.aml?

Don't correct it... re-patch based on current extract.
You must re-extact, re-patch after:
- any hardware change
- any BIOS option change
- any BIOS update
 
No need to correct any code in BAT0._STA.
The code there is correct.



Don't correct it... re-patch based on current extract.
You must re-extact, re-patch after:
- any hardware change
- any BIOS option change
- any BIOS update

hy again,
i have re-extracted and re-patched everything, and have got a prohibit sign and a kernel panic with a glitch that i cannot read. i´ve try lots of ways: with your Recommended patches, without some of them, a dsdt clean without errors, and the same result, KP. this time the ASUS N55/vivobook patch did not gave me any BTIX error.

i've tested with and without SSDT.aml because i´m a kaby lake, and since is not official supported it could be from there, but no, same prohibit sign with a glitch that i cannot read.

here´s the process in attach. i did not create the ioregister because i booted using USB installer.

i don't know code but i know is something i´m doing wrong.

i've seen other user with the UX330 and with DSDT patched ok, i´ve seen his SSDT´s clover origin but they are different than mine. he also try later the hot patches method.

could you please take a look at my zip file and try fix my DSDT.

thank you
 

Attachments

  • ux330.zip
    4.7 MB · Views: 116
Last edited:
hy again,
i have re-extracted and re-patched everything, and have got a prohibit sign and a kernel panic with a glitch that i cannot read. i´ve try lots of ways: with your Recommended patches, without some of them, a dsdt clean without errors, and the same result, KP. this time the ASUS N55/vivobook patch did not gave me any BTIX error.

here´s the process in attach. i did not create the ioregister because i booted using USB installer.

i don't know code but i know is something i´m doing wrong.

i've seen other user with the UX330 and with DSDT patched ok, i´ve seen his SSDT´s clover origin but they are different than mine. he also try later the hot patches method.

could you please take a look at my zip file and try fix my DSDT.

thank you

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
here it is in the attachment. thanks you

No photo of the KP is provided. Read "Problem Reporting" again. Carefully.
 
Status
Not open for further replies.
Back
Top