Attachment 140326 Details for Bug 107016 – attachment-20771-0.html

attachment-20771-0.html

attachment-20771-0.html (text/html), 2.75 KB, created by atirage21 on 2018-06-25 14:23:08 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: atirage21

Created: 2018-06-25 14:23:08 UTC

Size: 2.75 KB

patch

obsolete

><div dir="ltr">
><pre>But also is question: Why i had only 405 Mhz of core under kernel 4.x, if under kernel 3.19 was more options to see (and same more options is with propretiary driver):<br><br>[    4.311074] nouveau  [     CLK][0000:01:00.0] 07: core 270-405 MHz memory 810 MHz 
>[    4.311090] nouveau  [     CLK][0000:01:00.0] 0f: core 270-745 MHz memory 1800 MHz 
>[    4.311233] nouveau  [     CLK][0000:01:00.0] --: core 405 MHz memory 648 MHz</pre>
>
><br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-06-25 14:03 GMT+02:00  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>    
>      
>    
>    <div>
>      <p>
>        </p><div>
>            <b><a class="m_1018764637008235740bz_bug_link m_1018764637008235740bz_status_NEEDINFO" title="NEEDINFO - Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107016#c10" target="_blank">Comment # 10</a>
>              on <a class="m_1018764637008235740bz_bug_link m_1018764637008235740bz_status_NEEDINFO" title="NEEDINFO - Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107016" target="_blank">bug 107016</a>
>              from <span class="m_1018764637008235740vcard"><a class="m_1018764637008235740email" href="mailto:karolherbst@gmail.com" title="Karol Herbst &lt;karolherbst@gmail.com&gt;" target="_blank"> <span class="m_1018764637008235740fn">Karol Herbst</span></a>
></span></b>
>        <pre>@atirage21:
>
>were you actually able to reclock the GPU before in a stable way? It seems like
>we have to support a way of setting the voltage we don&#39;t implement yet (and
>never had).
>
>It is the first time actually seeing such a GPU, so I am not quite sure how we
>are able to get that working for now. Of course we could provide patches and
>hope it kind of works, but this would require testing from your side as well.</pre>
>        </div>
>      <p></p><span class="">
>
>
>      <hr>
>      <span>You are receiving this mail because:</span>
>
>      <ul>
>          <li>You reported the bug.</li>
>      </ul>
>    </span></div>
></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>S pozdravom / Mit freundlichen GrÃ¼Ãen / BarÃ¡ti udvozlettel / Best regards<br><br>Ing. Attila TÃ³th, PhD.<br><br>tel : +421 910 299 189 (4Ka - Slovak Republic)<br><br>Please consider your environmental responsibility before printing this <br>e-mail <br><br><br><br><br></div></div></div>
></div>

<div dir="ltr">
<pre>But also is question: Why i had only 405 Mhz of core under kernel 4.x, if under kernel 3.19 was more options to see (and same more options is with propretiary driver):<br><br>[    4.311074] nouveau  [     CLK][0000:01:00.0] 07: core 270-405 MHz memory 810 MHz 
[    4.311090] nouveau  [     CLK][0000:01:00.0] 0f: core 270-745 MHz memory 1800 MHz 
[    4.311233] nouveau  [     CLK][0000:01:00.0] --: core 405 MHz memory 648 MHz</pre>

<br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-06-25 14:03 GMT+02:00  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div>
      <p>
        </p><div>
            <b><a class="m_1018764637008235740bz_bug_link m_1018764637008235740bz_status_NEEDINFO" title="NEEDINFO - Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107016#c10" target="_blank">Comment # 10</a>
              on <a class="m_1018764637008235740bz_bug_link m_1018764637008235740bz_status_NEEDINFO" title="NEEDINFO - Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107016" target="_blank">bug 107016</a>
              from <span class="m_1018764637008235740vcard"><a class="m_1018764637008235740email" href="mailto:karolherbst@gmail.com" title="Karol Herbst &lt;karolherbst@gmail.com&gt;" target="_blank"> <span class="m_1018764637008235740fn">Karol Herbst</span></a>
</span></b>
        <pre>@atirage21:

were you actually able to reclock the GPU before in a stable way? It seems like
we have to support a way of setting the voltage we don&#39;t implement yet (and
never had).

It is the first time actually seeing such a GPU, so I am not quite sure how we
are able to get that working for now. Of course we could provide patches and
hope it kind of works, but this would require testing from your side as well.</pre>
        </div>
      <p></p><span class="">


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You reported the bug.</li>
      </ul>
    </span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>S pozdravom / Mit freundlichen GrÃ¼Ãen / BarÃ¡ti udvozlettel / Best regards<br><br>Ing. Attila TÃ³th, PhD.<br><br>tel : +421 910 299 189 (4Ka - Slovak Republic)<br><br>Please consider your environmental responsibility before printing this <br>e-mail <br><br><br><br><br></div></div></div>
</div>

Actions: View

Attachments on bug 107016: 140303 | 140305 | 140306 | 140307 | 140311 | 140318 | 140326 | 140327 | 140332 | 140333 | 140413 | 142724 | 145371

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.