From owner-freebsd-stable@freebsd.org Tue Sep 11 16:22:26 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 2D40A1095F4C for ; Tue, 11 Sep 2018 16:22:26 +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 C6CD27DF31 for ; Tue, 11 Sep 2018 16:22:25 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fzlQm-000MYf-RC; Tue, 11 Sep 2018 16:22:24 +0000 Subject: Re: Using drm-next in 11.2 To: CL Moonriver Cc: freebsd-stable@freebsd.org References: <20180911102947.3cd1ef88@wildfire.equinefiction.com> From: Pete French Message-ID: <97f2d757-466e-7bff-6f57-7615287a261d@ingresso.co.uk> Date: Tue, 11 Sep 2018 17:22:24 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180911102947.3cd1ef88@wildfire.equinefiction.com> 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: Tue, 11 Sep 2018 16:22:26 -0000 I dont have any other drm ports installed though - I think te clash is with the ones which are part of the standard kernel build maybe ? Possibly I could try building a custom kernel without them, but first am going to go susbscribe to x11 amiling list and see what they say. -pete. On 11/09/2018 16:29, CL Moonriver wrote: > 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" >