Hello,
My computer has installed Leap 16.0 using updater from 15.6 to 16.0.
I have got some problems with my gtraphic card (non-integrated), so you suggested me to dissaqble some drivers. I did it. But: I don’t know how, in BIOS my boot is set on secure boot, but as I remember, last time, i set it on “simple” no-secure boot. Does it matter regarding graphic card problems, how boot is set?
Sorry if my question is stupid. Thank you for answering it.
Let us know what the problems are !!!
… do you have Intel or AMD hardware and does your cpu support graphics?
Hello, can you, please, tell me how to detect it. I just know it is not integrated. I am not familiar with hardware. I think it is intel graphics. Is there some command to detect it?
Thamk you for answering my questions.
This is what I get after applied command hwinfo --short
:
graphics card:
ATI Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM]
This is about processor:
cpu:
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
Intel(R) Core™ i5-9400 CPU @ 2.90GHz, 800 MHz
@vajcek Not having secure boot enabled or not should be be fine. It seems you have been running Leap 16.0 for some time now?
I refer you back to this thread https://forums.opensuse.org/t/screen-trembles-on-web-browsers-leap-16-0/191856
Is this the sort of problem your having?
Are you using the Mesa drivers from Packman?
Hello,
First of all: SUSE version of driver is checked in Myrlin and in brackets says “installed”.
Since topic @malcolmlewis mentions, I reconect my monitor: now it is connected to computer using HDMI connector.
Problem with display trembelling sometimes happens, but I think (it is my impression) - as system updates come, it is less and less. I think it is almost “zero appearence”.
I did not ask question in topic the right way: topis I started is because of boot priority before start installing: does the first to boot before installation have to be “secure boot Leap” or “simple” option (that not secure)? Does it make difference regarding graphic card functioning duriing installation and also when installing ended??
I think now I asked the way I wanted. Thank you for answering my questions.
Problem with trembeling My problem is now that screen suddenly freezes, then screen got black, be like that for a few saconds and then: either gets back like nothing happened, or I have to restart computer. I also hope that this would be solved after fresh installation of Leap 16.0.
Thank you for answering my questions.
@vajcek can you post the output from inxi -GSaz and perhaps @mrmazda can offer additional advice when he sees the output.
Oland is GCN#1 amdgpu, possibly troubling without employing cmdline options radeon.si_support=0 amdgpu.si_support=1 in /etc/default/grub’s GRUB_CMDLINE_LINUX_DEFAULT=. My Oland is in a system with CPU that does not support 16.0. I use those options in TW, 15.6, Fedora, Debian and Ubuntu in order to utilize the amdgpu kernel module, and, optionally, the amdgpu display driver, instead of the slower/older/default radeon kernel module.
@malcolmlewis here is:
zlatic@localhost:~> inxi -GSaz
System:
Kernel: 6.12.0-160000.29-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.29-default
root=UUID=950fca0f-94e8-472f-b494-9b60730573c9 splash=silent
resume=/dev/disk/by-uuid/514d3993-f4f2-40f5-a0af-a185edf2509a
preempt=full mitigations=auto quiet security=apparmor radeon.si_support=0
amdgpu.si_support=1 rd.driver.blacklist=radeon
Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_wayland tools: avail: xscreensaver vt: 1 dm: SDDM
Distro: openSUSE Leap 16.0
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Oland XT [Radeon HD 8670 / R5
340X OEM R7 250/350/350X OEM] vendor: ASUSTeK driver: amdgpu v: kernel
alternate: radeon arch: GCN-1 code: Southern Islands process: TSMC 28nm
built: 2011-20 pcie: gen: 3 speed: 8 GT/s lanes: 8 ports: active: HDMI-A-1
empty: DVI-D-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6610 class-ID: 0300
temp: 36.0 C
Device-2: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:5 chip-ID: 046d:0825
class-ID: 0102 serial: <filter>
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: AMD Radeon R7 200 Series (radeonsi oland LLVM
19.1.7 DRM 3.61 6.12.0-160000.29-default) device-ID: 1002:6610
memory: 1000 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 1 device: 0 type: discrete-gpu name: AMD
Radeon R7 200 Series (RADV OLAND) driver: N/A device-ID: 1002:6610
surfaces: xcb,xlib,way
If I just can add this about trambelng: I opened new user account in my computer and it trembeling- It is very strange to me, because I made new, thinking it would perfectly work. At the moment - my old account works better regarding trembelling.
Possibly it would be useful for you to run command glmark2 (if it runs in Wayland; otherwise, try running it in Plasma X11, or in both Wayland and X11) and report your score(s) here. With 15.6 and Plasma 5 on my Oland with Intel Core2 6700 CPU (2 cores, 2 threads), the following were run both with and without kernel cmdline option rd.driver.blacklist=radeon, and with (separately) both amdgpu display driver, and modesetting display driver:
host fi965 running amdgpu module & amdgpu DDX on 15.6/Plasma5 X11
cmdline parameters radeon.si_support=0 amdgpu.si_support=1 rd.driver.blacklist=radeon:
# glmark2
=======================================================
glmark2 2021.12
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 17.0.6, DRM 3.57, 6.4.0-150600.23.100-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 23.3.4
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
...
=======================================================
glmark2 Score: 1411
=======================================================
#
host fi965 running amdgpu module & modesetting DIX on 15.6/Plasma5 X11
cmdline parameters radeon.si_support=0 amdgpu.si_support=1 rd.driver.blacklist=radeon:
# glmark2
=======================================================
glmark2 2021.12
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 17.0.6, DRM 3.57, 6.4.0-150600.23.100-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 23.3.4
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
...
=======================================================
glmark2 Score: 1413
=======================================================
#
host fi965 amdgpu module & modesetting DIX on 15.6/Plasma5 X11
cmdline parameters radeon.si_support=0 amdgpu.si_support=1:
# glmark2
=======================================================
glmark2 2021.12
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 17.0.6, DRM 3.57, 6.4.0-150600.23.100-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 23.3.4
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
...
=======================================================
glmark2 Score: 1414
=======================================================
#
host fi965 running amdgpu module & amdgpu DDX on 15.6/Plasma5 X11
cmdline parameters radeon.si_support=0 amdgpu.si_support=1:
# glmark2
=======================================================
glmark2 2021.12
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 17.0.6, DRM 3.57, 6.4.0-150600.23.100-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 23.3.4
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
...
=======================================================
glmark2 Score: 1413
=======================================================
#
Aside conclusions:
rd.driver.blacklist=radeon does nothing more than bloat grub.cfg and logs; IOW, it’s unnecessary when radeon.si_support=0 amdgpu.si_support=1 are used.amdgpu DDX or modesetting DIX display driver along with amdgpu kernel module. (last I tested, it was markedly worse using radeon kernel module, aka not including radeon.si_support=0 amdgpu.si_support=1 parameters).Hello,
In new account I made (after upgrade from 15.6 to 16.0), command glmark2 gives
============================
glmark2 2023.01
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 19.1.7, DRM 3.61, 6.12.0-160000.29-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 24.3.3
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 6374 FrameTime: 0.157 ms
=======================================================
glmark2 Score: 6373
=======================================================
In account that rest from 15.6 and previous linux installations, I ve got:
localhost:~ # glmark2
=======================================================
glmark2 2023.01
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: AMD Radeon R7 200 Series (radeonsi, oland, LLVM 19.1.7, DRM 3.61, 6.12.0-160000.29-default)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 24.3.3
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 6316 FrameTime: 0.158 ms
=======================================================
glmark2 Score: 6315
=======================================================
Anotherone question: how can I know if I use plasma or wayland? How to do codse above in X11 (if I use X11)?
Thank you for answering my questions.
zlatic@localhost:~> echo $XDG_SESSION_TYPE
wayland
zlatic@localhost:~>
Sorry for this spamming. Result of command you suggested is in window above.
We already knew you’ve been running Wayland. 
I just ran glmark2 on an Intel Kaby Lake system from 2017 running Neon and Plasma 6 and scored 5708, indicating most likely that glmark2 scores on X11 and Wayland are not comparable. On Neon at least they are provided by separate packages: glmark2-x11 and glmark2-wayland:
# ls -Ggh /usr/bin/glmark2*
-rwxr-xr-x 1 588K Mar 31 2024 /usr/bin/glmark2
-rwxr-xr-x 1 616K Mar 31 2024 /usr/bin/glmark2-wayland
#
Your glmark2 scores suggests Wayland is doing fine, so your trouble likely has something to do with Plasma, unless what you’re experiencing is a faulty Oland, or your display or cable is faulty. If your Oland is a discrete GPU, you could try replacing it. If it’s an APU (part of the CPU, integrated), the issue might be solvable by CPU/APU replacement. inxi -CM output should show us whether a suitable change of CPU or discrete GPU might be practical, as well as suggesting whether your GPU is a discrete component. Before considering such replacements, try a different HDMI cable, and a different display. Most modern flat panel TVs have HDMI inputs, so you may already have a TV to test with.
This tells us inxi is unable to give us some display information that it provides from X11 sessions. Please show output from command wlr-randr, which produces similar info and may provide a clue to your issue.
Another thing that may help us understand what is happening is to make a video of your problem to show us using a mobile phone, uploaded via susepaste command.
This requires multiple answers and things to do. Some of them I can do just for weekends (after work, I am not that useful ).
Anyway, thank you for this answer. Regarding connectivity, things started to be a little bit better when I connect monitor via hdmi (previous it was VGA). My doubt is cable, but maybe connection on graphic card (…)
I tried to connec TV and PC using HDMI - it was perfect! Maybe I did not connected them long enough to shom some error, but - it did not show.
Now, test you suggested:
zlatic@localhost:~> inxi -CM
Machine:
Type: Desktop Mobo: Gigabyte model: H310M M.2 2.0 v: x.x
serial: <superuser required> UEFI: American Megatrends v: F13
date: 01/21/2020
CPU:
Info: 6-core model: Intel Core i5-9400 bits: 64 type: MCP cache: L2: 1.5 MiB
Speed (MHz): avg: 800 min/max: 800/4100 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800
zlatic@localhost:~>
Your i5-9400 was launched in Q1-19. Your Oland is about 6 years older, so very likely the iGPU in your i5-9400 would be a better performer. Your H310M motherboard provides both VGA and HDMI ports, so you should be able to simply remove the Oland from the PC, connect the HDMI cable to the motherboard’s HDMI port, boot Leap, and run glmark2 again to see whether it is the better performer, as well as whether it solves your issue.
For optimal performance from the UHD Graphics 630 in your i5-9400, you may need to remove display driver package xf86-video-intel, which is often installed by default, but rarely preferable to the modesetting display driver default. Showing inxi -GSaz output again after the change will let us know whether that would be necessary.
My friends, I almost everything (almosr, I said ) can type and click, but I musn’t touch any mechanical thing in computer. If I must, I would get back my integrated card, Friend of mine installed this independent videocard, because my idea was to get RAM-memory free for processor’s stuff.
There is not big chance for me to do it myself.
So, if you (now, when you know “my configuration”) can say: do I have to see option Secure boot or withouit secure boot when I install new operating system (my plain is to do one fresh installation of Leap 16.0)?
Thank you for help me. “You” is any of you helped me ever.
do I have to use… not see.
inxi -m output would report how much RAM you have so we can suggest whether RAM used by the iGPU would be consequential or not. Adding RAM could be less expensive than upgrading to a dGPU that performs better than what you have.