Date: Sun, 22 May 2016 12:13:21 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Matthew Macy" <mmacy@nextbsd.org> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Note on CFT image Message-ID: <154d9e2d1ee.1112a8b40129540.1579569326496248589@nextbsd.org> In-Reply-To: <154d9b8d0a3.1072249ba128924.7972504336631390470@nextbsd.org> References: <154d9b8d0a3.1072249ba128924.7972504336631390470@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Sun, 22 May 2016 11:27:28 -0700 Matthew Macy <mmacy@nextbsd.org> wrote ---- > To improve the user experience I disabled debug logging by default. Before reporting a non-fatal error with i915 load the drm2 module first, then: sysctl dev.drm.drm_debug=-1 to enable full logging. Once you have done that you can then load i915. The "unimplemented" and "dodgy" warnings are expected, they're just placeholders to remind me to get back to them. When I specified the disk image name I assumed it was self-evident that 'YYMMDDHH' is the date format. Looking at the access logs it appears that many took that literally. You can find the most recent at: http://www.bsddesktop.com/images/ Currently there is only one, disk_16052200.img.xz. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154d9e2d1ee.1112a8b40129540.1579569326496248589>