[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Martin Peres changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|---

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #14 from Karol Herbst --- (In reply to Pekka Paalanen from comment #13) > Seems unlikely I will ever get around to make that mmiotrace. Should we > close this report? can you run the nvidia legacy driver and

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #12 from Pekka Paalanen --- Note to self: need to rebuild my kernel without CONFIG_TRIM_UNUSED_KSYMS. Otherwise the driver won't install. -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #11 from Karol Herbst --- but you can use OpenGL stuff to confirm if it doesn't use the higher clocks -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #10 from Karol Herbst --- (In reply to Pekka Paalanen from comment #9) > (In reply to Karol Herbst from comment #8) > > it would be quite unpleasant if nvidia would indeed use the highest clock > > level here.

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Pekka Paalanen changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #8 from Karol Herbst --- it would be quite unpleasant if nvidia would indeed use the highest clock level here. And that mmiotrace seems a bit odd, because it accesses a GPIO which shouldn't exist and in any

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Pekka Paalanen changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Pekka Paalanen changed: What|Removed |Added Status|NEW |NEEDINFO ---

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #5 from Ilia Mirkin --- Huh. Well, this is what's in the vbios: Voltage table at 0xd0c9. Version 32. Header: 0xd0c9: 20 06 02 04 00 01 mask = 0x1 2 entries -- Vid = 0x0,

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #4 from Pekka Paalanen --- (In reply to Ilia Mirkin from comment #2) > Without looking at your VBIOS, I suspect if you first clock to 07 and then > to 0f, you'll be able to get 07's core/shader speeds and the

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #3 from Pekka Paalanen --- Created attachment 129841 --> https://bugs.freedesktop.org/attachment.cgi?id=129841=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #2 from Ilia Mirkin --- This is probably apparent to anyone investigating, but for your benefit... what's happening is that memory reclock works fine, but changing core/shader clocks requires a voltage

[Nouveau] [Bug 99913] [G96] Reclocking fails on voltage

https://bugs.freedesktop.org/show_bug.cgi?id=99913 --- Comment #1 from Pekka Paalanen --- Created attachment 129840 --> https://bugs.freedesktop.org/attachment.cgi?id=129840=edit VBIOS from /sys/kernel/debug/dri/0/vbios.rom -- You are receiving this mail because: You are