similar to: [Bug 61069] New: Crash while displaying large image

https://bugs.freedesktop.org/show_bug.cgi?id=92863 Bug ID: 92863 Summary: Complete freeze even with NvGrUseFW=1 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau

Hi there, I have just decided to try this new driver stuff (used 2.6.27 earlier and a proprietary nvidia driver) but the monitor (Samsung 214T) becomes black and the power LED starts flashing (standby) after loading nouveau module (from a fresh 2.6.33). For now I am trying framebuffer only. The monitor is connected with a single link DVI cable. lspci -nn 03:00.0 VGA compatible controller

https://bugs.freedesktop.org/show_bug.cgi?id=69349 Priority: medium Bug ID: 69349 Assignee: nouveau at lists.freedesktop.org Summary: Random image corruptions (in Debian Wheezy with Linux 3.2) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

Hi, I am trying to use a G94GL based card (Quadro FX1800) on an arm64/aarch64 based board. As the board is running linux-4.1.8, I had to apply the following patches to get the kernel module / drm working: https://lkml.org/lkml/2015/5/15/83 https://lists.freedesktop.org/archives/dri-devel/2015-July/085449.html So far everything seems to work, the card modesets correctly, and the kernel log also

http://bugs.freedesktop.org/show_bug.cgi?id=20341 Summary: NV31 lockup Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: detringj at

https://bugs.freedesktop.org/show_bug.cgi?id=110830 Bug ID: 110830 Summary: [nouveau] GeForce GTX 1660 Ti (mobile) not supported (NV168/TU116) Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

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

I'm trying to put to work the nouveau driver on slackware 64 bits current, kernel 4.4.*. I've thought the hardware to be some obscure OEM variant of GT610. However, kind soul on IRC pointed out that it's a G98 really, 'GeForce 9300 GS or 8400 GS'. Proprietary NVIDIA drivers: * 340.96 installs okay, console works, but X doesn't start, with unspecified error occuring

On 07/05/2017 23:50, Ilia Mirkin wrote: > You have two issues: > > (a) nouveau's GL driver messed something up, causing a read fault error > (b) nouveau's kernel driver tried to recover. It failed. > > Solution to #1: None, really. You can try updating mesa, and hope it > helps. Not sure what version you're on. Here's my packages version: ii

https://bugs.freedesktop.org/show_bug.cgi?id=49397 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aplattner at nvidia.com |nouveau at lists.freedesktop.o | |rg

https://bugs.freedesktop.org/show_bug.cgi?id=85495 Bug ID: 85495 Summary: nouveau: xft fonts not rendered on Dell M4800 (QHD+) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hello I recently switched from Nvidia binary driver to Nouveau. I have encountered a possible bug in the kernel module. Before I file a bug report I would like to know if this is a known issue or not. I believe it is related to sleep state and power management of the driver. The Bug: When the computer is left on it's own to go to a power save mode X takes 100% CPU-time in its thread. A

http://bugs.freedesktop.org/show_bug.cgi?id=21273 Summary: Driver can't detect video output and xserver doesn't start Product: xorg Version: git Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

My new GTX 960 (GM206, I think) says: [ 10.329351] nouveau ![ DEVICE][0000:09:00.0] unknown Maxwell chipset [ 10.329355] nouveau E[ DEVICE][0000:09:00.0] unknown chipset, 0x126010a1 [ 10.329356] nouveau E[ DRM] failed to create 0x00000080, -22 [ 10.330129] nouveau: probe of 0000:09:00.0 failed with error -22 Hacking up nouveau so that it treats it like a GM204 doesn't work. Are

https://bugs.freedesktop.org/show_bug.cgi?id=77494 Priority: medium Bug ID: 77494 Assignee: nouveau at lists.freedesktop.org Summary: [NVE7] fails to load due to unknown opcode 0xc4 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mpredosin at

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:

Hello Ilia, > > [ 7.569394] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x0ac080b1 > > [ 7.569460] nouveau [ DEVICE][0000:02:00.0] Chipset: MCP79/MCP7A (NVAC) > > [ 7.569530] nouveau [ DEVICE][0000:02:00.0] Family : NV50 > > [ 7.571151] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image... > > [ 7.633082] nouveau [ VBIOS][0000:02:00.0]

https://bugs.freedesktop.org/show_bug.cgi?id=49786 Bug #: 49786 Summary: In xterm, some rectangles are not redrawn when the window is partly covered Classification: Unclassified Product: xorg Version: 7.6 (2010.12) Platform: Other OS/Version: All Status: NEW Severity: normal

https://bugs.freedesktop.org/show_bug.cgi?id=91779 Bug ID: 91779 Summary: MacBookPro3,1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...