search for: 10200c

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 had this idea myself... :-( > > Here are the results as root: > > [aloew at aloew-lap envytools-master]$ sud...

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 aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10 0010200c: SS SS SS SS SS...

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, or is it all good? What does the peek return? (I'm wondering if it's an initialization order issue or something.) What issues are you seeing with the blob driver? I'd also sti...

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: [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 0010200c: SS > We...

...n 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 GitHub: https://github.com/envytools/envytools/archive/master.zip [aloew at aloew-lap nva]$ sudo ./nvapeek 10200c ... [aloew at aloew-lap nva]$ sudo ./nvapoke 10200c 10 [aloew at aloew-lap nva]$ sudo ./nvapeek 10200c ... Maybe now another bug, as we don't seem to get any hex address and/or value output? Please advise if we need to pass any additional parameters to get hex ouput... BR, Andreas -- You a...

...m.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]$ ./nva/nvapeek 10200c > WARN: Can't probe 0000:01:00.0 > PCI init failure! > > [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. > > I'd also still be interested in knowing whether a pr...

...ug.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! [aloew at aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10 WARN: Can't probe 0000:01:00.0 PCI init failure! > and see what's in dmesg? No additional output in dmesg - probably because of the "PCI init failure"... >...

...> [ 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 > FAULT at 0x103d94 > [ 19.026027] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000010 > FAULT at 0x10200c These errors should go away with the patch. > > but also > > [ 18.984164] nouveau E[ PTHERM][0000:01:00.0] unhandled intr 0x00000161 I believe this is unrelated. > > When I use the kernel option nouveau.config=PCRYPT=0 it doesn't eliminate > the errors and X still...