Displaying 20 results from an estimated 700 matches similar to: "Quadro 4000 with iiyama B2783QSU should be 2560x1440 but detected as 1920x1080."
2016 Sep 21
0
Quadro 4000 with iiyama B2783QSU should be 2560x1440 but detected as 1920x1080.
I think you want the reduced blanking modeline:
$ cvt -r 2560 1440
# 2560x1440 59.95 Hz (CVT 3.69M9-R) hsync: 88.79 kHz; pclk: 241.50 MHz
Modeline "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448
1481 +hsync -vsync
This matches your monitor's detailed timings:
[ 55.220] (II) NOUVEAU(0): Supported detailed timing:
[ 55.220] (II) NOUVEAU(0): clock: 241.5 MHz Image
2014 Oct 26
9
[Bug 85471] New: nouveau/kernel 3.18.0-rc1: nouveau deadlocks on 2nd Xorg start or reboot
https://bugs.freedesktop.org/show_bug.cgi?id=85471
Bug ID: 85471
Summary: nouveau/kernel 3.18.0-rc1: nouveau deadlocks on 2nd
Xorg start or reboot
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
2012 Apr 09
12
[Bug 48464] New: Crash when GLXVBlank set to true
https://bugs.freedesktop.org/show_bug.cgi?id=48464
Bug #: 48464
Summary: Crash when GLXVBlank set to true
Classification: Unclassified
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2019 Aug 06
2
unstable refresh rate
I think I may have updated the tv firmware between when it worked and
when it didn't.
I wonder it it has to do with bit depth.
I use lubuntu and it doesn't let me pick the bit depth so I don't know
what it using.
2015 Aug 08
4
[PATCH 0/2] drm/nouveau: add support for 2560x1440@56 over HDMI
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
2016 May 10
14
[Bug 95334] New: GM107 with 2560x1440 display on HDMI selects suboptimal resolution 1920x1080
https://bugs.freedesktop.org/show_bug.cgi?id=95334
Bug ID: 95334
Summary: GM107 with 2560x1440 display on HDMI selects
suboptimal resolution 1920x1080
Product: xorg
Version: 7.7 (2012.06)
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2019 Aug 12
0
limited resolution on DVI and HDMI at the same time
I got 1920x1200 at 59.95Hz via DVI and 3840x2160 at 60.00Hz via HDMI at the
same time with the proprietary nvidia driver.
I get flickering on the 1920x1200 at 59.95 with the nouveau driver (it
doesn't flicker if I lower it to 1920x1080 at 59.96).
Any idea why?
proprietary:
$ xrandr
Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1200+0+0
2020 May 05
1
problems with NVS310
I guess the DVI adapter is passive.
$ xrandr --props
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 8192 x 8192
XWAYLAND1 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 510mm x 290mm
??? non-desktop: 0
??? ??? supported: 0, 1
?? 1920x1080???? 59.96*+
XWAYLAND4 connected 2560x1440+1920+0 (normal left inverted right x axis
y axis) 600mm x 340mm
??? non-desktop:
2016 May 05
6
CentOS 7 and 4K display
I installed C7 along with MATE desktop...
My monitor is a 4K unit but when I goto the
System -> preferences -> hardware -> Displays
there is selection for the 4K display. It stops at 1920x1080.
The var log x file shows the 4K resolutions in the file so that is good.
How do I get the selections for 4K to show up?
Thanks,
Jerry
2018 Jun 21
10
[Bug 106994] New: [PATCH] Fix null pointer dereference in drmmode_output_dpms
https://bugs.freedesktop.org/show_bug.cgi?id=106994
Bug ID: 106994
Summary: [PATCH] Fix null pointer dereference in
drmmode_output_dpms
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component:
2018 Jun 23
1
Problem with external monitor on laptop
I am running opensuse Leap 15 on an Alienware laptop. When I plug a
monitor into the HDMI socket xrandr shows that is disconnected. How can
I get the system to send an event or something so it will look and see
that a monitor is there. If I cycle power on the computer with the
monitor connected both monitors come up connected. The command xrandr
--auto does not bring the disconnected monitor
2015 Oct 10
2
[PATCH v2 0/2] drm/nouveau: add support for 2560x1440@56 over HDMI
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
2015 Jan 12
2
2460x1440 video card recommendation
Can someone recommend a video card that's capable of driving a monitor at 2560x1600 or 2560x1440 and just works with Centos 7 without requiring any outside video drivers?
I would prefer to stay with the built-in video drivers that are included with Centos 7 if possible; I don't play games and such, so I'm not looking for high performance 3D -- I just want a high resolution desktop.
2008 Feb 18
6
system-config-display wrongly sets up Viewsonic VG730m monitor
I originally set up this monitor with an analogue lead. Everything seemed
fine, so I didn't check xorg.conf at all. Then I bought a digital lead, and
since then the monitor blinks. Running system-config-display identifies it
as a 1280 x 1084 CRT monitor. It is an LCD monitor.
That model is not on the drop-down list, so assuming that a specific driver
wasn't available for it, I
2015 Jan 31
3
Intel Displayport on Centos 7
On Sat, 31 Jan 2015 12:21:07 -0500
Lamar Owen wrote:
> I like the full-size DisplayPort connector the best of any video
> connector I've dealt with,
Thanks!
I'm waiting to see if my current monitor actually dies. It's an Asus 1920x1200 monitor that I like rather a lot, but it occasionally acts a bit flaky when coming back out of sleep mode. (The screen fills with a white
2015 May 27
11
[Bug 90682] New: failed to idle channel 0xcccc0001 then crash
https://bugs.freedesktop.org/show_bug.cgi?id=90682
Bug ID: 90682
Summary: failed to idle channel 0xcccc0001 then crash
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee:
2020 Feb 28
2
where to report modesetting DDX bug?
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
2018 Sep 07
2
Strange monitor behavior on forced DVI-D output
Hello ,
I'm new here but I hope I can describe my problem exactly.
I'm trying to get my DVI-Monitor to work with nouveau. The monitor is
automatically reported as not connected. LVDS is detected. Forcing it
on Xorg.conf didn't work, KMS does:
video=DVI-D-1:1920x1200e video=LVDS-1:d
X started with 1024x768, but could switch by xrandr to 1920x1200.
The viewed picture now is
2016 Sep 06
15
[Bug 97614] New: occasional screen distortions with nouveau under 4.8.0-rc4+
https://bugs.freedesktop.org/show_bug.cgi?id=97614
Bug ID: 97614
Summary: occasional screen distortions with nouveau under
4.8.0-rc4+
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
2017 May 07
2
GT 730 freeze : how do diagnose / debug ?
Hi,
I own an Asus GT730-SL-2GD3-BRK, trying to drive two monitors at 2560x1440
resolution. Using gnome-shell with either Xorg or wayland I get screen
freezes very frequently. Those freezes usually require a reboot to get
working graphics (below a sample trace that I got yesterday).
I am running Ubuntu 17.04 with the latest kernels avalable, I also tested
various more recent kernels including