search for: aloew

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]$...

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:...

...NV_ERROR(drm, "failed to initialise sync subsystem, %d\n", ret); but the result is that after the GUI login screen (gdm) which works fine, I get a complete hang when GNOME starts up using compiz (cannot even switch to a text vt any more) and lots of the following output: Dec 15 23:23:05 aloew-lap kernel: nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - ch 4 [compiz[4637]] subc 0 mthd 0x0018 data 0x00000002 Dec 15 23:23:05 aloew-lap kernel: nouveau E[ PFB][0000:01:00.0] trapped write at 0x0000000114 on channel 0x0000f949 [unknown] PFIFO/PFIFO_READ/SEMAPHORE reason: PT_NOT_PRESENT Dec...

...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 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...

...--- 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]$ ./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...

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-m...

...m 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 ./nvapeek 154c 0000154c: 0000009c [aloew at aloew-lap nva]$ sudo ./nvapeek 1540 00001540: b1010001 Looking at the patch you provided, if the rusty binary arithmetics chip in my brain is still valid, this means for my case: vdec = nv_rd32(device, 0x1540) & 0x40000000;...

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! [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...

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 attachment was scrubbed... URL: <http://lists.freedesktop.org/archi...