similar to: [Bug 111128] New: Impossible to change pstate on GT610M

Greetings! I have very old notebook with 8400M Gs. I'm experience some overheating on high clocks. I want to change pstate for AC mode. Currently I have sudo cat /sys/kernel/debug/dri/0/pstate 20: core 169 MHz shader 338 MHz memory 100 MHz 21: core 275 MHz shader 550 MHz memory 200 MHz 22: core 400 MHz shader 800 MHz memory 400 MHz AC: core 275 MHz shader 550 MHz memory 199 MHz And I want to

Greetings! I have very old notebook with 8400M Gs. And I'm experience some overheating on high clocks. I want to change pstate for AC mode. Currently I have sudo cat /sys/kernel/debug/dri/0/pstate 20: core 169 MHz shader 338 MHz memory 100 MHz 21: core 275 MHz shader 550 MHz memory 200 MHz 22: core 400 MHz shader 800 MHz memory 400 MHz AC: core 275 MHz shader 550 MHz memory 199 MHz And I want

this makes the code easier, because we can compare the id with pstate->pstate and safe us the trouble iterating over the entire pstate list Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/nouveau_debugfs.c | 6 ++--- drm/nouveau/nvkm/subdev/clk/base.c | 49 +++++++++++--------------------------- 2 files changed, 17 insertions(+), 38 deletions(-) diff --git

This makes the code easier, because we can compare the id with pstate->pstate and safe us the trouble iterating over the entire pstate list to match the index. Signed-off-by: Karol Herbst <karolherbst at gmail.com> Reviewed-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/nouveau_debugfs.c | 6 +-- drm/nouveau/nvkm/subdev/clk/base.c | 78

This makes the code easier, because we can compare the id with pstate->pstate and saves us from the trouble of iterating over the pstates to match the index. v2: reword commit message Signed-off-by: Karol Herbst <karolherbst at gmail.com> Reviewed-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/nouveau_debugfs.c | 6 +-- drm/nouveau/nvkm/subdev/clk/base.c | 78

we will access the current set cstate at least every second and this safes us some CPU cycles looking them up every second. Signed-off-by: Karol Herbst <nouveau at karolherbst.de> --- drm/nouveau/include/nvkm/subdev/clk.h | 2 +- drm/nouveau/nvkm/engine/device/ctrl.c | 5 ++++- drm/nouveau/nvkm/subdev/clk/base.c | 12 ++++++++---- drm/nouveau/nvkm/subdev/pmu/gk20a.c | 23

2016-04-20 20:53 GMT+00:00 Martin Peres <martin.peres at free.fr>: > On 18/04/16 22:14, Karol Herbst wrote: >> >> we will access the current set cstate at least every second and this safes >> us > > saves >> >> some CPU cycles looking them up every second. >> >> Signed-off-by: Karol Herbst <nouveau at karolherbst.de> >> ---

https://bugs.freedesktop.org/show_bug.cgi?id=89113 Bug ID: 89113 Summary: NVA8 constantly flickers when clocked to lowest pstate Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

We will access the current set cstate at least every second and this safes us some CPU cycles looking them up every second. Signed-off-by: Karol Herbst <karolherbst at gmail.com> Reviewed-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/include/nvkm/subdev/clk.h | 4 +++- drm/nouveau/nvkm/engine/device/ctrl.c | 5 ++++- drm/nouveau/nvkm/subdev/clk/base.c | 17

We will access the current cstate at least every second and this saves us some CPU cycles looking them up every second. v2: Rewording commit message. Signed-off-by: Karol Herbst <karolherbst at gmail.com> Reviewed-by: Martin Peres <martin.peres at free.fr> --- drm/nouveau/include/nvkm/subdev/clk.h | 4 +++- drm/nouveau/nvkm/engine/device/ctrl.c | 5 ++++-

With the third generation Opteron parts, AMD switched to an architecturally defined interface for PowerNow! that uses different MSRs than previous versions. This patch brings the PowerNow! driver up to match the mainline Linux driver and provide support for all AMD parts that use or will use the architectural pstate interface. It also removes a WARN_ON statement in kernel/cpu.c that highlights a

On 2017-09-15 — 17:11, Karol Herbst wrote: > This makes the code easier, because we can compare the id with > pstate->pstate and saves us from the trouble of iterating over the pstates > to match the index. I don’t remember whether I have already done this comment before, but I am not sure where your iterating over the pstates savings are, as in this patch at least, you iterate as

http://bugzilla.mindrot.org/show_bug.cgi?id=734 Summary: Misleading error message when host key verification is impossible / SSH_ASKPASS impossible. Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh

The patch seems fine but I found it super confusing that sometimes `pstate` is a pointer (for example `clk->pstate`), sometimes it is an int (for example `args->v0.pstate`). On 2017-09-15 — 17:11, Karol Herbst wrote: > We will access the current cstate at least every second and this saves us > some CPU cycles looking them up every second. > > v2: Rewording commit message. >

On 18/04/16 22:14, Karol Herbst wrote: > we will access the current set cstate at least every second and this safes us saves > some CPU cycles looking them up every second. > > Signed-off-by: Karol Herbst <nouveau at karolherbst.de> > --- > drm/nouveau/include/nvkm/subdev/clk.h | 2 +- > drm/nouveau/nvkm/engine/device/ctrl.c | 5 ++++- >

Have you disconnected all your usb hardware before trying the repair? I've repaired my box more times than I can count and the only time I've seen lots of hdd activity is when I had some weird hardware attached. Geoff Sent from my BlackBerry wireless handheld. -----Original Message----- From: gjgowey at tmo.blackberry.net Date: Sun, 18 Nov 2007 18:01:11 Subject: [centos] dual boot

"Alain Spineux" <aspineux at gmail.com> wrote: >> probably I will need to wipe the HD and install both OS's again. Lanny >> > > Yes and keep on hand a bart-pe boot disk, this time :-) > That's probably "a good thing". You don't know what else was changed (e.g., registry entries, etc.) that won't keep the system from

Hi Several times, I unsuccessfully tried to unsubscribe from lartc via the web interface and mailto:lartc-request@mailman.ds9a.nl?subject=unsubscribe. I also contacted the mailing list admin but got no reply. Even resubscribing did not work. I have posted here since I am running out of options. This posting is addressed to the list admin in charge: Please remove my email address from the

Hello, I searched the archives mailing list of LARTC. Everyone discussed about marking outbound ftp traffic . I could not find any thread discussed about marking inbound ftp traffic. With inbound ftp traffic , we don''t know the random ports specified by ftp servers in passive mode ? So marking inbound ftp traffic is impossible ? If it is possible, can you tell me, Thanks in

I created a runner script to send a newsletter. I found this hack where you pass a controller and specify a helper: http://wiki.rubyonrails.org/rails/pages/HowtoUseUrlHelpersWithActionMailer But in a runner script there is no controller to pass. So, it looks like it''s impossible to use url_for in the mailer template this way. Another way around the no url_for problem is to pass the