21:04UrbanMusic: Hello ive read threw the help on freedesktop and ive done many searches without finding a fix or way to change my car
21:11UrbanMusic: I installed a geforece GTX 560 Ti 2g ddr5 in a pc using a sabertooth 990fx board with AMD-4130 cpu. the desktop was very unresposive and slugish. I used CPU-X and that showed the GTX560 running a gpu clock 50mhz and memory at 150mhz. I checked output of /sys/kernel/debug/dri/card/0/pstate that also showed 50mhz gpu and 150mhz memory
21:14UrbanMusic: I know changing pstate has been deprecated, searches came up with module option nouveau.config=NvClkMode=15 to set the card to the max available 903mhz gpu and 2000mhz memory
21:14UrbanMusic: I set it as boot option, no change I tried it in /lib/modprobe.d/nouveau.conf no change
21:15UrbanMusic: I then tried the NvBoost= option in the same ways again no change from 50mhz gpu 150mhz memory.
21:16UrbanMusic: my previous card geforce GTS 250 also ran at lowest setting but that was 300mhz GPU and 300mhz memory whcih meant card was useable
21:17UrbanMusic: the GTX560 crashes the system if I try to play a video in vlc with default options
21:19UrbanMusic: My quetion, is there a configuration error on my part or a way to get the card to run at higher speed
21:20karolherbst: UrbanMusic: reclocking is just not supported on Fermi GPUs sadly
21:21UrbanMusic: I am using kernel-6.4-rc5-rt4 Ive also tried kernel-6.1.30 amd kernel-6.3.3 all show the same gpu and memory speeds. I can't and would'nt use the nvidia drivers as I run an RT kernel and have found them very buggy in the past
21:22karolherbst: there is nothing which can be done about it sadly
21:22karolherbst: unless you want to implement it
21:23UrbanMusic: okay karolhebst does reclocking work on a gtx 660 Ti as thats kelper based I think
21:23karolherbst: it works no quite a lot of GPUs, but it might be broken on a handful of GPUs
21:23karolherbst: there have been bugs especially around GPUs with higher clocks than other models
21:24UrbanMusic: I watched roy spliets video from 2014 on reclocking
21:24karolherbst: we know that GPUs like 780 (ti) generally work, but we also know that some other models e.g. 750 can cause issues as they clock to way higher clocks
21:25UrbanMusic: okay is there a list any were I can refer to
21:25karolherbst: but yeah.. all kepler GPUs are more or less supported
21:25karolherbst: not really
21:25karolherbst: it's more of a best effort thing, not something users should plan around
21:25karolherbst: all this stuff is super complex and different on every single GPU
21:25UrbanMusic: okay thats not to bad Luckily ebay does have quite a few kelper bassed cards
21:25karolherbst: even two GPUs from the same product line can have different clocking parameters
21:26karolherbst: the code even has to take into account properties fused in while the chip was produced, it's... kinda annoying, but there is nothing we can guarentee
21:26UrbanMusic: at resonable prices yes I got that from Roy's video and also lack of feedback when you do make changes
21:27karolherbst: we fixed a few bugs since that video though
21:27karolherbst: UrbanMusic: btw.. maxwell 1st gen GPUs are also supported, like the 750 and 750 ti
21:27UrbanMusic: my previous card GTS 250 has run flawlessly with nouveau driver for last 5 years
21:27karolherbst: anything with GK* and GM10* should work
21:27karolherbst: well.. kinda
21:28karolherbst: there is a chance it works :)
21:28UrbanMusic: Okay ill look at those to my motherboard is only pcie 2.0 with 3 x16 slots
21:29karolherbst: pcie version doesn't matter
21:29UrbanMusic: cool
21:29karolherbst: yeah, pcie is forward and backwards compatible by design
21:30karolherbst: the clocking code also switches between pcie versions and just caps to whatever the system supports
21:30UrbanMusic: only anoying part with the GTS 250 with my mboard gets stuck at X8 due to above bridge yet with the GTX 560 it was at x16
21:30UrbanMusic: thats very helpfull info
21:31karolherbst: could be that the GPU only does x8
21:31karolherbst: there are some gpus around with a x16 slot, but only x8 enabled
21:32karolherbst: but the pcie speed doesn't really matter
21:32karolherbst: I've seen like <5% perf ganes when switching from 1.0 to 3.0 on max clocks across the board
21:32karolherbst: soo.. whatever
21:33UrbanMusic: acording to it's specs gts is an X16 card it just doesnt play well with the bridges
21:33karolherbst: could also be a buggy pcie 2.0 implementation
21:34karolherbst: I know that e.g. G8x gpus do have the registers for PCIe 2.0 but there it was just plain broken
21:34karolherbst: and pre spec even
21:34karolherbst: and the GTS 250 seems to be a G92 which is the first gen with 2.0
21:34karolherbst: so.. could just be buggy
21:35UrbanMusic: on my specific board asus has a buggy bios with no updates since 2016 and bad implementation of memory alocation even with various kernel boot options
21:35karolherbst: ouch
21:40UrbanMusic: yeah Im planing an upgrade to a ryzen bassed system I'm trying to research a motherboard that fully supports a PCIE to PCI adapters for dual delta1010's the PC runs a music studio
21:41UrbanMusic: thanks very much for all the info I shall do some searches for models folks have reclocked
21:42UrbanMusic: one last question which is the best option to use NvClkMode or NvBoost
21:47karolherbst: those are differnt things, NvBoost kinda impacts the max clock being used. NvBoost 0: base clock, 1: boost clock 2: highest valid clock config
21:47karolherbst: it's not really advised to use anything besides 0 unless you monitor the GPU temperature, because we don't have any automatic adjustments in place
21:47karolherbst: to e.g. react on high GPU temperatures
21:48karolherbst: 0 is deemed always safe, 1 in almost all cases, and 2 kinda varies a lot on the workload
21:48karolherbst: and cooling
21:48karolherbst: 1 is also sometimes calld "Average boost" or something.. dunno.. it's kinda weird
21:53UrbanMusic: okay and NvClkMode uses the modes shown by pstate, I have lm-sensors setup so I can easily monitor gpu temps