From owner-freebsd-stable@freebsd.org Tue Sep 11 17:06:17 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 CE5FF1096F44 for ; Tue, 11 Sep 2018 17:06:16 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-09-3.privateemail.com (mta-09-3.privateemail.com [68.65.122.19]) (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 6C8517FD27 for ; Tue, 11 Sep 2018 17:06:16 +0000 (UTC) (envelope-from clmoonriver@equinefiction.com) Received: from MTA-09.privateemail.com (localhost [127.0.0.1]) by MTA-09.privateemail.com (Postfix) with ESMTP id EAD0460047; Tue, 11 Sep 2018 13:06:08 -0400 (EDT) Received: from wildfire.equinefiction.com (unknown [10.20.151.246]) by MTA-09.privateemail.com (Postfix) with ESMTPA id 8A9DC60041; Tue, 11 Sep 2018 17:06:08 +0000 (UTC) Date: Tue, 11 Sep 2018 12:06:06 -0500 From: CL Moonriver To: Pete French Cc: freebsd-stable@freebsd.org Subject: Re: Using drm-next in 11.2 Message-ID: <20180911120606.536ddfa7@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:06:17 -0000 P.S. I can pretty guarantee you that you do NOT need to build a custom kernel. I have an A10 series CPU with onboard Radeon R7 graphics. So again, if amdgpu isn't working, try radeonkms instead. Maybe that will fix your problem. Also, are you booting using UEFI or Legacy / BIOS mode? 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" > >