vajcek
February 17, 2026, 9:51am
1
Hello,
I updated my Leap from 15.6 to 16.0 using updater from YaST. Now, my Firefox and Chrome display tremble. Especially in Google-chromme.
What it needs to be added to make things right?
This is my repository list:
zlatic@localhost:~> LANG=C zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
--+-----------------------------+---------------------------+---------+-----------+---------+------+----------+--------+------------------------------------------------------------------------------+---------
1 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | openSUSE:repo-non-oss | repo-non-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
3 | openSUSE:repo-non-oss-debug | repo-non-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
4 | openSUSE:repo-openh264 | repo-openh264 (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap_16 | openSUSE
5 | openSUSE:repo-oss | repo-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
6 | openSUSE:repo-oss-debug | repo-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
7 | openSUSE:repo-oss-source | repo-oss-source (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/distribution/leap/16.0/repo/oss | openSUSE
8 | packman | packman | Yes | (r ) Yes | Yes | - | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/ |
9 | snappy | snappy | No | ---- | ---- | - | 99 | rpm-md | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.6 |
Thank you for answering my questions.
I don’t know the actual solution to your problem, sorry.
But just recently, you posted
Then afterwards and just now:
vajcek:
This is my repository list:
zlatic@localhost:~> LANG=C zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
--+-----------------------------+---------------------------+---------+-----------+---------+------+----------+--------+------------------------------------------------------------------------------+---------
1 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | openSUSE:repo-non-oss | repo-non-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
3 | openSUSE:repo-non-oss-debug | repo-non-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
4 | openSUSE:repo-openh264 | repo-openh264 (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap_16 | openSUSE
5 | openSUSE:repo-oss | repo-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
6 | openSUSE:repo-oss-debug | repo-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
7 | openSUSE:repo-oss-source | repo-oss-source (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/distribution/leap/16.0/repo/oss | openSUSE
8 | packman | packman | Yes | (r ) Yes | Yes | - | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/ |
9 | snappy | snappy | No | ---- | ----
Already back then it was said:
Maybe, your system is somehow badly scrambled?! In the past, your repo list was not OK at all , and it still isn’t for some aspect.
Maybe, during your upgrade, some things got mixed up and damaged.
What to do now — besides a fresh and clean install! — I don’t know, sorry.
vajcek
February 17, 2026, 11:27am
3
I did not touched anything in last upgrading. Also, Snappy Repository is disabled. I 've had to do this upgrade because time is running out for Leap 15.6, and also I have problems to partitioning disc with agama installer. I know fresh installation is solution, but there are some crucial questions. Thank you for your effort to help me.
mrmazda
February 17, 2026, 12:29pm
4
A solution may depend on your GPU(s). Please show inxi -GSaz here using PRE tagging (</> icon), or place your paste in between two lines containing only ``` on each, to preserve inxi’s formatting.
vajcek
February 17, 2026, 12:45pm
5
Here is copied from Console:
localhost:~ # inxi -GSaz
System:
Kernel: 6.12.0-160000.9-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.9-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
Console: pty pts/0 wm: kwin_wayland 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: radeon v: kernel
alternate: amdgpu 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,VGA-1 empty: DVI-D-1 bus-ID: 01:00.0 chip-ID: 1002:6610
class-ID: 0300 temp: 43.0 C
Display: unspecified 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: radeon display-ID: :1 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
s-diag: 583mm (22.95")
Monitor-1: VGA-1 res: 1920x1080 hz: 60 dpi: 93
size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.5 vendor: amd mesa v: 24.3.3 glx-v: 1.4
direct-render: yes renderer: OLAND (radeonsi LLVM 19.1.7 DRM 2.50
6.12.0-160000.9-default) device-ID: 1002:6610 memory: 1000 MiB unified: no
API: Vulkan Message: No Vulkan data available.
localhost:~ #
Thank you for help me.
mrmazda
February 17, 2026, 1:02pm
6
When inxi -G is run from a tty instead of within an X session, some of the data presented is either misleading and/or incomplete. e.g. you can see it says “unspecified” for Display, and “Console: pty” instead of the DE you are using.
Anyway, I have an Oland OEM as well, but in a PC not supporting 16.0, so cannot try to reproduce. You can try at your Grub menu appending the following to the linu line after striking the E key: radeon.si_support=0 amdgpu.si_support=1 before proceeding with boot. This should switch you from using the old radeon kernel module to the newer amdgpu for that one boot.
Also if you are using Wayland, try X11, and let us know if either makes any difference.
1 Like
@vajcek Consider switching to the amdgpu driver?
I use an additional option as well as the ones provided by @mrmazda … rd.driver.blacklist=radeon
My full entry is amdgpu.cik_support=1 amdgpu.si_support=0 amdgpu.ppfeaturemask=0xffffffff rd.driver.blacklist=radeon
AFAIK, only the relevant xf86 package provides blacklisting radeon, if not running Xorg, then add the option blacklist option and get the best of both worlds…
Part of my setup script for AMD;
if [ $AMD_GPU == 1 ]; then
echo "Adding AMD GPU options"
update-bootloader --add-option amdgpu.cik_support=1
update-bootloader --add-option amdgpu.si_support=0
update-bootloader --add-option amdgpu.ppfeaturemask=0xffffffff
update-bootloader --add-option rd.driver.blacklist=radeon
update-bootloader
fi
1 Like
vajcek
February 17, 2026, 2:36pm
9
@vajcek as suggested by @mrmazda add those options at boot to test, just to be sure add rd.driver.blacklist=radeon boot, if all good in the output of inxi -GSaz, you can make these permanent by switching to root user and run;
update-bootloader --add-option radeon.si_support=0
update-bootloader --add-option amdgpu.si_support=1
update-bootloader --add-option rd.driver.blacklist=radeon
update-bootloader --config
1 Like
mrmazda
February 17, 2026, 3:25pm
11
# inxi -GSaz --vs --za --hostname
inxi 3.3.40-01 (2025-11-25)
System:
Host: fi965 Kernel: 6.18.8-1-default arch: x86_64 bits: 64 compiler: gcc
v: 15.2.1 clocksource: tsc avail: hpet,acpi_pm
parameters : root=LABEL=... ipv6.disable=1 net.ifnames=0
radeon.si_support=0 amdgpu.si_support=1 noresume consoleblank=0
mitigations=off
Desktop: KDE v: 3.5.10 tk: Qt v: 3.3.8c wm: kwin with: kicker vt: 7 dm:
1: KDM note: stopped 2: XDM Distro: openSUSE Tumbleweed 20260204
Graphics:
Device -1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R5 430
OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: amdgpu v: kernel
alternate: radeon arch: GCN-1 code: Southern Islands process: TSMC 28nm
built: 2011-20 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3
speed: 8 GT/s ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0
chip-ID: 1002:6611 class-ID: 0300 temp: 49.0 C
Display : x11 server: X.Org v: 21.1.21 compositor: kwin driver: X:
loaded: modesetting dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 4240x1440 s-dpi: 120 s-size: 897x304mm (35.31x11.97")
s-diag: 947mm (37.29")
Monitor-1: DP-1 pos: primary,left model: Acer K272HUL serial: ...
built: 2018 res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: DVI-I-1 pos: right model: Dell P2213 serial: ...
built: 2013 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.4 glx-v: 1.4
direct-render: yes renderer: AMD Radeon R7 200 Series (radeonsi oland ACO
DRM 3.64 6.18.8-1-default) device-ID: 1002:6611 memory: 1000 MiB
unified: no
API: Vulkan v: 1.4.341 layers: 2 device: 0 type: discrete-gpu name: AMD
Radeon R7 200 Series (RADV OLAND) driver: mesa radv v: 25.3.4
device-ID: 1002:6611 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.8 128 bits) driver: mesa llvmpipe v: 25.3.4 (LLVM 21.1.8)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo x11: xdriinfo,
xdpyinfo, xprop, xrandr
...
#
Above is approximately what you should see in an Xorg/X11 session using my previously suggested kernel command line options in Grub, just with 16.0 software versions instead of Tumbleweed and KDE3.
@mrmazda User is running Wayland, lets stick with that as this is the default going forward.
1 Like
vajcek
February 18, 2026, 10:49pm
13
If I understood right, i have to type this:
radeon.si_support=0 amdgpu.si_support=1
Where to add
rd.driver.blacklist=radeon
What does in mean:
if all good in the output of inxi -GSaz
Where I can see if it is good?
I know how to enter GRUB menu, but where to add things I mentioned - I am not sure (or, better - don’t know).
Sorry for my rookie questions, but I really want to make this works perfectly as I accustomed during all there almost 20 years of using OpenSUSE.
Thank you for answering my questions.
All are for grub at boot, so add them all and if/when these work you can use that update-bootloader command to make it permanent.
vajcek
February 19, 2026, 5:48pm
15
I tried - everything is perfect: nothing trembles, nothing flickers (this trembling, flickering happened in Google chrome the most; I even can say only, but it was frustrated that you can not use one of web-browsers).
But: time after time, display freezes and got dark
Now, I have got some questions:
What is inxi -GSaz ? Is it something I have to type in console, or something other? And, at the end of my question-list:
update-bootloader --add-option radeon.si_support=0
update-bootloader --add-option amdgpu.si_support=1
update-bootloader --add-option rd.driver.blacklist=radeon
update-bootloader --config
section above type in terminal as root user (I suppose yes, but question more is better than mistake more) ?
Thank you for answering my questions.
mrmazda
February 19, 2026, 6:37pm
16
It’s the same thing you did in post #5 here, typing it in Konsole.
When you reboot to start over after this happens, do the following in Konsole and copy and paste here the result:
sudo journalctl -b -1 -p3.
vajcek:
update-bootloader --add-option radeon.si_support=0
update-bootloader --add-option amdgpu.si_support=1
update-bootloader --add-option rd.driver.blacklist=radeon
update-bootloader --config
section above type in terminal as root user (I suppose yes, but question more is better than mistake more) ?
Hi, yes this makes the changes and saves for when you boot the system so no need to add manually.
vajcek
February 20, 2026, 5:26pm
18
My friends, what else can I say but thank you! You are just wizards! I did these update-boot lines (after I edited grub) , so now there is no trembling and flickering. I wait to see if display will get dark.
vajcek
February 20, 2026, 7:20pm
20
This is one of you asked. But, I first updated, and now I posted this what I have had to post before.