Jump to content

nmindz

Members
  • Content Count

    8
  • Joined

  • Last visited

Everything posted by nmindz

  1. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    I tried Ukelele after you mentioned it but it didn't "fit my needs". I was able to easily remap two of the swapped keys, but the quotes one was a no-go (it was not being recognized in the keyboard layout.). Then I went into VoodooPS2Keyboard.kext's Info.plist and checked TimeWalker's implementation of the WN09 profile. Turns out he had remapped those three keys there inside, probably to match the XPS/Vostro layout he described in the comment key. Mine didn't need such remap, so I removed it: ... <key>Custom PS2 Map</key> <array> <string>56=2b</string> <string>29=56</string> <string>2b=29</string> <string>e01e=e037</string> <string>e037=e01e</string> </array> </dict> Removing the "56=2b", "29=56" and "2b=29" lines, saving to the .kext and rebuilding kextcache completely solved all issues. Can't believe I've got all my keyboard functions working perfect. Now I'm just missing effective power management and battery status (after OS X 10.11 Beta 2, VoodooBattery.kext no longer works.) for a fully functional hackintosh. Didn't test HDMI audio/video but if I remember back then when I had Mavericks, it worked fine. Thanks for your priceless help, RehabMan... and also to all the others who've contributed to the projects I'm currently using.
  2. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    AFAIK it's not a system keyboard layout issue (as there is only two keyboard layouts which hold the "Ç" key without having to combine ' + C, which are Brazilian ABNT and Brazilian ABNT2). Both have this key swapping issue. I'd rather believe it's due to to the "exotic" layout Dell has put up in this keyboard. Looking at their picture in Sysprefs > Keyboard > Input Sources, I can clearly see that my backslash, close quotes and forward slash keys are the only that fall outside the key layouts (they are within the blank key icons.). The funny thing is that forward slash works fine. Therefore it does makes sense that it has got messed up. I'll have a go trying to remap those. Thanks again. Keep up the excellent work man!
  3. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    I had no clue you could select a VoodooPS2 profile through the DSDT nor how to do it. The FN keys were completely solved (including wifi toggle and brightness), but some stuff got mixed in and are kinda messy. Well for some reason ever since I've been using OS X in this laptop, the "windows key" (which should be "Command") is actually ALT while ALT itself is Command. After the DSDT patch three keys were swapped. Quotes became backslash, close braces became quotes and backslash became close braces. The ALT/Command swap is still the same as usual. Anyway, thank you so much for your work on the PS2 driver and for your help sorting this out. I think I could remap the keys myself through Info.plist inside the VoodooPS2, am I correct? If so, is there any good source about doing it? Thanks!!!
  4. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    If by "native" you mean the non-patched one, which I dumped from Linux, here it is: /* * Intel ACPI Component Architecture * AML Disassembler version 20100331 * * Disassembly of iASL9aFYGv.aml, Mon Aug 24 00:49:48 2015 * * * Original Table Header: * Signature "DSDT" * Length 0x0000AB28 (43816) * Revision 0x02 * Checksum 0xB0 * OEM ID "DELL" * OEM Table ID "WN09" * OEM Revision 0x00000022 (34) * Compiler ID "INTL" * Compiler Version 0x20051117 (537202967) */ DefinitionBlock ("iASL9aFYGv.aml", "DSDT", 2, "DELL", "WN09", 0x00000022) { ... } If you want to take a look at the whole thing, it is attached. Thanks! DSDT_original.aml.zip
  5. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    That's right, Sir.
  6. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    With this I realized that I didn't had a clue whether my keys were ACPI or PS2 controlled. While I tried to realize which was the case, I found this (please correct me if that's the wrong method.): From here. I recognize that those are your own instructions even though the guy who posted it didn't seem to link the work to it's man. After running "ioio -s ApplePS2Keyboard LogScanCodes 1", I went to the Console.app and filtered by "ApplePS2Keyboard", where I found the following output: Aug 23 00:21:20 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 3b=7a down // F1 Aug 23 00:21:22 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 3c=78 down // F2 Aug 23 00:21:24 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 3d=63 down // F3 Aug 23 00:21:25 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 3e=76 down // F4 Aug 23 00:21:27 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 3f=60 down // F5 Aug 23 00:21:29 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 40=61 down // F6 Aug 23 00:21:30 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 41=62 down // F7 Aug 23 00:21:32 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 42=64 down // F8 Aug 23 00:21:33 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 43=65 down // F9 Aug 23 00:21:35 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 44=6d down // F10 Aug 23 00:21:36 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 57=67 down // F11 Aug 23 00:21:44 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key 58=6f down // F12 Aug 23 00:21:48 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e020=4a down // Mute Sound, next key after F12 - it's a multimedia-only key // FN+F1 didn't output anything // FN+F2 Couldn't be tried as it would kill my WiFi (the OFF effect always works the *1st* time, then I can't turn it on) Aug 23 00:24:40 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e01e=80 down // FN+F3 Aug 23 00:22:14 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e005=91 down // FN+F4 - Brightness Down // FN+F5 - Brightness Up, which didn't 'work' after the previous combo was pressed // FN+F6 - no function assigned (no orange icon) // FN+F7 - no function assigned (no orange icon) Aug 23 00:27:43 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e010=4d down // FN+F8 Aug 23 00:27:44 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e022=34 down // FN+F9 Aug 23 00:27:45 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e019=42 down // FN+F10 Aug 23 00:27:47 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e02e=49 down // FN+F11 Aug 23 00:27:48 Evandros-MacBook-Air kernel[0]: ApplePS2Keyboard: sending key e030=48 down // FN+F12 So I guess my keys are PS2 controlled. Thanks in advance. PS: A note on the "sending key e005=91 down // FN+F4" line. A few hours ago I did press "FN+F5" which is "Brightness Up", setting my brightness to max level. Just afterwards neither of brightness controls seemed to work. (as I already expected.) Just now as I write this and had this debugging phase ongoing, I forgot the effects of "FN+F4" (which would usually render my screen completely black). It didn't - the brightness splash icon and slider appeared on the screen - but they still showed "max" and didn't decrease this time. Right after I tried "FN+F5" which seemed to have no effect and to output nothing to the console as well. It seems that some weird looping is going on once it first enters the GPE _L17 method/area. Like if further keydowns won't trigger the method anymore as it is still running, not until the loop ends, at least. Not to mention that it seems the "method" stores the data from the first loop and all further calls will just set the previous values. Really don't know what else to try.
  7. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    I'm using your VoodooPS2Controller.kext.
  8. nmindz

    GUIDE: How to Fix Brightness hotkeys in DSDT

    Thanks to RehabMan, Toleda and a tons of people whose names I can't remember (I've been reading a lot of InsanelyMac and others for the past few months.) I've got myself running a decent a usable daily driver hackintosh on my Dell Inspiron 14z 5423 (Ultrabookish version, i7 3rd gen model.). 1) Syspref > Displays has a working brightness slider. 2) However the Fn+F5 (Brightness Increase) and Fn+F4 (Brightness Decrease) shows odd behavior. Each boot, they will work once. If I Press Fn+F5 it will MAX (no stepping.) my LCD brightness. Further Fn+F5 or Fn+F4 keystrokes do nothing. If I rather press Fn+F4 it will decrease my brightness to ZERO w/o any stepping either (plain dark, impossible to see anything at all.) which often causes me to boot the system from power off button. After the key combo has been first pressed, Fn+F5 won't work either. When I tried to patch my DSDT with "Instrument EC Queries" I realized I've got no "_Q##" methods at all. I then checked the next patch below it and the "Instrument GPE Queries" had something in store (matches and patches.) so I applied it. Installed ACPIDebug.kext to S/L/E and booted. Now, every time I do the key combo it gives me the output of "GPE _L17". But as others have mentioned above, it seems that _L17 is a shared method because both Fn+F5 and Fn+F4 will call the same method. Nevertheless, I identified another 2 buttons (!!) which will invoke the same method (_L17), those are the "W"-like button (sometimes referred to as "Wave") and the Dell-custom button to set your own hotkeys in Windows, which are located in the upper-right area of the top cover (Silver buttons. The "gears" button has no output in Console.app.). (See attached "silver-button.jpg" image.) Anyone has any idea of what I should do/look for next? If anyone thinks this deserves a new thread (if it feels like any sort of 'hijacking'.) please just PM me and I'll copy/paste this into a new thread and delete this message. Reason I thought of leaving this attached to this thread is just for further reference of fellow 14Z 5423 owners which might have a hard time finding this stuff later. Attached are a photo of the whole keyboard "layout", the custom Dell keys which share the _L17 method and my original (extracted from Linux.) DSDT.aml (DSDT_notfixed.aml) and the one I'm currently booting with ("DSDT_current.aml"). Also a kextstat output with any custom .kexts I'm loading other than Apple's default/AppleHDA patched. If any more info is to be provided, let me know. Thanks a lot to anyone willing to help me and look into this. DSDT.zip kextstat.txt
×