<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI" href="https://bugs.freedesktop.org/show_bug.cgi?id=94259#c38">Comment # 38</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI" href="https://bugs.freedesktop.org/show_bug.cgi?id=94259">bug 94259</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to caozong from <a href="show_bug.cgi?id=94259#c35">comment #35</a>) Hi Zong, > Hi Kevin, > I've tried the OpenChrome Version 0.4.179 on KMS and UMS(I renamed drm.ko > drm_kms_help.ko and via.ko). Cursor shows up on UMS!! And it works well. But > it remain the same on KMS. > > > Setup: Wyse V90LE <a href="http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90LE.shtml">http://www.parkytowers.me.uk/thin/wyse/vx0/WyseV90LE.shtml</a> > Chipset: CN700 > System: Ubuntu 12.04 > Kernel: linux 3.19 drm-openchrome > DDX: xf86-video-openchrome release 0.4.0 > Monitor:LEN E2323swA (DVI-D) Someone pointed out a regression I caused with Version 0.4.177 (<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Can't use 1920x1080 on VGA with versions newer than 0.4.176" href="show_bug.cgi?id=96500">Bug 96500</a>). This affects monitors with 1920 dots horizontal resolution (i.e., 1920 X 1080) for IGA1. This bug was just fixed. Use Version 0.4.180 or later. <a href="https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=d234cdf68ea6a27718a948918b3075ad257e8a0f">https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=d234cdf68ea6a27718a948918b3075ad257e8a0f</a> I think for now, by luck, DVI is getting assigned to IGA2, and probably why you did not encounter the bug (The bug only affects IGA1.). Anyway, I am glad that DVI coming out of VT1632A is now working with CN700 chipset. Regarding the cursor bug, I will put more time into it when I start working towards releasing OpenChrome Version 0.6. Right now for Version 0.5, I have a few more things to work on, along with a bug that has become an effective blocker for release of Version 0.5 (Bug 95420). Unfortunately, fixing one bug often takes tremendous amount of concentration depending on how tricky it is to fixing it, and as a result, I have not been able to spend adequate amount of time on helping to fix the OpenChrome DRM / KMS bug you have reported.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>