Date: Tue, 19 Feb 2019 00:01:51 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 235203] Xorg crashes on startup since updating 2019-01-24 Message-ID: <bug-235203-7141-PDwOGWgtDd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235203-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-235203-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=3D235203 --- Comment #4 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Jason W. Bacon from comment #0) > I tried switching to graphics/drm-kmod and /boot/modules/i915kms.ko, > but this causes a panic instead. Can you report the panic to https://github.com/FreeBSDDesktop/kms-drm/issue= s/ ? Also try newer FreeBSD version (or just kernel) which supports newer drm-*-kmod. Probably all hardware supported by drm2 (i915kms, radeonkms) from base or drm-legacy-kmod is supposed to work with drm-kmod. Obviously, there're bugs because the focus is on recent hardware, usually *not* supported by drm2. (In reply to Jason W. Bacon from comment #1) > Same issue on a ThinkCenter M92p, also using modesetting driver from > base. In this case, switching to drm-kmod resolved the issue. SandyBridge is known to work on drm-kmod, so IvyBridge also working isn't surprising. Did you test on the same FreeBSD version? I'm curious if drm-fbsd11.2-kmod is less stable on old hardware. --=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-235203-7141-PDwOGWgtDd>