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 #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 #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 #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 #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 #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 #69 from Andreas Loew <awl1 at gmx.net> --- > 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... OK - that might indeed explain the issues seen... Here you are: [aloew at aloew-lap nva]$ sudo

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 >

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #44 from Ilia Mirkin <imirkin at alum.mit.edu> --- Try commenting the same line out and see what happens... (i.e. the one with 0x74c1) FWIW I do remember seeing some PCRYPT-related (and PVP/PBSP-related) errors on start in the form of MMIO write failures in your log and thinking it odd: nouveau E[ PBUS][0000:01:00.0] MMIO

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 #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 --- 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 #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 #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 #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 #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 #68 from Ilia Mirkin <imirkin at alum.mit.edu> --- Created attachment 91714 --> https://bugs.freedesktop.org/attachment.cgi?id=91714&action=edit patch to honor disabled engines Give this a shot (without forcing PCRYPT=0). You should hopefully see a message saying that it and a few other engines are disabled. This needs