| View previous topic :: View next topic |
| Author |
Message |
LemonBreezes
n00b
Joined: 04 Aug 2022
Posts: 4
|
 Posted: Fri Aug 05, 2022 12:06 am Post subject: Screen tearing in TTY after switching to gentoo-kernel-bin |
 |
|
Hello everyone. Previously, I compiled my kernel from source and the TTYs worked fine. Now, after switching to sys-kernel/gentoo-kernel-bin, I get this screen tearing after the initial kernel output is finished. Here is a picture:
https://imgur.com/a/grEk3JZ |
|
| Back to top |
|
 |
chithanh
Developer
Joined: 05 Aug 2006
Posts: 2158
Location: Berlin, Germany
|
| Posted: Fri Aug 05, 2022 5:42 am Post subject: |
|
|
This does not look like tearing but more like graphical corruption. Tearing is transient while moving things are displayed on the screen and goes away when the screen is static again.
DRM uses handover which first loads a generic DRM/framebuffer driver (like simpledrm, fb_simple, efifb, vesafb, etc.) and then switches over to a hardware-specific driver (like i915, amdgpu, nouveau, radeon, etc.). Sometimes this does not work properly.
What you can do is look in dmesg for the handover message and explicitly disable the generic driver using video=drivername:off kernel parameter. Post the entire dmesg here if you don't find it. |
|
| Back to top |
|
|
LemonBreezes
n00b
Joined: 04 Aug 2022
Posts: 4
|
| Posted: Sat Aug 06, 2022 9:53 pm Post subject: |
|
|
| chithanh wrote: | This does not look like tearing but more like graphical corruption. Tearing is transient while moving things are displayed on the screen and goes away when the screen is static again.
DRM uses handover which first loads a generic DRM/framebuffer driver (like simpledrm, fb_simple, efifb, vesafb, etc.) and then switches over to a hardware-specific driver (like i915, amdgpu, nouveau, radeon, etc.). Sometimes this does not work properly.
What you can do is look in dmesg for the handover message and explicitly disable the generic driver using video=drivername:off kernel parameter. Post the entire dmesg here if you don't find it. |
Hello chithanh. Here is my dmesg output: http://ix.io/46Ra/text. Also, I finally fixed it! Adding line "options nvidia-drm modeset=0'' to /etc/modprobe.d/nvidia.conf completely fixed the issue for me. |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2892
|
| Posted: Sun Aug 07, 2022 5:16 am Post subject: |
|
|
gentoo-kernel-bin uses fedora's configs and they recently enabled CONFIG_DRM_SIMPLEDRM in 5.18+ which typically takes over from things like FB_EFI and FB_SIMPLE (may have unexpected consequence and is generally broken with nvidia)
You could try force-disabling it in the kernel command line to see if it helps: initcall_blacklist=simpledrm_platform_driver_init (I think that should work anyway, haven't tried -- should fallback to FB_EFI which fedora recently re-enabled) |
|
| Back to top |
|
|
LemonBreezes
n00b
Joined: 04 Aug 2022
Posts: 4
|
| Posted: Sun Aug 07, 2022 5:28 am Post subject: |
|
|
| Ionen wrote: | gentoo-kernel-bin uses fedora's configs and they recently enabled CONFIG_DRM_SIMPLEDRM in 5.18+ which typically takes over from things like FB_EFI and FB_SIMPLE (may have unexpected consequence and is generally broken with nvidia)
You could try force-disabling it in the kernel command line to see if it helps: initcall_blacklist=simpledrm_platform_driver_init (I think that should work anyway, haven't tried -- should fallback to FB_EFI which fedora recently re-enabled) |
Hello Ionen. I still have the issue where the TTYs don't work after I run startx, even though there is no longer any visible corruption. I am indeed on 5.18.16 currently. I tried adding initcall_blacklist=simpledrm_platform_driver_init to my kernel parameters but that led to no visible output after the "loading initramfs" line. |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2892
|
| Posted: Sun Aug 07, 2022 5:31 am Post subject: |
|
|
I see, I guess it doesn't fallback to EFI with that then (sorry). Unfortunately not sure what else to suggest right now (haven't experimented with this).
I imagine stable gentoo-kernel-bin-5.15.x would work meanwhile though. |
|
| Back to top |
|
|
LemonBreezes
n00b
Joined: 04 Aug 2022
Posts: 4
|
| Posted: Sun Aug 07, 2022 5:58 am Post subject: |
|
|
| Ionen wrote: | I see, I guess it doesn't fallback to EFI with that then (sorry). Unfortunately not sure what else to suggest right now (haven't experimented with this).
I imagine stable gentoo-kernel-bin-5.15.x would work meanwhile though. |
Thanks. Downgrading to the stable gentoo-kernel-bin fixed the TTY switching issues. Now all the issues are fixed. I was using 5.17.x when I ran my manually configured kernel and updated to 5.18.x when I switched to gentoo-kernel-bin. |
|
| Back to top |
|
|
chithanh
Developer
Joined: 05 Aug 2006
Posts: 2158
Location: Berlin, Germany
|
| Posted: Tue Aug 09, 2022 11:27 am Post subject: |
|
|
| Code: | | [ 2.279739] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device |
That can be disabled with video=simpledrmdrmfb:off kernel parameter. Should fallback to efifb then, or worst case have no console until nvidia driver loads. Going back to older kernel is only a temporary workaround, and disabling kernel modesetting for nvidia causes the TTY switching issues (I think). |
|
| Back to top |
|
|
|
Kernel & Hardware
