similar to: Envytools moved to another home, please update your git repos!

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

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

To whom it may concern I hope here is the right place to ask about envytools. I am working on securing our GPUs in the case of an OpenStack infrastructure, where GPUs can be bound and unbound to VMs from different clients. I wanted to use envytools to retrieve the VBIOS our cards, then check after each VM deletion if somebody changed the VBIOS (potentially a threat). The VBIOS would be read

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

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:

On 29 July 2015 at 22:20, Ben Pye <ben at curlybracket.co.uk> wrote: > Not sure if you got the other message, I think I managed to split the topic > as I wasn't subscribed to receive the previous message. This error has been > on the Raspberry Pi 2, so that's a Cortex A7 I believe, certainly ARMv7. Excellent! > I > haven't yet built trunk as on the device I run

--- rnndb/nv50_pgraph.xml | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/rnndb/nv50_pgraph.xml b/rnndb/nv50_pgraph.xml index 92d69ea..6499631 100644 --- a/rnndb/nv50_pgraph.xml +++ b/rnndb/nv50_pgraph.xml @@ -93,6 +93,9 @@ <value value="0x23" name="XY_OUT_OF_BOUNDS"> <!-- m2mf at least. 2d too? --> <brief>Your x/y coords

--- nvbios/info.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/nvbios/info.c b/nvbios/info.c index 87a33d8..6b8d209 100644 --- a/nvbios/info.c +++ b/nvbios/info.c @@ -119,6 +119,10 @@ int envy_bios_parse_bit_i (struct envy_bios *bios, struct envy_bios_bit_entry *b bios->chipset_name = "G72"; break; case 0x0573: + if (!bios->parts) { +

--- nvbios/nvbios.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nvbios/nvbios.c b/nvbios/nvbios.c index 4fc667b..7bb768a 100644 --- a/nvbios/nvbios.c +++ b/nvbios/nvbios.c @@ -797,9 +797,9 @@ void find_strap(char *filename) { path = (char*) malloc(base_length + strlen(strap_filename)+1); strncpy(path, filename, base_length); - strncpy(path+base_length,

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

On Mon, Aug 25, 2014 at 2:58 PM, Christian Costa <titan.costa at gmail.com> wrote: > --- > nvbios/info.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/nvbios/info.c b/nvbios/info.c > index 87a33d8..6b8d209 100644 > --- a/nvbios/info.c > +++ b/nvbios/info.c > @@ -119,6 +119,10 @@ int envy_bios_parse_bit_i (struct envy_bios *bios, struct

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

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/.gitignore | 53 +++++++++++++++++++++++++++-------------------------- 1 file changed, 27 insertions(+), 26 deletions(-) diff --git a/nva/.gitignore b/nva/.gitignore index 5c9184b..72de056 100644 --- a/nva/.gitignore +++ b/nva/.gitignore @@ -1,39 +1,40 @@ +evotiming +libnva.a +libnva.so +nv01dump +nv01post +nvacounter +nvadownload +nvaevo +nvafakebios nvafill +nvaforcetemp +nvafucstart

Le 31/08/2014 16:11, Martin Peres a ?crit : > On 31/08/2014 16:01, Christian Costa wrote: >> 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

Le 31/08/2014 16:23, Martin Peres a ?crit : > On 31/08/2014 16:19, Christian Costa wrote: >> Le 31/08/2014 16:11, Martin Peres a ?crit : >>> On 31/08/2014 16:01, Christian Costa wrote: >>>> 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.

On 31/08/2014 16:01, Christian Costa wrote: > 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

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

Le 31/08/2014 17:18, Christian Costa a ?crit : > Le 31/08/2014 16:23, Martin Peres a ?crit : >> On 31/08/2014 16:19, Christian Costa wrote: >>> Le 31/08/2014 16:11, Martin Peres a ?crit : >>>> On 31/08/2014 16:01, Christian Costa wrote: >>>>> Le 31/08/2014 15:12, Martin Peres a ?crit : >>>>>> On 31/08/2014 15:00, Christian Costa wrote:

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