search for: 165mhz

...Various HDMI versions enable higher and higher pixel clocks. However individual GPUs are not required to support the maximum pixel clock supported by the spec in order to be compliant. It appears that some GPUs max out at 225MHz while others at 297MHz (while others still, I assume, are limited to 165MHz, esp among the older ones). We've been unable to find this in the VBIOS (I had a thought that it was in the table pointed to by the 'T' table, but we have a counterexample to that). Could you suggest a way to find this information either from the VBIOS or based on the GPU? Are there di...

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

https://bugs.freedesktop.org/show_bug.cgi?id=93405 Bug ID: 93405 Summary: nouveau: Xorg crashes sooner or later in 3840x2160 mode Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

Thank you for your quick reply. I have a Gigabyte GT-730 2GB card hooked directly via a high quality HDMI cable to a 65 inch Samsung curved screen LCD 4K monitor. I'm not sure what I am looking for in dmesg and xorg log. Please advise. I have built the 3.19.8 kernel and enabled frame buffer support. I can see 7 out of the 8 penguins when I boot. My ultimate goal is to be able to boot to

...ad > Debian Buster/kernel 4.19.x OK > Fedora 31/5.5.5 kernel bad > > http://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-gt218-stw-modesetting-OOR-0x1e > http://fm.no-ip.com/Tmp/Linux/Xorg/gt218-dmesg-stw.txt Those HDMI mode clocks are too high against the nominal single-link 165MHz TMDS. You can set your own maximum with nouveau.hdmimhz=300 (for example) to allow it. I believe the connectors aren't rated for that though. The commit which fixed this is commit d1084184789d677df4e9c110f38cb3f3d709195d Author: Ben Skeggs <bskeggs at redhat.com> Date: Wed May 29 09:58...

...ay_mode *umode, switch (nv_encoder->dcb->type) { case DCB_OUTPUT_TMDS: if (nv_encoder->dcb->sorconf.link & 1) { - if (mode->clock < 165000) - proto = 0x1; - else - proto = 0x5; + proto = 0x1; + /* Only enable dual-link if: + * - Need to (i.e. rate > 165MHz) + * - DCB says we can + * - Not an HDMI monitor, since there's no dual-link + * on HDMI. + */ + if (mode->clock >= 165000 && + nv_encoder->dcb->duallink_possible && + !drm_detect_hdmi_monitor(nv_connector->edid)) + proto |= 0x4;...

...nv_encoder->dcb->type) { case DCB_OUTPUT_TMDS: if (nv_encoder->dcb->sorconf.link & 1) { - if (mode->clock < 165000) - proto = 0x1; - else - proto = 0x5; + proto = 0x1; + /* Only enable dual-link if: + * - DCB says we can + * - Need to (i.e. rate > 165MHz) + * - Not an HDMI monitor, since there's no dual-link + * on HDMI. Of course in order to determine that, + * we need the EDID. So if no EDID, just let it + * slide. + */ + if (mode->clock >= 165000 && + nv_encoder->dcb->duallink_possible &am...

Video and input drivers Subgroups and projects on gitlab does not list modesetting DDX, presumably because it's not packaged separately from the server. Where's the right place to report a modesetting DDX bug that manifests only on an NVidia GPU? Directly against the server https://gitlab.freedesktop.org/xorg/xserver? Here are some particulars: How can I tell whether this should be

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

https://bugs.freedesktop.org/show_bug.cgi?id=40747 Summary: The new nouveau kernel module fails to use my monitor's native resolution Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi Gordan, I wanted to let you know that today I decided to have a try for my GTX 680. Gigabite GTX 680 2048 MB GDDR5. I know that this particular card could be hard-moded to GRID K2 so VGA passthrough could work. Following instructions found on http://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/420/ I just removed two resistors. Here is a screenshot

Hi Gordan, I wanted to let you know that today I decided to have a try for my GTX 680. Gigabite GTX 680 2048 MB GDDR5. I know that this particular card could be hard-moded to GRID K2 so VGA passthrough could work. Following instructions found on http://www.eevblog.com/forum/chat/hacking-nvidia-cards-into-their-professional-counterparts/420/ I just removed two resistors. Here is a screenshot