Yung Fatso Chow

My kext is not working well with some newer models from Asus. So, I'll have to debug and modify the code again. Right now, I'm busy with touchpad driver for Elan and doing all this in little spare time. So, I'll look into this as soon as possible.

Okay. Get the touchpad working first, as I think that is more useful.  I'm in the process of installing Windows so I can grab the DSDT and other info for you from Windows...

Yes, but with the extracted and untouched dsdt we will find this untill we compile it for errors. That's why I meant this. I'll correct this with explanation.

I was suggesting that you could just code it so that it would be case-insensitive.  From even my novice view/experience, there are minor errors throughout the ASUS Zenbook (and maybe other models') DSDTs, and I doubt they are going to fix it.

 

But I figured most people would have corrected their DSDT anyway because I don't know of any Asus laptops that work OOTB without some DSDT changes  

 

I'm installing it now and will let you know what works, what doesn't in a few!

 

EDIT (after install with Kext Wizard and rebuilt cache/permissions, then reboot):

Fn+F1: SleepFn+F2: WiFi/BT Fn+F7: BacklightFn+F8: Screen goes dark, then comes back onScroll Lock (external keyboard) (Fn irrelevant): Brightness Down (16 Values) With Animation Pause/Break (Fn irrelevant): Brightness Up (16 Values) With Animation

This seems to what would happen with or without the kext.  I checked with terminal:

kextstat | grep Asus

and did not see it listed/loaded.

 

Could it be because I'm using these Voodoo PS2 kexts? 

 

   33    0 0xffffff7f81ef2000 0x3000     0x3000     com.yourcompany.driver.AppleACPIPS2Nub (1.0.0d1) <9 7 5 4 3 1>

   39    2 0xffffff7f80804000 0x11000    0x11000    org.voodoo.driver.PS2Controller (1.1.0) <9 7 5 4 3 1>

   58    0 0xffffff7f8081b000 0x3000     0x3000     org.voodoo.driver.PS2Keyboard (1.1.0) <39 34 7 6 5 4 3 1>

   59    0 0xffffff7f80815000 0x3000     0x3000     org.voodoo.driver.PS2Mouse (1.2.0) <39 34 7 6 5 4 3 1>

 

If so, what should I replace them with?

 

My DSDT (again, I'm using the one patched for UX31A, where they added stuff to try and make keyboard work without any additional kexts) is enclosed.

DSDT-cyf.aml.zip

If you ever update this, please note that according to ACPI spec, the HID including PNP device names should be in capitals.  E.g. "PNP0c14" = "PNP0C14"

 

So maybe make it case-insensitive?

Hi All, i just want to confirm the command for REBRANDING BROADCOM,

 

Update the sprom – Open up a terminal window and execute the following commands:

 

==================

ssb-sprom -i ssb_sprom_copy –subv 0xaaaa –subp 0xbbbb –regrev 0×0001 –ccode US -o new_ssb_sprom_copy

==================

 

the aaaa, bbbb, is the product id an vendor id i should put base on the guide right ?

 

thanks all

 

Yes, I just did this, and the guide should be upgraded because it doesn't have the two dashes ("-") in front of the subv, subp, regrev, and ccode options, and it helps a lot to see that the "aaaa" and "bbbb" is where the vendor ("0xaaaa" without the quotes) and the product ("0xbbbb" without the quotes) IDs should go. I note that the aaaa and dddd should be in lower-case.

 

For example, for my BCM94312HMG (Dell DW1397 802.11bg, I used this:

 

ssb-sprom -i ssb_sprom_copy --subv 0x106B --subp 0x004e --regrev 0×0001 --ccode US -o new_ssb_sprom_copy

Hi, Have a Zenbook UX21A and have sent my DSDT AND other related files to your e-mail. Hope to hear from you soon!

 

EDIT: I forgot to mention--although I did so in my e-mail, that I am using DSDT patched from UX31A but it's not working perfect. I sent you both my original and the incomplete patched version. You can choose to start fresh or not.