From owner-freebsd-questions@freebsd.org Mon Jul 29 09:31:04 2019 Return-Path: Delivered-To: freebsd-questions@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 46F16A3F80 for ; Mon, 29 Jul 2019 09:31:04 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (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 63AAC704CC for ; Mon, 29 Jul 2019 09:31:03 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 45xvZ76w76z3wvk for ; Mon, 29 Jul 2019 11:30:55 +0200 (CEST) From: Evilham To: freebsd-questions@freebsd.org Subject: Re: Hang on boot References: <20190729051333.GA1899@snow.home> In-reply-to: <20190729051333.GA1899@snow.home> Date: Mon, 29 Jul 2019 11:30:52 +0200 Message-ID: <72db458b-f2f4-4ee9-873c-a82f4e90a165@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 63AAC704CC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-4.34 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-0.75)[asn: 196752(-3.77), country: NL(0.01)]; MX_GOOD(-0.01)[yggdrasil.evilham.com,mail.evilham.com]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; NEURAL_HAM_SHORT(-0.79)[-0.794,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 09:31:04 -0000 Hello, On dl., jul. 29 2019, Kurt Hackenberg wrote: > Hello people, > > So here's a question. I'm trying to run FreeBSD 12.0 on a new > AMD > desktop PC, and it's not working. I've read the relevant parts > of the > handbook and release notes, installed the package > drm-kmod-g20190710, > and added > > kld_list="/boot/modules/amdgpu.ko" > > to rc.conf. Booting ends up in a silent hang: screen goes dark, > keyboard and mouse get no response, the system doesn't answer > pings. > The only way out is to pull the plug. > > Without loading that module, booting succeeds, but /dev/dri > doesn't > exist and the X server refuses to run. I was hit by a very similar thing, though more complex because AMD Ryzen laptop. For reference, this applied to a ThinkPad A485, but I think the X driver bits apply to you. First of all, AMZ Ryzen laptops are affected by bug #231760, which keeps them from booting normally, I had gotten around it by setting hw.pci.mcfg=0 in the boot loader; this is not relevant to you, but it is in the global setting. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760 At that point, I had the laptop's bios at version 1.16, and was experiencing random crashes, which I thought were related to WireGuard. drm-kmod from 12-RELEASE worked just fine. While researching the random crashes, someone suggested that I triple check the bios version, which I did to 1.24. This, and only this, broke drm-kmod and left it in the same state you mention, except, after I booted single-user mode and removed drm-kmod, X started, but only on the laptop's screen (no external one, because no graphics card detected). For reference, this is the bug (needs update and closing): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760 Since, at this point I had 13-CURRENT compiled and running with a patch for 231760, I discovered that there is drm-devel-kmod in there, which at time of this email is version 5.0.g20190722, as opposed to drm-kmod's which is 4.16.g20190722. Installing that and rebooting resulted in a fully functional X with external screens. So, my guess is that your card would work with drm-kmod 5.0, in fact, when I mentioned on the current ML that my system had fully functional X in 12-RELEASE, people were a bit amazed by it, it looks like support for AMD Ryzen cards has improved a lot between the versions. https://lists.freebsd.org/pipermail/freebsd-current/2019-July/073862.html Basically: try to get drm-kmod 5.0 in your system, maybe that'd help. You'd do that by compiling from source or checking the ports tree to find how drm-devel-kmod is built in 13-CURRENT and maybe that'd build for 12-RELEASE, someone else might be more useful here. If you do manage and it solves your issue, documenting it might be useful for those that come afterwards with similar hardware and similar problems wanting to run 12-RELEASE. -- Evilham