search for: reclock

...16 um 13:43 > geschrieben: > > Hi! > > Did you check on different Fermi chipsets or only with one variant? currently I only checked that on my nvc1, but I thought I could just send the patches and it is easier for others to try it out this way. > > Are you sure that engine reclocking works as expected on Fermi? Because > enabling it without a strong inspection sounds like a prediction and it > might not work. It seems to work, because I got a huge performance increase in gputest_pixmark_piano, check the second commit for details ;) > > On 01/13/2016 01:25 PM...

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 questions feel > free to...

...ou check on different Fermi chipsets or only with one variant? > > currently I only checked that on my nvc1, but I thought I could just send the > patches and it is easier for others to try it out this way. Yeah, you need to have more feedbacks on different chips. What about fixing memory reclocking instead of this series which is going to be somehow useless when this will be done? I mean memory reclocking probably offers more performance increase that engine reclocking, no? > >> >> Are you sure that engine reclocking works as expected on Fermi? Because >> enabling...

https://bugs.freedesktop.org/show_bug.cgi?id=58428 Priority: medium Bug ID: 58428 Assignee: nouveau at lists.freedesktop.org Summary: X crashes when running opengl application after reclocking nouveau driver to use highest speed QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: amade at asmblr.net Hardware: x86-64 (AMD64) Status: NEW Version: unsp...

Hi! Did you check on different Fermi chipsets or only with one variant? Are you sure that engine reclocking works as expected on Fermi? Because enabling it without a strong inspection sounds like a prediction and it might not work. On 01/13/2016 01:25 PM, Karol Herbst wrote: > some chipset have working engine reclocking, but broken memory reclocking like > Fermi. We should for now, add the fu...

https://bugs.freedesktop.org/show_bug.cgi?id=89273 Bug ID: 89273 Summary: [NVA8] nouveau screen corruption and X lockup when reclocking Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> Adds a NvReclock boolean option to allow the user to enable (or disable) >> reclocking. All chipsets default to off, except NVAA/NVAC, which are >> reportedly complete. > Hey Ilia, > > I think I've expressed my thoughts on this previously via IRC, but let me > stick them here too so ther...

...Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: >> > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> >> >> Adds a NvReclock boolean option to allow the user to enable (or >> >> disable) >> >> reclocking. All chipsets default to off, except NVAA/NVAC, which are >> >> reportedly complete. >> > Hey Ilia, >> > >> > I think I've expressed my thoughts on this...

some chipset have working engine reclocking, but broken memory reclocking like Fermi. We should for now, add the functionality to allow partly reclocking for those. Allthough this doesn't give as much performance as one might wish, it is till noticeable and may improve performance enough to be noted. Karol Herbst (2): clk: seperat...

...y 2014 13:39, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: > > On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: > >> > >> Adds a NvReclock boolean option to allow the user to enable (or disable) > >> reclocking. All chipsets default to off, except NVAA/NVAC, which are > >> reportedly complete. > > Hey Ilia, > > > > I think I've expressed my thoughts on this previously via IRC, but let me > &g...

https://bugs.freedesktop.org/show_bug.cgi?id=104784 Bug ID: 104784 Summary: Unable to do reclocking manually Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.o...

https://bugs.freedesktop.org/show_bug.cgi?id=99505 Bug ID: 99505 Summary: Attempting to reclock GeForce GT740M (GK208) cause GPU and system to hang Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau...

Although memory reclocking seems to be completely broken on my GF119, we can at least allow users to enable reclocking for the core clock. Signed-off-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> --- drm/nouveau/nvkm/subdev/fb/ramgf100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/...

...8:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/server/ctdb_recoverd.c:1267 Starting do_recovery 2018/02/12 19:38:57.886187 ctdb-recoverd[7182]: Attempting to take recovery lock (/share-fs/export/ctdb/.ctdb/reclock) 2018/02/12 19:38:57.886243 ctdb-recoverd[7182]: Set cluster mutex helper to "/usr/libexec/ctdb/ctdb_mutex_fcntl_helper" 2018/02/12 19:38:57.899722 ctdb-recoverd[7182]: Unable to take recovery lock - contention 2018/02/12 19:38:57.899763 ctdb-recoverd[7182]: Unable to get recovery lock -...

...https://wiki.archlinux.org/index.php/PRIME#Discrete_Card_as_Primary_GPU) - This setup works fine under Windows 10, and the eGPU gives a lot better performance than the intel chip even with the limited PCIe link. - I compiled nouveau.ko, and nothing else, from your out-of-tree fork (branch stable_reclocking_kepler, HEAD at bc4767c (bios/fan: hardcode the fan mode to linear)) With and without your patches, I get lockups when attempting to reclock to the highest level (echo 0f > /sys/.../pstate) and then running an actual game (Dota 2 in this instance). Reclock as such appears to work fine in...

First patch fixes a potential vbios parsing bug on Fermi GPUs, but it may also affect Kepler ones. Second patch wakes the GPU up whenever the user tries to reclock to prevent the write to the pstate file from freezing. Karol Herbst (2): bios/vpstate: There are some fermi vbios with no boost or tdp entry debugfs: Wake up GPU before doing any reclocking drm/nouveau/nouveau_debugfs.c | 4 ++++ drm/nouveau/nvkm/subdev/bios/vpstate.c | 10 ++++++++...

Hi, I have a GTX 770 (NVE4) back on 3.16.X kernel i was able to reclock my gpu using /sys/class/drm/card0/device/pstate but now on 3.18 (rc4) all proper reclocking support is gone from pstate. how should i be able to reclock again my GPU? cheers Lucas.

https://bugs.freedesktop.org/show_bug.cgi?id=88890 Bug ID: 88890 Summary: Reclocking of core speed fails on non-reference ASUS GeForce GTX650 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Componen...

...8:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/server/ctdb_recoverd.c:1267 Starting do_recovery 2018/02/12 19:38:57.886187 ctdb-recoverd[7182]: Attempting to take recovery lock (/share-fs/export/ctdb/.ctdb/reclock) 2018/02/12 19:38:57.886243 ctdb-recoverd[7182]: Set cluster mutex helper to "/usr/libexec/ctdb/ctdb_mutex_fcntl_helper" 2018/02/12 19:38:57.899722 ctdb-recoverd[7182]: Unable to take recovery lock - contention 2018/02/12 19:38:57.899763 ctdb-recoverd[7182]: Unable to get recovery lock -...

...8:57.886134 ctdb-recoverd[7182]: Node:1 was in recovery mode. Start recovery process 2018/02/12 19:38:57.886160 ctdb-recoverd[7182]: ../ctdb/server/ctdb_recoverd.c:1267 Starting do_recovery 2018/02/12 19:38:57.886187 ctdb-recoverd[7182]: Attempting to take recovery lock (/share-fs/export/ctdb/.ctdb/reclock) 2018/02/12 19:38:57.886243 ctdb-recoverd[7182]: Set cluster mutex helper to "/usr/libexec/ctdb/ctdb_mutex_fcntl_helper" 2018/02/12 19:38:57.899722 ctdb-recoverd[7182]: Unable to take recovery lock - contention 2018/02/12 19:38:57.899763 ctdb-recoverd[7182]: Unable to get recovery lock -...