What is is it with "nvidia-smi"? It works just fine on my 580 with latest beta driver and reports running cuda applications, fanspeed etc.
Announcement
Collapse
No announcement yet.
Two Hacks For The NVIDIA Linux Graphics Driver
Collapse
X
-
Originally posted by blackout23 View PostWhat is is it with "nvidia-smi"? It works just fine on my 580 with latest beta driver and reports running cuda applications, fanspeed etc.
Code:nvidia-smi -q --display=UTILIZATION
I've had an idea to benchmark compositing performance; with this:
Code:#!/bin/bash export LD_LIBRARY_PATH=/tmp/nvml_fix/built/319.32/ while true ; do gpuuse=$(nvidia-smi -q --display=UTILIZATION |grep Gpu|sed 's/ //g'|cut -d ":" -f 2|cut -d "%" -f 1) echo -n $gpuuse" " #test $gpuuse -gt 1 && echo "higher" || echo "lower" sleep 0.5 done
Anyway, you can monitor the gpu use on little cpu cost (0%cpu on an E7500@3Ghz).
Code:GPU: 9500GT Vsync: enabled (without vsync you have always 100% gpu) App: glxgears (that is not a benchmark, but in this case it IS) WM: Kwin-4.10.5 Resolution: 1280x1024 Maximized as a frontmost window: gpu=20% Effects disabled:gpu=10% Fullscreen and window unredirected (so effects enabled): 11%
Comment
-
Originally posted by thefirstm View PostI am pretty sure that the pixels of LCD monitors remain "lit" continuously without regard to the refresh rate of the signal. This is, in my opinion, what makes them so much better than CRTs and plasmas because they never flicker, even at "low" refresh rates like 60hz.
The limiting factor on the refresh rate of LCD's is mostly the pixel response time, ie. the time it takes for a pixel to transition from completely lit to completely dark, or vice versa.
Comment
-
Originally posted by CFSworks View PostWhile there's no 1440p monitor that will advertise support for 120Hz, since it's way outside of the DVI spec, there are a few monitors that have been found capable of overclocking that high.
(As an FYI, both monitors I mentioned have incorrect EDID checksums, for some reason - you'll have to configure your display server to ignore that or the monitor will not be detected correctly.)
Comment
-
Originally posted by agd5f View PostProbably whatever "vendor" hacked the EDID to expose the 120Hz mode didn't update the EDID properly to fix the checksum.
The vendor never intended for these to do 120Hz, so the EDID only reports 2560x1440@60Hz. To get 120, you have to write the modeline yourself.
My guess is the OEM only tested the EDID on Windows, which seems to ignore the EDID checksum.
Comment
-
Originally posted by CFSworks View PostBut that would make too much sense.
The vendor never intended for these to do 120Hz, so the EDID only reports 2560x1440@60Hz. To get 120, you have to write the modeline yourself.
My guess is the OEM only tested the EDID on Windows, which seems to ignore the EDID checksum.
Comment
-
Originally posted by agd5f View PostSome 3rd parties sell pre-hacked monitors with a hacked EDID on ebay for people looking to use 120hz modes. Some users also hack their EDIDs themselves to add the 120hz modes. It's also possible the original vendor also messed up the EDID.
Regardless, no, these monitors do not report any mode other than 2560x1440@60Hz. Instead, I think the OEM that makes the PCBs (which seems to be the same across the Catleap, QX2710, and X-Star DP2710) simply didn't verify their EDID checksum, and shipped it without ever realizing that it was wrong.
Comment
-
Checksum error QNIX2710
Originally posted by CFSworks View Post(As an FYI, both monitors I mentioned have incorrect EDID checksums, for some reason - you'll have to configure your display server to ignore that or the monitor will not be detected correctly.)
Do you mind pointing me towards any resources that show me how to ignore checksum errors, and how to set-up a correct Monitor section in xorg.conf for this monitor?
Thank you
Comment
-
Originally posted by koolkao View PostDo you mind pointing me towards any resources that show me how to ignore checksum errors, and how to set-up a correct Monitor section in xorg.conf for this monitor?
Thank you
Note: I'm not an expert at writing xorg.conf's, so please don't use mine as a prime example. Also, I don't know if those timings are optimal, but they do produce pretty stable 120Hz output for me at least.
Note #2: When you use NoEdidModes, the nvidia driver seems to insert 800x600 mode on its own. Using this mode will not work; your monitor will start displaying a bunch of test patterns until you set it back to 2560x1440.
For an explanation on all of the driver options, see Appendix D of the driver manual.
Hope this helps!
Comment
Comment