similar to: [Bug 70389] [prime] unsynchronised rendering on secondary displays

https://bugs.freedesktop.org/show_bug.cgi?id=70389 Chris Wilson <chris at chris-wilson.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|chris at chris-wilson.co.uk |nouveau at lists.freedesktop.o | |rg QA

https://bugs.freedesktop.org/show_bug.cgi?id=70389 --- Comment #1 from Kevin Murphy <kemurphy.cmu at gmail.com> --- Also experiencing this on a Thinkpad T530 running Arch with kernel 3.11.6. 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21f5 Control: I/O+ Mem+

https://bugs.freedesktop.org/show_bug.cgi?id=70389 --- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> --- Try updating your intel ddx -- nouveau is not responsible for the contents of the images it renders when in reverse-prime mode -- the primary gpu is (in your case, intel). -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=70389 Christopher M. Penalver <christopher.m.penalver at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from

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

I'm having a problem with both the 5.8 and 5.9 kernels using the nouveau DRM driver. I have a laptop with a VGA card (specs below) connected to a 5120x1440 screen. At boot time, the card correctly detects the screen, tries to allocate fbdev fb0, then the video hangs completely for 15-30 seconds until it goes blank. This used to work in Linux 5.7 and earlier, although it allocated a 3840x1080

I have an ASUS UX50V laptop with a "NVIDIA Corporation: G98M [GeForce G 105M]" video card. Linux Mint 18.1 64-bit is installed with xserver-xorg-video-nouveau 1:1.0.12-1build2. The Nouveau driver does not seem to be recognizing my HDMI monitor that's plugged in. Here's the output of xrandr: Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767 LVDS1 connected

I am trying to get the screen capture to work from command line (remotely). I am getting the wrong screen shot. This is what xrandr is giving me... xrandr --query Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right

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

This xrandr output only represents outputs on your Intel iGPU, not your NVIDIA G98 dGPU. You may find reading http://nouveau.freedesktop.org/wiki/Optimus instructional. Cheers, -ilia On Thu, Dec 29, 2016 at 8:48 PM, Terra Frost <terrafrost at gmail.com> wrote: > I have an ASUS UX50V laptop with a "NVIDIA Corporation: G98M [GeForce G > 105M]" video card. Linux Mint 18.1

On Thu, Jan 12, 2017 at 3:51 AM, Sylvain Fabre <sylvain at lahiette.com> wrote: > xrand > > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 > eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y > axis) 344mm x 194mm > 1920x1080 60.02*+ 47.99 > 1400x1050 59.98 > 1280x1024 60.02 > 1280x960 60.00

https://bugs.freedesktop.org/show_bug.cgi?id=99841 Bug ID: 99841 Summary: Switching to VT freezes X only on a dual screen Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks

Hi, all -- Here's a small patch that gives better diagnostics on the daemon side if it fails to start up due to inability to create or bind the socket. Presently, it gives a log entry indicating that no sockets could be bound, but crucially does *not* have the system error message (i.e. errno) from the failed call, making it difficult or impossible to determine the problem. I do have a

Hi, Distribution: openSUSE 42.2 Beta, Kernel: 4.4. The box is a Dell Precision T7500 with an nVidia Quadro 4000 card and a displayport connected iiyama B2783QSU 2560x1440 monitor identified as DP-1. Problem: The monitor is detected as 1920x1080 and not 2560x1440. See Xorg log file at http://rogerprice.org/Xorg.0.log . There is no file /etc/X11/xorg.conf and in the directory

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

https://bugs.freedesktop.org/show_bug.cgi?id=100139 Bug ID: 100139 Summary: [DRI2][PRIME] nouveau driver cannot find any connected connector Product: Mesa Version: 10.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi, Matthew -- Regarding your message of 05-Jul-2005 concerning rsync memory usage (sorry that I am not directly replying to it; I am not as yet subscribed to the list and my mailer doesn't allow me to hard-code an In-Reply-To or References header): While I applaud anyone who wants to encourage open-source development, it seems to me that, if in fact your problem is that you are running out

https://bugs.freedesktop.org/show_bug.cgi?id=101404 Bug ID: 101404 Summary: GTX 970M (GM204-A) not powered off when not in use (DynPwr in stead of DynOff) Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=92192 Bug ID: 92192 Summary: nouveau does not detect monitor native resolution Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at