CPU Usage running almost 100% - What is going on?

English Applications
#1

Last night I shut down my machine and this morning on starting I found my mouse very sluggish so I checked my System Monitor and am seeing two possible culprits I do not understand:-
kwin_wayland, now showing averages of 60%
baloo_file, now almost constant at 4%

Since I have only just enabled my pCloudDrive I can understand that baloo might be busy. I still don’t know if it is any use!!!

I have not a clue about kwin_wayland. I consciously did not include wayland when I selected the patterns for the upgrade and noted that wayland was not highlighted so I have no idea why wayland is involved. At some point I am able and willing to switch over to wayland but I would like to do this on my choice and understanding what I am doing.

Meanwhile as I type my cpu usage and mouse behaviour are still very difficult and would make some work tasks tiresome.
Any ideas?

#2

I assume TW has brought some new challenges and this issue with kwin_wayland is the start. Here is the information on kwin from my system:-

alastair@HP-Z640-1:~> qdbus org.kde.KWin /KWin supportInformation
If 'qdbus' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf qdbus
alastair@HP-Z640-1:~> sudo qdbus org.kde.KWin /KWin supportInformation
[sudo] password for root: 
sudo: qdbus: command not found
alastair@HP-Z640-1:~> qdbus-qt5 org.kde.KWin /KWin supportInformation
KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.27.7
Qt Version: 5.15.10
Qt compile version: 5.15.10
XCB compile version: 1.15

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: SUSE LINUX
Vendor Release: 12301002
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: 
Plugin recommends border size: None
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: 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
=======
Active screen follows mouse:  yes
Number of Screens: 1

Screen 0:
---------
Name: DP-2
Enabled: 1
Geometry: 0,0,2560x1440
Scale: 1
Refresh Rate: 59951
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL version string: 4.5 (Core Profile) Mesa 23.1.5
OpenGL platform interface: EGL
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class: Unknown
OpenGL version: 4.5
GLSL version: 4.50
Mesa version: 23.1.5
Linux kernel version: 6.4.11
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
screenshot
screenedge
zoom
desktopgrid
highlightwindow
overview
tileseditor
windowview
startupfeedback
kscreen

Currently Active Effects:
-------------------------

Effect Settings:
----------------
colorpicker:

outputlocator:

screenshot:

screenedge:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

desktopgrid:
activeView: 
gridRows: 1
gridColumns: 1
animationDuration: 150
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 150
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 150
layout: 1
ignoreMinimized: false
mode: 115
partialActivationFactor: 0
gestureInProgress: false
searchText: 

startupfeedback:
type: 1

kscreen:


Loaded Plugins:
---------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

alastair@HP-Z640-1:~>

Can anybody pick the bones out of this?

#3

You can choose the preferred desktop session at the login screen. If the Plasma Wayland session is not working for you, log out and select Plasma X11 instead.

#4

Hi Dean,
Many thanks. Just starting again with TW on this machine I thought the option was not there but it is and I have been able to select it and now at least I can work.
I feel I have jumped from the pan to the fire!

I note that there are many posts about the cpu problem but most are specific to other systems or their own problems. Not much help on openSUSE that I can find but I live in hope.

#5

Graphics hardware?

inxi -Ga
#6

Hi Dean. Thanks for picking up on this. Here is my result:-

alastair@HP-Z640-1:~> inxi -Ga
Graphics:
  Device-1: NVIDIA GK107 [NVS 510] driver: nvidia v: 470.199.02
    alternate: nouveau,nvidia_drm non-free: series: 470.xx+
    status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
    process: TSMC 28nm built: 2012-18 pcie: gen: 2 speed: 5 GT/s lanes: 16
    ports: active: none off: DP-2 empty: DP-1,DP-3,DP-4 bus-ID: 03:00.0
    chip-ID: 10de:0ffd class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_x11 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 118 s-size: 551x313mm (21.69x12.32")
    s-diag: 634mm (24.95")
  Monitor-1: DP-2 mapped: DP-5 note: disabled model: Asus PB258
    serial: FCLMTJ054496 built: 2015 res: 2560x1440 hz: 60 dpi: 118 gamma: 1.2
    size: 553x311mm (21.77x12.24") diag: 634mm (25") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: OpenGL v: 4.6.0 NVIDIA 470.199.02 renderer: NVS 510/PCIe/SSE2
    direct-render: Yes
alastair@HP-Z640-1:~>
#7

The Plasma/Wayland/Nvidia - KDE Community Wiki suggests that this driver is too old for Wayland.

#8

Hi and thanks for this. I assume however that the driver that is installed is the “best” that I can use on my existing graphics card given that my system includes proprietary drivers but perhaps not. How do I find out?

If I have maxed out the capability of my existing card how do I find out what are the parameters I need to check in the specifications for a possible newer replacement which would be compatible with my HP_Z640?

#9

Maybe go for an nvidia rtx with probably 8GB memory. My guess is to consider your power supply and the pcie type also.

#10

@Budgie2 As indicated if you want to stay with Nvidia a RTX, or depending on your needs a T series Mobile RTX.

inxi -Ga

Graphics:
  Device-1: NVIDIA GP104GL [Tesla P4] driver: nvidia v: 535.104.05
    alternate: nouveau,nvidia_drm non-free: N/A status: unknown device ID pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
    bus-ID: 03:00.0 chip-ID: 10de:1bb3 class-ID: 0302
  Device-2: NVIDIA TU117GLM [Quadro T400 Mobile] driver: nvidia
    v: 535.104.05 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DP-1,DP-2,DP-3 empty: none bus-ID: 04:00.0
    chip-ID: 10de:1fb2 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: gnome-shell v: 44.3 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x572mm (40.00x22.52")
    s-diag: 1166mm (45.9")
  Monitor-1: DP-1 pos: top-left res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  Monitor-2: DP-3 pos: primary,bottom-c res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  Monitor-3: DP-5 pos: top-right res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  Monitor-4: DVI-D-1-0 size-res: N/A modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.104.05 renderer: NVIDIA T400/PCIe/SSE2
    direct-render: Yes

Whilst the model I have only has 2GB of RAM, it’s sufficient for my needs as have the P4 for offload for more graphics demanding applications.

The T series also don’t use much power and can use the X16 3.0 slot fine. If was going to replace it I’d look at the T1000 with just 4GB.

#11

I’m wondering if something in one of the recent changes to the Plasma packages might be causing something…I haven’t had many historical issues with my gaming laptop, but over the past couple days I’ve noticed some full system 1-2 second pauses (not the AMD fTPM style stutters, but full pauses)…

Then, last night, about 30 seconds after launching a full screen game, I experienced a near-freeze so hardcore I needed to Magic SysRq out of it, but it wasn’t totally frozen - it must have been some crazy CPU usage, because the Caps Lock light took about 30 seconds to respond but eventually did. Could just be random, of course, but maybe something related?

My system info:

Operating System: openSUSE Tumbleweed 20230823
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10
Kernel Version: 6.4.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: HP Pavilion Gaming Laptop 15-ec2xxx

What the system logs show leading up to the “freeze”:

Aug 25 22:18:31 hostname plasmashell[2168]: file:///usr/share/plasma/plasmoids/org.kde.kscreen/contents/ui/InhibitionHint.qml:27:5: QML Label: Binding loop detected for property "verticalAlignment"
Aug 25 22:18:33 hostname plasmashell[17419]: [17471:17471:0825/221833.504362:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
Aug 25 22:18:33 hostname plasmashell[17419]: [17471:17471:0825/221833.510708:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:33 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556b9b04a10, parent=0x5556b9a67250, geometry=0,0 63x23.5)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556ba102430, parent=0x5556b95d3f20, geometry=0,0 246x115)
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556ba102430, parent=0x5556b95d3f20, geometry=0,0 246x115)
Aug 25 22:18:34 hostname kwin_wayland[2043]: kwin_screencast: Dropping a screencast frame because the compositor is slow
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556ba102430, parent=0x5556b95d3f20, geometry=0,0 246x115)
Aug 25 22:18:34 hostname pipewire[2409]: mod.client-node: 0x563c6cd71650: unknown peer 0x563c6ce9af10 fd:67
Aug 25 22:18:34 hostname plasmashell[2168]: kpipewire_logging: Window not available PipeWireSourceItem_QML_1065(0x5556ba068760, parent=0x5556b9a78930, geometry=0,0 63x23.5)
Aug 25 22:18:38 hostname systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 25 22:18:42 hostname plasmashell[18048]: Assertion failed: !status && "vkQueuePresentKHR", file ../src-wine/dlls/winevulkan/loader_thunks.c, line 5517
Aug 25 22:18:42 hostname plasmashell[18048]:

Sorry if this is unrelated, but maybe a connection?

#12

If your existing NVidia is in an electrically standard PCIeX16 slot, then any PCIe card v3.0 or above that fits the chassis should be 100% compatible. Pre-3.0 cards would most likely work fine as well. There’s some very slight chance that a new PCIe 6.0 card of any brand could be less than ideal for an older PC with PCIe 3.0, but vendors generally offer a return/exchange policy you could use to deal with such an event.

Now is your opportunity to switch to a gfxcard that offers an expectation of support for more than 10 years. If you’re adventurous you might try one of the new Intel gfxcards. Both Intel and AMD provide support by long having been, and continuing to be, active contributors to FOSS gfx driver development and maintenance that NVidia only just started, which it does only for the newest of its products.

#13

Hi and thanks for the suggestions. I have no particular need or wish to stay with Nvidia. My power supply should be OK at about 950W but I may have slot space issues as I have a second processor board and on the Z640 it has a large add-in module taking up space and slot space.

I will check the specs as I am not sure about mobo options. Perhaps Malcolm can advise as he is familiar with HP Z machines.

I am not a gamer so do not seek anything special although working with photos with digiKam will need a suitable card. Low power and noise are favoured over gee whiz speed. Not urgent if my system remains stable but if it goes wrong again I shall have to get a new card as I have wasted hours of my and your time and work has suffered.

Thanks again, will check out gfx cards.

#14

Hi Malcolm,
I am lost in the maze of graphics cards and specs. My machine is an HP Z640 with add-in second processor so not sure about slot availability and width available. I can open up and check but I do have some recollection that there is significance between P3 and P4 with respect to processors. I shall have to check the documentation about what fits but I am not anxious to spend any more than I have to.
I note that the T1000 is significantly more expensive than the Tesla P4 although most are selling from China so have to be careful but there are new Tesla P4 8Gb at around GBP 80.00 whereas the T1000 are much more.
What about mrmazda’s suggestions. What is the AMD equivalent to your own Tesla P4 and why do you prefer the T1000?

#15

@Budgie2 The Tesla P4 is a vGPU, no outputs :wink: For virtualization, CUDA and Prime Render Offload… That price sounds about right, they are all second-hand or refurbished, mine is but not from China…

The Quadro T series are low profile (like the Tesla P4) the T400 I have has three outputs (mini-HDMI) is a x16, PCIe 3.0 card with 2GB of RAM and uses a max of 30W. I’ve not had any RAM issues as in getting to the full 2GB.

The T1000 has a few more cores, RAM and 4 outputs.

If you went the AMD way, I have an RX550 with 4 standard HDMI outputs in runs fine, only an x8 card and 2GB of RAM.

Look for something in the workstation AMD Series Wxxxx that may work.

Note: HP Z series workstations if you run a second GPU will need a front fan installed else you get a BIOS warning…

#16

Hi Malcolm, many thanks for the additional info. Not sure I understand it all. First my processors are V3 (not P3) and memory is suited for V3 not V4 which runs on faster memory afaik. I am not anxious to change processors and funds are tight.
Regarding fans I am not sure about front fan but I believe it is lurking behind a plastic moulding and almost impossible to see. I have not had any BIOS complaints about cooling.

I do not understand the “no outputs.” Would that mean I needed another card. Not for me I think.

I have AMD RX 550 and AMD Radeon Pro WX7100, Nvidia Quadro T400 and T1000 all available on ebay at around GBP150 except the T1000 which is significantly more. The WX7100 looks like a good fit, included in HP docs as as suitable, card has 130w max listed and slot OK for 150 max (or 2x75).
I think I shall look out for one on ebay. No rush at present as I have not had a crash all day!!!
Regards,
Alastair.

#17

@Budgie2 Not the CPU Version as such, but PCIe 3.0 relates to the card slots. Need to see the specs for the CPU to see what it supports lscpu | grep "Model name:"

Yes the Telsa cards are not for you :wink:

The WX7100 sounds good, but I think a T400 also would be fine.

#18

Hi Malcolm,
Here is what I have on my HP_Z640_1 system:-

alastair@HP-Z640-1:~> lscpu | grep "Model name:"
Model name:                         Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz

This is what I had understood. What I could not work out is whether by mobo can work with V4 processors if I wanted to? I am not rushing to change as with the necessary memory upgrade it would be very expensive for little return.

OTOH the graphics processor is worth pursuing and I have found a suitable WX7100 on line so have decided to go ahead. Will get back to you when I have it if I have any problems but fingers crossed.
Regards,
Alastair.

#19

@Budgie2 You CPU is PCIe 3.0 specification;
https://ark.intel.com/content/www/us/en/ark/products/83352/intel-xeon-processor-e52620-v3-15m-cache-2-40-ghz.html

Don’t confuse the v3 or v4 CPU designation, that is not related to PCIe specification :wink:

#20

OK, I understand my board has PCIe 3.0. My question is will the v4 cpus work in my machine?