search for: e118

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)

...gt; On 22/11/17 04:06, Ilia Mirkin wrote: >>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>> Martin's question was very long, but it boils down to this: >>> >>> How do we compute the correct values to write into the e114/e118 pwm >>> registers based on the VBIOS contents and current state of the board >>> (like temperature). >> >> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >> GF119+, or 0x200cd/d0 on Kepler+. >> >> At least, it looks like we know...

...n > what's in that code. Absolutely :) I have not updated Nouveau yet, in fear of setting a value lower than what the proprietary driver does... > > Martin's question was very long, but it boils down to this: > > How do we compute the correct values to write into the e114/e118 pwm > registers based on the VBIOS contents and current state of the board > (like temperature). Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on GF119+, or 0x200cd/d0 on Kepler+. At least, it looks like we know which PWM controler we need to drive, so I did not want to...

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:

...in wrote: >>>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>> Martin's question was very long, but it boils down to this: >>>>> >>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>> registers based on the VBIOS contents and current state of the board >>>>> (like temperature). >>>> >>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>> GF119+, or 0x200cd/d0 on Kepler+. >>&g...

...t;> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>>> Martin's question was very long, but it boils down to this: >>>>>>> >>>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>>> registers based on the VBIOS contents and current state of the board >>>>>>> (like temperature). >>>>>> >>>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>>> GF11...

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

...r, Andy! > > On 22/11/17 04:06, Ilia Mirkin wrote: >> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >> Martin's question was very long, but it boils down to this: >> >> How do we compute the correct values to write into the e114/e118 pwm >> registers based on the VBIOS contents and current state of the board >> (like temperature). > > Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on > GF119+, or 0x200cd/d0 on Kepler+. > > At least, it looks like we know which PWM controler we nee...

..., I believe). The bios stuff is parsed in nvkm/subdev/bios/fan.c and therm.c, although I believe Martin's latest analysis is more advanced than what's in that code. Martin's question was very long, but it boils down to this: How do we compute the correct values to write into the e114/e118 pwm registers based on the VBIOS contents and current state of the board (like temperature). We generally do this right, but appear to get it extra-wrong for certain GPUs. Cheers, -ilia

...04:06, Ilia Mirkin wrote: >>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>> Martin's question was very long, but it boils down to this: >>>> >>>> How do we compute the correct values to write into the e114/e118 pwm >>>> registers based on the VBIOS contents and current state of the board >>>> (like temperature). >>> >>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>> GF119+, or 0x200cd/d0 on Kepler+. >>> >>> At l...

...t;>>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>> Martin's question was very long, but it boils down to this: >>>>>> >>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>> registers based on the VBIOS contents and current state of the board >>>>>> (like temperature). >>>>> >>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>> GF119+, or 0x200cd/d0 on...

...t;> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>>> Martin's question was very long, but it boils down to this: >>>>>>> >>>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>>> registers based on the VBIOS contents and current state of the board >>>>>>> (like temperature). >>>>>> >>>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>>> GF11...