This triple booted rig ( LMDE 7, Debian Trixie Cinnamon and Slackware) has been giving me problems for about 3 weeks now.
I thought that Modicia (the first distro in the Grub Menu) was the problem. Come to find out after a fresh install of LMDE 7 the issue is still present so the mixed config that Modicia has wasn't the issue.
Things I tried:
1- Adding amdgpu.sg_display=0 to the /etc/default/grub config file in the GRUB_CMDLINE_LINUX_DEFAULT string.
2- Adding dcdebugmask=0x10 made the flickering and screen tearing even worse
3- Changing the GFX resolution from 1920x1080 to 1024x768
4-Changing the Hz on the monitor from 60Hz to 120 Hz or 100 Hz
All 3 distributions once they finally boot from log in are fine. With one exception, in Debian Trixie as it has a solid thin black line across the center of the screen at all times.
AI suggests that there is some sort of mismatch with the kernel buffer and the amd graphics driver.
I'm not so sure I can trust this.
The firmware and graphics driver is installed in Debian. I haven't done much with the fresh install of LMDE 7 that I just performed yesterday.
In many years of running Slackware I've never seen this behavior before. Perplexing to say the least:-
Sometimes the Grub Menus is clear and I can see all 3 distro's listed and sometimes not.
The boot-up process shows lots of heavy flickering and screen tearing in all 3 distro's. The log in screens are so flickery and show so much screen tearing that I can barely see to log in.
In the meantime I'll download a fresh .iso and make sure the RAM isn't on it's way out.
Any help is greatly appreciated.

Hmmm. Possibly GPU? Bad drivers for graphics?
Hmmm. Possibly GPU? Bad drivers for graphics?
I’m thinking of a regression in the graphics drivers. If you can find a older version, it might help
Hmmm. Possibly GPU? Bad drivers for graphics?
How do I test?
Modeprob the driver?
Drivers installed are:
Code:
apt list --installed | grep -E "nvidia-driver|nvidia-.*-server|amdgpu|libgl1-mesa"
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libdrm-amdgpu1/stable,now 2.4.124-2 amd64 [installed,automatic]
libgl1-mesa-dri/stable,now 25.0.7-2+deb13u1 amd64 [installed,automatic]
xserver-xorg-video-amdgpu/stable,now 23.0.0-1 amd64 [installed,automatic]
@debianbox:~$From what I can tell the kernel in Debian is using the amdgpu driver:
Code:
lspci -knn | grep -iA3 vga
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b04]
Kernel driver in use: amdgpu
Kernel modules: amdgpuCode:
@debianbox:~$ inxi -G
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.16 driver: X: loaded: amdgpu
dri: radeonsi gpu: amdgpu resolution: N/A
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.7-2+deb13u1
renderer: AMD Radeon RX 550 / 550 Series (radeonsi polaris12 ACO DRM 3.64
7.1.7+deb13-amd64)
Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandrI'll have to look for an older version later. Got things going on that require my attention.
In among your 'tryouts' re gpu....disable the driver/gpu completely. Maybe in driver manager there may be a possibility to use onboard graphics in its place ?
Worth a try
In among your 'tryouts' re gpu....disable the driver/gpu completely. Maybe in driver manager there may be a possibility to use onboard graphics in its place ?
Worth a try
Would I need to disable/blacklist the driver in LMDE 7 or all 3 distro's?
Would I need to disable/blacklist the driver in LMDE 7 or all 3 distro's?
No idea. Disable it in lmde 7 and take it from there...
If you boot into your BIOS, (F2 key) you should see under one of the menu tabs your GPU, and an option to enable or disable it....... hopefully
With one exception, in Debian Trixie as it has a solid thin black line across the center of the screen at all times.
AFAIK, that's a GPU Issue. I am uncertain (Unless it is unified) if that would be any good. I believe some machines might have a inbuilt diagnostic to determine if the issue is hardware or software.
I know dell usually has this, but I am uncertain about other brands.
Brave's AI Reccommended a GPU tester called amd-gpu-burn. I never used it, don't know much about it, but if you look into it it might help determine if it's the GPU or the driver.
some AI prompting leads to info about plymouth conflicting with the monitor's native refresh rate & it recommends to disable the loading logo via:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet fbdev=1"hope that helps!
...and if the above ^^^^ fails. Alex have you tried inserting into the GRUB_CMDLINE_LINUX_DEFAULT string
nomodeset
??
You could try it in one, update grub and reboot, and if successful try it in others.
HTH
Chris
I'm preparing (looking for) a usb thumb drive so I can run Memtest.
Be back in a little while and to answer all of you from post #10 on.
Code:
debianbox:~/Downloads$ sudo dd if=~/Downloads/memtest86-usb.img of=/dev/sdc bs=4M status=progress
0+1 records in
0+1 records out
1474560 bytes (1.5 MB, 1.4 MiB) copied, 0.192582 s, 7.7 MB/sLast edited: Sep 17, 2026
No idea. Disable it in lmde 7 and take it from there...
If you boot into your BIOS, (F2 key) you should see under one of the menu tabs your GPU, and an option to enable or disable it....... hopefully
Thanks.
Before entering the BIOS I'll create a blacklist ('/etc/modprobe.d/<modulename>.conf') file and add the amdgpu driver that the kernel is using, reboot and be back to tell you if that helped.....or not.
Additionally, there is more than one module in lsmod that makes the amdgpu run so this is getting interesting to say the least.
Code:
amdgpu 14487552 13
drm_buddy 12288 1 amdgpu
amdxcp 12288 1 amdgpu
drm_exec 12288 1 amdgpu
gpu_sched 65536 1 amdgpu
video 81920 2 asus_wmi,amdgpu
i2c_algo_bit 16384 1 amdgpu
drm_suballoc_helper 12288 1 amdgpu
drm_display_helper 274432 1 amdgpu
cec 69632 1 drm_display_helper
rc_core 73728 1 cec
drm_ttm_helper 16384 2 amdgpu
crct10dif_pclmul 12288 1
crc32_pclmul 12288 0
xhci_pci 24576 0
ttm 106496 2 amdgpu,Sometimes more than one module has to be blacklisted:-
Last edited: Sep 17, 2026
Weeding out the modules in the kernel listed in /proc/modules so I know which to blacklist. Also looking at the defaults on the Asus Tuff Gaming mobo because if I blacklist the amdgpu_sched 655361 module I may not have a display at all.
There are 2 asus_wmi modules in the kernel for this mobo so I'm glad I found that out first.
Last edited: Sep 17, 2026
some AI prompting leads to info about plymouth conflicting with the monitor's native refresh rate & it recommends to disable the loading logo via:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet fbdev=1"hope that helps!
I tried that, updated grub and rebooted. No dice:-
...and if the above ^^^^ fails. Alex have you tried inserting into the GRUB_CMDLINE_LINUX_DEFAULT string
nomodeset
??
You could try it in one, update grub and reboot, and if successful try it in others.
HTH
Chris
Tried adding "nomodset" to the GRUB_CMD.. string in the /etc/default/grub file, updated grub and rebooted.
Unfortunately mate, nothing changed.
It looks like there are only 2 others (maybe) 3 options here for me to try.
1- Figure out which modules that the kernel is using and add them to the modprobe .config. Haven't done yet as I don't have clarity yet.
2- Find gpu-burn that @Rocketing-warp9 suggested.
3- Go into the BIOS which I really don't want to make that adjustment as I don't know if the mod's that the kernel is using on the Asus mobo is correct info. that I think I understand.
System wide settings in the BIOS could give me a black display and then I'm really at a loss.
It's evening now and I have other tasks that need my attention. Tomorrows another day.
Last edited: Sep 17, 2026
2- Find gpu-burn that @Rocketing-warp9 suggested
Just make sure you use the amd-gpu-burn, as from what I have seen, the regular version is Nidiva only.
Hope all goes well! ![]()
Just make sure you use the amd-gpu-burn, as from what I have seen, the regular version is Nidiva only.
Hope all goes well!
Does this link look correct to you?
I read the ReadMe. I'm not that good at building Rocketing-warp9 so I hope there aren't any make errors.
Memtest did it's job and the RAM is ok. Zero errors I'm glad to report.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Перечислены ускоряющие компьютер настройки | 0 | 10 | 05-10-2026 |
| 2 | grub чего-то не может | 1 | 15.57 | 04-10-2026 |
| 3 | Suggested Distro for GPD MicroPC 2 (completely new user) | 0 | 21.11 | 05-10-2026 |
| 4 | Re: grub чего-то не может | 0 | 10.37 | 04-10-2026 |
| 5 | Mehrere Probleme in glibc (Fedora) | 0 | 10 | 01-10-2026 |
| 6 | My TV as a Monitor | 0 | 10 | 05-10-2026 |
| 7 | Назван способ найти поломку компьютера | 0 | 10 | 05-10-2026 |
| 8 | Обзор ASUS Zenbook DUO: ноутбук, после которого одного экрана уже мало | 0 | 11.05 | 30-09-2026 |
| 9 | Раскрыты тормозящие Windows настройки | 0 | 10 | 30-09-2026 |
| 10 | Обзор и тестирование экрана Turzx 3.5 для мониторинга параметров ПК | 0 | 9.6 | 03-10-2026 |