<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#c19">Comment # 19</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>Hi Eric, I think I have some explanations on why the cursor does not show up on your screen. The way VIA Technologies Chrome family of IGP (Integrated Graphics Processor) works is that it contains 2 display controllers internally. They call this IGA1 and IGA2 (I do not know what IGA stands for.). Most likely what is going on is that OpenChrome is not really using one of the display controller, but the display controller is still functioning. What this means is that the display controller hardware is still running, but because OpenChrome is not really using this display controller, it is not turning on the hardware cursor. The hardware cursor has to be actively managed by OpenChrome like determining the X and Y coordinate on the screen. Previously, I have been fairly reluctant to make extensive code changes due to the fact that OpenChrome has had many lines of "legacy" code that did not have to be there (i.e., known device table, legacy user mode setting, and VBE mode setting). Now that stuff is gone, and I have a freer hand in adding more lines of code that does something useful. It might take a while until the issue can be resolved to your satisfaction, so please be patient.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>