similar to: [Bug 58378] [NV86] Distorted graphics on NVIDIA GeForce 8400M G after upgrade the kernel to 3.7.0 version

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #37 from Andreas Loew <awl1 at gmx.net> --- Hello again, Ilia, ok, I see - did some further reading and I think I now fully understand the way it works: This also means that you are NOT regularly pulling the updates from Linus' central git into the nouveau git, but typically only do this ONCE after Linus released a new

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #34 from Andreas Loew <awl1 at gmx.net> --- Bad news once again... I applied the following single-line patch to a stock 3.12.4 kernel in order to switch to the NV50 fence: diff -Nrpu linux-3.12.4.orig/drivers/gpu/drm/nouveau/nouveau_drm.c linux-3.12.4/drivers/gpu/drm/nouveau/nouveau_drm.c ---

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #31 from Ilia Mirkin <imirkin at alum.mit.edu> --- You really need to figure out how to do things inside the git tree and not do some sort of crazy export. That will speed things up by an order of magnitude. To get the list of nouveau changes between 3.4 and 3.5: git log v3.4..v3.5 -- drivers/gpu/drm/nouveau To do a bisect

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #39 from Andreas Loew <awl1 at gmx.net> --- > You really want to be doing a git bisect to do the least amount of work; I > don't see what you mean by "move forward" but I really hope that you are > testing the commits in a binary tree style. Yup. Indeed, I am trying to use a "binary" approach to

https://bugs.freedesktop.org/show_bug.cgi?id=58378 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Distorted graphics on |[NV86] Distorted graphics |NVIDIA GeForce 8400M G |on NVIDIA GeForce 8400M G

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #29 from Andreas Loew <awl1 at gmx.net> --- OK, finally I have some more encouraging news: It now looks like the issue indeed started much earlier than initially thought, namely already between the 3.4 and 3.5 kernel series!!! Results from my testing with stock kernels obtained from kernel.org (I've never ever before

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #77 from Andreas Loew <awl1 at gmx.net> --- Sorry that it took me longer to get back here - I needed an additional rpmbuild run due to running out of disk space for my first attempt... But I can give an all clear signal - at least for my machine, AFAIK, everything seems to be fine: Kernel command line: ro

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #43 from Andreas Loew <awl1 at gmx.net> --- Hello again, so it looks like I have now tracked the issue down. The "offending" commit seems to be: 4c193d254ee94da02857b9670e815b1765a9579b (the first commit which showed the issue - I tried for more than half an hour with its direct predecessor

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #45 from Andreas Loew <awl1 at gmx.net> --- Hmm... While my card definitely is not at all defective (it works the exact same way it always has), I indeed also have some issues that make it impossible for me to still use the "blob" even on an attic distro like RHEL6: The most recent version of the NVidia proprietary

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #58 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10 > > 0010200c: SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS > > nvapeek 10200c without the 10. (Not sure what that does.... maybe reads out > 0x10 regs) yes - seems to read 10 registers:

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #66 from Andreas Loew <awl1 at gmx.net> --- A Happy New Year to everybody! :-) Just wondering whether you intend to simply close this issue down with the workaround "solution" for me to set kernel option nouveau.config=PCRYPT=0 or whether you are still interested in finding out *why* my Quadro NVS 130M and other

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #28 from Andreas Loew <awl1 at gmx.net> --- This gets really interesting now: Oracle public yum "playground" 3.6.11-3.6.y.20121225.ol6 (should be stock kernel 3.6.11) does NOT show any hangs, but DOES INDEED ALREADY show the graphics corruption issue FOR ME (although it was thought by the original posters here that it

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #17 from Andreas Loew <awl1 at gmx.net> --- Created attachment 90715 --> https://bugs.freedesktop.org/attachment.cgi?id=90715&action=edit Distorted graphics with RHEL6/OL6 showing uname -a kernel 3.12.4 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #18 from Andreas Loew <awl1 at gmx.net> --- Created attachment 90717 --> https://bugs.freedesktop.org/attachment.cgi?id=90717&action=edit Distorted graphics: Icons (on kernel 3.12.4) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #80 from Thomas <tomshere at t-online.de> --- Hello, I have the same NVIDIA GeForce NVS 130M with the disabled functions. I checked with nvapeek: 0000154c: 0000009c 00001540: b1010001 uname -a delivers Linux mobuntu 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I do not have any

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #81 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #80) > Hello, > > I have the same NVIDIA GeForce NVS 130M with the disabled functions. > I checked with nvapeek: > 0000154c: 0000009c > 00001540: b1010001 > > uname -a delivers > Linux mobuntu 3.11.0-15-generic #23-Ubuntu SMP Mon

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #21 from Ilia Mirkin <imirkin at alum.mit.edu> --- (a) Can we see a full boot log (e.g. output of dmesg) with a recent kernel? Ideally it would include the time that the visual issues happen. (b) This looks like it could be a fencing issue, i.e. we try to draw to a texture, but then instead of waiting, we don't wait. There

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #22 from Andreas Loew <awl1 at gmx.net> --- Hello Ilia, regarding (a) and (b): I am just waiting for a rpmbuild of an OL6 version of 3.13-rc3 to finish and will report back on my findings and include a dmesg output from that version. Regarding (c): Would'nt it make more sense than starting with 3.6 release and 3.7 release

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #23 from Ilia Mirkin <imirkin at alum.mit.edu> --- The mega-commit is ebb945a94bba2ce8dff7b0942ff2b3f2a52a0a69. So you could check out ebb945a94bba^ and see if it works, and then test ebb945a94bba to see if it doesn't. In either case, you could use those as your new "good" or "bad" starting points. You

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #24 from Andreas Loew <awl1 at gmx.net> --- Created attachment 90764 --> https://bugs.freedesktop.org/attachment.cgi?id=90764&action=edit dmesg output on 3.13-rc3 while the issue was seen -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML