Search results

I just experienced this, for some reason when I did this the first time I did not run into any usb issues after sleep, but I guess maybe I was not running the usb related kext that I using now. I should probably try rebooting without it and see how it goes. I assume I patched everything in my...

I did patch my own and it does work better. I probably need to start over however and upgrade my BIOS as well.

@pgh550 it would be ideal if you could go back and update your original post with the current DSDT that works with 10.11.6 (if you are using that). I know Sierra is about to come up and we'll all want to be on that, I personally don't care to be on the beta cycle of OSX. The DSDT that is...

People actually read threads starting from page 1? :P

Ah I see the connection now with OSI... "If (LGreaterEqual (\_SB.OSID (), 0x20))" It is comparing OSID values to 0x20, anything that is equal to or greater should be good. WIN7, WIN8 and WN81 should certainly be that as they have values of 0x80. Previously I should have instrumented SMEE...

I did attempt to force SMIE by moving it from the expected If statement (14), looking for Local0 to equal 0x080 I believe, to the 10th if statement looking for 0x800. It had no effect, even though my SMIE has been instrumented none of it was triggered, it is like something crashes that method...

That's the log from 10.10.5. The kexts of course are little different and so would the config.plist. I'll try and setup a usb drive with 10.11 for more testing when I can find the time. I don't like swapping out these ssd drives and I use this setup as an actual workhorse, it has been that...

That may be, but I am back on Yosemite here and it is working just fine with the old BAT1 info in the DSDT. That doesn't really bother me much, its the brightness controls, the lack of wifi after sleep that is now apparent, and the lack of bluetooth in El Capitan. All things that were more...

Method (SMEE, 1, NotSerialized) { Store (Arg0, Local0) Store (GENS (0x11, Zero, Zero), Local0) If (LGreaterEqual (\_SB.OSID (), 0x20)) { If (And (Local0, 0x04)) { EV5 (One, Zero) //Brightness up...

On my system the brightness keys were not working at all until I did this. The OS still does not report that the brightness settings are being triggered, but the OEM backlight I guess works. I think I am about to bow out and go back to Yosemite for now... I hate that, but between this issue and...

Concur, enabling Legacy resolved this for me. I already added the fix in the config.plist so I am not sure if I need it at all now, but it did not have any affect until I enabled legacy boot.

I figured out our issue. Enable Legacy boot in your BIOS, I am willing to bet it is not enabled. I had given up on it for the time being and decided to fix the garbled mess that was my load screen. It was easy to work around (go to sleep and then wake back up), so I did not fix it earlier. It...

This is what I have tracked the issue down to Method (ECR2, 1, NotSerialized) { \RMDT.P2 ("ECR2 enter Arg0", Arg0) Store (ECR1 (Arg0), Local0) \RMDT.P2 ("ECR2 new Local0 from ECR1", Local0) Increment (Arg0)...

Ok I just tried that and the same issues persists. Nothing has changed in the log read out.

Sorry, should have mentioned that I returned zero on the STA method inside BAT1, that completely resolved the issue. But yes I will try relocating Darwin to Win8 and I will report back.

I've taken it as far as I know how to take it and instrumented all that appears to be relevant... but I guess I am missing something. Just to be clear, this is what reads out in the console when I press either brightness up or down...

EDIT: Should have read a few comments back, Rehabman has already provided the info I needed, the OSI OS names were mucking part of it up. I can now instrument the rest. I went ahead and tried instrumenting this thing while I am in here and I at a loss atm. The brightness keys generate ACPI...

Well it is really odd, I thought I had fixed the brightness issue and then I started to re-apply patches to the original A05 DSDT to find that a manual fix has to be added to remove BAT1 (STA must return 0) from showing up in ioreg. Once that happens the brightness controls no longer dim back...

If the same DSDT patch that worked for Yosemite is supposed to work for El Capitan then it is broken for this specific model laptop. I applied the patch myself to A05 and remapped the keys appropriately while others did not bother because it went deeper than what most guides went into. Also the...

I just upgraded from Yosemite and as far as I know the brightness fix is actually broken in El Capitan, why others are not reporting this I am not sure. The key mapping was never fixed, but I did fix that in Yosemite and made a post about it. It looks like that is broken once again though, and I...