Date: Sun, 13 Dec 2020 17:10:05 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 250700] drm-kmod i915kms binary package not working on 12.2-RELEASE Message-ID: <bug-250700-7141-IaPY5PeHsV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250700-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250700 --- Comment #16 from Niclas Zeising <zeising@FreeBSD.org> --- (In reply to Bruce Lilly from comment #15) Hi! The drm-fbsd12.0-kmod issue is unfortunate, but it is a known issue. Ranting about it does not help much, what helps is supporting development. That said, it looks like something else is hosed on your system apart from the issue with drm-fbsd12.0-kmod. I have had no problem upgrading both test and production systems to 12.2 (I have compiled drm-fbsd12.0-kmod locally though), and an issue with ld-elf.so.1 would have been all over the mailing lists. I also don't think that downgrading a system with freebsd-update is supported. Using ZFS snapshots and rolling back those works though (as long as you don't do zpool upgrade), or using boot environments. The coredump from conftest is usually autotools (configure scripts) that does things to detect the system, so that should be quite alright, and even expected if you are building ports on the system. ps not being POSIX is for historical reasons. While it might be unfortunate, it's just the way it is. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250700-7141-IaPY5PeHsV>
