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 #35 from Andreas Loew <awl1 at gmx.net> --- Follow-up question note that I am digging deeper into git... ;-) >From the commits in the v3.4..v3.5 range, only two of them: 9bd0c15fcfb42f6245447c53347d65ad9e72080b (dated Jun 26, 2012) and e9bf5f36b09f8ec6c168ef58ee7d4890545ede1c (dated Jun 27) when looking at the global

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 #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 #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 #19 from Andreas Loew <awl1 at gmx.net> --- Hello, I would like to join discussions in this bug, as I have found myself affected after the recent update from Red Hat Enterprise Linux/Oracle Linux 6.4 (stock RHEL kernel 2.6.32-358.23.2) to RHEL/OL 6.5 (RHEL kernel 2.6.32-431). My graphics card is NVidia Quadro NVS 130M: BOOT0

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #20 from Andreas Loew <awl1 at gmx.net> --- Had been missing my "lspci -nnvv" information: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro NVS 130M] [10de:042a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0002] Control: I/O+ Mem+

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #46 from Ilia Mirkin <imirkin at alum.mit.edu> --- Well, given that it doesn't work on the blob makes it sound like you have some sort of funkiness in your hardware. One unsubstantiated theory is that the vdec clock is *disabled*, and pcrypt is hooked up to that clock. Or perhaps that clock is somehow broken. It'd be

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #50 from anakin.cs at gmail.com --- For the reclocking to work on 3.13 you need to apply this patch: http://cgit.freedesktop.org/~darktama/nouveau/commit/?h=devel-pm&id=74556533b2cc3dd787ba9fc8a346177116d1a68e And you can change the performance level with /sys/class/drm/card0/device/pstate (I think the command line options

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

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #25 from Andreas Loew <awl1 at gmx.net> --- Created attachment 90765 --> https://bugs.freedesktop.org/attachment.cgi?id=90765&action=edit dmesg output in debug mode (nouveau.debug=debug) on 3.13-rc3 while the issue was seen -- You are receiving this mail because: You are the assignee for the bug. -------------- next

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #26 from Andreas Loew <awl1 at gmx.net> --- Hi again, sorry, it took longer than needed for me to find my way through compiling recent kernels with rpmbuild and an appropriate spec file. The result of my testing is negative: The bug is still included in the most recent 3.13-rc3 kernel... :-( >From the attached dmesg output

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #72 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #71) > Would 3.12.6 be an appropriate version to apply your updated patch to > successfully? I'm working against, effectively, 3.13-rc8. I'd think it would apply to 3.12, and just about any other semi-recent kernel, but I guess RHEL does

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #47 from Andreas Loew <awl1 at gmx.net> --- Hi - it's me again ;-) > Well, given that it doesn't work on the blob makes it sound like you have some > sort of funkiness in your hardware. One unsubstantiated theory is that the > vdec clock is *disabled*, and pcrypt is hooked up to that clock. Or perhaps >

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: