From owner-freebsd-stable@freebsd.org Wed Sep 12 10:29:59 2018 Return-Path: Delivered-To: freebsd-stable@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 644FA108EEFB for ; Wed, 12 Sep 2018 10:29:59 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0BE127C8A0 for ; Wed, 12 Sep 2018 10:29:58 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.240.30] (helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g02PC-0007gF-HG; Wed, 12 Sep 2018 10:29:54 +0000 Subject: Re: Using drm-next in 11.2 To: Claude Buisson , freebsd-stable@freebsd.org References: <84e213db-1833-0788-ad72-fa598dba8b73@orange.fr> From: Pete French Message-ID: Date: Wed, 12 Sep 2018 11:29:54 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <84e213db-1833-0788-ad72-fa598dba8b73@orange.fr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2018 10:29:59 -0000 > Starting from the beginning: > > how the "drm.ko" is loaded ? Thats a very good question! I am not loading it myself explicitly anyhere, so my guess is that xorg is loading it. On the machine right now (which I was using with X11 yesterday) it only has drm2 loaded - again, I assume from starting X > My experience (with the drm2 from base) is that drm.ko and drm2.ko must > not be loaded at the same time. OCuld it be that X is not recognising the amdgpu module because I dont have the right driver, and is thus trying to load up the old drm as it has a radeon driver ? -pete.