<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - nouveau: Xorg crashes sooner or later in 3840x2160 mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=93405#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - nouveau: Xorg crashes sooner or later in 3840x2160 mode" href="https://bugs.freedesktop.org/show_bug.cgi?id=93405">bug 93405</a> from <a class="email" href="mailto:estellnb@elstel.org" title="Elmar Stellnberger <estellnb@elstel.org>"> Elmar Stellnberger</a> <pre>Great! With nouveau.hdmimhz=225 I can yield such modes like 3840x2160@23/24Hz whereby 23Hz is stable and 24Hz sometimes starts to flurr. For those who prefer a higher freuquency 2560x1600@47 should be a tip. 25MHz for 2840x2160 will make my display stay black and 48Hz for 2560x1600 results in considerable pixel flurring. I have also tried it with 3840x2160@48i interlaced. However with all 3840x2160 interlaced modes the mouse pointer disappears. I can still move the mouse highlighting the icons where the mouse moves over but the mouse pointer will be no more visible as soon as I select an interlaced mode. I don`t know whether a fix would be possible for the interlacing mouse pointer issue but that would even give a better 4K experience on elder cards as modes with 24/25/30Hz yield a somewhat deferred moving of animated objects like the mouse pointer. Nonetheless the joy of running a full 4K display with my Nvidia G96M [GeForce 9600M GT] is a thriving experience. To make this report complete nouveau.hdmimhz=297 will let my HDMI output simply stay black. The support of the hdmimhz parameter is an amazing feature that no proprietary driver will give; neat work!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>