From owner-freebsd-x11@freebsd.org Thu Aug 2 23:16:28 2018 Return-Path: Delivered-To: freebsd-x11@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 8BC8F10539F4 for ; Thu, 2 Aug 2018 23:16:28 +0000 (UTC) (envelope-from clmoonriver@equinedreams.art) Received: from NEW-01-1.privateemail.com (new-01-1.privateemail.com [198.54.122.45]) (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 29FEF8182B for ; Thu, 2 Aug 2018 23:16:27 +0000 (UTC) (envelope-from clmoonriver@equinedreams.art) Received: from MTA-06-1.privateemail.com (unknown [10.20.147.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by NEW-01.privateemail.com (Postfix) with ESMTPS id 5D2B46021A; Thu, 2 Aug 2018 23:16:19 +0000 (UTC) Received: from MTA-06.privateemail.com (localhost [127.0.0.1]) by MTA-06.privateemail.com (Postfix) with ESMTP id 3075C6007B; Thu, 2 Aug 2018 19:16:19 -0400 (EDT) Received: from wildfire.equinedreams.art (unknown [10.20.151.200]) by MTA-06.privateemail.com (Postfix) with ESMTPA id 992EA60074; Thu, 2 Aug 2018 23:16:18 +0000 (UTC) Subject: Re: X11 not working on 11-STABLE with AMDGPU To: Greg V , Pete Wright Cc: freebsd-x11@freebsd.org, pkubaj@anongoth.pl References: <20180801092849.GA75303@KGPE-D16> <95b8cfa0-0908-3321-5155-ef49b1bb0a64@equinedreams.art> <20180801141207.GA5202@smtp.iq.pl> <4266f156-3a83-a45d-fab0-cde090c139ba@equinedreams.art> <67630578-f418-b435-9bb0-b40f12e9d881@nomadlogic.org> <1533215599.23824.0@hraggstad.unrelenting.technology> From: CL Moonriver Message-ID: <73d85e29-be1d-a8a8-0fe9-81889a4a429f@equinedreams.art> Date: Thu, 2 Aug 2018 18:16:17 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <1533215599.23824.0@hraggstad.unrelenting.technology> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 23:16:28 -0000 Thanks for the heads up. Are you sure this is still relevant in drm-next? I don't see any dmesg error about disabling GPU acceleration. I did what you suggested, but nothing seems to have changed except I get no text until radeonkms has loaded (I don't get garbage I get nothing at all). I still get dmesg errors regarding ring test failures and such, so turning the EFI framebuffer off doesn't appear to have actually changed anything. On 8/2/18 8:13 AM, Greg V wrote: > Hi everyone, > > Please keep in mind that both radeonkms and amdgpu from drm-*-kmod > currently conflict with the EFI framebuffer. > > https://github.com/FreeBSDDesktop/DEPRECATED-freebsd-base-graphics/issues/170 > > > I currently have hw.syscons.disable=1 in boot/loader.conf to work > around that. > That knob literally turns the EFI framebuffer off, so in between the > boot loader screen and the GPU driver loading, there will be garbage > on screen :) if the driver fails to load, you keep the garbage. If you > want to debug the driver with this workaround on (read dmesg, try > loading, etc.) you have to SSH into the box. >