search for: reclocking

...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, K...

...tential > under load. A performance level comprises the clock speed and voltage > for several subcomponents in the GPU. The difference between the > lowest and highest performance level can be as much as a factor 10 in > clock speed. > > Despite hard work from many developers, reclocking support in Nouveau > still has quite a few loose ends: engine reclocking is mostly in place > but not always reliable, there are several missing routines related to > memory reclocking and in general the actions required to perform > voltage- and frequency scaling are not or only pa...

...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 it...

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: unspeci...

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 funct...

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 there's a record of the current state... > > For nvaa/nvac, yes, let...

...1: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 there's a record...

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: seperate e...

...gt; > 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 there's a record of the current state... > >...

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.org...

...Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: stu_dby at 126.com QA Contact: xorg-team at lists.x.org Created attachment 129107 --> https://bugs.freedesktop.org/attachment.cgi?id=129107&action=edit The dmesg output after reclocking When I tried to reclock the GT740M (the GK208 one) on my laptop with: # echo "07" > /sys/kernel/debug/dri/1/pstate The shell process in which I enter the command became unkillable (state D+ in ps) and the GPU would hang (rendering stops). Attempting to shutdown the computer would comp...

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/nou...

------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba@lists.samba.org <samba@lists.samba.org> 日 期 ：2018年02月26日 17:10 主 题 ：[ctdb] Unable to take recovery lock - contention When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The

...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 initi...

...n 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 ++++++++-- 2 files changed, 12 insertions(+), 2 deletions(-) -- 2.17.1

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 Component:...

When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060

Am Montag, 26. Februar 2018, 17:26:06 CET schrieb zhu.shangzhong--- via samba: Decoded base64 encoded body with some chinese characters: ------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba at lists.samba.org <samba at lists.samba.org> 日 期 ：2018年02月26日 17:10 主 题 ：[ctdb] Unable to take recovery lock - contention When the ctdb is starting, the "Unable to take recovery lock