Date: Mon, 23 May 2016 14:21:37 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Matthias Haas" <freebsd-x11@mathaas.de> Cc: "freebsd-x11" <freebsd-x11@freebsd.org>, "freebsd-current" <freebsd-current@freebsd.org>, <owner-freebsd-x11@freebsd.org> Subject: Re: CFT update day 2 Message-ID: <154df7e9d46.f8f6c67384567.4803192402268842079@nextbsd.org> In-Reply-To: <c76ca16e9392c9a0559c08e1b63124ca@mathaas.de> References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> <c76ca16e9392c9a0559c08e1b63124ca@mathaas.de>
next in thread | previous in thread | raw e-mail | index | archive | help
=20
=20
Have you tried with the xf86-intel in ports. That actually work=
s better for most. Also try SNA. What does pciconf -lvbc show for graphics?=
---- On Mon, 23 May 2016 14:17:41 -0700 Matthias Haas<freebsd-x11@mathaas.=
de> wrote ----First of all thanks for your great work so far. I have tried=
the driver on my notebook with Iris 550. After patching libdrm with https=
://cgit.freedesktop.org/mesa/drm/commit/?id=3De3623d34cad0ac3f181b0deee0931=
df202b8f909 and installing the experimental xf86-video-intel driver it is =
partially working. What's not working is: - 3D-acceleration - multi-monito=
r support (only tried with hdmi), after loading the i915kms driver the out=
put is duplicated, but there is no way of controlling the outputs independ=
ently (xfce also shows only one connected display) - Xorg refuses to start=
unless I kldload i915kms manually before trying to start Xorg - there are=
some rendering issues (pink lines, weird transparency where there should =
be no transparency), but I don't know if these are related to i915, the ex=
perimental xf86-video-intel driver or the software renderer On 2016-05-23=
10:12, 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 t=
o > enumerate the GPU's interrupt. > - Will Andrews identified a conditio=
nally uninitialized return in > idr_find that could lead to a panic in so=
me cases. > - Fixed a panic in mtrr_del frequently seen when attach failed.=
> - Sleep/wakeups with interrupts are largely implemented correctly > no=
w. Previously a polling 10ms sleep was used. I'm still > concerned that t=
he code really needs to be level-triggered. > > Cleanups: > - Logging is n=
ow enabled for the first 10s after attach unless > dev.drm.drm_debug_keep=
=3D1. > - Unimplemented warnings are off by default. > > As of this moment=
the latest USB image is: > http://www.bsddesktop.com/images/cftdisk_20160=
52307.img.xz > > The USB image now has sync disabled on var. This should i=
mprove > 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". > > The USB image now includes kde4 and xfce. It=
is also much larger, for > this iteration you will need a 16GB USB key. Th=
e next one will probably > not be quite so large. If size is a common probl=
em let me know. It's > difficult to buy a USB key that is less than 16GB to=
day. > > joeuser's .xinitrc is configured to start xfce with startx. To s=
tart > kde > run: service kdm4 onestart. > > Note that the image name has=
changed. The most recent should be > self-evident in: http://www.bsddeskto=
p.com/images > > Helpful hint: use a 1MB blocksize for dd and run gpart re=
cover > to fix label warnings. Assuming your USB pen drive shows up as > /d=
ev/da0 and cftdisk image is the one I just posted: > > unxz -f cftdisk_201=
6052307.img.xz; dd if=3Dcftdisk_2016052307.img > of=3D/dev/da0 bs=3D1M; gpa=
rt 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.con=
f > 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 mail=
ing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsu=
bscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" =20
=20
=20
=20
=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154df7e9d46.f8f6c67384567.4803192402268842079>