Mini DisplayPort to Dual-Link DVI Adapter creates jumpy mouse cursor

Same issue here with MacBook Pro 2.53 and Cinema Display 30'. Started after connecting using the $100 display adapter.

Where do you get the Capture Data app from? Anyplace to download or do you need to get in touch with a Apple support.

This actually makes the whole system less responsive as well. Also I am having stutters while watching 1080p trailers in Quicktime.

Heya everybody,

I'm having this exact issue with an external monitor (1440x900) via the single-link DVI adapter and the MacBook Pro's internal display active. It doesn't seem to matter which video chip I'm using or which display I make primary.

It is truly frustrating, I hope Apple comes up with a fix soon.

Thanks

The Data Capture.app is provided by an Apple tech when they want you to send information in about your system. If you call Apple and are escalated to a product specialist, they will get involved.

This "fix" (if you can call it that) has been working for me for almost a week. However, the dpEvents come back when:
- The computer wakes from sleep
- The computer restarts
- The mini DisplayPort cable is unplugged or
- The display sleeps

Very annoying to run this program every time I leave my computer for a while.

I went to a local Apple Store "Genius" Bar today. They were clueless about this. I pointed them to this thread. I asked for the Data Capture.app, but they declined to give it to me. They said it is not something they can give to the customers. Which of course made no sense, as it is a diagnostic app for customers to collect data and send it back to their support engineers. Anyways it was a frustrating visit.

I am wondering what is it that app doing that makes it stop the event or logging of the event. This is likely a bogus conflict error in the kernel probably in the USB driver or the new display port driver. Since when you run the app, things work all fine, the conflict is most probably bogus to start with. And with a kernel debugger and a little bit more data point, I am guessing it may not be that difficult to fix.

Options on what that app might be doing are:

a) Somehow app is redirecting the system log events, so even though the events are still fired by the kernel, they are not logged but logged in the capture app itself. Do you keep the app running, or run it once? When the system wakes up from sleep, is the app still running if you kept it running? Is any other event logged while the app is running?

b) Whatever the dp events: 0x04 means, the data capture app stops that happening. So the capture app may be shutting down a system service that is getting confused. And then when the system wakes up from sleep, the service auto starts. This option seems more plausible to me, since simply writing something to an event log should not cause such severe implications. To test this, can you take a look at your Activity monitor and see if any of the system services stop when you run the data capture app? If we can pinpoint a system service, as a workaround we may be able to stop it without using the app itself.

<rant> What is really mind boggling is, how something so trivially easy to replicate slip through the QA department of Apple. I mean all they needed to test was to connect a MacBook Pro to a Cinema display using their new adaptor and look at the system log. It is not a huge test matrix or a complicated test!?!?!? After all this happens to a brand new MacBook Pro, not like there are lots and lots of apps installed. I have a feeling, this is indeed happening to all the adaptors out there, but most people are either ignoring or not yet really using their machines heavily. For example this starts happening much frequently when I start using Photoshop. While just plain surfing, it does not really happen that frequently and in fact I even ignored it in the first few hours of installation. </rant>

Kerem,

Can we talk via email? (If you don't mind posting your email address or adding it to your profile)

I can tell you all my observations about the Data Capture.

Just a heads up...I filed my complaint yesterday. The gent helping me was very apologetic and was trying his best to accommodate me.

He clarified a few things:
1. it is a known issue they are working on (we knew this)
2. the engineer's weren't aware that it was happening with non apple displays as well (this seemed odd) but he asked me if I had a Samsung monitor (I'm guessing someone reported issues with a samsung monitor as well) which I dont. He let them know my Dell 3008wfp is having the same issues.

Basically said he would email me a patch if they give him one soon - otherwise to expect this fixed shortly.

I think the best way to get this handled soon is to NOT sit there waiting for a patch. Take the 15 minutes to call in and log the case so they know how many people this is affecting. I'm pretty sure this is a problem with every single 10.5.6 install - however, some people just don't notice it or it really isn't affecting their daily performance. PLEASE CALL.

Just talked to the Apple support guy again. We found another way to stop the jumpiness (besides running the Data Capture App).

Go to About This Mac and click the more info button. Then go to View-->Refresh and File-->Send to Apple. This will poll the I/O registers (similar to one of the steps in the Data Capture Application).

One caveat: You are sending your system info to an Apple server when you do this, but it's much quicker than running the Date Capture App.

Support is going to talk to Engineering again and see if they can give me a Terminal Command or quick script to run that will solve this problem in the interim until a software update is released. He reiterated that a number of people have now reported this problem and they are actively working on a fix.

UPDATE: I took my MBP into an apple store... We tried a dual-link DVI adapter and the problem persisted.

They took my machine so they could study it (they called it a "Capture") and gave me another one on the spot. If you're having this problem you may want to call Apple (even if you already have) and see if they've made their capture quota. Be sure to tell them about this thread, I did. The genius that took my machine said mine was capture #1.

It's fairly safe to assume whatever fix apple comes out with should fix both single and dual-link adapters. That being said, that dual-link adapter is a gnarly looking beast.

Good luck.

sure enough that worked magic...thanks!

What a bizarre fix!

That works for me too.

But I am now having freezing issues. My computer freezes (approximately every day for the last 2 days) . My older MacbookPro was usually up 30+ days with no issues (in fact only down for software updates beyond that.)

Does anyone have similar freezing issues? In one instance I could not even boot up my machine without disconnecting the display port.

Also in an unrelated note, Safari does not seem to hold on to the cookies. Every random intervals, all my cookies get expired and I have to login to all the sites....

All in all, this is such a horrible experience so far.

Oh and here is another one.

Whenever I set my video card to the more 9600, after booting back up it resets back to 9400. So that does not stick either.

In fact the whole two cards thing is such an annoyance anyways. Now I have to check which card is active and have log out and in, closing all my apps etc...

I found another way to stop the jumpiness. Download ONYX (a free program) and choose the "INFO" tab at the top. This gathers system info like the "Send to Apple" option in System Profiler and the Data Capture App described above.

I've been Send-to-Apple'ing the last few days - has worked wonders. However, I did make one observation...upon starting up, I had not noticed I was using the 9400m and even after doing the above 'fix' I had a few skips.

This could have been just my eyes playing games on me as I only noticed it once or twice, but it was a pretty obvious and very exaggerated. I dont really need to run it in battery save mode too much so it isn't a big deal, however I hope a fix comes soon.

I have to wonder exactly what it was added in 10.5.6 that is causing this since I can clearly use this in both windows and 10.5.5 without issues.

Actually in my case, everytime I reboot (and yes I am rebooting once a day due to freezing), the card is reset back to 9400M. Setting to 9600 does not stick and goes back to 9400 after a reboot.

It's nowhere near as gnarly as the old DVI to ADC adapter that Apple had out for early model (plastic casing) studio and cinema displays.