Jump to content

bisk

Members
  • Posts

    73
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by bisk

  1. v208 came installed but is not offered as an upgrade via Asus support, interesting. Maciasl, that's what I figured. Yea, that app never let's me save anything either. It is handy to apply patches so I used to use Maciasl for that but then I'd copy all the text out of the editor, paste it into TextEdit and save it that way. Then compile. Finally got sick of that and just took to applying patches manually. I like to comment all changes anyway which autopatching will not do. But the keyboard backlight still won't work Hey, you are loading both the ElanSmartTouchPad AND this AsusFNKeys kext, right ?
  2. Hmmm, where do u get v208 ? I can't find anything beyond v207 out there. I said that your DSDT was original but not quite. Yours does have a PNLF (video backlight mod) so there was some success in modding there. What are u using to edit DSDTs ? I just use TextEdit. That lets u save anything. Then I compile from the command line with iasl <DSDT .dsl file name>. U need PWKB and BOFF with the K/B backlight patch or u will get undefined variable compile errors. Feel free to grab my DSDT above. It's heavily commented source. Just use FileMerge (XCode) to add what makes sense. U might just find that there are not much in the way of changes from v207-v208. Tell me where to find it and I will move to that version. In the mean time, I'll continue to look for it. U might just be able to compile and use mine but watch for Wifi card. The backlight patches won't work at all though. Our backlight read/set functions are different than all other Asus DSDT code that I have seen. We need a guru from this site who really understands Asus keyboard backlight to show us how to modify this patch. Good luck, lmk.
  3. Aloha all ! First, things first. Thanks for all the hard work that has gone into this project OK, I am really stuck trying to get my keyboard backlight working. I have an Asus Q500a which is an Ivy-Bridge laptop that should be just about the right age machine to still be supported by this kext. This is a simple HD4000 laptop with no dedicated video chip and I'm running Sierra 10.12.6. Here is a rundown of my FKey action with version 2.6 of the kext NOT loaded: FN+F1 sleep FN+F2 nothing (stock WiFi card was swapped out) FN+F3 nothing (keyboard backlight unaffected) FN+F4 nothing (keyboard backlight unaffected) FN+F5 nothing (video backlight unaffected) FN+F6 nothing (video backlight unaffected) FN+F7 nothing (video backlight unaffected) FN+F8 Display Scrambled ~ unrecoverable ! FN+F9 nothing (trackpad unaffected) FN+F10 nothing (audio unaffected) FN+F11 nothing (audio unaffected) FN+F12 nothing (audio unaffected) FN+F13 DVD eject w/animation FN+<numlock> audio mute toggle w/animation FN+<numpad5> audio mute toggle w/animation FN+<down arrow> launch iTunes and Here is a rundown of my FKey action with version 2.6 of the kext LOADED: FN+F1 sleep FN+F2 nothing (stock WiFi card was swapped out) FN+F3 nothing (keyboard backlight unaffected) FN+F4 nothing (keyboard backlight unaffected) FN+F5 video backlight brightness- w/animation FN+F6 video backlight brightness+ w/animation FN+F7 video backlight toggle off/on FN+F8 nothing FN+F9 trackpad toggle off/on FN+F10 audio mute toggle w/animation FN+F11 audio- w/animation FN+F12 audio+ w/animation FN+F13 DVD eject w/animation FN+<numlock> audio mute toggle w/animation FN+<numpad5> audio mute toggle w/animation FN+<down arrow> launch iTunes I should mention that I must have my DSDT perform a WIndows 2006 (Windows Vista) init for all of this to work. If I do either a Windows 2009 (Win7) or Windows 2012 (Win8) init then video brightness FKeys will not work whether the kext is loaded or not. Anyway, this is all cool except for the fact that I still have no keyboard backlight. I tried the 4 level and 16 level patches a couple of different ways and patched the _Q functions for the F3/F4 keyboard backlight keys too all with no effect. I require no patching in any of my other FKey _Q() methods for those FKeys to work. Once booted, my keyboard backlight does begin as illuminated but the FKeys have no effect on the level of brightness and the backlight shuts off with sleep and will not come back on after wake. In fact, it will not come back on again unless I boot into Windows first and then boot Mac again. Yes, I did try the _WAK patch from rehabman, no help. I have looked at a few other Ivy-Bridge laptop DSDTs and do notice a difference from mine. In all of the other DSDTs, In the SLKB() function I see a line of code like: ^^PCI0.LPCB.EC0.WRAM (0x044B, Local0) But in my SLKB() function, I have nothing like this. Here is mine: Method (SLKB, 1, NotSerialized) { And (Arg0, 0xFF, Local0) Store (Local0, KBLD) If (And (KBLD, 0x80)) { And (Local0, 0x7F, Local0) If (LEqual (Local0, Zero)) { ^^PCI0.LPCB.EC0.ECXT (0xB6, 0xFF, Zero, Zero, Zero, Zero) } If (LEqual (Local0, One)) { ^^PCI0.LPCB.EC0.ECXT (0xB6, 0xAA, Zero, Zero, Zero, Zero) } If (LEqual (Local0, 0x02)) { ^^PCI0.LPCB.EC0.ECXT (0xB6, 0x55, Zero, Zero, Zero, Zero) } If (LEqual (Local0, 0x03)) { ^^PCI0.LPCB.EC0.ECXT (0xB6, Zero, Zero, Zero, Zero, Zero) } } Else { ^^PCI0.LPCB.EC0.ECXT (0xB6, 0xFF, Zero, Zero, Zero, Zero) } Return (One) } Also, I get these syslog messages at boot: ApplePS2Keyboard: keyboard backlight is 0xea ApplePS2Keyboard: keyboard backlight is 0x1 ApplePS2Keyboard: keyboard backlight set to 0xed and now a bunch of these ... default 09:14:59.969870 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0x0 Plus I get AsusNBFnKeys.kext complaining that I have no ALSS method. default 09:12:07.827845 -1000 kernel AsusNBFnKeys: Cannot find the method ALSS. Which I do not as I doubt that this laptop has an ambient light sensor. I have attached my original and modified DSDTs + the config files of AsusNBFnKeys.kext, ApplePS2SmartTouchPad and and ApplePS2Keyboard in case I screwed up that part. I am running ApplePS2SmartTouchPad v4.68 (latest beta, I believe) Any help here would be so awesome ! For now, gonna try to hook my SLKB() into the SKBL() from the patch ... UPDATE >>>> Did try some hacking in my DSDT and just made things worse, lol ! When I insert a dummy ALSS method to suppress the warning, my display backlight continuously resets to about 1/4 illumination. I kick it back up to 100% and in a few seconds, it autosets back down kinda like when mom used to dim my bedroom lights in hope of having me finally go to sleep ! I also reset patches back to standard and so I see these warnings reprint about every 2-3 seconds ... default 11:40:21.472551 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0x1 default 11:40:21.473993 -1000 kernel ApplePS2Keyboard: Keyboard backight level set to 0xea default 11:40:22.889587 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0xed default 11:40:22.889650 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0x1 default 11:40:22.899270 -1000 kernel ApplePS2Keyboard: Keyboard backight level set to 0xea default 11:40:24.319724 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0xed default 11:40:24.319786 -1000 kernel ApplePS2Keyboard: Keyboard backight value from DSDT is 0x1 default 11:40:24.323492 -1000 kernel ApplePS2Keyboard: Keyboard backight level set to 0xea and of course ... default 11:41:27.624715 -1000 kernel AsusNBFnKeys: Cannot find the method ALSS. default 11:41:30.625484 -1000 kernel AsusNBFnKeys: Cannot find the method ALSS. default 11:41:33.626543 -1000 kernel AsusNBFnKeys: Cannot find the method ALSS. default 11:41:36.627543 -1000 kernel AsusNBFnKeys: Cannot find the method ALSS. HELP !!! Asus_Q500a.zip
  4. Aloha ! I have the same laptop as you. Did you say that your Fkeys are working fine ? Does your keyboard backlight work with Fn+F3 and Fn+F4 ? I can't get mine to work at all. What version of the BIOS do you have installed. I am on v207. I found no patches in your DSDT. I fixed the one compilation error, just search for "FIX:" and you'll find my mod. You do not have the variable "KBLV" in your DSDT, you have "KBLD" instead. You need to either change KBLV to KBLD in the patch or KBLD in your DSDT to KBLV, your choice. The PWKB variable is also from the K/B backlight patch just like KBLV. Only PWKB is actually defined in the patch. You must have included the part of the patch with the reference but left out the definition. Your 5th error is just a problem with scope, bad placement of the code. In any event, this patch was not at all in the DSDT which you attached here. This one looks to be an original/freshly extracted DSDT. Heck, the error that I just fixed would have prevented any of those others from even getting a chance to happen. Lmk if you need more help to compile. I've been hacking at this for some time and still no K/B backlight control. DSDT.Q500a.Chuck.dsl.zip
  5. Hi, This is not a touchpad issue, per se but, rather, is in the PS2Keyboard portion. But it's something that I am experiencing while using this kext so, here goes ... I am currently building out 2 systems to run 10.12.6 and this kext is doing the job on both just fine, including K/B backlight control. One is a Latitude E6540 and the other a Latitude E6420. Now both are exhibiting the exact same FKey behavior which is quite excellent except for: the video brightness- => Fn+F3 the video brightness+ => Fn+F15. I would like to move these functions to the up and down arrow keys. The keys with the blue brightness+/- icons on them. That's right next to the key that is already controlling the K/B backlight wonderfully. How do I best achieve this ? Thanks in advance
  6. Yep, I wonder if you even require the K/B backlight patch in your SSDT. Did you try your K/B backlight w/o it ? Yep, I don't think that there are any clover patches for K/B backlight, hence "hotpatching" is not really relevant here. Believe me, if I could find clover patches for the K/B backlight, I'd try 'em ! Hey, if you can compile my DSDT from the command line but not from a GUI tool, what does that tell you about the tool ? Lol ! It's not the number of warnings and remarks so much as types that matter. Unused vars are no biggie, right ? But what are u gonna do with my DSDT after you compile it anyway ? My ATKD.SKBL() and ATKD.GKBL() came from a well published patch by the author of this kext and are pretty much identical to yours and all others that I have seen. My DSDT does not have the "KBLV" variable, it has "KBLD" so I changed KBLV to KBLD in the patch code rather than rename KBLD throughout my DSDT to KBLV. That's pretty obvious if u inspect at my DSDT source. While I agree that every tool possible should be considered to hack these pcs, I would prefer not to lose sight of the importance of being as familiar as possible with the ins and outs of direct DSDT modding. I believe that this is still central to full success. Yes, I absolutely agree that figuring out the proper PCI0.LPCB.EC0.WRAM address seems key right now. Unfortunately, that thread proposes 2 addresses that I have already tried, the one that you use, for Haswell-based Asus and the other, for a Broadwell-based Asus. My Q500a is a generation older than yours, Ivy-bridge. So perhaps my secret door lies at yet another memory address. Might be time to do some snooping on the Windows side using RWEverthing or Aida64 ... Anyway, I have a few more tricks up my sleeve and so the hunt goes on. If I get the keyboard backlight then I will have a near perfect HackBook Pro. Sleep, SpeedStep, video acceleration, USB2, USB3, internal speakers, HDMI video and audio, WiFi, ethernet, all other FKeys, WebCam, sD card reader, etc. Just the microphone and K/B backlight remain. Thanks again for attention and good luck in your projects !
  7. Oh don't worry. Thanks for the effort. As I said, our K/B backlight patch is identical and you are not even patching the F3/F4 keys so this tells me that your Fn Keys are performing properly w.o. you even needing to fix them so how can you be expected to help me fix a problem that you have not experienced ? I know all about patching through Clover and often use it when needed for "on the fly" kext patching, etc. That's how I get my HDMI working for this rig amongst other things. I do, however, prefer to just simply keep as many fixes as possible within a single place, namely my main DSDT file. If you know of a Clover patch that can help get my K/B backlight popping then I'm definitely onboard with that. If it matters, send me the compiler errors that you are seeing and I'll help u. Or I can supply the compiled version for you to decompile. I just figured that you would prefer to see the comments to more easily follow the changes that I made to the original. There were quite a few. If you use Clover to patch your DSDT rather than edit and recompile it yourself then I would need to see your clover.plist as well. But if all that you are using are the prepackaged patches like DTGP, OSI, RTC. etc then don't bother, I do all of those directly. Can't compile ? Hmmm ... definitely compiles for me. Maybe it's a versioning problem ? No matter. It sounds like I am just wasting your time here. Thanks again !
  8. No problem. Thanks again. I downloaded your mods. Looking at your SSDTs, I can see you made the same K/B backlight mod that I have. Your FKey mods look to be for the LCD display backlight +/- rather than the K/B backlight +/- tho'. Do you do add'l mods in your main DSDT? I didn't see a DSDT in your files, only SSDTs. Perhaps you prefer to leave your DSDT untouched. If you modified your main DSDT, I would certainly like to see that as well. I don't usually touch SSDTs, I just modify the main DSDT. This site looks like it's still down for uploading so ... https://drive.google.com/drive/folders/16vjYtoqbCLBRZh3eMNXAokPF8HPpByIb?usp=sharing Has my original and modified DSDTs. Just search for "FIX:" and you will find all of my mods in DSDT.4. Lmk if anything jumps out at you. Thanks again
  9. Continuously getting: "The server returned an error during upload" for a 57K zipped .dsl file. I cannot attach a file !
  10. Aloha Zach, appreciate the response I have an Asus Q500a which is an Ivy bridge laptop. Looks like yours is a Haswell ... still worth a shot. I am very curious what you will come up with. My unmodified DSDT is attached so as not to influence your research. Could you also post your DSDT, with the keyboard backlight mods, if you had done any ? Did you do any DSDT mods to get your F3/F4 keys working ? Did you need the AsusNBFnKeys.kext ? Interestingly, the keyboard backlight patch file provided online by the talented author of this kext (EMlyDinEsh) is named for a Haswell/Ivy system but the notes within the mod file seem to indicate that it is good only for a Haswell system. I had incorporated both the 4 and 16 brightness level mods with no effect on my dead F3 and F4 keys Server keeps uploading my whole file and then I get : "The server returned an error during upload" for a 57K zipped .dsl file. I will try again later ...
  11. Hey, hey, thx again but this time looking through this thread does not really help. I've also consulted a much older thread specific to AsusNBFnKeys.kext. No help there either Seems as though I require some custom mods to my DSDT that I am missing and have no basis to add. I have already activated the K/B backlight options in the ApplePS2SmartTouchPad.kext, have the AsusNBFnKeys.kext installed AND have tried the basic DSDT mods for both 4 and 16 level K/B backlight brightness adjustments as advised. Thanks to AsusNBFnKeys.kext, I have all F keys working as they should with the exception of F3 and F4, K/B backlight+/-. My K/B backlight works initially when I boot up but then goes away with sleep and does not return after wake. The F3 and F4 keys never do anything and often, I need to boot into Windows before booting back into Mac just to get the backlight to initially illuminate again. Anybody with Asus K/B backlight success out there ? TIA
  12. Well, thank you. Not sure how that could have been any more obvious. I was sure lazy here. OK, I have most everything working the way I like it except for the keyboard backlight. The F3 & F4 keys do nothing. All of the other F keys for audio, video illumination, sleep, etc. all work fine. I have turned on the K/B backlight options in the config file, added the 16 level brightness patch in the DSDT, and do load AsusNBFnKeys.kext. I am seeing the AsusNBFnKeys error: "Cannot find method ALSS" while booting. Found the ALS patch but have no ALS device in my DSDT. I have an Asus Q500a. Anybody out there have K/B backlight control with this laptop ? I'm running 10.12.6. Thx !
  13. OK, so I figured out what kept making me change desktops ... setting VirtualMiddleButton to NO fixed that. But what controls the tap repeat sensitivity ? Mine is out of control. Where can the help on this extensive Info.plist be found ? S
  14. Aloha all ! I am having a really hard time with the 4.6.8 version of this kext. A single left click results in 10+ clicks and and some clicks toward the center of the trackpad change the desktop and oftentimes, just the slightest contact with the trackpad causes a click, sometimes not ! I find myself needing to use a mouse to get anything done. I have also tried the last production version with the same results. This behavior was sort of present on my Acer 5755 but manageable but on this Asus Q500a, it's a real killer. Is anybody else using this kext on an Asus Q500a and if so, could I see your Info.plist file ? TIA, bisk
  15. Oh sure thing shatterhenner, I assume that you are familiar with DSDT modding. If not, please go out and grab iasl and read docs on how to use it to compile/decompile DSDT files. Use the F4 feature of your clover boot manager to extract a raw version of your current DSDT. Decompile DSDT.aml with iasl -d and then search for the OS specific init function. It can go be many names depending on M/B. Could be _INI(), OSFG(), OSYS(), etc. You will see code like this ... Method (OSYS, 0, NotSerialized) { Store (0x10, Local0) If (CondRefOf (_OSI, Local1)) { If (_OSI ("Windows 2000")) { Store (0x12, Local0) } If (_OSI ("Windows 2001")) { Store (0x13, Local0) } If (_OSI ("Windows 2001 SP1")) { Store (0x13, Local0) } If (_OSI ("Windows 2001 SP2")) { Store (0x13, Local0) } If (_OSI ("Windows 2001.1")) { Store (0x14, Local0) } If (_OSI ("Windows 2001.1 SP1")) { Store (0x14, Local0) } If (_OSI ("Windows 2006")) { Store (0x15, Local0) } } Else { If (MCTH (_OS, "Microsoft Windows NT")) { Store (0x12, Local0) } Else { If (MCTH (_OS, "Microsoft WindowsME: Millennium Edition")) { Store (0x11, Local0) } If (MCTH (_OS, "Linux")) { Store (One, Local0) } } } Return (Local0) } The simplest thing is to change it to this: Method (OSYS, 0, NotSerialized) { Store (0x13, Local0) Return (Local0) } If you are a purest, you could go ahead and work in a block with: If (_OSI ("Darwin")) { Store (0x13, Local0) } but why bother since it's highly unlikely that this DSDT will be used for any other OS. Alternatively, there is supposed to be a clover config option to do this but I have had mixed results with that for other fixes so I tend to avoid clover "on the fly" patches. Hope this helps.
  16. Hey, turns out that I solved this one myself ! All I needed to do was to add a DSDT mod such that a "Windows 2001" style _INI() executes. Now this HackPro wakes from sleep properly every time AND no more intermittent black screens following the clover boot menu at startup. All is good So for all of you experiencing the reboot on wake thing, be sure to consider doing the "Windows Init" DSDT mod. Bye for now ...
  17. Aloha, I have an old series 4 board running 10.11.6. All is great except audio and a reboot on wake problem. It turns out that the ALC889A audio on my board exhibits a ghost/phantom codec which renders native AppleHDA mods ineffective so I simply use VoodooHDA and all is well on that front. However the reboot on wake problem persists ! This system sleeps with NO blinking power button light as if it is off. When I click the mouse or tap the K/B, it reboots instantly upon wake with NO desktop screen. This HackPro used to do a CMOS reset as well despite the DSDT RTC fix but that was remedied by installing a patched AppleRTC kext. Never used to need to do BOTH ! This is a Gigabyte GA-EG45M-UD2H motherboard with Core 2 Quad Q6600 overclocked from 2.4GHz to 3.0GHz. The BIOS is upgraded to the final F4 version and I am booting clover v2.3k r3998 defined as a MacPro3,1. I know that these Gigabyte boards always had reboot on wake tendencies but there was a DSDT fix that declared 2 new vars: SLPE and AG3E which were then used in the _PTS() and _WAK() fuctions to fix the problem. Unfortunately, what worked for SnowLeo/Lion/MountainLion does not seem to work for El Capitan Everything else works fine including SpeedStep but seemingly with only 2 speeds, 2GHz and 3Ghz. But my temps are super cool in the upper 30's-lower 40's C, never even reaching 45C. I'm hoping that there is a DSDT guru out there who can help me with this reboot on wake issue. Here is my hibernate settings info ... pmset -g Active Profiles: AC Power -1* Currently in use: hibernatemode 0 womp 1 networkoversleep 0 sleep 60 (sleep prevented by softwareupdate_notify_agent) Sleep On Power Button 1 ttyskeepawake 1 hibernatefile /var/vm/sleepimage autorestart 0 disksleep 10 displaysleep 20 Another strange behavior is that right after the clover boot menu, sometimes I get a blank display and system freeze instead of the verbose log screen. It may take 2 or 3 reboots until I finally get the line of: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ and the system log ... What causes this ? What exactly happens in between the clover boot menu and the screen dump ? Any help to point me in the right direction will be greatly appreciated. I enclose my DSDT, config.plist and ioreg. Thanks in advance ! HelpFiles.zip
  18. Aloha, I have a nearly perfect, vanilla HackBook Pro thanks mainly to this site and this guide ... https://osxlatitude.com/index.php?/topic/6372-dell-latitude-5x30-6x30-clover-install-guide/ However, one serious hurdle remains. This laptop will not recognize USB 3.0 drives reliably. It never sees them when first attached but sometimes after I sleep the unit and rewake it, they will then pop up along with a "not properly unmounted" message. I ended up using the GenericUSBXHCI.kext along with FakePCIID + USBMux kexts to get this far but I think that even the developer of these kexts believes that they are not appropriate for this native Intel USB3 chip as the stock AppleXHCI will load if I remove the Generics. However, then the system freezes permanently when a USB 3.0 device is attached. I should mention that USB 2. devices work just fine. This is all running Yosemite 10.10.5 on a Dell Latitude E6330 with BIOS A11. Heavy artefacts result with BIOS A12 and above on this one. Anybody out there have one of these on 10.10.5 with solid USB 3.0 ? Thanks in advance, bisk
  19. Ah, looking up my i5-2520m, it appears that I do have a vpro version. I'll try to adapt the video mods from that DSDT in your link, nonetheless, then report back. Thanks
  20. Great suggestion, Jake Lo. I did give this a whirl but not involving another HDD, What I did, was ... 1. mv GeForce* and NVDA* kexts out of SLE 2. Dropped NULLCPUPM.kext back into EE 3. Rebooted into setup and enabled Optimus 3. bypassed my dsdt at startup w/ DSDT=/nada and ... The notebook just reboots. I tried with both GraphicsEnabler= Yes && No If I boot -v, I see the initial kext paths loading fly by and then right when the screen would stabilize to begin showing the console, the notebook simply restarts. I'll try the usual -x, cpus=, etc. but this looks pretty bad right now ... not holding out too much hope here
  21. OK, I have your Alps touchpad kext installed on my E6420 running 10.8.5 and it's working great ! Click & drag, 2 finger scrolling, edge scrolling ... so far so good ! I'll drop this on the Inspiron 3520 when I see it next and let you know. I likey
  22. Hey npjohnson, Sorry for my absence. I actually do not have the Inspiron 3520 ATM but expect to see it again in another week or so. Now, I am actually doing a Latitude E6420 with NVidia video chip. I'll try your touchpad kext on it. Also, did anyone ever crack the sleep on the E6420+NVidia Quadro NVS 4200M ? I just need sleep and the touchpad and I'm pretty much there thanks to the SDHC kext that you provided in another place.
  23. Hey bmp152, I'm with the kext you posted. It's not so bad but then I don't use this Inspiron 3520 notebook all that much anymore and it might be going in the next few days. That'll take me out of the beta testing pool, unfortunately
  24. Let me revise my previous post. I tried some more 3 finger gestures and the vast majority of the time it either does absolutely nothing or causes scrolling (probably a finger slips a bit ?). However, every once in a great while I do hear a little error funk tone. It's kinda rare tho'. Maybe this helps ?
  25. Hey npjohnson, My system does not beep. I'm not sure what you mean by "does 3 finger fire off". I am a very simple user and do nothing unusual other than 2 finger scrolling. Basically, If I can click, grab, drag and 2 finger scroll reliably, I'm happy.
×
×
  • Create New...