Bug 58784 - Nouveau on NVCE, reclocking: memory type not supported?
Summary: Nouveau on NVCE, reclocking: memory type not supported?
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-26 20:12 UTC by miga-anyandall
Modified: 2015-02-13 14:08 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
lspci_output, nvce_strap_peek, nvce_timing_peek, nvce_bios.rom, and nvce_vbios_parsed (70.51 KB, application/zip)
2012-12-26 20:12 UTC, miga-anyandall
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description miga-anyandall 2012-12-26 20:12:18 UTC
Created attachment 72144 [details]
lspci_output, nvce_strap_peek, nvce_timing_peek, nvce_bios.rom, and nvce_vbios_parsed

I understand reclocking on Nouveau is very experimental still, but I figured I might as well send in this bug report anyway.

On my NVCE (GTX 560 from EVGA), the standard (boot) clock speeds are 50 MHz core, 100 MHz shader, and 135 MHz memory. Naturally because of this, OpenGL performance is terrible (possibly worse than older Intel chips like the 4500HD), about 15-20 FPS in Red Eclipse and about 5 FPS in Xonotic.

I am able to reclock the card, however, upon doing so, it comes up with this error in dmesg:
[11245.600378] nouveau E[     DRM] cannot reclock unsupported memtype

So, I'm able to get the GPU core and shader to run at their highest speeds (850 MHz and 1701 MHz respectively), but the memory speed stays at 135 MHz (when it should be at 2052 MHz). Even though I can change the clock speeds, after a while, the card will crash, forcing me to have to reboot.

I'm also uploading things such as my lspci_output, nvce_strap_peek, nvce_timing_peek, nvce_bios.rom, and nvce_vbios_parsed, so it'll hopefully help you guys out on getting things working.
Comment 1 Tobias Klausmann 2015-02-01 00:00:30 UTC
is this still a problem with newer version of the kernel while booting with the _experimental_ nouveau.pstate=1 and change the clocks at the pstate file
"echo 0f /sys/class/drm/{nvidia_card}/device/pstate" ?
Comment 2 Ilia Mirkin 2015-02-01 00:24:19 UTC
(In reply to Tobias Klausmann from comment #1)
> is this still a problem with newer version of the kernel while booting with
> the _experimental_ nouveau.pstate=1 and change the clocks at the pstate file
> "echo 0f /sys/class/drm/{nvidia_card}/device/pstate" ?

Yes, it is. There's no reclocking support on nvc0.
Comment 3 arabek 2015-02-12 20:44:52 UTC
Is there any chance to get this working? I volunteer to even burn my card for the sake of testing stuff if you provide me with patches.
Comment 4 Ilia Mirkin 2015-02-12 20:48:44 UTC
(In reply to Wojciech Arabczyk from comment #3)
> Is there any chance to get this working? I volunteer to even burn my card
> for the sake of testing stuff if you provide me with patches.

No one has stepped up with the time (and effort) required to make it happen.
Comment 5 arabek 2015-02-13 09:02:02 UTC
> No one has stepped up with the time (and effort) required to make it happen.

What kind of effort and knowledge would be needed to make it happen? Perhaps a bounty? To my knowledge the 560 was/is a really popular graphics adapter amongst the community.

According to the steam survey, 550/560/560 Ti are amongst top20 used cards around the globe.

source: http://store.steampowered.com/hwsurvey/
Comment 6 Ilia Mirkin 2015-02-13 14:08:13 UTC
(In reply to Wojciech Arabczyk from comment #5)
> > No one has stepped up with the time (and effort) required to make it happen.
> 
> What kind of effort and knowledge would be needed to make it happen?

a few $k for buying up lots of cards for testing, and probably 3-4 months of full-time work for someone familiar with the project; add a month for someone who isn't.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.