<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - No recognition of DVI-D monitor" href="https://bugs.freedesktop.org/show_bug.cgi?id=108047#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - No recognition of DVI-D monitor" href="https://bugs.freedesktop.org/show_bug.cgi?id=108047">bug 108047</a> from <a class="email" href="mailto:wolle321@freenet.de" title="Wolfgang <wolle321@freenet.de>"> Wolfgang</a> <pre>Finally I got a workaround, with a lot of pain. The problem, that Nouveau doesnt find my connected DVI-display still persists. I tried to load a custom EDID-file from /lib/firmware/edid/. This failed, it seems that the driver doesnt load EDID for "not connected" displays. Forcing enabled DVI-D-1 didnt help too, I think the display is enabled to late. But for those, who want to fix wrong EDID-Data this wight work: The kms-parameter was on older kernels: drm_kms_helper.edid_firmware=edid/your_custom_edid.bin actually with newer kernels it is drm.edid_firmware=edid/your_custom_edid.bin But the idea was not so bad: how to get correct EDID-data for my DVI-monitor: I installed nvidia-driver (which freezes after 20 min but detects the monitior out of the box). The same thing like under nouveau: only the LVDS-monitor EDID is found with get-edid, but xrandr --verbose showed me the EDID of the DVI-Monitor (why? thanks you xrandr!). I wrote the EDID in a Hex-editor and parsed it with parse-edid. So I got the definitely working modeline for 1920x1200 for my DVI-Monitor. (It looks different from cvt-generated one, and I think the kernel uses the same algorithm, when I force the resolution with kms video=DVI-D-1:1920x1200e, which produced the 960x1200 monitor resolution with the 1920x1200 desktop resolution behind). So the final workaround back on nouveau is: 1.booting with video=DVI-D-1:e and starting up with 1024x768 kernel default resolution. 1.1 Also add a grub entry without enabling the DVI port because the LVDS doesnt show the LightDM login dialog, when DVI is forced enabled but not plugged in. 2.When logging in calling a script, what creates, adds and calls the right modline (stolen from nvidia-driver) for my DVI-display. Not very nice, but works. Could you explain, why nouveu doesnt detect the DVI-monitor, but nvidia does? Is this a bug? Thanks to Ilia Mirkin, who how gave me some hints.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>