Jump to content


  • Content count

  • Joined

  • Last visited

About glitchbit

  • Rank
    InsanelyMac Geek
  1. Dell XPS 13 9343 Touch thread

    I am fairly amazed that this is still a thing. Cordially.
  2. Dell XPS 13 9343 Touch thread

    Ah, guess it'd make sense that turning off a feature in the BIOS from on to off would have an effect. Still at least people can compare the original and final DSDTs for differences, but yea I need to definitely up a patch file version. I will probably just create a separate repo for Maciasl to pull in patches that are specific to the 9343.
  3. Dell XPS 13 9343 Touch thread

    To those interested I have dumped the A05 firmware and decompiled it to dsl files. Once the compile bugs are worked out the existing patches for fixing brightness controls on our chipset platform by Rehabman should then work. We're not doing anything that hasn't been done a thousand times over, so I am surprised that no one has clearly fixed this and uploaded the proper DSDT files for others to use. (Granted if other parts of your config differs, kext or boot flag wise then the DSDT may behave in unexpected ways, but that's part of it.) https://github.com/rbreaves/XPS-13-9343-DSDT https://github.com/RehabMan/Laptop-DSDT-Patch
  4. I am using one of these two loaders, which one, I am not sure - PC EFI 9.4 - boot-9-4 by Netkas or - PC EFI 10.5 - Chameleon 2 RC3 (r658) PC EFI 10.5 by Netkas is PC EFI 10.5 derived from chameleon? All I know is that I can enable themes for the chameleon bootloader if I want, and I did for awhile, but have reverted back to the normal darwin terminal screen.
  5. I'm running the 1600x900 screen so it is not specific to the DSDT, whatever your problem is I am pretty sure you are looking in the wrong places. I wish I knew what is different about your setup vs mine, because I know I hate hearing that something works for User X yet the same files don't work for me as expected. But I am telling you its got to be related to something else, maybe another OS or your bios setup or version is doing something weird, I dunno. Only other thing I can say is that I always install osx using SnowOSX v3.6, but I am trying to remember, was it you that said that disc did not work for you? Of course they say if you use a distro like that people here won't "support" you lol. hmm.. that is odd I had problems decompiling someones dsdt file here in the past myself.. not sure why mine would have the same issue. Also I am not certain what bootloader I using, whatever bootloader comes on the SnowOSX v3.6 disc is what I am currently using. I have not spent any time upgrading it.
  6. I'd give it a shot this person with a real mac has no issues with it http://blogs.zdnet.com/Apple/?p=4786 Also oddly enough when I have a problem with my install I have found better help from legit macbook forums and even apples support forums than what I have found here.. probably because there are quite a few bugs that actually relate to SL across the board than my non-macbook laptop. It is a little irritating though for people like us because our first reaction, is oh it must be because it is a hack and we rarely think oh it must be OSX lol. That typically is a very distant after thought, but it really shouldn't be...
  7. iaslme also decompiles the files as well you can simply drag any of my aml files on it and it will spit out the dsl file.. vice versa of course. Also concerning your F4/F5 keys not working, I would suggest that you shut down your laptop, unplug any hdmi or displayport connector if you have a monitor plugged in and unplug your laptop from your power adapter. Then boot back up into OSX and see if your F4/F5 keys work, because while may keys usually works, I have noticed that if they don't, then I can certainly get them to work via that method. Also sometimes the VoodooBattery kext does not load properly, and that may be why the power adapter needs to be unplugged. Also I have had to become corrupt once and I had to replace the VoodooBattery kext.
  8. I use iaslMe, and the autodimming feature as far as switching from power adapter to battery does work for me. Also it appears that removing ntfs for mac osx did not fully resolve my esata issue after sleep.. its just a hit or miss it appears.
  9. I edit in a normal text editor (Komodo Edit) the backlighting works perfectly for me so I suggest that you look outside the DSDT for your solution. Maybe you should boot into windows and play with your backlighting some and then go back into OSX. Are you using Ubuntu any? (I personally haven't). You may even want to try messing with your BIOS settings and maybe swapping out your media key config and booting into OSX with "-v -x -f" then reboot normally. There are a lot of things I would play around with like that if I were you before messing with the DSDT. Also are you sure your backlighting does not work with a fresh install of OSX? It could be software related too, I know NTFS for Mac OSX screws with our eSATA ports and usb ports and I think it even causes VMWare fusion to perform horribly bad!! Ever since I removed that piece of {censored} my systems runs as stable as it did when I first installed OSX on here. Good luck!
  10. I'm afraid I have created a lot of confusion regarding my DSDT v3r45 release, so I am going to try and clear this up. A lot of it was due to uncertainties on whether my DSDT was the cause of certain issues (such as eSATA disappearing after sleep & wake, but it indeed was software related.. either ntfs for mac or vmware, have not confirmed yet). Also I was not sure if speedstepping was working all CPU models, and from the best of knowledge these DSDT files are not CPU specific like some other Dell notebooks. I can confirm that speedstepping works as expected in T6600, and there is no reason speeding should not work with P8600+ or any other, assuming the proper kext files are in place in EE or even SLE if you want. And I did not re-upload the wrong file as v3r45, I kept the original zipped file which is dated Feb 12th, and the file inside was Feb 1st. I tested it for several days before releasing it, every revision I have made since then does not noticeable improve any functionality, nor do I see any future room for improvement in the DSDT. Instead the best thing I can advise is for you to thoroughly test all functionalities, sleep & wake, firewire, esata, usb drives and the like the best you can on a fresh install once I did this I found that everything appeared to work properly and only after installing my required applications did I find issues that primarily relate to esata de-activating upon sleep, but again it is not something that can be fixed in the DSDT. As far as I am concerned, my tweaking of the DSDT is done, I'd love to figure out audio over HDMI, but short of that I have all functionality working on my system. I will let someone else figure out audio over HDMI for the MCP79 platform and someone here will probably add it in to ours sometime in the future before I even notice a solution for the audio. There is a hardware fix for it though, if you buy the right adapters at monoprice, you could theoretically take your audio out and merge it with your hdmi a couple of ways probably. 14z_v3r45.zip - DSDT http://www.multiupload.com/QHTR6LKWFE - I think these are the last extensions I posted - eliminated all compiler warnings from iaslme, removed a lot of useless return zeros added a lot of return zeros. - renamed several devices to match the original macbookpro5,5 dsdt, which uses the same MCP79 chipset - applied known fixes for the USB devices to enable sleep without sleepenabler (other people here I am sure applied it to theirs too) - applied additional USB fix to prevent eject error when waking back up from sleep - modified several scope entries to match macbookpro5,5 - Power button device modified, added Sleep button device entry - Added power state methods to PCI device
  11. As far as I can tell speedstepping works fine on T6600 and it should on the others, I just needed to confirm it because other laptop models apparently have DSDT files that differ depending on the CPU used for it. The other question was if the DSDT for T6600 differed slightly, could it still work for other CPU's but just not as well as it could/should. I believe the answer is that my DSDT should work just as well for P8700 or whatever model CPU as it does for T6600. Also I am confused as to why your acceleration is lost, that makes no sense because it ought to detect the built in kext just fine assuming that you booting with the DSDT file you were using earlier. Maybe you should boot with "-v -f" to force all the kexts to reload?
  12. No, I am running on A04 just like you. I just compared your A04 DSDT to my old DSDT original since I could not find my A04 original, it should not really make a difference though.. From what I can tell there is either a lack of speedstepping info in our DSDT compared to most other or the code for it is a good deal different and I just can't seem to find the proper entries for it.. I found the normal _PR scope and cpu entries, but it takes up all of about 3 lines of code where as others have it take a dozen or more lines code and the frequencies and voltages are fairly easy to read, but ours does not have that kind of code that I have been able to find thus far. I thought maybe it was because I have a lower end T6600, and assumed it has less speedsteps, but I guess it is either in the DSDT somewhere else. I don't expect to find any CPU related differences later though, because every instance where the DSDT files did not match up I pretty much googled all of the entries so I could confirm what they were related to and it was mostly differences in WMI and AWM interfaces which as far as I can tell will not be controlling the speedstepping our cpu's.
  13. Ok I just looked it over and I cannot tell any difference between my T6600 cpu and yours. So I guess that is probably good news, we can keep 1 DSDT file that should apply to others. Unless I missed something. What I did notice though is that between BIOS version A01 and A04, there are differences in the WMI and AMW interface implementations. This would explain why the media keys on our keyboards function properly in BIOS A04 and not A01 (or maybe just more consistently?). Dell most likely did not fully implement WMI in A01 which affected its linux users so they updated the WMI code for A04. Only other notable difference was a slight change to the usb devices, they added an RHUB device too it, not sure if that really makes any difference at all in OSX.
  14. I assume you mean the 3g card needs antenna's and not the bluetooth? My bluetooth adapter works fine without any atenna attachment. Also I have re-uploaded my v3r45 DSDT to the forum, since mediafire appears to be a very temporary file storage solution I will have to start uploading files elsewhere. Yea, I've been rather busy myself and for the last 48 hours I came down with something pretty bad.. my entire weekend has been wasted. Well I looked at your DSDT and appears like your system grabbed the modified DSDT file in your Extra folder. If the DropSSDT=y does not work like I thought it would then maybe you will just have to remove the DSDT from your extra folder altogether until after you extract your real DSDT. On the autodimming feature, it appears to work on my install fine, although it appears like I have a way of consistently breaking eSATA and even USB that causes them to eject on sleep improperly. Even worse eSATA will not start to work again until after I reboot. I do not know which software I installed that causes this issue. I suspect vmware or ntfs for mac. Neither software applications would have been tested with eSATA and certainly not native eSATA and removing said software does not seem to fix it, but those were the last 2 programs I installed immediately before I started having issues with my eSATA. 14z_v3r45.zip
  15. I just realized I did not fully answer tamorgen. As far as what is left to fix, it seems like my usb and esata issues after sleep may not be an issue related with my DSDT file at all and instead, an issue with either vmware or ntfs for mac. So short of that I do not really feel like there are any pressing matters to go after. The sound issue is a minor convenience but it works really well most of the time. I would like to figure out how to output sound with my hdmi but I do not have time right now to go after something like that. Also I think it's a good idea to keep an eye on other MCP79 laptops out there such as the mini HP 311, if any significant developments happen over there or the Zotac 9300 ion they may be applicable to our system as well. I will gladly take a look at DSDT files from 14z's that have cpu's that differ from my T6600 and see if I need create separate DSDT files for them, as soon as they are posted.