From owner-freebsd-current@freebsd.org Tue Feb 27 14:50:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D10EEF2C36D for ; Tue, 27 Feb 2018 14:50:58 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CD767B4E2 for ; Tue, 27 Feb 2018 14:50:57 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Date: Tue, 27 Feb 2018 09:43:40 -0500 To: Greg V From: Mylan Connolly Cc: Pete Wright , "freebsd-current@freebsd.org" Reply-To: Mylan Connolly Subject: Re: Compilation failure of the kernel for drm-next Message-ID: In-Reply-To: References: Feedback-ID: LynW_1UfPsCNIeRmn6VnQX7Jv_J-d7679pwNAQLet51aNK-bYdze1ldqgK4iRhJvu9suK3NkzvrvvdOCSoLZ4w==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 14:50:59 -0000 Thanks for the help, all. Last night I set my computer to compile from the 12-CURRENT head and went t= o sleep. This morning, I installed the graphics/drm-next-kmod port and after a littl= e troubleshooting (I had to set the compat.linuxkpi.enable_hangcheck=3D0 bo= otflag) I got it up and running. The only issue now is I cannot adjust the = backlight. Thanks again for all the help =E2=80=8BMylan =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On February 27, 2018 3:51 AM, Greg V wrote: > On 2/27/2018 5:03 AM, Pete Wright wrote: >=20 > > On 02/26/2018 17:17, Mylan Connolly wrote: > >=20 > > > Hello all, > > >=20 > > > I'm not sure if this is the best place to send this, but it looks > > >=20 > > > like the issue tracker in Github is a bit dead. > >=20 > > there may not be much traffic on it recently, but people are def still > >=20 > > actively working on the repository and will see when new issues are > >=20 > > reported. > >=20 > > as of now your best to to use or test out the drm-next bits is to run > >=20 > > a recent 12-CURRENT with no patches applied.=C2=A0 then you can build t= he > >=20 > > port or package via the ports tree under graphics/drm-next-kmod.=C2= =A0 it > >=20 > > currently runs on my end under 12-CURRENT and 11-STABLE. >=20 > Yeah, and the issue tracker for drm-next-kmod is >=20 > https://github.com/FreeBSDDesktop/kms-drm/issues >=20 > NOT https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues