search for: gf108

Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/203 Fixes: 5728d064190e1 ("drm/nouveau/fb: handle sysmem flush page from common code") Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/gf108.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/gk104.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/gk110.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/gm107.c | 1 + 4 files changed, 4 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/gf108.c b/drivers/gpu/drm/nouveau/nvkm/sub...

https://bugs.freedesktop.org/show_bug.cgi?id=64772 Priority: medium Bug ID: 64772 Assignee: nouveau at lists.freedesktop.org Summary: nouveau GF108 kernel errors and graphics corruption when enabling second output QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: pasik at iki.fi Hardware: Other Status: NE...

Hi All, I'm having this really weird issue with broken hotplug on a Dell Latitude E6430 with hybrid gfx, with a gf108 as discrete GPU. The LCD panel and VGA are connected through a mux to the iGPU, but the HDMI is only connected to the nvidia dGPU. Plugging in a HDMI monitor when the dGPU is suspend works fine, the ACPI event fires and everything works as it should. Unplugging the HDMI OTOH, or plugging it in wh...

...performing the copy. It has a variety of limitations (e.g., >> > cannot handle blocklinear format), and was only in a few Fermi chips, >> > as I understand it. >> >> According to our driver source, GF100, GF104, GF110, GF114, and GF116 >> all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only >> had problems reported against GF116... and only for some people. > > Hmm, some of our internal documentation is inconsistent about whether it > applies to GF100, but otherwise what I see matches your list. I guess > "few&qu...

https://bugs.freedesktop.org/show_bug.cgi?id=39330 Summary: nVidia GF108 [Quadro 1000M] gives: "PGRAPH: unsupported chipset, please report!" Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium...

...erforming LZO decompression as > part of performing the copy. It has a variety of limitations (e.g., > cannot handle blocklinear format), and was only in a few Fermi chips, > as I understand it. According to our driver source, GF100, GF104, GF110, GF114, and GF116 all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only had problems reported against GF116... and only for some people. > > It is probably easiest to just ignore it. You can distinguish this > decompress engine from normal copy engine by looking at the CE capability > register on falcon (0x...

https://bugs.freedesktop.org/show_bug.cgi?id=86794 Bug ID: 86794 Summary: Several nouveau related errors with xf86-video-nouveau with NVIDIA G92 [GeForce 9800 GT] and GF108 [GeForce GT 620] (rev a1). Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at l...

...few more lines of the dump (see console-output.txt). dmesg output attached. My bitmap is 720x512. Below is the library versions, and amount of vram. Any feedback is appreciated. Thanks. Steve [steve at localhost ~]$ lspci -nn -d 10de: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GF108 High Definition Audio Controller [10de:0bea] (rev a1) [steve at localhost ~]$ rpm -qa | grep libdrm libdrm-2.4.60-3.el7.x86_64 libdrm-devel-2.4.60-3.el7.x86_64 [steve at localhost ~]$ rpm -qa | grep mesa m...

...blob apparently doesn't use the result of S2R Rx, SR_INVOCATION_ID wholesale in TCS. It either passes it through a I2I.S32.S32 Rx, |Rx| (i.e. absolute value), or even more paradoxically, shl 2; shr 2; which removes the top *2* bits, rather than just the top 1. However I see no such behaviour on GF108. I'm going to test out tomorrow whether this is the cause of my GK208 woes. On Fri, May 22, 2015 at 5:10 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Mon, May 18, 2015 at 4:48 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> Hello, >> >> I've b...

https://bugs.freedesktop.org/show_bug.cgi?id=103467 Bug ID: 103467 Summary: [NVC0/GF108] fifo: read fault at cd90f4d000 engine 07 [PFIFO] client 07 [BAR_READ] reason 00 [PT_NOT_PRESENT] on channel 1 [003fe11000 DRM] Product: xorg Version: 7.7 (2012.06) Hardware: PowerPC OS: All Status:...

...> > part of performing the copy. It has a variety of limitations (e.g., > > cannot handle blocklinear format), and was only in a few Fermi chips, > > as I understand it. > > According to our driver source, GF100, GF104, GF110, GF114, and GF116 > all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only > had problems reported against GF116... and only for some people. Hmm, some of our internal documentation is inconsistent about whether it applies to GF100, but otherwise what I see matches your list. I guess "few" was not entirely ac...

...has a variety of limitations (e.g., > >> > cannot handle blocklinear format), and was only in a few Fermi chips, > >> > as I understand it. > >> > >> According to our driver source, GF100, GF104, GF110, GF114, and GF116 > >> all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only > >> had problems reported against GF116... and only for some people. > > > > Hmm, some of our internal documentation is inconsistent about whether it > > applies to GF100, but otherwise what I see matches your list. I gue...

...of limitations (e.g., >>>>> cannot handle blocklinear format), and was only in a few Fermi chips, >>>>> as I understand it. >>>> >>>> According to our driver source, GF100, GF104, GF110, GF114, and GF116 >>>> all have it. [So GF106, GF108, GF117, GF119 don't have it.] We've only >>>> had problems reported against GF116... and only for some people. >>> >>> Hmm, some of our internal documentation is inconsistent about whether it >>> applies to GF100, but otherwise what I see matches your...

....txt). dmesg output attached. > > My bitmap is 720x512. Below is the library versions, and amount of vram. > > Any feedback is appreciated. > > Thanks. > Steve > > [steve at localhost ~]$ lspci -nn -d 10de: > 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) > 01:00.1 Audio device [0403]: NVIDIA Corporation GF108 High Definition Audio Controller [10de:0bea] (rev a1) > > [steve at localhost ~]$ rpm -qa | grep libdrm > libdrm-2.4.60-3.el7.x86_64 > libdrm-devel-2.4.60-3.el7.x86_64 > > [steve at lo...

https://bugs.freedesktop.org/show_bug.cgi?id=79266 Priority: medium Bug ID: 79266 Assignee: nouveau at lists.freedesktop.org Summary: (two) GT 430 / GF108 sluggish, unstable performance and blue tint with vdpau QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter: afasdfsdfaa at master.ms Hardware: x86-64 (AMD64)...

Hello, There's a long-standing bug on nouveau (this is a sample bug, but the issue has been around for a while: https://bugs.freedesktop.org/show_bug.cgi?id=85465) whereby we attempt to use the second PCOPY engine on GF116, and it is sometimes does nothing, despite mmio register 22500 saying that it's not disabled (0x22500 == 0 for this user). In the bug you can see a dump from

...might help identify potential issues that >> were fixed. > > Greetings, > Here is the lspci info. I will try and grab the kernel versions from the > discs tomorrow (I left them at work). > Thanks! > ~Stack~ > >> 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [Quadro >> 1000M] (rev a1) (prog-if 00 [VGA controller]) GF108 (NVC1) had some issues for a kernel release or two (3.11 and 3.12 iirc). The fix was backported to the -stable kernels, but who knows whether the livecd you're trying has the relevant fixes or not :( -ilia

--- man/nouveau.man | 9 ++++++++- src/nv_driver.c | 8 ++++++-- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/man/nouveau.man b/man/nouveau.man index 07d53c8..4878f24 100644 --- a/man/nouveau.man +++ b/man/nouveau.man @@ -63,7 +63,14 @@ GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119 GK104, GK106, GK107, GK110, GK208 .TP 22 .B GeForce GTX 750 -GM107 +GM107, GM108 +.TP 22 +.B GeForce GTX 9XX +GM200, GM204, GM206 +.TP 22 +.B GeForce GTX 10XX +GP102, GP104, GP106, GP107, GP108 + .SH CONFIGURATION DETAILS Please refer to __xconfigfile__(__f...

Hello, I've been debugging a few different tessellation shader issues with nouveau, but let's start small. I see this issue on my GK208 with high frequency, and I *think* I've seen it once or twice on my GF108, but it's exceedingly rare, if it does happen. I don't have a GK10x to test on, unfortunately, but I assume it'll have the same issue as the GK208. The issue is this -- a bunch of triangles that should come out of the tessellator end up black. I also see a GPC0/TPC1/MP trap: MEM_OUT_OF...

Hi, I am getting a crash in nouveau in my application. It's basically a java application, and I am loading a bitmap into an opengl texture and showing it in a panel. Below is a snippet of the console output. Sometimes I will get a lock up instead of a crash. My whole desktop will lock up, but I can still move the mouse pointer around. Please let me know if you need more information. Your