| 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@lists.freedesktop.org |
| Reporter | berillions@gmail.com |
| QA Contact | xorg-team@lists.x.org |
Hi,
I have a laptop with Optimus technology, my Nvidia card is a GTX 640MX. I u=
se
Debian Unstable x86_64 with nouveau 1.0.15 and Mesa 17.3.3
Unfortunatly, it's impossible to do reclocking with Nouveau and my GPU.
When i launch "cat /sys/kernel/debug/dri/1/pstate", i have these =
results :
07: core 270-405 MHz memory 648 MHz
0a: core 270-601 MHz memory 1600 MHz
0f: core 270-614 MHz memory 2800 MHz
AC: core 0 MHz memory 0 MHz
------
It's anormal to have these line "AC: core 0 MHz memory 0 MHz", ri=
ght ?
Because when i set "echo 0f > /sys/kernel/debug/dri/1/pstate",=
the console (not
the system) hangs. And when i launch a game (Tyranny), it does not work.
Hello, > AC: core 0 MHz memory 0 MHz means your GPU is actually suspended: since you have an Optimus configurati= on, the NVIDIA GPU will suspend automatically if it hasn=E2=80=99t received any= work to do in a short while. Try for example to run `DRI_PRIME=3D1 glxgears`, keep it running and reissue the cat command: you should not see actual clocks for on the AC line. Have a look at ht= tps://nouveau.freedesktop.org/wiki/Optimus/ to learn how to configure Prime. As for the system hang when trying to reclock a suspended GPU, patches have been sent to the Nouveau mailing list, but haven=E2=80=99t been merged yet.= You can find them here: https://github.com/karolherbst/nouveau/commits/clk_cleanup_for_real > And when i launch a game (Tyranny), it does not = work. What is not working? If you didn=E2=80=99t specify anything, the game shoul= d run on the =E2=80=9Cprimary=E2=80=9D GPU by default, which quite often tends to be the= Intel GPU.
(In reply to Pierre Moreau from comment #1) > Hello, >=20 > > AC: core 0 MHz memory 0 MHz >=20 > means your GPU is actually suspended: since you have an Optimus > configuration, the NVIDIA GPU will suspend automatically if it hasn=E2= =80=99t > received any work to do in a short while. Try for example to run > `DRI_PRIME=3D1 glxgears`, keep it running and reissue the cat command:= you > should not see actual clocks for on the AC line. > Have a look at https://nouveau.freedesktop.org/wiki/Optimus/ to learn how to > configure Prime. >=20 > As for the system hang when trying to reclock a suspended GPU, patches= have > been sent to the Nouveau mailing list, but haven=E2=80=99t been merged= yet. You can > find them here: > https://github.com/karolherbst/nouveau/commits/clk_cleanup_for_re= al I added to my ~/.xinitrc this line =C2=AB xrandr --setprovideroffloadsink n= ouveau Intel=C2=A0=C2=BB I see correctly the Intel GPU when i launch =C2=AB=C2=A0glxinfo | grep =C2= =AB=C2=A0OpenGL vendor string=C2=A0=C2=BB=C2=A0=C2=BB and the Nvidia GPU if i add DRI_PRIME=3D1. > > And when i launch a game (Tyranny), it does= not work. >=20 > What is not working? If you didn=E2=80=99t specify anything, the game = should run on > the =E2=80=9Cprimary=E2=80=9D GPU by default, which quite often tends = to be the Intel GPU. In fact the games runs with Nouveau and DRI_PRIME=3D1. It does not work after to do the reclocking =3D> the game=E2=80=99s proc= ess exist but the game=E2=80=99s window does not appear. Are you French, if yes it=E2=80=99s easiest to explain : Lorsque je lance la commande pour faire le reclocking, je n=E2=80=99ai plus= acc=C3=A8s au prompt, comme si la commande continue de travailler en arri=C3=A8re plan. S= i je verifie l=E2=80=99=C3=A9tat de pstate dans une autre commande, le reclockin= g a l=E2=80=99air d=E2=80=99avoir =C3=A9t=C3=A9 fait.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/iss= ues/404.