Date: Tue, 16 Oct 2018 17:16:34 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Niclas Zeising <zeising@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: Latest update to ATI driver broke in same way as using DRM-next did Message-ID: <e5e96331-fac7-8c9d-aa49-ac5bc5b351d2@ingresso.co.uk> In-Reply-To: <95d9506d-bc56-7562-8e9d-dc2d4e7c600e@freebsd.org> References: <E1g9pJI-00011K-5m@dilbert.ingresso.co.uk> <95d9506d-bc56-7562-8e9d-dc2d4e7c600e@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e5e96331-fac7-8c9d-aa49-ac5bc5b351d2>