From owner-freebsd-current@freebsd.org Sun Jul 21 16:34:08 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 A9F32B7BC2 for ; Sun, 21 Jul 2019 16:34:08 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [IPv6:2a02:2770::216:3eff:fee1:cf9]) (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 AFD3B8663B for ; Sun, 21 Jul 2019 16:34:07 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (p200300C27F4C6B00EA6A64FFFECACA55.dip0.t-ipconnect.de [IPv6:2003:c2:7f4c:6b00:ea6a:64ff:feca:ca55]) (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 45s9L525Rjz3wts for ; Sun, 21 Jul 2019 18:34:05 +0200 (CEST) From: Evilham To: freebsd-current@freebsd.org Subject: Re: acpi issues on FreeBSD-current_r350103 on Thinkpad A485 References: In-reply-to: Date: Sun, 21 Jul 2019 18:34:02 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: AFD3B8663B 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 2a02:2770::216:3eff:fee1:cf9 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-5.49 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-1.73)[ipnet: 2a02:2770::/32(-4.92), asn: 196752(-3.73), country: NL(0.01)]; MX_GOOD(-0.01)[cached: yggdrasil.evilham.com]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; NEURAL_HAM_SHORT(-0.95)[-0.955,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:2a02:2770::/32, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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: Sun, 21 Jul 2019 16:34:08 -0000 On dg., jul. 21 2019, Cristian Pogolsha wrote: > Hi, > > Thank you for the instructions. I have a question related to > post-installation. My system doesn't boot after installing and > rebooting > the system. It just doesn't find the partition on the drive. I > get a blank > screen when selecting from the boot media list. What > partitioning scheme > did you use for your installation? Or is this problem > addressable with step > #2 in your instructions? Putting in the boot/loader.conf -> > set.hw.pci.mcfg=0? The **hw.pci.mcfg=0** line in /boot/loader.conf is so that your booting won't hang the same way it did on installation without manual parameters, shouldn't be related to your current issue. Remember to add the comment linking to the bug as well, so that you can remove it when those changes land in -CURRENT Also add yourself to the CC field in the bug, that way you can help test those changes. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760q Your current issue sounds like a problem with the way you installed / set up the system and is probably better for freebsd-questions: https://lists.freebsd.org/mailman/listinfo/freebsd-questions FWIW: I boot using EFI from ZFS in a geli-encrypted partition in a GPT disk, I recall some manual fiddling but those were likely because I needed sth particular. -- Evilham