Date: Sat, 28 May 2016 09:07:40 -0400 From: Eric McCorkle <eric@metricspace.net> To: Matthew Macy <mmacy@nextbsd.org>, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: CFT update day 2 Message-ID: <10B94EF2-4D0E-4A53-B95C-12D832362C50@metricspace.net> In-Reply-To: <FF565F5E-7ED8-48DC-B776-03745763C570@metricspace.net> References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> <FF565F5E-7ED8-48DC-B776-03745763C570@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, When I load the module, it the screen blanks for a second as it does when sw= itching framebuffer drivers. However, it looks like this fails, as the last= kernel message is *ERROR*: switching to FCLK failed Not sure how I can get more detailed information. > On May 26, 2016, at 19:08, Eric McCorkle <eric@metricspace.net> wrote: >=20 > 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 repor= t=20 >=20 >> On May 23, 2016 4:12:52 AM EDT, Matthew Macy <mmacy@nextbsd.org> wrote: >>=20 >> The highlights for today are the following: >>=20 >> 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. >>=20 >> Cleanups: >> - Logging is now enabled for the first 10s after attach unless >> dev.drm.drm_debug_keep=3D1. >> - Unimplemented warnings are off by default. >>=20 >> As of this moment the latest USB image is: >> http://www.bsddesktop.com/images/cftdisk_2016052307.img.xz >>=20 >> 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=3Denabled zrootusb/var". >>=20 >> The USB image now includes kde4 and xfce. It is also much larger, for=20 >> 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=20 >> difficult to buy a USB key that is less than 16GB today. >>=20 >> joeuser's .xinitrc is configured to start xfce with startx. To start >> kde=20 >> run: service kdm4 onestart. >>=20 >> Note that the image name has changed. The most recent should be >> self-evident in: http://www.bsddesktop.com/images=20 >>=20 >> 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: >>=20 >> unxz -f cftdisk_2016052307.img.xz; dd if=3Dcftdisk_2016052307.img >> of=3D/dev/da0 bs=3D1M; gpart recover da0 >>=20 >> 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. >>=20 >> If using the github repo, make sure you're using the drm-next-4.6 >> branch. >>=20 >> Cheers. >>=20 >> -M >>=20 >> _______________________________________________ >> 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" >=20 > --=20 > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10B94EF2-4D0E-4A53-B95C-12D832362C50>