Date: Sun, 18 Apr 2021 07:51:34 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 255040] Xorg sever terminates with error on 13.0-RELEASE Message-ID: <bug-255040-7141-AtA6rGeFTF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255040-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-255040-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255040 --- Comment #9 from Niclas Zeising <zeising@FreeBSD.org> --- There is no need to build anything from source if you are following a RELEA= SE branch. Installing drm-kmod is all you need, it will pull in the correct drm-*-kmod from ports. For FreeBSD 13 that is drm-fbsd13-kmod. If you are tracking STABLE or CURRENT, then it is better to compile the module locally= , to avoid issues. On the other hand, if you are tracking STABLE or CURRENT, you need to recompile the whole base system and kernel, so I don't see why an e= xtra kmod would be that much extra effort. There are several of us spending a substantial amount of our time and energ= y in improving the FreeBSD desktop experience, everything on a volunteer basis. = I can not speak for the offshoot projects, but they are using our effort as w= ell, as without it there would be no desktop experience in the first place. dmesg is easily fetched by running dmesg. There is also usually a file in /var/log called dmesg.boot, that saves the latest dmesg. You say that you are not using the drm driver. Are you then using plain ve= sa or sc without any acceleration at all? That should work, but does not give such great performance and experience. Do you have any xorg.conf or similar? If so, can you try without it? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255040-7141-AtA6rGeFTF>