---- On Mon, 23 May 2016 19:37:43 -0700 huanghwh <huang...@163.com> wrote ----
> Hi,
> I try to test drm-next-4.6 on my MacBookPro 15(2015),
> kldload i915kms show:
>
> [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 == 0)
> [drm] Memory usable by graphics device = 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=11 height=1800 width=2880 depth=32
> cmsize=16 size=21196800
> pbase=0x90000000 vbase=0xffffffff82210000
> name=drmn0 flags=0x0 stride=11776 bpp=32
> cmap[0]=0 cmap[1]=7f0000 cmap[2]=7f00 cmap[3]=c4a000
> end FB_INFO
> drmn0: fb0: inteldrmfb frame buffer device
>
> But VT console looks like move to bottom right, I could not see the whole
> screen.
>
> The mate desktop can show, but quickly panic:
>
> vm_radix_insert: key 33 is already present:
>
> http://sw.gddsn.org.cn/freebsd/drm-4.6-next-panic.jpg
That should be easy to fix. However, I wont have time to get to it for a day or
two. Could you please file a PR and assign it to me? I think that I can have
that fixed by the next update.
-M
>
> At 2016-05-23 16:12:52, "Matthew Macy" <mm...@nextbsd.org> 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 m
ost 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-...@freebsd.org
mailing list>https://lists.freebsd.org/mailman/listinfo/freebsd-x11>To
unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"
>
>
>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
