From owner-freebsd-stable@freebsd.org Tue Oct 16 16:16:38 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 BC87410D92A0 for ; Tue, 16 Oct 2018 16:16:38 +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 5F84373DCA; Tue, 16 Oct 2018 16:16:38 +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 1gCS1K-0007ym-8k; Tue, 16 Oct 2018 16:16:34 +0000 Subject: Re: Latest update to ATI driver broke in same way as using DRM-next did To: Niclas Zeising , freebsd-stable@freebsd.org References: <95d9506d-bc56-7562-8e9d-dc2d4e7c600e@freebsd.org> From: Pete French Message-ID: Date: Tue, 16 Oct 2018 17:16:34 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <95d9506d-bc56-7562-8e9d-dc2d4e7c600e@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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, 16 Oct 2018 16:16:38 -0000 I am using drm-next, but actually I ended up getting this to work by stripping off all packges from the machine yesterday, deleting all of /usr/local and starting adding things from scratch. Am now running fine with drm-next and all works as expected. When I was having the issues, however, xrandr only showed one outout on the card, which puzzled me (there are 4 outputs). -pete. [copying to -stable so others know the outcome] On 16/10/2018 12:39, Niclas Zeising wrote: > On 10/9/18 12:32 PM, Pete French wrote: >> So this is kind of interesting - I posted here last month about trying to >> use drm-next and it not finding my 2nd monitor properly. I did try and >> subscribe to x11@ but for some reaosn that didnt work, and I didnt worry >> abotu it too much so didnt investigate further as I wont be running 12.0 >> for a while. .... > > Which drm driver are you using?  Is this with drm-stable, drm-next or > the driver in base?  Which verison of FreeBSD are you running this on? > What's the output from xrandr in both the working and non-working case? > Regards