Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Oct 2018 17:57:44 +0000
From:      Johannes Lundberg <johalun0@gmail.com>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        freebsd-current@freeebsd.org, x11-list freebsd <freebsd-x11@freebsd.org>
Subject:   Re: drm2 again
Message-ID:  <CAECmPwu3ndCzQa0S2hQHmyOoXQaZRAwaUjGGcApPEX3dZXH%2Byw@mail.gmail.com>
In-Reply-To: <20181031172832.GA28293@troutmask.apl.washington.edu>
References:  <20181031172832.GA28293@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi

> graphics/drm-legacy-kmod is simply broken, which has been previously
reported.

This is not really helpful. What is the error you get?
We know there has been problems with firmware loading which we have been
working on but since the latest update we have not heard back a word from
any testers.

Ports was updated to use the latest snapshot from
https://github.com/FreeBSDDesktop/drm-legacy 4 days ago. Hopefully this
will fix the last outstanding issues we've had.

<https://github.com/FreeBSDDesktop/drm-legacy>;


On Wed, Oct 31, 2018 at 5:29 PM Steve Kargl <
sgk@troutmask.apl.washington.edu> wrote:

> It's me, again.
>
> With the branching for freebsd-12, the top-of-tree
> (aka freebsd13) has introduced knobs that prevent
> the building and installation of drm and drm2.  These
> knobs have been set to 't'.  Thus, my last world
> update did not install the in-tree drm and drm2.
> So, it seemed like a good time to switch to one of
> the drm ports (as suggested by src/UPDATING).
>
> graphics/drm-legacy-kmod is simply broken, which has
> been previously reported.
>
> graphics/drm-stable-kmod fills /var/log/messages with
>
> Oct 30 14:50:35 troutmask kernel: fence_wait returned with error -512
> Oct 30 14:50:35 troutmask syslogd: last message repeated 10 times
> Oct 30 16:30:16 troutmask kernel: fence_wait returned with error -512
> Oct 30 16:30:16 troutmask syslogd: last message repeated 4 times
>
> It seems that setting WITHOUT_DRM_MODULE=t and
> WITHOUT_DRM2_MODULE=t is premature.
>
> Yes, I am aware that I can set WITH_MODULE_DRM and
> WITH_MODULE_DRM2 in /usr/src.conf, and recover the
> missing in-tree modules.
>
> PS: /usr/src/UPDATING spells the WITHOUT_* knobs as for
> example WITHOUT_DRM2_MODULE while src.conf(8) documents
> a WITH_MODULE_DRM2 knob.  I suspect UPDATING is wrong.
>
> % find /usr/src -name \*.mk | xargs grep _DRM
> /usr/src/sys/conf/kern.opts.mk:    MODULE_DRM \
> /usr/src/sys/conf/kern.opts.mk:    MODULE_DRM2 \
> % find /usr/src -name Make\* | xargs grep _DRM
> /usr/src/sys/modules/Makefile:.if ${MK_MODULE_DRM} != "no"
> /usr/src/sys/modules/Makefile:.if ${MK_MODULE_DRM2} != "no"
> /usr/src/sys/modules/Makefile:.if ${MK_MODULE_DRM} != "no"
> /usr/src/sys/modules/Makefile:.if ${MK_MODULE_DRM2} != "no"
>
>
> --
> Steve
> _______________________________________________
> 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?CAECmPwu3ndCzQa0S2hQHmyOoXQaZRAwaUjGGcApPEX3dZXH%2Byw>