search for: e11c

...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 muddy the water even more by giving register >> addresses, rather concentrating on the problem at hand...

...r 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 muddy the water even more by giving register addresses, rather concentrating on the problem at hand: How to compute the duty value for the PWM...

...t;>> >>>>> 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 muddy the water even more by giving register >>>> addresses, rat...

...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 muddy the water even more by giving register...

...tin'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 muddy the water even more by giving register > addresses, rather concentrating on the problem at hand: How to compute &g...

...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 muddy the water even more by giving register >>> addresses, rather concentrating on...

...gt;>>> 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 muddy the water even more by giving register >>>&gt...

...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 muddy the water even more by giving register...

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