veedub89 Posted April 1, 2014 Author Share Posted April 1, 2014 I was rebooting to get into the setup screen and pressed f12 when it happened. It wont even get into the bios. I've attached a picture of what it looks like. It's just stuck there. I tried removing everything. And have done the single stick of memory trick. Still nothing. Unplugged the cmos battery, and restarted. Still nothing. Did what dell suggests by removing power, pressing the power button for 30 seconds, repower the system, and still nothing. Is there another method of reseting the bios? Link to comment Share on other sites More sharing options...
veedub89 Posted April 1, 2014 Author Share Posted April 1, 2014 Just found out that if you hold the Fn button, and turn the power on, you get a diagnostic test with the status lights( Hdd, Bat, Wifi). My Hdd light, and the Bat light were flashing, and the wifi light was solid, indicating the graphics chip is bad, and needs to have the motherboard replaced. I already have one on order, and will have it by Monday. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted April 2, 2014 Administrators Share Posted April 2, 2014 wow that sucks. sorry to hear that. Link to comment Share on other sites More sharing options...
veedub89 Posted April 5, 2014 Author Share Posted April 5, 2014 New mobo is installed, and I'm up and running again. Still get the artifacts though(see pic). Tried the AppleIntelSNBGraphicsFB Jake mentioned, with no luck. Removed it all together as suggested, and no luck as well. The full force memory switch does work for updating to the latest chameleon, but the update didn't help the artifact problem at all. I've reset the bios as instructed, and no help there either. I noticed this popping up in system.log though: stampWait: Overflowed checking for stamp 0x396c on MAIN ring: called from timestamp = 0x396b **** Debug info for *possible* hang in MAIN graphics engine **** ring head = 0x02403490, wrap count = 18 ring tail = 0x00003810 ring control = 0x0000f801 enabled, auto report disabled, waiting, semaphore not waiting, length = 0x010 4KB pages timestamps = 0x396b Semaphore register values: VRSYNC: (0x12044) = 0x396b BRSYNC: (0x22040) = 0x0 RVSYNC: (0x 2040) = 0x0 BVSYNC: (0x22044) = 0x0 RBSYNC: (0x 2044) = 0x0 VBSYNC: (0x12040) = 0x0 Looks like MAIN ring is stuck waiting on an event After attempt to clear wait condition = 0x0000f401 no longer waiting trying to clear semaphore wait on MAIN ring After attempt to clear semaphore wait = 0x0000f001 no longer waiting stampWait: Overflowed checking for stamp 0x39ed on MAIN ring: called from timestamp = 0x39ec **** Debug info for *possible* hang in MAIN graphics engine **** ring head = 0x02405c50, wrap count = 18 ring tail = 0x00005fd0 ring control = 0x0000f801 enabled, auto report disabled, waiting, semaphore not waiting, length = 0x010 4KB pages timestamps = 0x39ec Semaphore register values: VRSYNC: (0x12044) = 0x39ec BRSYNC: (0x22040) = 0x0 RVSYNC: (0x 2040) = 0x0 BVSYNC: (0x22044) = 0x0 RBSYNC: (0x 2044) = 0x1 VBSYNC: (0x12040) = 0x0 Looks like MAIN ring is stuck waiting on an event After attempt to clear wait condition = 0x0000f001 no longer waiting Not sure what all that means but I'm hoping someone here does. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted April 7, 2014 Administrators Share Posted April 7, 2014 hmm i wonder if it is looking for your screens EDID info. i think switchresx app helps with that. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted April 8, 2014 Moderators Share Posted April 8, 2014 New mobo is installed, and I'm up and running again. Still get the artifacts though(see pic). Tried the AppleIntelSNBGraphicsFB Jake mentioned, with no luck. Removed it all together as suggested, and no luck as well. The full force memory switch does work for updating to the latest chameleon, but the update didn't help the artifact problem at all. I've reset the bios as instructed, and no help there either. I noticed this popping up in system.log though: stampWait: Overflowed checking for stamp 0x396c on MAIN ring: called from timestamp = 0x396b **** Debug info for *possible* hang in MAIN graphics engine **** ring head = 0x02403490, wrap count = 18 ring tail = 0x00003810 ring control = 0x0000f801 enabled, auto report disabled, waiting, semaphore not waiting, length = 0x010 4KB pages timestamps = 0x396b Semaphore register values: VRSYNC: (0x12044) = 0x396b BRSYNC: (0x22040) = 0x0 RVSYNC: (0x 2040) = 0x0 BVSYNC: (0x22044) = 0x0 RBSYNC: (0x 2044) = 0x0 VBSYNC: (0x12040) = 0x0 Looks like MAIN ring is stuck waiting on an event After attempt to clear wait condition = 0x0000f401 no longer waiting trying to clear semaphore wait on MAIN ring After attempt to clear semaphore wait = 0x0000f001 no longer waiting stampWait: Overflowed checking for stamp 0x39ed on MAIN ring: called from timestamp = 0x39ec **** Debug info for *possible* hang in MAIN graphics engine **** ring head = 0x02405c50, wrap count = 18 ring tail = 0x00005fd0 ring control = 0x0000f801 enabled, auto report disabled, waiting, semaphore not waiting, length = 0x010 4KB pages timestamps = 0x39ec Semaphore register values: VRSYNC: (0x12044) = 0x39ec BRSYNC: (0x22040) = 0x0 RVSYNC: (0x 2040) = 0x0 BVSYNC: (0x22044) = 0x0 RBSYNC: (0x 2044) = 0x1 VBSYNC: (0x12040) = 0x0 Looks like MAIN ring is stuck waiting on an event After attempt to clear wait condition = 0x0000f001 no longer waiting Not sure what all that means but I'm hoping someone here does. IMG_0141.JPG Post #7 you mentioned you have i7-2620QM, but your signature is i7-2720QM. I have an E6420 with i7-2620M without the Q, and bootpack only has SSDT for i7-2720QM, i7-2620M, i7-2760QM, i5-2520M. Perhaps using the wrong SSDT might cause such effects. Link to comment Share on other sites More sharing options...
veedub89 Posted April 8, 2014 Author Share Posted April 8, 2014 hmm i wonder if it is looking for your screens EDID info. i think switchresx app helps with that. Actually, I went down that route already on the same day that I got the new mobo installed. Found a discussion on another board(i'll leave unnamed) about display problems that had instructions on how to manually ad the EDID data in. That didn't fix it. Then I found this post on insanelymac that discussed the issue, and has a small app that will do it for you. It did the same as what doing it manually did, and still had no affect. I just installed SwitchResX. It didn't have any affect on my system either. Try updating AppleIntelSNBGraphicsFB with this one. If it's still causing artifacts, try without it. I was googling lines from the error showing in the console that I posted. I came across this thread on insanelymac where they were discussing the same issue as what I have been having. Much of the procedure that telanx discussed was talked about there too. This post in the thread has a cool script that pulls out the hex code for each of the connections that might come in handy for others when editing that kext later. I actually went and edited the kext to remove each connector one by one, until I was just left with the LCD connection left. Not one of them worked. Still had the error popping up, and the artifacts are still showing up. Post #7 you mentioned you have i7-2620QM, but your signature is i7-2720QM. I have an E6420 with i7-2620M without the Q, and bootpack only has SSDT for i7-2720QM, i7-2620M, i7-2760QM, i5-2520M. Perhaps using the wrong SSDT might cause such effects. My fault. It was a typo. My sig is correct, I have the 2720qm. I have checked and rechecked, and rechecked multiple times to make sure that I had the right SSDT. I have even gone as far as to create my own with revogirl's ssdtprgen script. Checked it to make sure that stepping worked before using it. It didnt help either. Link to comment Share on other sites More sharing options...
Darvinko Posted April 8, 2014 Share Posted April 8, 2014 Any possibility that the Bios version is creating the graphics issues, such as we saw on other models? Link to comment Share on other sites More sharing options...
veedub89 Posted April 8, 2014 Author Share Posted April 8, 2014 I can't say that I have done all the tests(i.e. adding edid info) at ALL the BIOS revisions. But I have rolled it back at least from A21 to A14, one revision at a time trying at least the initial boot pack that Jake posted and most of the DSDTs that pokenguyen posted. I even rolled back to A08 and tried it. After I replaced the mobo, it had rev A06 installed initially, where I tried it at that revision too. All have the same effect. That's why this is getting so frustrating for me. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted April 8, 2014 Administrators Share Posted April 8, 2014 yeah like darvinko mentions it could be bios downgrade to like A18 if possible Link to comment Share on other sites More sharing options...
Recommended Posts