From owner-freebsd-current@freebsd.org Sat Aug 24 08:29:59 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 797B0DA544 for ; Sat, 24 Aug 2019 08:29:59 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Frzn5DJdz4lHq for ; Sat, 24 Aug 2019 08:29:56 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Sat, 24 Aug 2019 08:29:53 +0000 Received: from [100.72.61.18] ([185.211.157.23]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 5F32DBA8-0C06-4C6A-8ED9-A2F712DB1406.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Sat, 24 Aug 2019 08:29:53 +0000 Date: Sat, 24 Aug 2019 11:29:50 +0300 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: "amdgpu and radeonkms are known to fail with EFI Boot" To: freebsd-current@freebsd.org, "Clay Daniels Jr." , "freebsd-current@freebsd.org" From: Greg V Message-ID: DKIM-Signature: v=1; a=rsa-sha256; bh=RSOb/X4sQnSkxv5JJx8hgq/DIPZEL8/3H0LKrEbKnoc=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=WFsP1Z5QRkq3ZfWWcE9vnpeA2Hh+9PgJzUrhqgPjIGwEJ9yNBCSK3xdleUxGdgNL7zj0L1i3vUfa3RkQeAhEIDiQI/PpzmdlB7F+NjkdI7EyOu1ikiRRs7ZuNP8PqvK0d0teflII9gVj+0uIHOP8FC/7ddx8UUqyLufidrJ88wk= X-Rspamd-Queue-Id: 46Frzn5DJdz4lHq X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=WFsP1Z5Q; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-6.59 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_IN_DNSWL_NONE(0.00)[63.223.121.91.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.60)[ip: (-9.84), ipnet: 91.121.0.0/16(-4.39), asn: 16276(1.24), country: FR(-0.00)]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Aug 2019 08:29:59 -0000 On August 24, 2019 10:15:22 AM GMT+03:00, "Clay Daniels Jr=2E" wrote: >From the kmod ports, dated 20190814 > > >/usr/ports/graphics/drm-current-kmod/pkg-descr > >"amdgpu and radeonkms are known to fail with EFI Boot" > > >/usr/ports/graphics/drm-current-kmod/pkg-message > >"some positive reports if EFI is not enabled" > > >Any practical suggestions on getting drm-current-kmod to work on an AMD >machine, including how to NOT enable EFI? I did not see that option on >the >install menu=2E "Not enabling" EFI means booting the installer in legacy more (CSM)=2E Ins= taller images are universal, so you'd have to instruct the firmware to igno= re the EFI loader on there=2E Deleting the EFI partition might work I guess= =2E rEFInd can force CSM boot a USB drive=2E I do not recommend this=2E Instead, there is a workaround for the EFI fram= ebuffer conflict=2E If you have it (i=2Ee=2E amdgpu fails to load, or hangs= when starting GUI), boot with hw=2Esyscons=2Edisable=3D1=2E You won't see = anything on the screen after the boot loader and before loading the driver = :) but that's not a big deal when the driver autoloads successfully=2E