Jump to content

Anjan Tek

Members
  • Content Count

    36
  • Joined

  • Last visited

About Anjan Tek

  • Rank
    InsanelyMac Protégé
  1. Oh, that is great! Could you please post your DSDT here, so I can compare the differences between what you and I have?
  2. Hey, thanks! Sorry for the late response. That backlight kext gives me a working backlight slider for me too. But the keyboard control doesn't work. I have tried following RehabMan's guide to "patching-dsdt-ssdt-for-laptop-backlight-control" on the other forum. It has a section dedicated to get the brightness keys work. But I am not able to follow that because the brightness keys do not generate any PS2 codes for me. The other keys generate PS2 keys which I can see in the system.log, but not the brightness keys. If @RehabMan is around, maybe he can help. Battery I still have a functional battery. But the battery status does not change after booting into Mac. Even adapter detection doesn't work. Very annoying. Again, I tried to follow RehabMan's "how-to-patch-dsdt-for-working-battery-status" on the other forum. But the "EmbeddedControl" which he asks us to find in the DSDT is not even present in our DSDT! It would REALLY help to have the battery status work. Right now, I am always on tenterhooks, guessing how much battery is left by keeping track of time. Some help, please?
  3. On El Capitan (10.11.x), do the brightness controls on the laptop keyboard work for anybody? It hasn't been working for me since Yosemite. Does anyone know how to solve it?
  4. I have the XPS M1530. The VoodooHDA that worked for me is attached. The VoodooHDA which I got from fusion71au's package worked for me, but there was a noticeable static in the audio. The kext I have attached works without producing any static. Archive.zip
  5. I have an XPS M1530 with the T9300 processor and GeForce 8600M GT GPU. I had Mavericks running without problems. Performance was not an issue at all. Everything was zippy. A couple of days back, I followed the instructions in post #1715 and installed a fresh copy of Yosemite (10.10.3). Everything went smooth and I am fully up and running (using Clover). But one thing that has become extremely obvious is that the computer has become unmistakably slower. Just switching between spaces takes a couple of seconds. Mission Control lags like crazy. Even switching between apps in the same space takes long. Dragging windows around is very choppy, moving in frames and creates artefacts on the screen. All this points to graphics issues. But I am not sure how to troubleshoot or solve this. Any ideas would be appreciated. I am attaching Clover's config.plist for your reference. $ kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) <Linked Against> 14 4 0xffffff7f82717000 0xb000 0xb000 org.netkas.FakeSMC (3.3.1) <11 7 5 4 3> 15 0 0xffffff7f82722000 0xd000 0xd000 org.kozlek.GeforceSensor (1.0.2d1) <14 12 7 5 4 3> 16 0 0xffffff7f82733000 0x2000 0x2000 org.slice.PC8739x (1) <14 7 5 4 3> 25 0 0xffffff7f8270a000 0x8000 0x8000 org.rehabman.driver.AppleSmartBatteryManager (1.50) <11 4 3> 26 0 0xffffff7f82736000 0x3000 0x3000 org.slice.HWInfo (1) <14 7 4 3> 27 0 0xffffff7f8273a000 0x6000 0x6000 org.slice.IntelCPUMonitor (1.1) <14 7 5 4 3> 35 0 0xffffff7f82741000 0xa000 0xa000 org.voodoo.driver.PS2Controller (1.1.0) <11 7 5 4 3 1> 42 0 0xffffff7f8274b000 0x4000 0x4000 org.voodoo.driver.PS2Keyboard (1.1.0) <38 5 4 3> 43 0 0xffffff7f825f8000 0x2000 0x2000 net.osrom.kext.Disabler (1.0.1) <4 3> 51 0 0xffffff7f8274f000 0xd000 0xd000 org.voodoo.driver.PS2Trackpad (1.1.0) <38 5 4 3> 66 0 0xffffff7f80b6b000 0x48000 0x48000 at.obdev.nke.LittleSnitch (4240) <5 4 3 1> 83 0 0xffffff7f80df1000 0x7000 0x7000 VoodooSDHC (1.1d1) <19 12 5 4 3> 90 0 0xffffff7f80eb5000 0x21000 0x21000 org.voodoo.driver.VoodooHDA (2.8.7) <89 12 7 5 4 3> I would really appreciate some help, because my machine is pretty much unusable at the moment. UPDATE: It turned out to be a widely reported issue with Yosemite - the WindowServer process using up very high CPU. My WindowServer process was constantly at 70+%. That was what was bringing my machine to a crawl. I tried a lot of combination of fixes. At the moment, it seems to be solved after "Reducing Transparency" from the Accessibility settings in System Preferences. I tried a lot of things, including installing the nvidia web drivers. I have now uninstalled them. config.plist.zip
  6. I have an XPS M1530 and I have been using OS X trouble free since 10.5 . I had installed Mavericks sometime when it released last year and was on 10.9.2 for a looong time, without any problems (this thread is usually my source of info - I am using the DSDT from the first post). Last week, I decided to upgrade to 10.9.5 . I used the combo update. Everything went fine. But ever since then, my computer has been extremely sluggish. It takes a solid 2m30s+ to boot. And after typing the password on the login screen, it takes another 30s just for the desktop to appear (before it even starts loading the startup items). That's the general pattern. Everything is slow. There is heavy HDD access throughout the boot process and login / startup. The HDD light doesn't even flicker, it is just ON. I have seen the verbose boot and I don't see anything very obvious slowing it down. Although, I have noticed that the filesystem check runs almost on every boot ("almost" being the keyword). It must be some updated kext(s) which is causing this. Could anybody give me some ideas on how to troubleshoot this?
  7. @luggi - Just to clarify: Are you saying that you are not using the DSDT_M1530_NVIDIA_ANYCPU_20111029.zip posted by immo, but using a modified version to support the external monitor? Then Chimera is not to blame?
  8. I mean the latter. The laptop screen + an external monitor connected via an HDMI-to-DVI cable. Very similar to luggi's screenshot in Post 964. Yeah, then I guess it has something to do with Chimera. Let me try Chameleon version that you have. What exactly do you mean when you say "Graphics Injection from DSDT_M1530_NVIDIA_ANYCPU_20111029.zip"? I thought that DSDT did not inject anything related to graphics.
  9. Regarding the DSDT without the NVIDIA graphics injection (DSDT_M1530_NVIDIA_ANYCPU_20111029.zip), I can confirm that a dual-monitor setup does NOT work with this DSDT. I have tested this extensively. And I have seen that the second monitor (connected via an HDMI-to-DVI cable) does not get detected when using this DSDT. The same behavior is observed when using the DSDT from post 963 too. The second monitor DOES get detected when using the DSDT from October 23 (DSDT_M1530_NVIDIA_ANYCPU_20111023.zip) and everything works fine. So, at least for me, the NVIDIA graphics injection in the DSDT makes a big difference, since I use a dual-monitor setup everyday. Maybe the issue is with my Chameleon? I am using Chimera version 1.6 (which is the latest). The sleep behavior is as described by phile.
  10. I can test both injection types on my M1530. To confirm, to remove the DSDT injection, do I just have to remove the section described under the heading "Optional: NVidia Injection (also required for clamshell and sleep)" from my DSDT? Or if somebody could post their non-graphics-injected DSDT for the M1530 (any CPU), that would be great.
  11. @luggi, I guess there was a misunderstanding. My question regarding multi-monitor setup was for DarwinX, because he was saying that it is unnecessary for the DSDT to have the injection in it. So, I was wondering if the multi-monitor setup works with the plain Chameleon injection (GraphicsEnabler=Yes), without the DSDT injection. My multi-monitor setup IS working with the DSDT injection. As mentioned earlier, having the DSDT injection in place ignores the Chameleon injection. So, GraphicsEnabler=Yes doesn't have any effect with our DSDTs. Thanks.
  12. I didn't mean to find fault. I only wanted to know if there is some other problem with the new DSDT patch which is why it had not been put up in the first post. Thank you for the excellent work!
  13. @DarwinX: Have you tried a multi-monitor setup? I use a HDMI to DVI cable to connect an external monitor to my M1530 (through the HDMI port). I had used a DSDT which you had posted somewhere in this thread and I found that when using your DSDT, my external monitor was not detected.
  14. Since all the DSDT files attached in the first post include graphics injection, having GraphicsEnabler=Yes in the boot.plist has no effect, right? As suggested in the first post, even with the DSDT based injection, I still have GraphicsEnabler=Yes. But that didn't prevent the black screen when I upgraded to 10.7.2 . The only way GraphicsEnabler=Yes is going to have an effect is if we edit the DSDT files to remove the graphics injection.
  15. Thanks. Yes, I realized my mistake. I am using pro6,1 now. As I mentioned in the edits to my previous post, the problem was that we need a DSDT edit for 10.7.2 . I wonder why this new DSDT has not made it to the first post.
×