From owner-freebsd-x11@freebsd.org Sun Aug 12 07:12:54 2018 Return-Path: Delivered-To: freebsd-x11@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 6401D1067025 for ; Sun, 12 Aug 2018 07:12:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D825B7C380 for ; Sun, 12 Aug 2018 07:12:53 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9C8101067024; Sun, 12 Aug 2018 07:12:53 +0000 (UTC) Delivered-To: x11@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 7A9561067023 for ; Sun, 12 Aug 2018 07:12:53 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E71C67C37F for ; Sun, 12 Aug 2018 07:12:52 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id y207-v6so22310098oie.13 for ; Sun, 12 Aug 2018 00:12:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Tf1n/S4IRO5RWfDaIgVLNAWBLXCUjFMpYsvQ5ZHy5gQ=; b=t+Em0MazuFDH2mMgSv6oDzsxMQjrvndz2+ByZIdicuHpMC7Yxl0TIzfrkAKNWZSgA1 df6HsMK3zC9Q7B11sWP7z3Ln+bCT04s+qK69ZjwhkkD7jP5mPI0hhZ0VJOKFjO4MV5o9 PJDQFuKwAZ67QxKvv6hpQDusznQqgZES5vsb3KvwGrT+db52z4rWtLObjPFgwpZpd2rV qQU+/DEOYVL6ZjCQDXN/u9GerkReHSybkuMgIk8K1kIx+rmbDCCnzJtIuuTw49EZf9wx bEoXVgTDj8xsoKLyC2VzahcBcJUwN5MNnM5nkbgUNxI9lHiYDN2RjlVqj6toSCNtlvwG W+dQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Tf1n/S4IRO5RWfDaIgVLNAWBLXCUjFMpYsvQ5ZHy5gQ=; b=QmzeBTobWfRhs4Xs2DEzjfpdrHaJzKPUIJmevg5EYuk9mqhU9WlLLZ4wKBhk9yOszt 1lsD5uQ6qdMfRmO13i7MccB84qo09iXZ0yz2nNOcvmlwwK4UafuLEYa292GyPpJECff6 QstyER4+aKhrNzwH2tKSIgUIrdHLOaW3IFeOqf2j8GQefGgXP7FJBfhgu3Ai3yvB4uS8 rS7Tl3Uaejn5inBoq+lF4Uulwseeq++vC/S4NINVjlR++bR8Wb278FnGlOO3tCwv09L9 su+OVfe/qdwdGOmgoKrTMshPxi4HVpFj524EV69kKDHz7sJ7IKjOAjR/i6lyOQiXHWyA w/wg== X-Gm-Message-State: AOUpUlGbWFmUtXlGRmsNOKgfrSyOsTnYgdar1pLmlv8Hv3CcBbS+1TNb Uy86xBt97vFf/t+4oRywFwUidoSl3lzyt7SvlwE= X-Google-Smtp-Source: AA+uWPyw9KIhay/L21DaYiaH+pbNDP0ocRadznwiPPNrDH1eDUSRUSOBUpix/FnTCcy/UcsknBD/1ebGKl2rUCeiBEc= X-Received: by 2002:aca:5004:: with SMTP id e4-v6mr14228289oib.111.1534057971798; Sun, 12 Aug 2018 00:12:51 -0700 (PDT) MIME-Version: 1.0 References: <1534020277.35460.0@hraggstad.unrelenting.technology> <1534028064.35460.2@hraggstad.unrelenting.technology> In-Reply-To: <1534028064.35460.2@hraggstad.unrelenting.technology> From: Kevin Oberman Date: Sun, 12 Aug 2018 00:12:39 -0700 Message-ID: Subject: Re: Clarification on moving to drm-stable-kmod on 11.2 To: greg@unrelenting.technology Cc: pete@nomadlogic.org, "freebsd-x11@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 07:12:54 -0000 On Sat, Aug 11, 2018 at 3:54 PM Greg V wrote: > > > On Sun, Aug 12, 2018 at 1:12 AM, Pete Wright > wrote: > > > > > > On Aug 11, 2018 1:44 PM, Greg V wrote: > >> On Sat, Aug 11, 2018 at 9:58 PM, Kevin Oberman > >> wrote: > >> > A while ago I moved to running drm-stable-kmod on my 11.2 system > >> and > >> > have > >> > not had any issues, but I am unclear on what, if ny changes are > >> > appropriate > >> > in my loader.conf. I just noticed that the "old" kernel module is > >> > atill > >> > being loaded and I think that is wrong. > >> > > >> > My loader.conf contains: > >> > drm.i915.enable_rc6=3D7 > >> > # Enable semaphores > >> > drm.i915.semaphores=3D1 > >> > Are these appropriate to drm-stable-kmod? If so, is loader.conf the > >> > proper > >> > place for them? > >> > >> Hi, > >> > >> These don't work with drm-*-kmod, the new names are: > >> compat.linuxkpi.enable_rc6, compat.linuxkpi.semaphores, etc. > >> > >> And yeah, loader.conf is of course the right place. > >> > >> You can run 'sysctl -a | grep enable_rc6' =E2=80=94 if you see drm.i91= 5, > >> you're on the old module, if you see compat.linuxkpi, you're on the > >> new > >> one. > >> > > > > > > Out of curiosity, what do these knobs do? Or for the semaphor knob, > > when would you use this? > > rc6 is a lower power state. I think it should be enabled by default > anyway. > > semaphores enables, well, semaphores, for some synchronization in the > driver somewhere=E2=80=A6 idk really :) also should probably be default= =3D1 > Thanks! For the record, I see that compat.linuxkpi.enable_rc6 is set to 1 by default, but it's not clear which of the rc6 bits are set. If it is just 1, not all power savings are enabled, but it might now be a boolean and setting it sets all three rc6 bits. I know that I needed to enable the semaphores for some port, but I don't recall what it was. It now defaults to 1, as well. Thanks for the responses. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683