similar to: Questions about envytools: reading card VBIOS

https://bugs.freedesktop.org/show_bug.cgi?id=92386 Bug ID: 92386 Summary: Integrated sensor on nv43 doesn't work (wrong vbios parsing?) Product: xorg Version: git Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

The entry offset was use instead of the data it points to. Probably a regression. The files showing script parsing errors has been reduced from 410 to 6 with the database of 505 vbios. --- nvbios/mem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nvbios/mem.c b/nvbios/mem.c index 81f2d1b..e4797e3 100644 --- a/nvbios/mem.c +++ b/nvbios/mem.c @@ -232,11 +232,11 @@

Otherwise some values are not tested at all. --- nva/set_timings.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/nva/set_timings.c b/nva/set_timings.c index 6cd831c..7a8f845 100644 --- a/nva/set_timings.c +++ b/nva/set_timings.c @@ -408,7 +408,7 @@ static void iterate_values(struct nvamemtiming_conf *conf, FILE *outf, uint8_t index, enum color color) { uint8_t

--- nva/set_timings.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nva/set_timings.c b/nva/set_timings.c index 7376486..985a707 100644 --- a/nva/set_timings.c +++ b/nva/set_timings.c @@ -506,7 +506,7 @@ shallow_dump(struct nvamemtiming_conf *conf) if (conf->range.start == (unsigned char) -1) conf->range.start = 0; if (conf->range.end == (unsigned char) -1) -

On 25/08/2014 21:00, Christian Costa wrote: > --- > nva/set_timings.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/nva/set_timings.c b/nva/set_timings.c > index 7376486..985a707 100644 > --- a/nva/set_timings.c > +++ b/nva/set_timings.c > @@ -506,7 +506,7 @@ shallow_dump(struct nvamemtiming_conf *conf) > if (conf->range.start ==

- Sort commands by name for easier update - Make more readable - Remove no more existing commands --- nva/README | 81 +++++++++++++++++++++++++++++++++----------------------------- 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:

Hi fellow Nouveau devs and users, Envytools' repository moved to another home yesterday. We fixed as many urls as possible to link to the new repo but there are some links we cannot fix for you. So, please update your envytools repository to use the new repository and no other one. The new repository is https://github.com/envytools/envytools. Here is a summary of what made us move to this

- Sort commands by name for easier update - Make more readable - Remove no more existing commands --- nva/README | 83 +++++++++++++++++++++++++++++++++----------------------------- 1 file changed, 44 insertions(+), 39 deletions(-) diff --git a/nva/README b/nva/README index 625ea7c..d4347c5 100644 --- a/nva/README +++ b/nva/README @@ -3,7 +3,7 @@ registers. WARNING: these tools *can* and

On 11/06/2014 13:59, Roy Spliet wrote: > Dear Mr. Dew, > > I hereby wish to propose the X.org EVoC project "REclock - > Reverse-engineer and implement NVA3/5/8 Voltage- and Frequency Scaling > in Nouveau" for which I am willing to participate, and apply for the > associated funding. Full details below or on > http://nouveau.spliet.org/evoc.html . For any further

On Mon, Aug 25, 2014 at 6:35 PM, Martin Peres <martin.peres at free.fr> wrote: > On 25/08/2014 20:58, Christian Costa wrote: >> >> - Sort commands by name for easier update >> - Make more readable >> - Remove no more existing commands >> --- >> nva/README | 83 >> +++++++++++++++++++++++++++++++++----------------------------- >> 1 file

On 25/08/2014 20:58, Christian Costa wrote: > --- > 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 @@

Le 31/08/2014 15:12, Martin Peres a ?crit : > On 31/08/2014 15:00, Christian Costa wrote: >> Otherwise some values are not tested at all. > I would rather have a warning than the program doing stuff behind my > back. This is a dev tool, dumb == good ;) > But why didn't you call it Dumb mode rather that Deep mode. That way, I wouldn't have tried to use it and figure out

On 11/12/2017 06:29 PM, Martin Peres wrote: > Hello, > > Some users have been complaining for years about their GPU sounding like > a jet engine at take off. Last year, I finally laid my hand on one of > these GPUs and have been trying to fix this issue on and off since then. Some early feedback: can you tell us the exact SKUs you have? And are these production boards with

Hi guys and gals, I'm working on improving nouveau's support for MXM (Mobile PCI Express Module) chips and need some more data to check my implementation. To see if you can help, the first thing to do is jump over to /sys/firmware/acpi/tables and run "grep MXMS *". [root at nisroch tables]# grep MXMS * Binary file DSDT matches [root at nisroch tables]# If this isn't

Am 25.12.2015 um 19:37 schrieb Karol Herbst: > Hi Thomas, > > thanks for trying the branch out. Could you please send me your vbios? > > You can get it through installing envytools and nvagetbios or inside > /sys/kernel/debug/dri/*/vbios.rom > > The lookups can actually happen due to undervolting, my branch just fix the > issue that nouveau doesn't reclock at all.

https://bugs.freedesktop.org/show_bug.cgi?id=40894 Summary: nv30-/temperature: Reverse engineer the temperature coefficients Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

Hello, Some users have been complaining for years about their GPU sounding like a jet engine at take off. Last year, I finally laid my hand on one of these GPUs and have been trying to fix this issue on and off since then. After failing to find anything in the HW, I figured out that the duty cycle set by nvidia's proprietary driver would be way under the expected value. By randomly changing

I'm seeing new VBIOS W messages with 3.19-rcX+ on this workstation's FX570: [ 1.960786] nouveau W[ VBIOS][0000:02:00.0] M0203T not found [ 1.960848] nouveau W[ VBIOS][0000:02:00.0] M0203E not matched! Let me know if you want more info. Regards, Peter Hurley [1] nouveau/drm dmesg [ 1.766737] [drm] Initialized drm 1.1.0 20060810 [ 1.828516] nouveau [

On 25/03/2014 17:17, Christian Zander wrote: > On Mon, Mar 24, 2014 at 11:59:46AM -0700, Martin Peres wrote: >> Hello, >> >> One of my GPU (GK107/NVE7) fails to properly fetch its vbios from PROM >> at boot time but, if I blacklist the module and load it myself later on, >> it always succeeds. To make things weirder, the same card works great on >> another

Hi Martin, I was asked to clarify a few things: (1) Are all the user reports of loud fans on Fermi-era GPUs? (2) When the VBIOS POSTs the card, it loads initial ucode onto the Falcon processor (PMU), which will do basic fan management on its own. We call this init ucode "IFR" (Init From ROM). nvidia.ko will restore the IFR ucode when unloaded. I assume the loud fan symptom occurs