Contribute
Register

Buggy DSDT Asus Q501LA, help needed!

Status
Not open for further replies.
Joined
Dec 2, 2012
Messages
124
Motherboard
Huawei Matebook D 14
CPU
i5 8250U
Graphics
UHD 620
Hello people! :wave: I got the dump from my ACPI from Windows 8.1 but it was full of errors, so I tried Ubuntu instead. The problem is that I got 11 errors when I try to compile the DSDT extracted via Ubuntu :banghead::banghead: I'm completely lost 'cause I'm reading all over the Internet that there's a lot of buggy DSDT's coming from Asus. I need it fixed to get sound, keyboard backlight, card reader and full brightness screen to work! VodooHDA gives me kernel panic no matter what version I install...and I want to move to Clover.
Can anybody help me a little bit? :crazy:
I attach the files in case somebody could need them.
Thank you very much in advance and sorry for my english!

The Laptop:
[h=3]ASUS Q501LA-BBI5T03[/h]Intel i5 4200U
Intel HD4400
6Gb RAM

View attachment DSDT ASUS Q501LA 2.zip
 
Hello people! :wave: I got the dump from my ACPI from Windows 8.1 but it was full of errors, so I tried Ubuntu instead. The problem is that I got 11 errors when I try to compile the DSDT extracted via Ubuntu :banghead::banghead: I'm completely lost 'cause I'm reading all over the Internet that there's a lot of buggy DSDT's coming from Asus. I need it fixed to get sound, keyboard backlight, card reader and full brightness screen to work! VodooHDA gives me kernel panic no matter what version I install...and I want to move to Clover.
Can anybody help me a little bit? :crazy:
I attach the files in case somebody could need them.
Thank you very much in advance and sorry for my english!

The Laptop:
[h=3]ASUS Q501LA-BBI5T03[/h]Intel i5 4200U
Intel HD4400
6Gb RAM

View attachment 82742

The problem is not that the DSDT is buggy. The problem is you're not disassembling it correctly.

You need to disassemble it with iasl, giving iasl a chance to look at the related SSDTs as well as the DSDT:
Code:
iasl -e SSDT*.aml -d DSDT.aml

You will need a recent build of iasl: http://www.tonymacx86.com/attachmen...ell-inspiron-17-7000-hackintosh-able-iasl.zip

After that you will have only one error (make sure you're using ACPI 5.0).

The one error can be fixed with this patch:
Code:
into method label ADBG replace_content begin Return(0) end;
 
I was getting 2 errors, not just 1. Now just one... PARSEOP_LOCAL0.
When you say iasl do yo mean Maciasl?
I've checked that I select ACPI5.0, but I'm still getting an error
What do I do?

Read post #2 carefully. Your errors stem from improper disassembly. And no, when I wrote iasl, I actually meant 'iasl' exactly as I wrote.
 
Hi Rehabman and thanks for your patience!!
So, I went again into Ubuntu, and followed your steps to correctly dissemble the DSDT within iasl, and I'm getting the very same errors. I really didn't understand if you meant iasl within Mac or Ubuntu, because is out of my knowledge how to use iasl. But I think I managed to follow your commands within Ubuntu Terminal. At least it generated the files. Back into Mac, with the archives generated by Ubuntu and iasl, i get the same errors, 11 if I open the DSDT.dsl and just 2 if I open de DSDT.aml within Maciasl. Always acpi 5.0 in preferences.

After successfully patched my old DSDT for Desktop Gigabyte mobo, I'm just starting to think that I won't be able to make it. Could you be so kind to send me the error-free DSDT you got from my files?

And just another question, how do I know which SSDT from the 6 I got I have to keep?

Once I get a free-DSDT I will upload it so other can use it as a reference.

Thank you very much!
 
Hi Rehabman and thanks for your patience!!
So, I went again into Ubuntu, and followed your steps to correctly dissemble the DSDT within iasl, and I'm getting the very same errors. I really didn't understand if you meant iasl within Mac or Ubuntu, because is out of my knowledge how to use iasl.

Disassemble with the version of iasl I linked in OS X, not Ubuntu. After that, make sure you open the dsdt.dsl in MaciASL, not the dsdt.aml.

And just another question, how do I know which SSDT from the 6 I got I have to keep?

It depends on what you plan to do with the SSDTs... SSDT5.aml contains your graphics which you will probably end up patching to make brightness adjustment work. Same rule applies to it as to the DSDT. You must disassemble it correctly:
Code:
iasl -e DSDT.aml -d ssdt5.aml
 
Hi again Rehabman, and thank you for your help!
So now I got a error free DSDT, but when I try to patch let's say for example the Audio, I start to get errors again.

Now, forgeting about the DSDT issues, another problem arises.. and it's the fact that I cannot boot without Unibeast Install USB.

I've already tried to install chameleon to the EFI volume, but it seems my BIOS cannot detect GUID scheme, nor HFS format. I've tried to format the EFI volume in fat32, but no luck. Am I gonna be forced to use Clover? Will it solve the issue?

I guess is a problem of GUID vs MBR because the unibeast install USB has MBR, but my entire HDD (i don't plan to use any other OS) is in GUID.

Can someone give me some advice about this matter?
 
Hi again Rehabman, and thank you for your help!
So now I got a error free DSDT, but when I try to patch let's say for example the Audio, I start to get errors again.

Then your "patch" is causing the errors, or you again did not disassemble it correctly. Keep in mind you should always apply patches to the .dsl that you disassembled originally. Never open the resulting AML to apply additional patches.

Now, forgeting about the DSDT issues, another problem arises.. and it's the fact that I cannot boot without Unibeast Install USB.

I've already tried to install chameleon to the EFI volume, but it seems my BIOS cannot detect GUID scheme, nor HFS format. I've tried to format the EFI volume in fat32, but no luck. Am I gonna be forced to use Clover? Will it solve the issue?

Installing Chameleon requires the EFI volume to be HFS+. Normally it is FAT32.

You can use Clover for UEFI boot, but you can probably also get it to boot legacy. But BIOSes are quirky and it is sometimes difficult to discover what they actually require to successfully boot. Obvously, OEMs are only testing booting Windows. You should double check your work as far as bootloader on EFI:
- is the EFI partition active?
- is the /Extra folder present on the EFI partition
- is the EFI partition HFS+
- did you install boot0 to the MBR
- did you install boot1h to the PBR (EFI partition)

I'm using Clover lately and if you're tech savvy and have attention to detail, you should be able to get it to work.
 
I'll try to do all this once I get a fully functional system..and by the moment.. just 2 majors problems:

-No sound and disconnected usb devices after wake.
-No keyboard backlight (despite having AsusFNKeys installed and DSDT / SSDT patches applied)

And another thing... is it possible to get my Internal SD Card Reader to work? I've been researching and it seems that many people have issues with Realtek Card Reader Screen Shot 2014-02-11 at 11.59.50 PM.png
 
I'll try to do all this once I get a fully functional system..and by the moment.. just 2 majors problems:

-No sound and disconnected usb devices after wake.
-No keyboard backlight (despite having AsusFNKeys installed and DSDT / SSDT patches applied)
View attachment 83097

Do you mind to share your DSDT? thanks a lot!
 
Status
Not open for further replies.
Back
Top