akarichn Posted January 26, 2014 Share Posted January 26, 2014 Because his 14R has pretty much the same Intel Emerald Lake board that Vostro has. UPD: If yours is Intel-only model too please clarify on what files you are suing and what works for you (state your board number too!), perhaps the table in the original post needs to be updated to reflect more models. Sorry about the late reply, I've been working on some other stuff and haven't had much time to sit down at this system. It's interesting to me, but the InjectIntel problem was fixed by replacing the EDID in the config.plist for Clover with one I found with DarwinDumper. The EDID is as follows: 00ffffffffffff0030e4e9020000000000140104901f11780ab7a59758568f271f505400000001010101010101010101010101010101581b567e50000e302430350035ae10000019de12569a50001a302430350035ae10000019000000fe0039444d4b32803134305748340a0000000000004131940100000001010a2020007f I'm not sure what you mean by "board number" (or, if you mean motherboard serial, how I'd get that off of OSX), but I'll look for it in BIOS and update this when I grab that. I still get artifacts, although I don't see "fuzzy squares", per se. More, I see lines that go across the screen that appear to be garbage data from what was previously stored in the display/graphics memory/I don't even know where. They "stick" as though they were just some window, and I'll see them scroll with windows, hide behind windows (yet stay there), go over windows, etc. They can be blocks or lines, they flicker with videos/animations/etc, and they can easily go away just by minimizing and restoring a window, or allowing the system to go into the screensaver. I don't know if this is what's classified as graphics artifacts, but this is what I'm seeing and it seems like not many people see this. Also, I've lately had an issue with what I'd assume is the VoodooPS2Controller.kext. The trackpad will occasionally just shut off. I've tried using the disable/enable trackpad hotkey, and the orange light above the trackpad toggles as such, but the trackpad remains frozen. Sometimes it'll "unstuck" after a little while, but usually I have to cold reboot the system. And to be honest, neither of these issues really bug me as anything more than what I dealt with on other systems with more esoteric OSes, but if I can help work to fix these issues in any way whether they're of my fault or just some odd hardware difference, I'll be glad to help. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 26, 2014 Author Share Posted January 26, 2014 The board number can be obtained from Clover (either Options menu or preboot log - will be saved to /EFI/CLOVER/misc if you press F2 in GUI). In the log it appears as follows: 0:100 0:000 Clover revision: 2523 running on Dell System Vostro 3450 0:100 0:000 ... with board 0YW3P2 The EDID issue is to be expected, I didn't think it all the way through. I should exclude hardcoded EDIDs from configs when I next revise the files, because DisplayOVerrides are enough to deal with artifacts. You really need to fine tune your real EDID yourself.. @jkbuha seems to have put up a guide somewhere, but I wasn't lucky enough to stumble upon it. If he points to it here that'd be cool. About touchpad - if the keyboard remains functional then you are probably hitting print screen key by accident, which is tuned to also disable touchpad. See if tapping it brings the thing back to life. Link to comment Share on other sites More sharing options...
jkbuha Posted January 26, 2014 Share Posted January 26, 2014 That's because the site I had originally uploaded it to (t**ym*c) subsequently re-indexed and lost my content. Luckliy I had a backup of the post stored as a howto on my laptop, so I've repasted it here for anyone who needs it. Note: this is for the 15z (L511z) but the same method applies for all display overrides. Hi allHaving had all the freezing & artifact issues with my Dell XPS 15z (8GB RAM, HD3000 ID: 0126, 1920x1080 LVDS) and having tried all the proposed solutions in this forum (DSDT patching, SMCping, memory removal) but without success, I decided to investigate further and found this topic, courtesy of Micky1979: (external to t**ym*c)It still didn't solve my problem, but got me thinking as to whether there could be an issue with my LVDS EDID configuration. The reason for my suspicion was that with (i) an external monitor connected, or (ii) with the LVDS rotated to 1080x1920, no issues were encountered. So I replaced my XPS 15z EDID configuration with a quasi-identical XPS 15 EDID as follows:Original XPS 15z (L511z) EDID: 00FFFFFFFFFFFF0006AFED3000000000001401049022137802D1159E59539B271E505400000001010101010101010101010101010101B03680E0703808403064310058C11000001A752480E0703808403064310058C11000001A000000FE00303052344D80423135364857330000000000004122960111000002010A20200030 Replaced XPS 15 (L502x) EDID: 00ffffffffffff0006afed17000000000014010490221378022135ad5037aa2411505400000001010101010101010101010101010101783780ae703832403c30aa0058c11000001a783780ae703832403c30aa0058c11000001a000000fe004b5959564b804231353648573100000000000081029b0101000002010a20200001 Using the method described by Micky1979 in his post, adapted from insanelymac's CharredPC's method.Result: absolutely no freezing or artefacts after having hammered the machine for 72 hours continuously. dmesg is clean (no hangup messages) as well.What I'd like to know is this:i) Can someone who is EDID friendly point out what the differences are between my original XPS 15z and the XPS 15 EDID?ii) When (i) is identified, ca this change be applied to non-dell machines, ie any laptops/pcs which are experiencing hangups?iii) Is the issue due to an incorrect vendor EDID, or an ultra-sensitive HD3000 kext, or a combination?This should get us to properly understanding the HD3000 issue once and for all.Thanksjkbuha Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 26, 2014 Author Share Posted January 26, 2014 oh, so it wasn't a guide at all, just an observation. Basically, your 15z EDID has these standard timings for the panel: Detailed mode: Clock 140.000 MHz, 344 mm x 193 mm 1920 1968 2068 2144 hborder 0 1080 1083 1084 1088 vborder 0 +hsync -vsync Detailed mode: Clock 93.330 MHz, 344 mm x 193 mm 1920 1968 2068 2144 hborder 0 1080 1083 1084 1088 vborder 0 +hsync -vsync While L502x has these: Detailed mode: Clock 142.000 MHz, 344 mm x 193 mm 1920 1980 2028 2094 hborder 0 1080 1090 1100 1130 vborder 0 +hsync -vsync Detailed mode: Clock 142.000 MHz, 344 mm x 193 mm 1920 1980 2028 2094 hborder 0 1080 1090 1100 1130 vborder 0 +hsync -vsync And I bet this is not the stock L502x EDID, it has been definitely patched before to fix screen tearing and artifacts. They are essentially same 1080P panels, just slightly different model numbers (yours is AUO Model 30ed, while L502x has AUO Model 17ed). Link to comment Share on other sites More sharing options...
jkbuha Posted January 26, 2014 Share Posted January 26, 2014 Yes correct - I had posted how to override the existing settings with a functioning one. That said I'm not sure if the L502x was indeed modded at all (afaik no one who had a standard xps15 ever complained about hd3000 issues) - though why the 30ed would be 2MHz slower than the 17ed is anyone's guess... Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 26, 2014 Author Share Posted January 26, 2014 I had to up my frequency (by means of using SwitchResX) by at least 10MHz (default was 89 IIRC and i've upped it to 100) or else it popped with artifacts all over. Link to comment Share on other sites More sharing options...
akarichn Posted January 26, 2014 Share Posted January 26, 2014 The board number can be obtained from Clover (either Options menu or preboot log - will be saved to /EFI/CLOVER/misc if you press F2 in GUI). In the log it appears as follows: My board ID is 05TM8C. The EDID issue is to be expected, I didn't think it all the way through. I should exclude hardcoded EDIDs from configs when I next revise the files, because DisplayOVerrides are enough to deal with artifacts. You really need to fine tune your real EDID yourself.. @jkbuha seems to have put up a guide somewhere, but I wasn't lucky enough to stumble upon it. If he points to it here that'd be cool. As far as the EDID goes, I'll have to look into that. Would I be wrong to assume there are programs to help modify one's EDID? About touchpad - if the keyboard remains functional then you are probably hitting print screen key by accident, which is tuned to also disable touchpad. See if tapping it brings the thing back to life. Ah, that makes sense, thinking back to what would have triggered it. I'll try it out next time it happens (or just try to avoid hitting that key altogether). Thanks! Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 26, 2014 Author Share Posted January 26, 2014 Yup, got that model in the notes already (post #5 here), just need to make sure I remove the EDIDs from config and we get you a working EDID to fix the screen glitching. So far we have 3 possible screens on these laptops (honestly, I though only two were shipped - a glossy and a matte one): - AUO GP84R - [6af:183c] (produced late 2009) - LGD 9DMK2 - [30e4:2e9] (produced early 2010) - CMO KJ303 - [daf:1464] (produced early 2011) Your screen is LGD Model 2e9 while older revision 14R have AUO Model 183c, so thats why DisplayOverride do not match... nor does my CMO panel EDID matches. Checking @Zprood's DisplayOverride I can see same tendency as with 15z -> L502x EDID. Here's your LGD versus AUO screen LGD: Detailed mode: Clock 70.000 MHz, 309 mm x 174 mm 1366 1402 1450 1492 hborder 0 768 771 776 782 vborder 0 -hsync -vsync Detailed mode: Clock 48.300 MHz, 309 mm x 174 mm 1366 1402 1450 1520 hborder 0 768 771 776 794 vborder 0 -hsync -vsync AUO: Detailed mode: Clock 69.300 MHz, 309 mm x 173 mm 1366 1404 1426 1436 hborder 0 768 771 777 803 vborder 0 +hsync -vsync Detailed mode: Clock 69.300 MHz, 309 mm x 173 mm 1366 1404 1426 1436 hborder 0 768 771 777 803 vborder 0 +hsync -vsync I would only assume that if taking L502x EDID and applying it to 15z works it would work same way with different screen brands of 14R. Try taking DisplayOverride from14R arhive, rename DisplayVendorID-6af to DisplayVendorID-30e4 and rename DisplayProductID-183c to DisplayProductID-2e9, then install the override into System/Displays/Overrides and take a reboot. Link to comment Share on other sites More sharing options...
akarichn Posted January 26, 2014 Share Posted January 26, 2014 I would only assume that if taking L502x EDID and applying it to 15z works it would work same way with different screen brands of 14R. Try taking DisplayOverride from14R arhive, rename DisplayVendorID-6af to DisplayVendorID-30e4 and rename DisplayProductID-183c to DisplayProductID-2e9, then install the override into System/Displays/Overrides and take a reboot. Trying that out now and it seems fine so far, but the artifacts sometimes take a while to show up, so I'll probably update this tomorrow with more news. UPDATE: It didn't work, sadly. Made the screen a bit brighter though! Although I'm not sure if that's a result of the override or some other unassociated element. Link to comment Share on other sites More sharing options...
Zprood Posted January 29, 2014 Share Posted January 29, 2014 @TW, do u have interest in Fusion drive ? i just read something about it and we both have SSD & HDD inside. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 29, 2014 Author Share Posted January 29, 2014 I've tried it on my desktop and its a waste of time. Corestorage array is garbage. Link to comment Share on other sites More sharing options...
Zprood Posted January 30, 2014 Share Posted January 30, 2014 oh what a pity. i see someone have done it in other forum, the boot time is 15s. so i'm wondering whether it's worth to test. Link to comment Share on other sites More sharing options...
badman0_8 Posted January 30, 2014 Share Posted January 30, 2014 Hi!. thanks for this tutorial , but in my dell vostro 3450 sound, fn function is not working. My board id is 0K8WHD and i was rename 0YW3P2 folder to 0K8WHD but still not working . can you support me fix this issuer . thanks Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 30, 2014 Author Share Posted January 30, 2014 It should work regardless of what your board is (except touchpad disable hotkey, for that you need to edit the plist to include your model)... the rest is just standard scancodes. 1 Link to comment Share on other sites More sharing options...
badman0_8 Posted January 30, 2014 Share Posted January 30, 2014 edit plist file in voodoo kext or config.plist , i don'n know which the plist file. Link to comment Share on other sites More sharing options...
Inter95 Posted January 31, 2014 Share Posted January 31, 2014 tw, in my situation my mainboard model # doesnt read (0FH09V) what i have to do? because Trackpad doesn't work like i expect. can you take a look of my preboot.log to see if everything is ok? preboot.log.zip Link to comment Share on other sites More sharing options...
Zprood Posted January 31, 2014 Share Posted January 31, 2014 here it is one which edit default value, you can install without modification. What change: 1. enable Fn+F3 to diable trackpad. 2. three fingers assign gesture like: swipe down > mission control(F3), swipe up > show desktop(F5), swipe left and right > back & forward(CMD+[&]) 3. Context Key (App windows) > Launchpad 4, double finger click > right mouse click. VoodooPS2Controller.kext.zip 1 Link to comment Share on other sites More sharing options...
Inter95 Posted January 31, 2014 Share Posted January 31, 2014 (edited) thanks Zprood, it works great! Update: step 1, 2 and 4 work but Launchpad doesnt work. Edited January 31, 2014 by Inter95 Link to comment Share on other sites More sharing options...
badman0_8 Posted January 31, 2014 Share Posted January 31, 2014 thanks Zprood, it work for me , but fn+f2 not work . Link to comment Share on other sites More sharing options...
Zprood Posted January 31, 2014 Share Posted January 31, 2014 if you read TW's first page you should know Fn+F2 always does't work . Link to comment Share on other sites More sharing options...
TimeWalker75a Posted January 31, 2014 Author Share Posted January 31, 2014 .. this plist editing massacre reminds me i have to set up a default dell profile with all the aliases on a completely unrelated note - i've updated CodecCommander to 2.1.0, though since 10.9.2 is not yet officially out i'm not publishing the compiled kext as behavior may change again. works for me for the most part now with 2.6.0 AppleHDA from C44 build. Link to comment Share on other sites More sharing options...
Zprood Posted February 1, 2014 Share Posted February 1, 2014 @tw, i just download it from github, compile it. but failed after wakeup, is any modification needed ? EDIT: it works well, here is the working debug log. Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: commander initializing Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: board make - DELL Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: board model - 03NKW8 Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: commander probing Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: commander version 2.1.0 starting Feb 1 11:39:37 localhost kernel[0]: CodecCommander: hi: keyboard device attach Feb 1 11:39:37 localhost kernel[0]: CodecCommander: hi: keyboard device created Feb 1 11:39:37 localhost kernel[0]: CodecCommander: cc: awake Feb 1 11:39:37 localhost kernel[0]: CodecCommander: hi: keyboard initializing Feb 1 11:39:37 localhost kernel[0]: CodecCommander: hi: keyboard starting Feb 1 11:39:37 localhost kernel[0]: CodecCommander: w: ICW stored set command 1470c02 Feb 1 11:39:37 localhost kernel[0]: CodecCommander: w: ICB was set, sending verb over the link Feb 1 11:39:37 localhost kernel[0]: CodecCommander: rw: IRV was set by hardware Feb 1 11:39:37 localhost kernel[0]: CodecCommander: rw: IRV cleared, allowing new commands Feb 1 11:40:57 vts-Macbook-Pro kernel[0]: CodecCommander: cc: asleep Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: cc: awake Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: w: ICW stored set command 1470c02 Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: w: ICB was set, sending verb over the link Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: rw: PIO operation #1 Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV was set by hardware Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV cleared, allowing new commands Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: cc: workloop started Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: hi: scancode 20 in Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: hi: adb keycode 74 out Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: hi: scancode 20 in Feb 1 11:41:35 vts-Macbook-Pro kernel[0]: CodecCommander: hi: adb keycode 74 out Feb 1 11:41:40 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream active Feb 1 11:41:40 vts-Macbook-Pro kernel[0]: CodecCommander: r: ICW stored get command 14f0c00 Feb 1 11:41:40 vts-Macbook-Pro kernel[0]: CodecCommander: r: ICB was set, sending verb over the link Feb 1 11:41:40 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV cleared, allowing new commands Feb 1 11:41:40 vts-Macbook-Pro kernel[0]: CodecCommander: r: IRR is set, EAPD active Feb 1 11:41:45 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:41:50 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:41:55 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:42:05 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:42:35 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream inactive Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: r: audio stream active Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: r: ICW stored get command 14f0c00 Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: r: ICB was set, sending verb over the link Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV cleared, allowing new commands Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: r: IRR isn't set, EAPD inactive Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: w: ICW stored set command 1470c02 Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: w: ICB was set, sending verb over the link Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: rw: PIO operation #2 Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV was set by hardware Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: rw: IRV cleared, allowing new commands Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: cc: workloop ended after 2 PIOs Feb 1 11:42:55 vts-Macbook-Pro kernel[0]: CodecCommander: EAPD re-enabled Link to comment Share on other sites More sharing options...
TimeWalker75a Posted February 1, 2014 Author Share Posted February 1, 2014 Thanks for testing and feedback. The log is exactly what I expected it to happen and what I'm getting here on my laptop. I shall note that even though we have dealt with the problem of AppleHDADriver::runPowerManagmentTimerForEngine(bool*) starting at wake and disabling the EngineOutput and EAPD we still have the problem of AppleHDADriver::setAFGPowerForJackDetection(unsigned int, bool, bool) that is messing with jack detection, so plugging in headphones and external mic is not really detected until you do a sleep/wake cycle. I shall see if Jack Presence Detection can be overridden and controlled in some shape of form. Edit: yeah.. just as I though.. i've reverted all the changes to AppleHDA kext that I did before and used the kext (well, layout, platform and pinconfig really!) from the original post.. no jack sense problems now. So I must have messed up somewhere in the patching process, never found the mistake and started looking in completely different place. Link to comment Share on other sites More sharing options...
Zprood Posted February 2, 2014 Share Posted February 2, 2014 yeah, i don't see any logs like: AppleHDADriver::XXXX And new codecommander works well. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted February 2, 2014 Author Share Posted February 2, 2014 yeah, i don't see any logs like: And new codecommander works well. After updating to 10.9.2 build C48 yesterday I'm seeing different behavior in regards to EAPD. Now it takes only single PIO operation to remain enabled. Sometimes it takes 2 and sometimes 3, so I've disabled the loop timeout if update count is equal to 2 and made it go infinitely... I keep pushing changes to git as I test. Mind updating to C48 and testing it as well ? You can always remove comment marks from the code if you want it to timeout the loop after 2 PIO operations. Link to comment Share on other sites More sharing options...
Recommended Posts