search for: nvapeek

https://bugs.freedesktop.org/show_bug.cgi?id=107325 Bug ID: 107325 Summary: Reported temperature of nvidia card with nouveau driver is wrong Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

...ment (id=49565) --> (https://bugs.freedesktop.org/attachment.cgi?id=49565) vbios After a suspend/resume cycle, my brightness is stuck to some low value which can't be changed with the brightness buttons or nvapoke 0x61c084 0x80000200. Both of these do work before suspend. Output of "nvapeek 0x61c084" (both before and after suspend/resume): 0061c084: 00000401 Attached is /sys/kernel/debug/dri/0/vbios.rom. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=87885 Bug ID: 87885 Summary: Fan speed of Nvidia GeForce 9600GT (G94) constantly too high Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

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 ./nvapeek 154c 0000154c: 0000009c [aloew at aloew-lap nva]$ sudo ./...

...ed to use these tools while a driver is active for a given card. > > All programs except nvalist take an optional -c <card number> parameter. > @@ -13,43 +13,48 @@ by the nvalist program. > > The programs are: > > -nvalist: prints a list of cards > - > -nvapeek <address> [<byte count>]: reads 32-bit MMIO register at <address>. > -If byte count is also given, reads all registers in range [address, address > -+ byte count). > - > -nvapeek8 <address> [<byte count>]: like nvapeek, but does 8-bit MMIO accesses > - &...

https://bugs.freedesktop.org/show_bug.cgi?id=98852 Bug ID: 98852 Summary: Nvidia graphics card fan not running or to slow, danger of overheating Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=107016 Bug ID: 107016 Summary: Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02) Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

...> > 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 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) > [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapoke 10200c 10 > 0010200c: ERR S Oh well. Some sort of error. > [aloew...

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

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 GitHub: https://github.com/envytools/envytoo...

...ed yet. In most cases it's also not recommended to use these tools while a driver is active for a given card. All programs except nvalist take an optional -c <card number> parameter. @@ -13,43 +13,48 @@ by the nvalist program. The programs are: -nvalist: prints a list of cards - -nvapeek <address> [<byte count>]: reads 32-bit MMIO register at <address>. -If byte count is also given, reads all registers in range [address, address -+ byte count). - -nvapeek8 <address> [<byte count>]: like nvapeek, but does 8-bit MMIO accesses - -nvapoke <address> &...

...++++++++++++++----------------------------- 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: -nvalist: prints a list of cards - -nvapeek <address> [<byte count>]: reads 32-bit MMIO register at <address>. -If byte count is also given, reads all registers in range [address, address -+ byte count). - -nvapeek8 <address> [<byte count>]: like nvapeek, but does 8-bit MMIO accesses - -nvapoke <address> &...

...ile a driver is active for a given >> card. >> All programs except nvalist take an optional -c <card number> >> parameter. >> @@ -13,43 +13,48 @@ by the nvalist program. >> The programs are: >> -nvalist: prints a list of cards >> - >> -nvapeek <address> [<byte count>]: reads 32-bit MMIO register at >> <address>. >> -If byte count is also given, reads all registers in range [address, >> address >> -+ byte count). >> - >> -nvapeek8 <address> [<byte count>]: like nvapeek, but...

https://bugs.freedesktop.org/show_bug.cgi?id=80901 Priority: medium Bug ID: 80901 Assignee: nouveau at lists.freedesktop.org Summary: [NVCF] PWM fan speed too high under kernel 3.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: gianni at rootcube.net Hardware: x86-64 (AMD64)

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

...ap 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 SS SS SS SS SS SS SS SS SS SS SS [aloew at aloew-lap envytools-master]$ sudo ./nva/nvapoke 10200c 10 0010200c: ERR S [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 [aloew at aloew-lap e...

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=93887 Bug ID: 93887 Summary: Amilo Xi 3650: G96M [GeForce 9600M GT]: HDMI monitor stays black after s2ram Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

Hi All, So I've been working~w banging my head against the nv46 vblank bug again and I've been finding out some interesting things. This is all using the latest kernel + ddx + mesa code. All of this was tested with *cold* (power removed from wall outlet for 20 seconds) boots in between the scenarios because this is really weird, all boots where into text mode. Scenario 1: a) startx