similar to: [Bug 79912] New: Nouveau unuseable with 3 monitors and a geforce GTX 670

https://bugs.freedesktop.org/show_bug.cgi?id=87436 Bug ID: 87436 Summary: INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000 Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=73924 Priority: medium Bug ID: 73924 Assignee: nouveau at lists.freedesktop.org Summary: E[ PDISP][0000:01:00.0] chid 0 mthd 0x0080 data 0x00000000 0x00055080 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

https://bugs.freedesktop.org/show_bug.cgi?id=84203 Priority: medium Bug ID: 84203 Assignee: nouveau at lists.freedesktop.org Summary: HDMI gives no more signal QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jean-louis at dupond.be

In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: Here is a list of engines: DEVICE DMAOBJ PBSP PCE0 PCE1 PCE2 PCRYPT PDISP PFIFO PGRAPH PMPEG PPM PPPP PVP SW Also, in debug: CLIENT I have tried to find a description of those. https://envytools.readthedocs.io/en/latest/ help a bit, but I don't find a

On Mon, 4 Dec 2023 at 05:04, Paul Dufresne <dufresnep at zoho.com> wrote: > > In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: > Here is a list of engines: > DEVICE > DMAOBJ > PBSP > PCE0 > PCE1 > PCE2 > PCRYPT > PDISP > PFIFO > PGRAPH > PMPEG > PPM > PPPP > PVP

I'm running on Sun Blade 2500 with a GeForce 8400 GS PCI. After (maybe?) fixing a few errrors with bo allocation, I'm getting a lot of IB_EMPTY errors, ultimately resulting in a GPU lockup. I don't have any sort of framebuffer visible. After reading dma-pusher.txt, I see "An attempt to submit IB entry with length zero will raise DMA_PUSHER error of type IB_EMPTY." How would

https://bugs.freedesktop.org/show_bug.cgi?id=85160 Bug ID: 85160 Summary: [NV94] INVALID_STATE error, X fails to start on GeForce 9600 GT with dual monitors, kernels 3.18.0-0.rc0.git8.2.fc22.1 onwards Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=71035 Priority: medium Bug ID: 71035 Assignee: nouveau at lists.freedesktop.org Summary: EVO engine failure, probably (not?) related to EDID corruption QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

Hi, I have been using nouveau on my laptop (with GeForce GT 540M card) for a while, and it's been working quite well! Now I am trying to connect my TV using HDMI port, but wasn't so lucky with that. I would like to know the current status of HDMI out support for GF108 (NVC1). I am trying with the latest code from nouveau/master tree (2fee6f5). When I connect the tv, it's not

https://bugs.freedesktop.org/show_bug.cgi?id=90390 Bug ID: 90390 Summary: [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c | 174 ++++++++++++------------ 1 file changed, 88 insertions(+), 86 deletions(-) diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c b/drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c index 2fe14da3..76944c4 100644 --- a/drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c

https://bugs.freedesktop.org/show_bug.cgi?id=92420 Bug ID: 92420 Summary: X crash when with 2nd display connected via Display Port Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component:

Full piglit run with this patch: http://people.freedesktop.org/~mslusarz/chan_owners.txt This patch covers only a small subset of all error messages, so: Not-yet-signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Comments? Ideas? (This commit depends on this one: http://people.freedesktop.org/~mslusarz/0001-drm-nouveau-split-fifo-interrupt-handler.patch ) ---

https://bugs.freedesktop.org/show_bug.cgi?id=51862 Bug #: 51862 Summary: Shader optimizer is extremely slow Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component:

Just like how the P50 will occasionally leave the disp's core channel on before nouveau starts initializing, it will occasionally do the same thing with the rest of the dmac channel in addition to the core channel. Example: [ 1.604375] nouveau 0000:01:00.0: disp: outp 04:0006:0f81: no heads (0 3 4) [ 1.604858] nouveau 0000:01:00.0: disp: outp 04:0006:0f81: aux power -> always [

In this case, no class is available but the bind methods is sent too, so use it to keep track of what channel is 'bound' and find the software class id from it. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- calim can I get a tested-by? drivers/gpu/drm/nouveau/nouveau_software.h | 1 + drivers/gpu/drm/nouveau/nvc0_software.c | 35

On Thu, Feb 2, 2017 at 5:09 PM, Phil Turmel <philip at turmel.org> wrote: > On 02/02/2017 05:01 PM, Ilia Mirkin wrote: > >> Note that a lot of this stuff has been redone for kernel 4.10 to >> conform to atomic modesetting. I wouldn't be surprised if that >> jiggers things around enough to fix your issue. But perhaps not. >> Worth a shot. [As an aside, this

From: Dave Airlie <airlied at redhat.com> The fence code uses the total number of channel ids to allocate a bunch of memory for fencing. This is probably not the best way to do this, but it's hard to fix right now. The GSP code realises it can fit 8 channels into a USERD page, so it claims it can support 256 channels max, but it then allocates channel ids sparsely (0, 8, 16 etc). This

https://bugs.freedesktop.org/show_bug.cgi?id=96968 Bug ID: 96968 Summary: [NVC0] disp: ERROR 7 [INVALID_HANDLE] 00 [] chid 0 mthd 0088 data f000000 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

On Tue, 25 Aug 2020 at 17:21, Alexander Kapshuk <alexander.kapshuk at gmail.com> wrote: > > Since upgrading to linux-next based on 5.9.0-rc1 and 5.9.0-rc2 I have > had my mouse pointer disappear soon after logging in, and I have > observed the system freezing temporarily when clicking on objects and > when typing text. > I have also found records of push buffer errors in