From owner-freebsd-current@freebsd.org Sun May 22 19:13:24 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5C49B46077; Sun, 22 May 2016 19:13:24 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B81561C67; Sun, 22 May 2016 19:13:24 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1463944401442706.496849663476; Sun, 22 May 2016 12:13:21 -0700 (PDT) Date: Sun, 22 May 2016 12:13:21 -0700 From: Matthew Macy To: "Matthew Macy" Cc: "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <154d9e2d1ee.1112a8b40129540.1579569326496248589@nextbsd.org> In-Reply-To: <154d9b8d0a3.1072249ba128924.7972504336631390470@nextbsd.org> References: <154d9b8d0a3.1072249ba128924.7972504336631390470@nextbsd.org> Subject: Note on CFT image MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-ZohoMail: Z_57973067 SPT_1 Z_57973066 SPT_1 SLF_D X-Zoho-Virus-Status: 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 19:13:24 -0000 ---- On Sun, 22 May 2016 11:27:28 -0700 Matthew Macy 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