You are not logged in.
- Topics: Active | Unanswered
#1 2018-09-05 18:09:35
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Making 2d/3d acceleration working better with nouveau drivers [Solved]
Hello to everyone, Im new and proud Arch user.
I need some help for the proper configuration with the 2d and the 3d acceleration to my system, because im facing some kind of malfunction.
Excuse me if i dont use the proper way to paste the console's output. I ll use code format.
My DE is kde.
My graphics card:
lspci -k | grep -A 2 -E "(VGA|3D)"
01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce 9300M GS] (rev a1)
Subsystem: CLEVO/KAPOK Computer G98M [GeForce 9300M GS]
Kernel driver in use: nouveauI use nouveau drivers, i dont wanna use closed drivers.
So the first problem that i face is that when i ve installed the 2d driver xf86-video-nouveau i get a "flash". I ll upload image or video if needs but lets try to describe it. Its a flashing of a distorted image with distorted colors that includes my desktop in four duplicated peaces. Something like that. i Get this after booting then the screen turns to black and the becomes normal. I get this also when i shutdown the system again just for one second. When i dont have this driver installed at all everything s fine. So is it necessary? The other problem appears to the log out confirm dialog with the shutdown restart etc options. When it appears my mouse behavior becomes laggy and slow. So im not sure if its a problem with the 2d or the 3d acceleration. If i install just the nvidia.340xx utils without the driver i solve the problem the mouse respond is immediate and also i get o completely transparent dialog box instead of the blurry one that i get with the closed drivers. But something mess ups with qt i get a system tray notification about plasma renderer and i get no images on themes, or on background settings just a black pain. The options of the pictures are there but they are black and i cant see anything. I fix this with deleting the whole .kde and .config folders, resetting all the settings after uninstalling nvidia.340xx utils.
So lets also see the 3d acceleration outputs. I ve set it up using the wiki guide for the 3d acceleration for the open source drivers.
vainfo
vainfo: VA-API version: 1.2 (libva 2.2.0)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
<unknown profile> : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264High : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLDvdpauinfo
display: :0 screen: 0
API version: 1
Information string: G3DVL VDPAU Driver Shared Library version 1.0
Video surface:
name width height types
-------------------------------------------
420 8192 8192 NV12 YV12
422 8192 8192 UYVY YUYV
444 8192 8192 Y8U8V8A8 V8U8Y8A8
Decoder capabilities:
name level macbs width height
----------------------------------------------------
MPEG1 0 16384 2048 2048
MPEG2_SIMPLE 3 16384 2048 2048
MPEG2_MAIN 3 16384 2048 2048
H264_BASELINE 41 16384 2048 2048
H264_MAIN 41 16384 2048 2048
H264_HIGH 41 16384 2048 2048
VC1_SIMPLE 1 16384 2048 2048
VC1_MAIN 2 16384 2048 2048
VC1_ADVANCED 4 16384 2048 2048
MPEG4_PART2_SP --- not supported ---
MPEG4_PART2_ASP --- not supported ---
DIVX4_QMOBILE --- not supported ---
DIVX4_MOBILE --- not supported ---
DIVX4_HOME_THEATER --- not supported ---
DIVX4_HD_1080P --- not supported ---
DIVX5_QMOBILE --- not supported ---
DIVX5_MOBILE --- not supported ---
DIVX5_HOME_THEATER --- not supported ---
DIVX5_HD_1080P --- not supported ---
H264_CONSTRAINED_BASELINE 0 16384 2048 2048
H264_EXTENDED --- not supported ---
H264_PROGRESSIVE_HIGH --- not supported ---
H264_CONSTRAINED_HIGH --- not supported ---
H264_HIGH_444_PREDICTIVE --- not supported ---
HEVC_MAIN --- not supported ---
HEVC_MAIN_10 --- not supported ---
HEVC_MAIN_STILL --- not supported ---
HEVC_MAIN_12 --- not supported ---
HEVC_MAIN_444 --- not supported ---
Output surface:
name width height nat types
----------------------------------------------------
B8G8R8A8 8192 8192 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A4I4 I4A4 A8I8 I8A8
R8G8B8A8 8192 8192 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A4I4 I4A4 A8I8 I8A8
R10G10B10A2 8192 8192 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A4I4 I4A4 A8I8 I8A8
B10G10R10A2 8192 8192 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A4I4 I4A4 A8I8 I8A8
Bitmap surface:
name width height
------------------------------
B8G8R8A8 8192 8192
R8G8B8A8 8192 8192
R10G10B10A2 8192 8192
B10G10R10A2 8192 8192
A8 8192 8192
Video mixer:
feature name sup
------------------------------------
DEINTERLACE_TEMPORAL y
DEINTERLACE_TEMPORAL_SPATIAL -
INVERSE_TELECINE -
NOISE_REDUCTION y
SHARPNESS y
LUMA_KEY y
HIGH QUALITY SCALING - L1 y
HIGH QUALITY SCALING - L2 -
HIGH QUALITY SCALING - L3 -
HIGH QUALITY SCALING - L4 -
HIGH QUALITY SCALING - L5 -
HIGH QUALITY SCALING - L6 -
HIGH QUALITY SCALING - L7 -
HIGH QUALITY SCALING - L8 -
HIGH QUALITY SCALING - L9 -
parameter name sup min max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH y 48 2048
VIDEO_SURFACE_HEIGHT y 48 2048
CHROMA_TYPE y
LAYERS y 0 4
attribute name sup min max
-----------------------------------------------------
BACKGROUND_COLOR y
CSC_MATRIX y
NOISE_REDUCTION_LEVEL y 0.00 1.00
SHARPNESS_LEVEL y -1.00 1.00
LUMA_KEY_MIN_LUMA y
LUMA_KEY_MAX_LUMA y If you want me to provide more information let me know.
Thanks in advance.
Last edited by leopseft (2019-02-24 22:58:09)
Offline
#2 2018-09-05 18:19:33
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,427
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
If you remove xf86-video-nouveau and simply use the modesetting driver that's built into xorg, does the problem disappear?
Edit: Ah you tried that, yes you can do that xf86-video-nouveau isn't necessarily required and these days the modesetting driver might see more active development, so if that works for you you can definitely do that. The vdpauinfo output also looks like I'd expect it to.
Last edited by V1del (2018-09-05 18:21:16)
Offline
#3 2018-09-05 18:24:14
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
If you remove xf86-video-nouveau and simply use the modesetting driver that's built into xorg, does the problem disappear?
Edit: Ah you tried that, yes you can do that xf86-video-nouveau isn't necessarily required and these days the modesetting driver might see more active development, so if that works for you you can definitely do that. The vdpauinfo output also looks like I'd expect it to.
For the distorted desktop images mix flash, yes. But for the slowly and laggy behavior while log out confirm dialog no.
So im wondering whats wrong for this happening the 2d or the 3d acceleration configuration.
Last edited by leopseft (2018-09-05 18:33:56)
Offline
#4 2018-09-06 09:05:28
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,427
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
FWIW though I doubt this to be an issue can you post
glxinfo | grep OpenGL #Needs mesa-demosMaybe the blur effect is taking its toll on that old card, check if you can disable that (not on my KDE but should be somewhere in workspace or window effects).
Offline
#5 2018-09-06 21:08:52
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
FWIW though I doubt this to be an issue can you post
glxinfo | grep OpenGL #Needs mesa-demosMaybe the blur effect is taking its toll on that old card, check if you can disable that (not on my KDE but should be somewhere in workspace or window effects).
Well as i said this effect becomes completely transparent if i install just the nvidia utils and not the nvidia drivers. So i believe that my card isnt so old that cant handle this effect and should be the driver or the config...
$ glxinfo | grep OpenGL
OpenGL vendor string: nouveau
OpenGL renderer string: NV98
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.1.7
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.1.7
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.1.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:Offline
#6 2018-09-07 08:48:04
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,427
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
And your acceleration still works if you do that? I doubt it. Other things you could do is switching the compositing backends (to e.g. GL2 or even to XRender) FWIW can you post
qdbus org.kde.KWin /KWin org.kde.KWin.supportInformationfrom a "sluggish" and from a non sluggish session?
Offline
#7 2018-09-08 14:49:13
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
And your acceleration still works if you do that? I doubt it. Other things you could do is switching the compositing backends (to e.g. GL2 or even to XRender) FWIW can you post
qdbus org.kde.KWin /KWin org.kde.KWin.supportInformationfrom a "sluggish" and from a non sluggish session?
So... I thing we re both right... You re rignt that if i install only the nvidia utils without the nvidia drivers the blur effect doesnt work at all, thats why everything its completely transparent. But, if i install the nvidia driver aswell the effect loads and works like a charm without mouse slowly response.... So am i doomed to use the closed source drivers in order to get a smooth hardware acceleration??
With nouveau:
https://preview.ibb.co/ipCRX9/Screensho … 164415.png
==========================
Version
=======
KWin version: 5.13.5
Qt Version: 5.11.1
Qt compile version: 5.11.1
XCB compile version: 1.13
Operation Mode: X11 only
Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes
X11
===
Vendor: The X.Org Foundation
Vendor Release: 12001000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0
Decoration
==========
Plugin: org.kde.breeze
Theme:
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular
smallSpacing: 2
largeSpacing: 10
Platform
==========
Name: KWin::X11StandalonePlatform
Options
=======
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 101
glPlatformInterface: 1
windowsBlockCompositing: true
Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0
Screens
=======
Multi-Head: no
Active screen follows mouse: no
Number of Screens: 1
Screen 0:
---------
Name: LVDS-1
Geometry: 0,0,1680x1050
Scale: 1
Refresh Rate: 59.8833
Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: nouveau
OpenGL renderer string: NV98
OpenGL version string: 3.1 Mesa 18.1.7
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40
Driver: Nouveau
GPU class: G80/G90
OpenGL version: 3.1
GLSL version: 1.40
Mesa version: 18.1.7
X server version: 1.20.1
Linux kernel version: 4.18.5
Direct rendering: Requires strict binding: yes
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace: no
Loaded Effects:
---------------
zoom
kwin4_effect_morphingpopups
kwin4_effect_dialogparent
kwin4_effect_translucency
kwin4_effect_windowaperture
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fade
kwin4_effect_logout
kwin4_effect_login
slidingpopups
slide
screenshot
minimizeanimation
desktopgrid
colorpicker
presentwindows
highlightwindow
blur
contrast
startupfeedback
screenedge
kscreen
Currently Active Effects:
-------------------------
blur
contrast
Effect Settings:
----------------
zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1
kwin4_effect_morphingpopups:
kwin4_effect_dialogparent:
kwin4_effect_translucency:
kwin4_effect_windowaperture:
kwin4_effect_maximize:
kwin4_effect_frozenapp:
kwin4_effect_fade:
kwin4_effect_logout:
kwin4_effect_login:
slidingpopups:
fadeInTime: 150
fadeOutTime: 250
slide:
screenshot:
minimizeanimation:
desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true
colorpicker:
presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 150
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0
rightButtonDesktop: 0
highlightwindow:
blur:
contrast:
startupfeedback:
type: 1
screenedge:
kscreen: with nouveau and nvidia utils:
https://preview.ibb.co/dEWyep/Screensho … 165437.png
==========================
Version
=======
KWin version: 5.13.5
Qt Version: 5.11.1
Qt compile version: 5.11.1
XCB compile version: 1.13
Operation Mode: X11 only
Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes
X11
===
Vendor: The X.Org Foundation
Vendor Release: 12001000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0
Decoration
==========
Plugin: org.kde.breeze
Theme:
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular
smallSpacing: 2
largeSpacing: 10
Platform
==========
Name: KWin::X11StandalonePlatform
Options
=======
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: true
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 97
glPlatformInterface: 1
windowsBlockCompositing: true
Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0
Screens
=======
Multi-Head: no
Active screen follows mouse: no
Number of Screens: 1
Screen 0:
---------
Name: LVDS-1
Geometry: 0,0,1680x1050
Scale: 1
Refresh Rate: 59.8833
Compositing
===========
Compositing is active
Compositing Type: XRender
Loaded Effects:
---------------
kwin4_effect_morphingpopups
kwin4_effect_dialogparent
kwin4_effect_translucency
kwin4_effect_windowaperture
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fade
kwin4_effect_logout
kwin4_effect_login
zoom
slidingpopups
slide
screenshot
minimizeanimation
desktopgrid
presentwindows
highlightwindow
screenedge
kscreen
Currently Active Effects:
-------------------------
Effect Settings:
----------------
kwin4_effect_morphingpopups:
kwin4_effect_dialogparent:
kwin4_effect_translucency:
kwin4_effect_windowaperture:
kwin4_effect_maximize:
kwin4_effect_frozenapp:
kwin4_effect_fade:
kwin4_effect_logout:
kwin4_effect_login:
zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1
slidingpopups:
fadeInTime: 150
fadeOutTime: 250
slide:
screenshot:
minimizeanimation:
desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true
presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 150
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0
rightButtonDesktop: 0
highlightwindow:
screenedge:
kscreen:i also get the notification bellow, dont know why (when installing just the utils or both drivers and utils from nvidia)
https://preview.ibb.co/dTPJep/Screensho … 165253.png
with nvidia drivers and nvidia utils:
https://preview.ibb.co/gTBLs9/Screensho … 172025.png
==========================
Version
=======
KWin version: 5.13.5
Qt Version: 5.11.1
Qt compile version: 5.11.1
XCB compile version: 1.13
Operation Mode: X11 only
Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes
X11
===
Vendor: The X.Org Foundation
Vendor Release: 12001000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0
Decoration
==========
Plugin: org.kde.breeze
Theme:
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 14
font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular
smallSpacing: 3
largeSpacing: 14
Platform
==========
Name: KWin::X11StandalonePlatform
Options
=======
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: true
Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0
Screens
=======
Multi-Head: no
Active screen follows mouse: no
Number of Screens: 1
Screen 0:
---------
Name: LVDS-0
Geometry: 0,0,1680x1050
Scale: 1
Refresh Rate: 59.8833
Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 9300M GS/PCIe/SSE2
OpenGL version string: 3.3.0 NVIDIA 340.107
OpenGL platform interface: GLX
OpenGL shading language version string: 3.30 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 340.107
GPU class: G80/G90
OpenGL version: 3.3
GLSL version: 3.30
X server version: 1.20.1
Linux kernel version: 4.18.5
Direct rendering: Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace: no
Loaded Effects:
---------------
zoom
kwin4_effect_morphingpopups
kwin4_effect_dialogparent
kwin4_effect_translucency
kwin4_effect_windowaperture
kwin4_effect_maximize
kwin4_effect_frozenapp
kwin4_effect_fade
kwin4_effect_logout
kwin4_effect_login
slidingpopups
slide
screenshot
minimizeanimation
desktopgrid
colorpicker
presentwindows
highlightwindow
blur
contrast
startupfeedback
screenedge
kscreen
Currently Active Effects:
-------------------------
blur
contrast
Effect Settings:
----------------
zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1
kwin4_effect_morphingpopups:
kwin4_effect_dialogparent:
kwin4_effect_translucency:
kwin4_effect_windowaperture:
kwin4_effect_maximize:
kwin4_effect_frozenapp:
kwin4_effect_fade:
kwin4_effect_logout:
kwin4_effect_login:
slidingpopups:
fadeInTime: 150
fadeOutTime: 250
slide:
screenshot:
minimizeanimation:
desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true
colorpicker:
presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 150
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0
rightButtonDesktop: 0
highlightwindow:
blur:
contrast:
startupfeedback:
type: 1
screenedge:
kscreen: Mod Edit - Replaced oversized images with links.
CoC - Pasting pictures and code
Last edited by Slithery (2018-09-08 17:18:21)
Offline
#8 2018-09-08 15:04:27
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 25,427
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
I was more specifically talking about the Compositing settings in Display and Monitor -> Compositor or
kcmshell5 kwincompositingBut yes your outputs confirm it, it will simply fallback to XRender on the nvidia-utils and nouveau case, you could try specifically setting that and if you can live with that use nouveau but keep KWin on the XRender backend. However
So am i doomed to use the closed source drivers in order to get a smooth hardware acceleration?
that is pretty much the case with nvidia cards. Nouveau developers do not receive the kind of support for free drivers the other graphics vendors offer and thus will always be playing catch-up while nvidia provides well working proprietary offerings.
Offline
#9 2018-09-08 19:14:39
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
To be honest i ve tried that before you told me, i dont know if i need to reboot in order to take affect but i haven't seen any difference in the acceleration between openGL2.0 or 3.1. But im not sure about those settings cause in that dialog menu it has set the 2.0 version as highlighted that doesn't agree with the kosnole's output version.
Anyway do you have any idea about that Plasma Renderer notification? Should i just ignore it and hide it? Or maybe if i delete the .kde and .config.
And one last question about the proprietary drivers. When i use them i just install them i dont make any changes like generating the X11 config. Is it really necessary to generate it?
In fact except from the hardware acceleration it doesn't work so perfectly for instance in videos and i ve also need to check the force fonts dpi to 96 DPI cause everything is really huge with the closed drivers.
Nouveau developers have done amazing job without the appropriate support. If they had it they would have done miracles.
Edit: To answer my question by deleting the .kde and the .config folder indeed disappears the Plasma Renderer notification.
Last edited by leopseft (2018-09-08 22:10:28)
Offline
#10 2018-09-08 19:27:26
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,104
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
nvidia-340xx-utils supplies etc/ld.so.conf.d/00-nvidia.conf which contains /usr/lib/nvidia/ which means libs in /usr/lib/nvidia will be used in preference to /usr/lib
this has the result of nvidia libgl always being used as long as nvidia-340xx-utils is installed which breaks nouveau providing hardware acceleration using mesa.
nvidia will stop proving support for 340xx at the end of 2019 as per https://nvidia.custhelp.com/app/answers … /a_id/3142
Offline
#11 2018-09-08 21:26:40
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
nvidia-340xx-utils supplies etc/ld.so.conf.d/00-nvidia.conf which contains /usr/lib/nvidia/ which means libs in /usr/lib/nvidia will be used in preference to /usr/lib
this has the result of nvidia libgl always being used as long as nvidia-340xx-utils is installed which breaks nouveau providing hardware acceleration using mesa.
nvidia will stop proving support for 340xx at the end of 2019 as per https://nvidia.custhelp.com/app/answers … /a_id/3142
So thats why i dont need to generate the config? I use this legacy driver because i think this is the correct one for my card model. I ll check the nvidia and post back.
Edit: Doesnt work with the nvidia as i imagined. The nvdia-340xx is the correct one.
Last edited by leopseft (2018-09-08 21:47:35)
Offline
#12 2018-09-08 21:47:21
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,104
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
You do not need to generate an /etc/X11/Xorg.conf as Xorg autodetection detects the present devices and configures itself accordingly for most situations.
nvidia-xconfig generates a config that breaks all hybrid graphics configurations and in single GPU configurations what it does generate contains numerous settings that X will ignore as no longer supported or are already defeault.
Xorg :0 -configure generates a better configuration compared to the above but if you actually need configuration I would suggest using a .conf file in /etc/X11/xorg.conf.d setting just the option you want to change.
Offline
#13 2018-09-08 21:50:59
- leopseft
- Member
- Registered: 2018-09-05
- Posts: 29
Re: Making 2d/3d acceleration working better with nouveau drivers [Solved]
You do not need to generate an /etc/X11/Xorg.conf as Xorg autodetection detects the present devices and configures itself accordingly for most situations.
nvidia-xconfig generates a config that breaks all hybrid graphics configurations and in single GPU configurations what it does generate contains numerous settings that X will ignore as no longer supported or are already defeault.
Xorg :0 -configure generates a better configuration compared to the above but if you actually need configuration I would suggest using a .conf file in /etc/X11/xorg.conf.d setting just the option you want to change.
So you need the config only when you want to change a setting. Thank you for your help!!
Offline