search for: nvapok

...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> <value>: writes a 32-bit <value> to the MMIO register at > -<address>. > - > -nvapoke8 <address> <value>: like nvapoke, but does 8-bit MMIO access > - > -nvawatch [-t] <address>: reads MMIO register at <address> in a loop, pr...

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=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)

...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> <value>: writes a 32-bit <value> to the MMIO register at -<address>. - -nvapoke8 <address> <value>: like nvapoke, but does 8-bit MMIO access - -nvawatch [-t] <address>: reads MMIO register at <address> in a loop, prints -the value every tim...

...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> <value>: writes a 32-bit <value> to the MMIO register at -<address>. - -nvapoke8 <address> <value>: like nvapoke, but does 8-bit MMIO access - -nvawatch [-t] <address>: reads MMIO register at <address> in a loop, prints -the value every tim...

...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> <value>: writes a 32-bit <value> to the MMIO register >> at >> -<address>. >> - >> -nvapoke8 <address> <value>: like nvapoke, but does 8-bit MMIO access >> - >> -nvawatch [-t] <address>: reads MMIO register at...

--- rnndb/memory/nvc0_pbfb.xml | 37 ++++++++++++++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/rnndb/memory/nvc0_pbfb.xml b/rnndb/memory/nvc0_pbfb.xml index 500cea9..e006dbe 100644 --- a/rnndb/memory/nvc0_pbfb.xml +++ b/rnndb/memory/nvc0_pbfb.xml @@ -49,23 +49,54 @@ Most bitfields are unknown. </doc> <bitfield high="7"

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

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

...ut is set to 0x84 after a resume. It appears there's an init script in the bios dump which sets it to the value of 0x84. I have confirmed if I use the nouveau option nouveau.config=NvForcePost=1 that the behavior after booting is the same as after a resume. The value of 0x61c080 is 0x84. If I `nvapoke 0x061c080 0x1` after a resume the backlight seems to work fairly well. I created patch to test this. I expect it isn't the proper solution. I'm attaching the dmesg which includes a resume with the nouveau driver. I'll also attach the vbios dump, acpidump, dmidecode, lspci, I've...

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

...ied latest nouveau drivers I have no backlight control. Modifying nouveau_backlight.c adding a case for NV_DEVICE_INFO_V0_PASCAL I finally get /sys/class/backlight/nv_backlight/ but changing the backlight value in there is not working anyway. Trying to manually poke NV50_PDISP_SOR_PWM_CTL(1) with `nvapoke` has no effect whatsoever on the brightness (on or==1) Backlight control is not working using the proprietary 375 / 378 drivers either. Also in this case the value of NV50_PDISP_SOR_PWM_CTL is actually changed by `xbacklight` but with no visible effect. Any hint? -- You are receiving this mail...

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 still be i...

.../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 previously-known-good > > version of the blob still works. > > I am 99.9% certain it does, as my Windows install w...

...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 are receiving this mail because: You are the...

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 mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20131219/2a4cb...

...+++ b/nva/.gitignore @@ -1,39 +1,40 @@ +evotiming +libnva.a +libnva.so +nv01dump +nv01post +nvacounter +nvadownload +nvaevo +nvafakebios nvafill +nvaforcetemp +nvafucstart +nvafuzz +nvagetbios +nvagetpmu nvahammer nvalist +nvamemtiming +nvammiotracereplay nvapeek +nvapeeki nvapeekstat +nvapms nvapoke -nvapeeki -nvagetbios -nvafakebios +nvapy.c +nvapy.so nvascan +nvaspyi2c +nvastrscan nvatiming -nvapms -nvafuzz +nvaupload +nvavucstart nvawatch -nvacounter -nvastrscan -nvaevo -nvaxttime -nvaxtstart +nvaxtinsn nvaxtpeek nvaxtpoke nvaxtrsr nvaxtssr -nvaxtinsn -nvaupload -nvadownload -evotim...

...n 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"... > Do you see additional MMIO read/write failures, or is it > all good? What does the peek return? (I...

--- nvbios/nvbios.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/nvbios/nvbios.c b/nvbios/nvbios.c index f7aafe3..28e62ad 100644 --- a/nvbios/nvbios.c +++ b/nvbios/nvbios.c @@ -774,11 +774,12 @@ int set_strap_from_string(const char* strap_s) int set_strap_from_file(const char *path) { FILE *strapfile = NULL; - char tmp[21]; + char tmp[22]; strapfile =

https://bugs.freedesktop.org/show_bug.cgi?id=37922 Summary: NV86: too high power usage. Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: maximlevitsky