Date: Tue, 11 Feb 2025 10:54:55 +0100 From: =?UTF-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= <dumbbell@FreeBSD.org> To: freebsd-desktop@freebsd.org Subject: Re: panic -> switch to cosole with drm-kmod? Message-ID: <fea1f21e-574a-40d9-9ba4-ef8a02b81745@FreeBSD.org> In-Reply-To: <66o7so61-16o0-63q6-7nq3-92qs47479226@yvfgf.mnoonqbm.arg> References: <66o7so61-16o0-63q6-7nq3-92qs47479226@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/02/2025 23:33, Bjoern A. Zeeb wrote: > Problem now is that I can panic it quite badly but I am stuck on the X > screen. Was there a way to make it switch to v0 on panic so one can > use the kernel debugger? Hi! Also it didn’t always worked before, when I changed drm-kmod to integrate with vt(4) using a Linux-compatible fbcon API for the update to DRM 5.17, I think that part regressed even more. I couldn’t figure out what call(s) should be made to ask the driver to switch mode. Even in Linux, there are multiple code path that are unclear to me. None of the things I tried worked. I had to do this change because the amdgpu driver dropped the old way of integrating with the console (old way = driver-specific console setup) to use the generic code. The i915 and radeon drivers are still using the old approach but it is bound to the new integration and the switch during panic is broken for them too. -- Jean-Sébastien Pédron The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fea1f21e-574a-40d9-9ba4-ef8a02b81745>