Date: Mon, 23 May 2016 19:42:11 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "huanghwh" <huanghwh@163.com> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re:CFT update day 2 Message-ID: <154e0a4192a.e87a8ee1205348.4770904017869786762@nextbsd.org> In-Reply-To: <7b0b6eb4.2942.154e0a001a3.Coremail.huanghwh@163.com> References: <154dcac7f27.f5da66a0148247.6294302194451585046@nextbsd.org> <7b0b6eb4.2942.154e0a001a3.Coremail.huanghwh@163.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Mon, 23 May 2016 19:37:43 -0700 huanghwh <huanghwh@163.com> wrote = ----=20 > Hi, > I try to test drm-next-4.6 on my MacBookPro 15(2015), > kldload i915kms show: >=20 > [drm] Initialized drm 1.1.0 20060810 > bus_register unimplemented!!! > drmn0: <drmn> on vgapci0 > vgapci0: child drmn0 requested pci_enable_io > vgapci0: child drmn0 requested pci_enable_io > [drm] Found 128MB of eLLC > WARN_ON(domain->wake_count =3D=3D 0) > [drm] Memory usable by graphics device =3D 2048M > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] Driver supports precise vblank timestamp query. > [drm] Connector eDP-1: get mode from tunables: > [drm] - kern.vt.fb.modes.eDP-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector DP-1: get mode from tunables: > [drm] - kern.vt.fb.modes.DP-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-1: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector DP-2: get mode from tunables: > [drm] - kern.vt.fb.modes.DP-2 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-2: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-2 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-3: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-3 > [drm] - kern.vt.fb.default_mode > [drm] Initialized i915 1.6.0 20160229 for drmn on minor 0 > VT: Replacing driver "efifb" with new "fb". > start FB_INFO: > type=3D11 height=3D1800 width=3D2880 depth=3D32 > cmsize=3D16 size=3D21196800 > pbase=3D0x90000000 vbase=3D0xffffffff82210000 > name=3Ddrmn0 flags=3D0x0 stride=3D11776 bpp=3D32 > cmap[0]=3D0 cmap[1]=3D7f0000 cmap[2]=3D7f00 cmap[3]=3Dc4a000 > end FB_INFO > drmn0: fb0: inteldrmfb frame buffer device >=20 > But VT console looks like move to bottom right, I could not see the whol= e screen. >=20 > The mate desktop can show, but quickly panic: >=20 > vm_radix_insert: key 33 is already present: >=20 > http://sw.gddsn.org.cn/freebsd/drm-4.6-next-panic.jpg =20 That should be easy to fix. However, I wont have time to get to it for a da= y or two. Could you please file a PR and assign it to me? I think that I c= an have that fixed by the next update. -M >=20 > At 2016-05-23 16:12:52, "Matthew Macy" <mmacy@nextbsd.org> wrote:>>The h= ighlights for today are the following:>>Bug fixes:>- Will Andrews fixed att= ach 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 A= ndrews identified a conditionally uninitialized return in> idr_find that c= ould lead to a panic in some cases.>- Fixed a panic in mtrr_del frequently = seen when attach failed.>- Sleep/wakeups with interrupts are largely implem= ented 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=3D1.>- Unimplemented warnings are off by default.>>As of this mo= ment the latest USB image is:> http://www.bsddesktop.com/images/cftdisk_201= 6052307.img.xz>>The USB image now has sync disabled on var. This should imp= rove>responsiveness for most people with slow USB pen drives. If>you're hav= ing issues that require retaining logs you'll need>to "zfs set sync=3Denabl= ed zrootusb/var".>>The USB image now includes kde4 and xfce. It is also muc= h larger, for >this iteration you will need a 16GB USB key. The next one wi= ll 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: servi= ce kdm4 onestart.>>Note that the image name has changed. The most recent sh= ould be>self-evident in: http://www.bsddesktop.com/images >>Helpful hint: u= se a 1MB blocksize for dd and run gpart recover>to fix label warnings. Assu= ming 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=3Dcftdisk_201605230= 7.img of=3D/dev/da0 bs=3D1M; gpart recover da0>>And as a reminder, if you'r= e having problems with X on the USB>key, try disabling it by moving /etc/X1= 1/xorg.conf.d/20-intel.conf>somewhere else on your file system.>>If using t= he 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 unsu= bscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 > =20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154e0a4192a.e87a8ee1205348.4770904017869786762>