From owner-freebsd-x11@freebsd.org Thu May 26 23:08:14 2016 Return-Path: Delivered-To: freebsd-x11@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 77211B47C27; Thu, 26 May 2016 23:08:14 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 489D21663; Thu, 26 May 2016 23:08:14 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:94c9:651d:7312:89cd] (unknown [IPv6:2001:470:1f11:617:94c9:651d:7312:89cd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 3AABC12BD; Thu, 26 May 2016 23:08:07 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> MIME-Version: 1.0 Subject: Re: CFT update day 2 From: Eric McCorkle Date: Thu, 26 May 2016 19:08:03 -0400 To: Matthew Macy , "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2016 23:08:14 -0000 Letting you know, I had an error in detection. I'm trying to get a change done before code slush, but I will circle back and provide a detailed report On May 23, 2016 4:12:52 AM EDT, Matthew Macy wrote: > >The highlights for today are the following: > >Bug fixes: >- Will Andrews fixed attach for some laptops (such as the Carbon X1). > The Carbon X1 has a quirky BIOS that doesn't allow the OS to > enumerate the GPU's interrupt. >- Will Andrews identified a conditionally uninitialized return in > idr_find that could lead to a panic in some cases. >- Fixed a panic in mtrr_del frequently seen when attach failed. >- Sleep/wakeups with interrupts are largely implemented correctly > now. Previously a polling 10ms sleep was used. I'm still > concerned that the code really needs to be level-triggered. > >Cleanups: >- Logging is now enabled for the first 10s after attach unless > dev.drm.drm_debug_keep=1. >- Unimplemented warnings are off by default. > >As of this moment the latest USB image is: > http://www.bsddesktop.com/images/cftdisk_2016052307.img.xz > >The USB image now has sync disabled on var. This should improve >responsiveness for most people with slow USB pen drives. If >you're having issues that require retaining logs you'll need >to "zfs set sync=enabled zrootusb/var". > >The USB image now includes kde4 and xfce. It is also much larger, for >this iteration you will need a 16GB USB key. The next one will probably >not be quite so large. If size is a common problem let me know. It's >difficult to buy a USB key that is less than 16GB today. > >joeuser's .xinitrc is configured to start xfce with startx. To start >kde >run: service kdm4 onestart. > >Note that the image name has changed. The most recent should be >self-evident in: http://www.bsddesktop.com/images > >Helpful hint: use a 1MB blocksize for dd and run gpart recover >to fix label warnings. Assuming your USB pen drive shows up as >/dev/da0 and cftdisk image is the one I just posted: > >unxz -f cftdisk_2016052307.img.xz; dd if=cftdisk_2016052307.img >of=/dev/da0 bs=1M; gpart recover da0 > >And as a reminder, if you're having problems with X on the USB >key, try disabling it by moving /etc/X11/xorg.conf.d/20-intel.conf >somewhere else on your file system. > >If using the github repo, make sure you're using the drm-next-4.6 >branch. > >Cheers. > >-M > >_______________________________________________ >freebsd-x11@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-x11 >To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-x11@freebsd.org Thu May 26 23:18:58 2016 Return-Path: Delivered-To: freebsd-x11@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 BA8E8B47F69; Thu, 26 May 2016 23:18:58 +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 AD3151CF4; Thu, 26 May 2016 23:18:58 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1464304735232978.7128585958017; Thu, 26 May 2016 16:18:55 -0700 (PDT) Date: Thu, 26 May 2016 16:18:55 -0700 From: Matthew Macy To: "Eric McCorkle" Cc: "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Message-ID: <154ef5d13c7.128c042c1404712.5585765664970837921@nextbsd.org> In-Reply-To: References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> Subject: Re: CFT update day 2 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-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2016 23:18:58 -0000 ---- On Thu, 26 May 2016 16:08:03 -0700 Eric McCorkle wrote ---- > Letting you know, I had an error in detection. I'm trying to get a change done before code slush, but I will circle back and provide a detailed report Thanks. I'm not going to make slush for the changes to sys to support this. If dates are interpreted as being UTC then it's already started. -M > > On May 23, 2016 4:12:52 AM EDT, Matthew Macy wrote: > > > >The highlights for today are the following: > > > >Bug fixes: > >- Will Andrews fixed attach for some laptops (such as the Carbon X1). > > The Carbon X1 has a quirky BIOS that doesn't allow the OS to > > enumerate the GPU's interrupt. > >- Will Andrews identified a conditionally uninitialized return in > > idr_find that could lead to a panic in some cases. > >- Fixed a panic in mtrr_del frequently seen when attach failed. > >- Sleep/wakeups with interrupts are largely implemented correctly > > now. Previously a polling 10ms sleep was used. I'm still > > concerned that the code really needs to be level-triggered. > > > >Cleanups: > >- Logging is now enabled for the first 10s after attach unless > > dev.drm.drm_debug_keep=1. > >- Unimplemented warnings are off by default. > > > >As of this moment the latest USB image is: > > http://www.bsddesktop.com/images/cftdisk_2016052307.img.xz > > > >The USB image now has sync disabled on var. This should improve > >responsiveness for most people with slow USB pen drives. If > >you're having issues that require retaining logs you'll need > >to "zfs set sync=enabled zrootusb/var". > > > >The USB image now includes kde4 and xfce. It is also much larger, for > >this iteration you will need a 16GB USB key. The next one will probably > >not be quite so large. If size is a common problem let me know. It's > >difficult to buy a USB key that is less than 16GB today. > > > >joeuser's .xinitrc is configured to start xfce with startx. To start > >kde > >run: service kdm4 onestart. > > > >Note that the image name has changed. The most recent should be > >self-evident in: http://www.bsddesktop.com/images > > > >Helpful hint: use a 1MB blocksize for dd and run gpart recover > >to fix label warnings. Assuming your USB pen drive shows up as > >/dev/da0 and cftdisk image is the one I just posted: > > > >unxz -f cftdisk_2016052307.img.xz; dd if=cftdisk_2016052307.img > >of=/dev/da0 bs=1M; gpart recover da0 > > > >And as a reminder, if you're having problems with X on the USB > >key, try disabling it by moving /etc/X11/xorg.conf.d/20-intel.conf > >somewhere else on your file system. > > > >If using the github repo, make sure you're using the drm-next-4.6 > >branch. > > > >Cheers. > > > >-M > > > >_______________________________________________ > >freebsd-x11@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > >To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >