You are not logged in.
Pages: 1
Hey guys, with the latest updates of the nvidia driver my screen started to blur. How do I fix that?
I've tried to off these options
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On} , provided by wiki to solve tearing and it solved the blur, but screen tearing become again a problem.
My 20-nvidia.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 396.51 (builduser@svenstaro) Sun Aug 12 20:40:20 CEST 2018
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "AOC 1619w"
HorizSync 30.0 - 60.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 950"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "CRT-0"
Option "metamodes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSectionLast edited by josecleiton (2018-09-24 16:37:14)
Offline
Sorry, these options doesn't have influence in issue
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On} Offline
nvidia-settings -q FSAA
xrandr -qOnline
Nvidia-settings Output:
Attribute 'FSAA' (arch-desk:0.0): 0.
Valid values for 'FSAA' are: 0, 1, 5, 9, 10 and 11.
'FSAA' can use the following target types: X Screen.xrandr Output:
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384
DVI-I-0 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1366x768 59.86*+
1360x768 60.02
1024x768 75.03 72.00 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
640x400 70.10
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)Thanks for replying
Offline
The only suspicious thing is the "1360x768" modeline, rather that it *should* be used.
Is the output still "blurry" when you "xrandr --output DVI-I-0 --mode 1360x768"?
If so
a) get any compositor out of the equation, if it's not toggleable (that's probably not a woerd ;-) w/ your WM, try using openbox or so
b) can you capture the blurriness in a screenshot?
c) otherwise, can you make a photo showing the effect?
Online
Pages: 1