From owner-freebsd-stable@freebsd.org Tue Sep 11 17:01:52 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 7ED981096BC4 for ; Tue, 11 Sep 2018 17:01:52 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-05-3.privateemail.com (mta-05-3.privateemail.com [68.65.122.15]) (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 1B8007F89D for ; Tue, 11 Sep 2018 17:01:52 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-05.privateemail.com (localhost [127.0.0.1]) by MTA-05.privateemail.com (Postfix) with ESMTP id 29B3A60066; Tue, 11 Sep 2018 13:01:43 -0400 (EDT) Received: from wildfire.equinefiction.com (unknown [10.20.151.205]) by MTA-05.privateemail.com (Postfix) with ESMTPA id ADB3760056; Tue, 11 Sep 2018 17:01:42 +0000 (UTC) Date: Tue, 11 Sep 2018 12:01:40 -0500 From: CL Moonriver To: Pete French Cc: freebsd-stable@freebsd.org Subject: Re: Using drm-next in 11.2 Message-ID: <20180911120140.266d92e7@wildfire.equinefiction.com> In-Reply-To: <97f2d757-466e-7bff-6f57-7615287a261d@ingresso.co.uk> References: <20180911102947.3cd1ef88@wildfire.equinefiction.com> <97f2d757-466e-7bff-6f57-7615287a261d@ingresso.co.uk> 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 17:01:52 -0000 Well, I have one other suggestion, but this is just completely guesswork on my part. However, I ran into a problem where the "amdgpu" module did not work, though I can't remember the exact error messages I got. You mentioned you had the ATI driver installed in X. Given that, are you sure amdgpu is the right module you need in kld_list? Are you sure it's not radeonkms? Again. that's what nailed me the first time. I DO have an AMD GPU (A10 series). But it uses Radeon R7 graphics. So despite the fact that my GPU is build into the processor, I needed the radeonkms driver, not the amdgpu driver. On Tue, 11 Sep 2018 17:22:24 +0100 Pete French wrote: > 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" > >