From nobody Sat May 20 20:49:09 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QNwmr1Pplz4BWJ3 for ; Sat, 20 May 2023 20:49:16 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QNwmq3RFwz47Mj for ; Sat, 20 May 2023 20:49:15 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=0K3zW6SO; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="i 1rP9kr"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.19 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 27819320046F for ; Sat, 20 May 2023 16:49:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sat, 20 May 2023 16:49:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1684615752; x=1684702152; bh=wt5E/YBG69v1I8gE7oPHGQNcfQHWky7fD2L AIjT5xJo=; b=0K3zW6SOJrkei0g1Kxl7dJlOTCH8ydT2WTXj1wcKAlEW2oFrfGg ht8bKq4XzoEUvbRJjDU9nOeGCqXL6Ob/cqdoyL+bNoZAMj+AmhFQKcRNg7sPzCOg 57TwVlzIuBs6+87uoX77iyyFJ6dqWjig4Gwl6CO1PIUEiXuXPd0d9XniAxfB2M6Y RR1Ki41VwuGOYy9Cq9tdgNCYtmd8xOW1hzmIXgIxKUDeo9axVfktiIJOhjhyt8Mp 9CvqqYdL9HluzIN1zwFCg0RqrFDWkd90w+fXHSbJT+Op+E+MO9w8JW6+lScgrcRc 4CCcAEfhTvzyPxHq6y1cZ8fssgbq7O/bWCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1684615752; x= 1684702152; bh=wt5E/YBG69v1I8gE7oPHGQNcfQHWky7fD2LAIjT5xJo=; b=i 1rP9kr1DPU/rN4zk5Mnl6wsgguLGHxChQijMzJ6Od6uQOnaO1cjJ4lBxZAr4uLM6 ikYi+yFp4/zs0gcg4PHBFNef8mKcGp+Epa0C1sY1TnRJMNxgXTU9KLtWnOdlFCwn CszVrA0LOtCBZGaHqUQNi2bv5sJj61yJObmyMNpQXItAXtytcAHhUv2GCn4OGIZh h+CrBBdi5PLjUK4tVV2Wgrw4sA1K/4lTI50y6mfJTYJZpoe5xNHTp+CvSr6oZIne 8SGvdfbz+BE8l/4sTx/qW/IHoT1OxYnA00erHJID0qiIapEh3NAoZFI6L0XA17pQ Ja1goLvjBZXmkNveWa0Cw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeijedgudehtdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhephedtkeehfeelueehgfeuteegveeukedtuddtgeffhfeuue etleegieetveejueevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhephihurhhisegrvghtvghrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 20 May 2023 16:49:12 -0400 (EDT) Message-ID: <5fa6ffa2-2cfa-d5e6-7891-7e9388a81f3e@aetern.org> Date: Sat, 20 May 2023 22:49:09 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: FreeBSD wont boot on AMD Ryzen 9 7950X To: current@freebsd.org References: <22BF4CF1-FA3A-4901-B365-A7F1353BE50F@joscomputing.space> Content-Language: en-US From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QNwmq3RFwz47Mj X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm1]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N Mike Jakubik wrote: > Hello, > > Thanks for the info. At least I know it's not specific to my parts. Is > there any knob one can turn in the BIOS to enable/disable this feature? > iirc UART is old school serial ports? Wonder if removing UART support > from the kernel would be a workaround. Try the following from the loader prompt (option 3 from the beastie menu): set hint.uart.0.disabled=1 set hint.uart.1.disabled=1 boot