My second comment about a different GPU was just offered to cover the base of possibly not having motherboard port(s) with which to connect your display to your built-in newer, and apparently much faster, iGPU. Simply removing an ancient GPU in order to use the already present UHD 630 Intel iGPU should be easy-peasy, remove one screw and flip a plastic tab to release it once the cover is off, all at zero monetary cost if you already have the right cable. I wonder why that old NVidia was in your obviously much newer computer (5 years?) in the first place. 
1 Like
Ah, I think I better understand your post now. Are you saying that my motherboard port(s) will become active once I remove the GT 710?
Very likely, just check the system BIOS as well for GPU selectionâŚ
1 Like
Okay I will look into that. You give me hope sir. And, yes, I too wonder about the build I was handed by a local company. In hindsight, I made a mistake ordering a custom build through them. Lesson learned.
They certainly should. Most BIOS by default automatically select a dGPU if one is present, otherwise, the iGPU is used. They do usually offer overrides, which if selected, may (but should not) prevent use of the iGPU if not de-selected before dGPU removal, so check before dGPU removal to be sure of a compatible setting. Best also before removing dGPU, ensure kernel-firmware-i915 is installed. It may be more trouble to install after than before. Another possible annoyance is your initrd(s) may need to be regenerated before graphics output is fully performant.
If you bought that PC used, itâs possible the dGPU was in it because of some problem with use of the iGPU.
1 Like
Okay, I have verified kernel-firmware-i915 is installed, and I have set BIOS to enable: âiGPU Multi-Monitor,â and plugged the monitor into the motherboard. A HUGE improvement: the CPU fan is now not running at all, whereas before, the CPU fan was running like crazy. Also the display slightly lagging is GONE. Now, I want to follow up and remove that old GT 710. Question: Should I first select: âCPU Graphics as the Primary Displayâ in the BIOS before removing the GPU? Or, should I simply leave it as is, without removal of the GPU?
System:
Kernel: 6.12.0-160000.36-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.36-default
root=UUID=1090b6a1-8b8c-484e-be29-473817fbca16 splash=silent
mitigations=auto quiet security=selinux selinux=1 intel_iommu=on
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: HDMI-A-4 empty: DP-1, DP-2, DP-3, HDMI-A-2, HDMI-A-3
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Device-2: NVIDIA GK208B [GeForce GT 710] vendor: PNY driver: nouveau
v: kernel non-free: series: 470.xx+ status: legacy-active (EOL~2024-09-xx)
arch: Fermi-2 code: GF119/GK208 process: TSMC 28nm built: 2010-2016 pcie:
gen: 2 speed: 5 GT/s lanes: 8 ports: active: none
empty: DVI-D-1,HDMI-A-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:128b
class-ID: 0300 temp: 40.0 C
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel,nouveau,nv,nvidia dri: iris,nouveau gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-4 mapped: HDMI-4 model: ViewSonic VX3276-FHD
serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau platforms:
device: 0 drv: nouveau device: 1 drv: iris device: 2 drv: swrast gbm:
drv: nouveau surfaceless: drv: nouveau x11: drv: iris inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
device-ID: 8086:3e98 memory: 7.53 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CFL GT2) driver: N/A device-ID: 8086:3e98
surfaces: xcb,xlib
The meaning of BIOS settings for graphics devices are often clear as mud. I doubt you need to, but itâs certainly appropriate. If you were to do a full BIOS reset, whatever turns up there would be appropriate as well.
In one of my Haswells, an MSI motherboard with only an iGPU installed, âInitiate Graphics Adapterâ offers PEG (PCI Express Graphics, meaning dGPU (discrete)), and IGD (Integrated Graphics Device), which is set on PEG. It also has âIGD Multi-Monitorâ, which offers âenabledâ and âdisabledâ, which is set on âdisabledâ. Thus, itâs smart enough to use the iGPU when no dGPU is present even though it prefers a dGPU. AIUI, multi-monitor is to enable use of both iGPU and dGPU outputs, something I donât remember ever trying. On all my motherboards that have both, I only use the dGPU.
1 Like
Okay, I went ahead and removed the old GT 710 GPU, just to be sure zero resources were devoted to having it installed. I took the opportunity to clean the fans and all. Also discovered the computer builder used the tiniest dab of heat-sink compound on the CPU, so I made some up by mixing some small aluminum filings with a little lithium grease (when you live in the middle of nowhere, you learn to make do). There is now plenty of compound between the CPU and its heat sink.
In the BIOS, I disabled Dual-Monitor, and set the Primary Display to CPU Graphics. Everything seems to be running nice and quiet, with zero display lagging. There is one bit of an oddity, however: Running inxi -GSaz now returns the following, which is now missing the System: settings:
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: HDMI-A-3 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-3 mapped: HDMI-3 model: ViewSonic VX3276-FHD
serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
device-ID: 8086:3e98 memory: 7.53 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CFL GT2) driver: N/A device-ID: 8086:3e98
surfaces: xcb,xlib
Sensors:
System Temperatures: cpu: 72.0 C mobo: N/A
Fan Speeds (rpm): N/A
Does anyone know why this change occured? Here is the o/p of inxi -GSaz prior to making these GPU changes:
System:
Kernel: 6.12.0-160000.36-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.36-default
root=UUID=1090b6a1-8b8c-484e-be29-473817fbca16 splash=silent
mitigations=auto quiet security=selinux selinux=1
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: PNY driver: nouveau
v: kernel non-free: series: 470.xx+ status: legacy-active (EOL~2024-09-xx)
arch: Fermi-2 code: GF119/GK208 process: TSMC 28nm built: 2010-2016 pcie:
gen: 2 speed: 5 GT/s lanes: 8 ports: active: HDMI-A-1 empty: DVI-D-1,VGA-1
bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300 temp: 41.0 C
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,nouveau,nv,nvidia dri: nouveau gpu: nouveau
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: ViewSonic VX3276-FHD
serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: NV106 device-ID: 10de:128b memory: 1.94 GiB
unified: no
API: Vulkan Message: No Vulkan data available.
The first output is from inxi -Gsaz
The second output is from inxi -GSaz
-S and -s are different inxi options.
That is the reason why you always should post the terminal in- AND output including the initial command.
2 Likes
You got sensors instead of System, because itâs what you asked for. 
1 Like
Oh, got it. Thank you @hui and @mrmazda I am laughing pretty hard right now HAHA 
Okay, here is my current System Setting:
# inxi -GSaz
System:
Kernel: 6.12.0-160000.36-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.36-default
root=UUID=1090b6a1-8b8c-484e-be29-473817fbca16 splash=silent
mitigations=auto quiet security=selinux selinux=1 intel_iommu=on
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: HDMI-A-3 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-3 mapped: HDMI-3 model: ViewSonic VX3276-FHD
serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
device-ID: 8086:3e98 memory: 7.53 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CFL GT2) driver: N/A device-ID: 8086:3e98
surfaces: xcb,xlib
Everything seems nice and smooth. I will keep an eye on things for a day or two, and likely it will then be time to mark this âSOLVEDâ
Thank you @mrmazda @hui @malcolmlewis
I donât know what intel_iommu=on is good for. I havenât had use for it in the past 5 years, if ever. @malcolmlewis suggested it while you were still trying to get satisfaction from the GT 710, so probably itâs inapplicable now.
That looks fishy to me for a Plasma user, possibly fixed since Leapâs ancient inxi version 3.3.36. Inxi is at 3.3.41 now. OP should be able to upgrade to 3.3.41 thus: sudo inxi -U to see if it makes any difference.
1 Like
@mrmazda itâs a hardware security item, dma attacks. But also has benifits (IMHO) for hardware to be in itâs own iommu group when using virtualization. Systems seem to have it enabled in the BIOS automatically these daysâŚ
@bgreen777 I have multiple systems with the same GPU, one Leap 16.0, but itâs primary card is a Turing based Quadro T400 and this hardware switches the 630 gpu to a display controller for offload tasks especially when using wayland.
You should consider switching from X11 as wellâŚ
One other note if you look at the following inxi output (Tumbleweed/Hyprland) I have intel_pstate=passive as this CPU did not speed step clock frequiencies, so may be worth checking your setup and add if needed.
System:
Kernel: 7.1.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
clocksource: tsc avail: acpi_pm
parameters: initrd=\opensuse-tumbleweed\7.1.5-1-default\initrd-40f42a2f20183dc0fed5cd0af00f91cc33f09cca
root=UUID=964c5751-aca1-42e5-a10f-9ff5ee925b25 splash=silent
mitigations=auto quiet security= intel_iommu=on selinux=1
security=selinux intel_pstate=passive
Desktop: Hyprland v: 0.56.1 tools: hypridle
avail: hyprlock,swayidle,swaylock vt: 1 dm: N/A Distro: openSUSE Tumbleweed
20260803
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: Dell driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: HDMI-A-2 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-3 bus-ID: 00:02.0
chip-ID: 8086:9bc8 class-ID: 0300
Display: wayland server: Xwayland v: 24.1.13 compositor: Hyprland
v: 0.56.1 driver: gpu: i915 display-ID: 1
Monitor-1: HDMI-A-2 model: DT-156P-A1 serial: <filter> built: 2021
res: 1920x1080 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.6 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CML GT2)
device-ID: 8086:9bc8 memory: 14.88 GiB unified: yes
API: Vulkan v: 1.4.357 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CML GT2) driver: mesa intel v: 26.1.6
device-ID: 8086:9bc8 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 22.1.8 256 bits) driver: mesa llvmpipe v: 26.1.6 (LLVM 22.1.8)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo gpu: gputop,
intel_gpu_top, lsgpu wl: kanshi,swaymsg x11: xprop
If you want to see the hardware security (folks seem focused on software security?) run the command fwupdmgr security if you want links to the items pass or fail use fwupdmgr security --show-all
1 Like
Okay, as suggested by @mrmazda I ran sudo inxi -Uand so:
# inxi --version
inxi 3.3.41-00 (2026-07-01)
Also, I had removed intel_iommu=on as suggested, but if I understood @malcolmlewis correctly, it might make sense to have it, so I added it back.
As far as Wayland goes, per advice from @malcolmlewis I attempted to switch from X11, but every time I booted up, as soon as I attempted loading Chrome my computer rebooted. I tried several times with the same result. Wayland does not seem to like me. Prior to joining the openSUSE community, I ran with Garuda Linux for about 7 years. At one point, I attempted Wayland, and it seemed to cause thinkorswim app to suddenly quit after awhile. Switching back to X11 cured this. I switched to openSUSE when a recent Garuda update caused a glitching login screen. It seemed to be KDE-related, but the forum and I could not seem to find the fix for me, so I was running on a weeks-old snapshot. Thus, here I am, and I am liking it here at openSUSE. My computer is now running quieter and more efficient than it ever has. By far.
@malcolmlewis thank you for the additional advice on clocking and security. I will be studying up on those now.
# inxi -GSaz
System:
Kernel: 6.12.0-160000.36-default arch: x86_64 bits: 64 compiler: gcc
v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.36-default
root=UUID=1090b6a1-8b8c-484e-be29-473817fbca16 splash=silent
mitigations=auto quiet security=selinux selinux=1 intel_iommu=on
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: HDMI-A-3 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev,intel dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-3 mapped: HDMI-3 model: ViewSonic VX3276-FHD
serial: <filter> built: 2020 res: mode: 1920x1080 hz: 60 scale: 100% (1)
dpi: 70 gamma: 1.2 size: 698x393mm (27.48x15.47") diag: 801mm (31.5")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
device-ID: 8086:3e98 memory: 7.53 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CFL GT2) driver: mesa intel v: 24.3.3
device-ID: 8086:3e98 surfaces: xcb,xlib
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
You need to start the application from the command line when running Wayland to narrow down the issues, Iâve been running GNOME for awhile now on Wayland without issue, likewise Hyprland.
I suspect some environment tweaks are needed for the applications to behave.
1 Like
Okay, I am going to consider this issue âsolved.â The real âgroundbreakerâ for me was when @mrmazda stated:
Simply removing an ancient GPU in order to use the already present UHD 630 Intel iGPU should be easy-peasy
I had no idea I had that option, and had been solely focused on getting that darn GT710 to function. After removing that old GPU, and in the BIOS I disabled Dual-Monitor, and set the Primary Display to CPU Graphics. all my troubles seem to have vanished: my CPU fan quit running at a constant full-speed (barely runs now), and the display lag has completely disappeared. Further âtweaksâ suggested by @mrmazda @malcolmlewis and @hui have all been helpful, and I learned a lot.
I will continue to follow up with the suggestions by @malcolmlewis for further improvement, such as security, CPU clocking, utilizing Wayland and etc. I have a lot to learn, and these ideas will be a good starting point.
Meanwhile I cannot thank you enough. I am happy to have joined the openSUSE community. Folks like you are the backbone of the open source communityand your expertise is appreciated. Your useful combined knowledge of both software AND HARDWARE cannot be overstated. Thank you so kindly.
OPEN SOURCE IS THE WAY FORWARD
1 Like