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 #57 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #55) > > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > > WARN: Can't probe 0000:01:00.0 > > > PCI init failure! > > > You need to run these as root. > > Ouch - sorry - could have indeed

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #55 from Andreas Loew <awl1 at gmx.net> --- > > [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 > > WARN: Can't probe 0000:01:00.0 > > PCI init failure! > You need to run these as root. Ouch - sorry - could have indeed had this idea myself... :-( Here are the results as root: [aloew at

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #60 from Andreas Loew <awl1 at gmx.net> --- > There was a bug in nvapeek/poke (it was using the wrong address space by > default), can you update your pull and try again? [That explains why you saw > 'S' in the output.] Of course - here you are: The version I used is from the "Download ZIP" button in

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 #54 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #52) > Hello again, Ilia, > > > Can you grab envytools (https://github.com/envytools/envytools) and run > > bad news (or maybe expected from what we have been seeing earlier): > > [aloew at aloew-lap envytools-master]$

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #52 from Andreas Loew <awl1 at gmx.net> --- Hello again, Ilia, > Can you grab envytools (https://github.com/envytools/envytools) and run bad news (or maybe expected from what we have been seeing earlier): [aloew at aloew-lap envytools-master]$ ./nva/nvapeek 10200c WARN: Can't probe 0000:01:00.0 PCI init failure!

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #62 from Andreas Loew <awl1 at gmx.net> --- But generally, nvapeek seems to work fine now: [aloew at aloew-lap nva]$ sudo ./nvapeek 0 00000000: 086a00a2 Looking forward to your comments... BR, Andreas -- 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 #82 from Andreas Loew <awl1 at gmx.net> --- Hi Thomas, > I have the same NVIDIA GeForce NVS 130M with the disabled functions. > I checked with nvapeek: > 0000154c: 0000009c > 00001540: b1010001 great - finally somebody who confirms this issue. > uname -a delivers > Linux mobuntu 3.11.0-15-generic #23-Ubuntu

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 #67 from Ilia Mirkin <imirkin at alum.mit.edu> --- Could you provide the output of nvapeek 154c nvapeek 1540 Those registers specify which engines are there. I think we're ignoring them in nouveau... -- 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 #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 #51 from Ilia Mirkin <imirkin at alum.mit.edu> --- So actually I'm told that pcrypt is on the main clock, so that theory is out. Can you grab envytools (https://github.com/envytools/envytools) and run nvapeek 10200c nvapoke 10200c 10 nvapeek 10200c and see what's in dmesg?Do you see additional MMIO read/write failures,

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #59 from Ilia Mirkin <imirkin at alum.mit.edu> --- There was a bug in nvapeek/poke (it was using the wrong address space by default), can you update your pull and try again? [That explains why you saw 'S' in the output.] -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #61 from Andreas Loew <awl1 at gmx.net> --- Hmm... Looking at the code for nvapeek, I fear that nva_rd(...) still did not return any meaningful data, as it look like we get s == 0...!? int s = 0; for (i = j = 0; i < 16 && i < b; i+=rs.regsz, j++) { e[j] =

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #65 from Andreas Loew <awl1 at gmx.net> --- Oops - I just remembered that I am booting my kernel with "nouveau.config=PCRYPT=0" in the meantime... Does this make any difference, i.e. do I need to retry the nvapeek/nvapoke sequence without this kernel option? Sorry & thanks, Andreas -- You are receiving this

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #85 from Thomas <tomshere at t-online.de> --- (In reply to comment #82) > > I also have these errors in dmesg > > > > [ 18.985158] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 > > FAULT at 0x00fd94 > > [ 18.986213] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 >

- Sort commands by name for easier update - Make more readable - Remove no more existing commands --- nva/README | 83 +++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 44 insertions(+), 39 deletions(-) diff --git a/nva/README b/nva/README index 625ea7c..d4347c5 100644 --- a/nva/README +++ b/nva/README @@ -3,7 +3,7 @@ registers. WARNING: these tools *can* and

- Sort commands by name for easier update - Make more readable - Remove no more existing commands --- nva/README | 81 +++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 43 insertions(+), 38 deletions(-) diff --git a/nva/README b/nva/README index 625ea7c..cbe6ae3 100644 --- a/nva/README +++ b/nva/README @@ -13,43 +13,48 @@ by the nvalist program. The programs are:

On Mon, Aug 25, 2014 at 6:35 PM, Martin Peres <martin.peres at free.fr> wrote: > On 25/08/2014 20:58, Christian Costa wrote: >> >> - Sort commands by name for easier update >> - Make more readable >> - Remove no more existing commands >> --- >> nva/README | 83 >> +++++++++++++++++++++++++++++++++----------------------------- >> 1 file