SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Or maybe 1280x1024 and above, since I have the same (harmless) issue with a 1680x1050 display (though Franklin has a 1440x900 display, from the looks of it, and it is accurate).
After I bumped into that thread, I ran a quick test. I exited X and changed the xorg.conf from nvidia to nv (I keep copies of both configuration files for easy changes). I started X, checked the KDE control center and I saw 75 Hz. I ran xrandr and I saw 75 Hz. Perhaps then xrandr is not the culprit. Seems the nvidia driver is somehow confusing xrandr.
The solution for me, to eliminate the vertical refresh rate number discrepancies, was to add the following to the Screen section in my xorg.conf:
Option "DynamicTwinView" "false"
Now there is no discrepancy when using the 169.09 nvidia driver. Every tool reports 75 Hz, including xrandr, which now reports both frequencies that the monitor supports (60 and 75 Hz). KDE now even offers me the option to use 60 Hz.
The DynamicTwinView false also works for me, I have a two-screen setup that uses an emachine monitor (eview 17f3) and a Vizio HDTV and never had the correct refresh rates displayed for either, I believe 50Hz was shown for both screens. Adding that option shows the correct refresh rates for both screens now, with the CRT running at 1280x1024@60Hz and the HDTV running at 1024x768@75Hz.
The only thing I notice right away is that you can't use the twinview setup through nvidia-settings like you could before, which only makes sense since it's disabled now. Not a big deal to me since the screens are already set up how I want them.
I'd also like to mention that you can also check to see what refresh rate your monitor is running at by checking the on screen display if there is one. Even though KDE was showing 50Hz as my only option for vertical refresh, pushing the button to bring up the OSD for my monitor always showed 59.9Hz when I was running at 1280x1024. Another way to check vertical refresh, if you are using an nvidia card and the proprietary drivers at least, is to run nvidia-settings and under the opengl settings for your monitor check the Sync to VBlank box. Then run glxgears and the output should give you an idea. Doing this on my box gives something like:
303 frames in 5.0 seconds = 60.450 FPS
301 frames in 5.0 seconds = 60.023 FPS
301 frames in 5.0 seconds = 60.030 FPS
Which fits pretty well with what I already know it's running at.
To anybody interested, the problem solution posted in this thread is still required with the 180.29 drivers. I was testing a similar xrandr problem with the generic nv driver and I thought I'd check the proprietary side again. No change: without the xorg.conf options xrandr gets confused.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.