From owner-freebsd-stable@freebsd.org Tue Sep 11 15:30:01 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 5A60410947FD for ; Tue, 11 Sep 2018 15:30:01 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-10-3.privateemail.com (mta-10-3.privateemail.com [198.54.127.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "privateemail.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF98A7BC74 for ; Tue, 11 Sep 2018 15:30:00 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-10.privateemail.com (localhost [127.0.0.1]) by MTA-10.privateemail.com (Postfix) with ESMTP id 9E09560053; Tue, 11 Sep 2018 11:29:51 -0400 (EDT) Received: from wildfire.equinefiction.com (unknown [10.20.151.234]) by MTA-10.privateemail.com (Postfix) with ESMTPA id 3C1D760047; Tue, 11 Sep 2018 15:29:51 +0000 (UTC) Date: Tue, 11 Sep 2018 10:29:47 -0500 From: CL Moonriver To: Pete French Cc: freebsd-stable@freebsd.org Subject: Re: Using drm-next in 11.2 Message-ID: <20180911102947.3cd1ef88@wildfire.equinefiction.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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: Tue, 11 Sep 2018 15:30:01 -0000 I agree it sounds like a clash with older modules. Did you have drm-stable-kmod installed or drm-legacy-kmod installed? If so, make sure you remove them before. Sounds to me like what is probably happening is you have modules from two different drm ports installed. So I'd try a make deinstall inside drm-stable-kmod and drm-legacy-kmod directories and see if that fixes anything. On Tue, 11 Sep 2018 13:50:24 +0100 Pete French wrote: > So, I was trying to switch to using this, as I realise its where > things are heading, and I rather like the look of it. But I cant get > it to see my multiple monitors. I install the port, set > 'kld_list="amdgpu"' and it boots up with the new modules, and appears > to find all my displays in dmesg. But when I start X it only uses the > single display port, mirroring it to DVI. > > > When I start X what I am seeing in dmesg is this: > > module_register: cannot register drmn from drm2.ko; already loaded > from drm.ko Module drmn failed to register: 17 > KLD radeonkms.ko: depends on drmn - not available or version mismatch > linker_load_file: Unsupported file type > > Which make me think theres some clash with the old modules and thats > why its not working properly. Also xrandr only lists a single screen, > as default, unlike the list I get using the old drm, which lists all > the outpus correctly. > > Anyone got any advice, or can point me to the coorrect place for > this ? > > cheers, > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org"