From owner-freebsd-x11@freebsd.org Fri Aug 3 21:23:11 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 2B38B1051DAE for ; Fri, 3 Aug 2018 21:23:11 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A523F762A7 for ; Fri, 3 Aug 2018 21:23:10 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=V8Licq67Fnbhb8B52ExqxeR2xUNGJpBXQFTmRI/acdo=; b=KqM7RMtO6zFTVzzpdUsff9YWzE8Gxl4d596tpHdfqelpMTj3l7eC8AKvOpYSjIgfvWGG1WXeourCPHEeAtLvvjIQ7DxXskXi8TtoXc3CaBDmvJHh48zcVZhFhC/KLNkw8tBBbkBGl+HtPGdHlxEq65X9Tg3R645AEzooNpn29nw= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id ee135cc2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 3 Aug 2018 21:22:58 +0000 (UTC) Date: Sat, 04 Aug 2018 00:22:54 +0300 From: Greg V Subject: Re: X11 not working on 11-STABLE with AMDGPU To: CL Moonriver Cc: Pete Wright , freebsd-x11@freebsd.org, pkubaj@anongoth.pl Message-Id: <1533331374.1685.0@hraggstad.unrelenting.technology> In-Reply-To: <73d85e29-be1d-a8a8-0fe9-81889a4a429f@equinedreams.art> 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> <73d85e29-be1d-a8a8-0fe9-81889a4a429f@equinedreams.art> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable 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: Fri, 03 Aug 2018 21:23:11 -0000 On Fri, Aug 3, 2018 at 2:16 AM, CL Moonriver=20 wrote: > Thanks for the heads up. >=20 > Are you sure this is still relevant in drm-next? I don't see any=20 > dmesg error about disabling GPU acceleration. I did what you=20 > suggested, but nothing seems to have changed except I get no text=20 > until radeonkms has loaded (I don't get garbage I get nothing at=20 > all). I still get dmesg errors regarding ring test failures and such,=20 > so turning the EFI framebuffer off doesn't appear to have actually=20 > changed anything. Interesting. Are you 100% sure you're booting with UEFI, not CSM/legacy? Maybe radeonkms doesn't conflict anymore. Maybe this depends on the GPU=20 model or something? For amdgpu (RX 480), it's not an error about disabling acceleration,=20 the amdgpu driver *completely* fails to load when EFI framebuffer is=20 active. And I retested a few weeks ago. No one fixed this specifically=20 yet, so I'm not expecting it to magically stop conflicting=85 =