Date: Thu, 31 May 2018 09:28:52 +0200 From: Hans Petter Selasky <hps@selasky.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, Glen Barber <gjb@FreeBSD.org>, Philip Homburg <pch-fbsd-1@u-1.phicoh.com>, "K. Macy" <kmacy@FreeBSD.org>, "A. Wilcox" <AWilcox@wilcox-tech.com>, FreeBSD Current <freebsd-current@FreeBSD.org>, Ed Maste <emaste@freebsd.org> Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <24a94651-f516-485d-36f4-0937824ca3d7@selasky.org> In-Reply-To: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/30/18 23:51, O. Hartmann wrote: > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up in a trap > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does load without > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > So why should I vote for non-working drivers to replace perfectly working ones? Usually the crashes you get are low hanging fruit. Why not get the backtrace and resolve the crash? It should take less than 10 minutes. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24a94651-f516-485d-36f4-0937824ca3d7>