wrote: > > > > FreeBSD supports up to 256 CPU cores in the default kernel configuratio= n > > (on Tier-1 architectures). Systems with more than 256 cores are > > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s > > lifetime. The FreeBSD Foundation is supporting the effort to increase > > MAXCPU, and PR269572[1] is open to track tasks and changes. > > > > As a project we have scalability work ahead of us to make best use of > > high core count machines, but at a minimum we should be able to boot a > > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > > release that supports such a configuration. > > > > Some changes have already been committed in support of increased MAXCPU= , > > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > > 78cfa762ebf2 and 74ac712f72cf). > > > > The next step is to increase the maximum cpuset size for userland. > > I have this change open in review D39941[2] and an exp-run request in > > PR271213[3]. Following that the kernel change for increasing MAXCPU is > > in D36838[4]. > > > > Additional work on bloat reduction will continue after this change, and > > looking forward FreeBSD is going to need ongoing effort from the > > community and the FreeBSD Foundation to continue improving scalability. > > > > [1] https://bugs.freebsd.org/269572 > > [2] https://reviews.freebsd.org/D39941 > > [3] https://bugs.freebsd.org/271213 > > [4] https://reviews.freebsd.org/D36838 > > > > By any chance will this be merged into 13? > Nope. It breaks too many kernel KBIs that are exposed to at least some modules. Warner > > Kind regards, > Moin > --0000000000005b94b605fb21fe84 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Sun, May 7, 2023, 3:51 PM Moin Rahman <bofh@freebsd.org> wrote:

> On May 5, 2023, at 3:38 PM, Ed Maste <emaste@freebsd.org> wr= ote:
>
> FreeBSD supports up to 256 CPU cores in the default kernel configurati= on
> (on Tier-1 architectures).=C2=A0 Systems with more than 256 cores are<= br> > available now, and will become increasingly common over FreeBSD 14=E2= =80=99s
> lifetime.=C2=A0 The FreeBSD Foundation is supporting the effort to inc= rease
> MAXCPU, and PR269572[1] is open to track tasks and changes.
>
> As a project we have scalability work ahead of us to make best use of<= br> > high core count machines, but at a minimum we should be able to boot a=
> GENERIC kernel on such systems, and have an ABI for the FreeBSD 14
> release that supports such a configuration.
>
> Some changes have already been committed in support of increased MAXCP= U,
> including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of=
> changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf).
>
> The next step is to increase the maximum cpuset size for userland.
> I have this change open in review D39941[2] and an exp-run request in<= br> > PR271213[3].=C2=A0 Following that the kernel change for increasing MAX= CPU is
> in D36838[4].
>
> Additional work on bloat reduction will continue after this change, an= d
> looking forward FreeBSD is going to need ongoing effort from the
> community and the FreeBSD Foundation to continue improving scalability= .
>
> [1] https://bugs.freebsd.org/269572
> [2] https://reviews.freebsd.org/D39941
> [3] https://bugs.freebsd.org/271213
> [4] https://reviews.freebsd.org/D36838
>

By any chance will this be merged into 13?

Nope. It breaks too many kernel K= BIs that are exposed to at least some modules.

<= /div>

Warner

Kind regards,
Moin

--0000000000005b94b605fb21fe84-- From nobody Mon May 8 19:01:33 2023 X-Original-To: freebsd-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 4QFVy75y8Nz4BFpW; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QFVy75WDCz40QD; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683572495; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=naNyuef0hEVh7ER6V5H6FTzeZ6VyxOxioyEBOv+r7W0=; b=lwLpfL+EO9D8N8A3ioCLYPhTtKqcuNJr+8c/b7w246n2kGtXJ2A+ONwfRvO8G3E4uPfVJa 3ULj4HyGj+N6T+ph26MOT1LsLSInLWEaQNMV1qbu4r7FF7AZXHI2P4paNc48l3J8Jq4EjV KJSWPogPvg2x/otJFySr6K7juEBZze4hO6nSWbQLf7rIwNYmcwZvYGKUTuuPBljakpudLd F0Du0L/L+4wmEN3wiaxYUbcfJs+vVKiL8THd0Za6ytBomrprlTp58kB1k/iPJwwVLYHErz FY4MeRzg0XKBPHJbE2Mci6pOW+87Kablq+ZW1DZcIweO0zzdD7Q+C2NzWN6+0A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1683572495; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=naNyuef0hEVh7ER6V5H6FTzeZ6VyxOxioyEBOv+r7W0=; b=HhDFcnIrwgvrTDa5tBfvXctD6VVLevsbrxm0A74FoKtMxuVjEFeh6cChxI9twgeF9jq7Gj oIRbs8ZcjfiThRtg/EKfzLgeha1iudAcWwSbAlr0amUInky4Czpm108MkSL/aisUxr0I2r fDiFTjQvJjfvNtCx1oZc5RXptroXFINOvHyoqHxzqlmQW2yx7PTREKL7Ha5oR2SRnFTtSz siFKA7bLvSRORL5yAF/w/Brcc6EsOtMDtzIU0Ps1qXbtvBTQAMGwmiSVHU4J0UwZA4yNVo q3JK9L3o8lZLkAynRucqHBntK/G9MlghATtv0WCc0y7K6QjA6CwWCaMeEo03uA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1683572495; a=rsa-sha256; cv=none; b=urh9GxT+/EPhnDSiwxSj9xWox540k4J8JxwxPG+dT/jA4HkbT6l8ESIcHHwNM58Z7x9XTH P7TKuKgc8EpnLWfPQZUnb5wzORAEmoWQxhKrU9n49UCaZgWlJXmz0jvIwSvlZNaBEkILI7 eTH0GWF+nvNCQ1YhpUYaNyh+8JDp+ub5sFu1MPKvAoNRvEMB1N89ZaH+vVF6u0fBRjZyjP PNX3PO96ZQaTb+8GOQRP6pn7LuJSEhMPhWtNkws9CoZqW65R/Il0vL8sDYAoyjnENmdThW rV7nqcB2u+/E3jJlRjdkqn99zNmJKfdZA+pRHt8OZLQoqMbqQmG4V5lHoWuLfw== Received: from [IPV6:2601:648:8680:16b0:9597:2b45:6d3:31cd] (unknown [IPv6:2601:648:8680:16b0:9597:2b45:6d3:31cd]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhb) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QFVy72Cbvzy7H; Mon, 8 May 2023 19:01:35 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Message-ID: <5e59d762-6f58-46a4-bceb-de7fcb87682d@FreeBSD.org> Date: Mon, 8 May 2023 12:01:33 -0700 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 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: Support for more than 256 CPU cores Content-Language: en-US To: Ed Maste , freebsd-arch , FreeBSD Current References: From: John Baldwin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N On 5/5/23 6:38 AM, Ed Maste wrote: > FreeBSD supports up to 256 CPU cores in the default kernel configuration > (on Tier-1 architectures). Systems with more than 256 cores are > available now, and will become increasingly common over FreeBSD 14’s > lifetime. The FreeBSD Foundation is supporting the effort to increase > MAXCPU, and PR269572[1] is open to track tasks and changes. > > As a project we have scalability work ahead of us to make best use of > high core count machines, but at a minimum we should be able to boot a > GENERIC kernel on such systems, and have an ABI for the FreeBSD 14 > release that supports such a configuration. > > Some changes have already been committed in support of increased MAXCPU, > including increasing MAX_APIC_ID (commit c8113dad7ed4) and a number of > changes to reduce bloat (such as commits 42f722e721cd, e72f7ed43eef, > 78cfa762ebf2 and 74ac712f72cf). > > The next step is to increase the maximum cpuset size for userland. > I have this change open in review D39941[2] and an exp-run request in > PR271213[3]. Following that the kernel change for increasing MAXCPU is > in D36838[4]. > > Additional work on bloat reduction will continue after this change, and > looking forward FreeBSD is going to need ongoing effort from the > community and the FreeBSD Foundation to continue improving scalability. > > [1] https://bugs.freebsd.org/269572 > [2] https://reviews.freebsd.org/D39941 > [3] https://bugs.freebsd.org/271213 > [4] https://reviews.freebsd.org/D36838 FWIW, I think it will be useful for main to run with a larger userspace MAXCPU than kernel for at least a while so that we have better testing of that configuration and to give headroom for bumping MAXCPU in the kernel during the 14.x branch. The only other viable path I think which would be more work would be to rework cpuset_t in userspace to always use a dynamically sized mask. This could perhaps be done in an API-preserving manner by making cpuset_t an opaque wrapper type in userland and requiring CPU_* to indirect to functions in libc, etc. That's a fair bit more work however. -- John Baldwin From nobody Thu May 11 07:59: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 4QH46m5KFPz49tXD; Thu, 11 May 2023 07:59:28 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QH46l1mqXz3NPl; Thu, 11 May 2023 07:59:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mx header.b=GaIgsVh9; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.155.74 as permitted sender) smtp.mailfrom=manu@bidouilliste.com; dmarc=pass (policy=none) header.from=bidouilliste.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1683791959; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=cJOSb1n4c2IxKThNzWSeIwuLsKn0701s5fPxeejCEag=; b=GaIgsVh9pO2S/3HbaCiRSgeWhbHh8w18mJfmTKbJ7zt2lQlhI1hnRQaVNY7MNZ6KSlrj5J T6TvNO63FIsCGTjRjdePVlxeKwO7ZTv73oyFbY9/2o1KlH/pwpzakBZxX3CckeIFSQNLJ8 sCeMYtuW3GW6L2d0dUW+0kVrBTeYzKg= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 56e14c3e (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 11 May 2023 07:59:14 +0000 (UTC) Date: Thu, 11 May 2023 09:59:09 +0200 From: Emmanuel Vadot To: current@FreeBSD.org, x11@FreeBSD.org Subject: CFT: fwget(8) Message-Id: <20230511095909.2b4565365e0818fb20b08a8d@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[bidouilliste.com,none]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mx]; R_SPF_ALLOW(-0.20)[+ip4:212.83.155.74/32]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[x11@FreeBSD.org,current@FreeBSD.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FREEFALL_USER(0.00)[manu]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QH46l1mqXz3NPl X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Hello, Recently I've adde the fwget(8) utility, see https://cgit.freebsd.org/src/commit/?id=d198b8774d2cfb6f140893e1c6236af9e97d1497 The goal of this program is to scan the hardware and download the needed firmwares, for now it only do that for Intel GPUs and recent AMD GPUs (the one supported by amdgpu.ko). I'd like to know if I handled correctly the mapping between ids on Intel and AMD GPUs (for i915kms and amdgpu drm module). I'm pretty sure that Intel is correct but I could have messed up some AMD ones. Also for some AMD GPUs you need two firmware generations and it's hard to know by looking at the code. It would be good to fix any bugs/miss-match before 14.0 The best way to test if everything works is : 1/ pkg delete gpu-firmware-\* 2/ (optional) pkg install drm-515-kmod/drm-510-kmod (if you had the meta package drm-kmod installed it would have been removed in step 1) 3/ fwget 4/ kldload i915kms/amdgpu For i915kms just check dmesg for lines saying something like "drmn0: successfully loaded firmware image ...", this means that everything is correct for your hardware. If you see a line like "drmn0: could not load firmware image ..." please open a PR on bugzilla with dmesg and pciconf -vl attached. Note that firmware for i915kms are optional, they only help with power management and suspend/resume. For amdgpu the driver will fail to attach and you will loose the display if the firmwares aren't present so you will need to ssh into the machine to check for similar lines like i915kms. Thanks, -- Emmanuel Vadot From nobody Thu May 11 09:03:51 2023 X-Original-To: freebsd-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 4QH5YL2gDnz49y5v for ; Thu, 11 May 2023 09:04:06 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Received: from mail.flex-it.com.ua (mail.flex-it.com.ua [193.239.74.7]) (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 4QH5YJ3khrz3kbT for ; Thu, 11 May 2023 09:04:04 +0000 (UTC) (envelope-from shuriku@shurik.kiev.ua) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of shuriku@shurik.kiev.ua designates 193.239.74.7 as permitted sender) smtp.mailfrom=shuriku@shurik.kiev.ua; dmarc=none Received: from [188.231.181.61] (helo=[10.2.1.109]) by mail.flex-it.com.ua with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1px2DM-0002hn-3l for freebsd-current@freebsd.org; Thu, 11 May 2023 12:03:56 +0300 Content-Type: multipart/alternative; boundary="------------J4CvPguOCv1tJlNoqWQmldf0" Message-ID: Date: Thu, 11 May 2023 12:03:51 +0300 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 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: CFT: fwget(8) To: freebsd-current@freebsd.org References: <20230511095909.2b4565365e0818fb20b08a8d@bidouilliste.com> Content-Language: uk-UA From: Oleksandr Kryvulia In-Reply-To: <20230511095909.2b4565365e0818fb20b08a8d@bidouilliste.com> X-Spamd-Result: default: False [-2.92 / 15.00]; NEURAL_HAM_LONG(-0.92)[-0.917]; NEURAL_HAM_SHORT(-0.91)[-0.907]; NEURAL_HAM_MEDIUM(-0.80)[-0.797]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:35297, ipnet:193.239.72.0/22, country:UA]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[shurik.kiev.ua]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QH5YJ3khrz3kbT X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------J4CvPguOCv1tJlNoqWQmldf0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 11.05.23 10:59, Emmanuel Vadot пише: > Hello, > > Recently I've adde the fwget(8) utility, see > https://cgit.freebsd.org/src/commit/?id=d198b8774d2cfb6f140893e1c6236af9e97d1497 > > The goal of this program is to scan the hardware and download the > needed firmwares, for now it only do that for Intel GPUs and recent AMD > GPUs (the one supported by amdgpu.ko). > > I'd like to know if I handled correctly the mapping between ids on > Intel and AMD GPUs (for i915kms and amdgpu drm module). > I'm pretty sure that Intel is correct but I could have messed up some > AMD ones. Also for some AMD GPUs you need two firmware generations and > it's hard to know by looking at the code. It would be good to fix any > bugs/miss-match before 14.0 > The best way to test if everything works is : > > 1/ pkg delete gpu-firmware-\* > 2/ (optional) pkg install drm-515-kmod/drm-510-kmod (if you had the > meta package drm-kmod installed it would have been removed in step 1) > 3/ fwget > 4/ kldload i915kms/amdgpu > > For i915kms just check dmesg for lines saying something like > "drmn0: successfully loaded firmware image ...", this means that > everything is correct for your hardware. > If you see a line like > "drmn0: could not load firmware image ..." > please open a PR on bugzilla with dmesg and pciconf -vl attached. > Note that firmware for i915kms are optional, they only help with power > management and suspend/resume. > > For amdgpu the driver will fail to attach and you will loose the > display if the firmwares aren't present so you will need to ssh into > the machine to check for similar lines like i915kms. > > Thanks, > Hi, for me it correctly detects needed package gpu-firmware-intel-kmod-kabylake, but not install it. Propposed fix: - pkg install -q ${package} + pkg install -qy ${package} --------------J4CvPguOCv1tJlNoqWQmldf0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 11.05.23 10:59, Emmanuel Vadot пише:

 Hello,

Recently I've adde the fwget(8) utility, see
https://cgit.freebsd.org/src/commit/?id=d198b8774d2cfb6f140893e1c6236af9e97d1497

 The goal of this program is to scan the hardware and download the
needed firmwares, for now it only do that for Intel GPUs and recent AMD
GPUs (the one supported by amdgpu.ko).

 I'd like to know if I handled correctly the mapping between ids on
Intel and AMD GPUs (for i915kms and amdgpu drm module).
 I'm pretty sure that Intel is correct but I could have messed up some
AMD ones. Also for some AMD GPUs you need two firmware generations and
it's hard to know by looking at the code. It would be good to fix any
bugs/miss-match before 14.0
 The best way to test if everything works is :

 1/ pkg delete gpu-firmware-\*
 2/ (optional) pkg install drm-515-kmod/drm-510-kmod (if you had the
meta package drm-kmod installed it would have been removed in step 1)
 3/ fwget
 4/ kldload i915kms/amdgpu

 For i915kms just check dmesg for lines saying something like 
 "drmn0: successfully loaded firmware image ...", this means that
everything is correct for your hardware.
 If you see a line like
 "drmn0: could not load firmware image ..."
 please open a PR on bugzilla with dmesg and pciconf -vl attached.
 Note that firmware for i915kms are optional, they only help with power
management and suspend/resume.

 For amdgpu the driver will fail to attach and you will loose the
display if the firmwares aren't present so you will need to ssh into
the machine to check for similar lines like i915kms.

 Thanks,

Hi,
for me it correctly detects needed package gpu-firmware-intel-kmod-kabylake, but not install it.
Propposed fix:

- pkg install -q ${package}
+ pkg install -qy ${package} --------------J4CvPguOCv1tJlNoqWQmldf0-- From nobody Thu May 11 09:59:49 2023 X-Original-To: freebsd-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 4QH6nj2fgjz4B1kv for ; Thu, 11 May 2023 09:59:53 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QH6nh6M6gz3rY8 for ; Thu, 11 May 2023 09:59:52 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1683799190; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vdaJgv7W9GQiyV0yNCH+6EP/JnqPF1y7bJW06O60fdA=; b=AHmMOToiOno9BbVV/dPMIBvaOOJl8YwBEQ4OEVIiheXrIlPvMxK6rqVZXt/8AxDSctiW3j qpYB21m+Eq63wLAD7ctzGI3AgoFJHJBrdahVM+ptO84C/YTI8QIX3qJbFQL4FeCbqVZp6m mcEoZkKBaZVr1zBwvadz5XjBv5KFfwo= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 78389058 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 11 May 2023 09:59:49 +0000 (UTC) Date: Thu, 11 May 2023 11:59:49 +0200 From: Emmanuel Vadot To: Oleksandr Kryvulia Cc: freebsd-current@freebsd.org Subject: Re: CFT: fwget(8) Message-Id: <20230511115949.43846c83ebe51aba7d4acb14@bidouilliste.com> In-Reply-To: References: <20230511095909.2b4565365e0818fb20b08a8d@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QH6nh6M6gz3rY8 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, 11 May 2023 12:03:51 +0300 Oleksandr Kryvulia wrote: > 11.05.23 10:59, Emmanuel Vadot ????: > > Hello, > > > > Recently I've adde the fwget(8) utility, see > > https://cgit.freebsd.org/src/commit/?id=3Dd198b8774d2cfb6f140893e1c6236= af9e97d1497 > > > > The goal of this program is to scan the hardware and download the > > needed firmwares, for now it only do that for Intel GPUs and recent AMD > > GPUs (the one supported by amdgpu.ko). > > > > I'd like to know if I handled correctly the mapping between ids on > > Intel and AMD GPUs (for i915kms and amdgpu drm module). > > I'm pretty sure that Intel is correct but I could have messed up some > > AMD ones. Also for some AMD GPUs you need two firmware generations and > > it's hard to know by looking at the code. It would be good to fix any > > bugs/miss-match before 14.0 > > The best way to test if everything works is : > > > > 1/ pkg delete gpu-firmware-\* > > 2/ (optional) pkg install drm-515-kmod/drm-510-kmod (if you had the > > meta package drm-kmod installed it would have been removed in step 1) > > 3/ fwget > > 4/ kldload i915kms/amdgpu > > > > For i915kms just check dmesg for lines saying something like > > "drmn0: successfully loaded firmware image ...", this means that > > everything is correct for your hardware. > > If you see a line like > > "drmn0: could not load firmware image ..." > > please open a PR on bugzilla with dmesg and pciconf -vl attached. > > Note that firmware for i915kms are optional, they only help with power > > management and suspend/resume. > > > > For amdgpu the driver will fail to attach and you will loose the > > display if the firmwares aren't present so you will need to ssh into > > the machine to check for similar lines like i915kms. > > > > Thanks, > > >=20 > Hi, > for me it correctly detects needed package=20 > gpu-firmware-intel-kmod-kabylake, but not install it. > Propposed fix: >=20 > - pkg install -q ${package} > + pkg install -qy ${package} Yes this is on purpose, I didn't wanted to automatically install packages until bugs where solved, but I planned to enable this before 14.0. Cheers, --=20 Emmanuel Vadot From nobody Thu May 11 20:16:07 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 4QHNSr6dkLz49yJ8 for ; Thu, 11 May 2023 20:16:12 +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 4QHNSr3RDqz3rxS; Thu, 11 May 2023 20:16:12 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; none Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id A0A5932005B5; Thu, 11 May 2023 16:16:10 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 11 May 2023 16:16:10 -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= 1683836170; x=1683922570; bh=aI32JB1vNDLzaVmpVmaC9ZwkPpXfIOq6PXz nXjyxGDI=; b=Xzd2I45rDuuQOnHnWrs3CxU/O4V+0UfKla2bCxSa15b9V9VVlqj ko1AdU9O9+mCLmHgla7D73u5OxrLpzX+yh04UvI0iYOrTXzmuvNrO4HMf5/ZRYjz 4lwrKlFBfG4fMzct56cWdEOfvG7i0cq5sAAlB1KS+DmQcp99JbtsmsLsV4Paa71p g9SM9nNBzQkzNIY2wsRaWt3YTat2FFA/fiPQYCK/R4dScxkmPf3XfkKe4yddQVqa SnfmgxSK9YJpVlkBKvHS9OnvXDm+W6AUtNYPq8OTk5ey1c+ZjKSTER3HaaoEhEPb EaAV69fT38hMLbPo/0PUKvyOTN77xT5/jWw== 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=fm3; t=1683836170; x= 1683922570; bh=aI32JB1vNDLzaVmpVmaC9ZwkPpXfIOq6PXznXjyxGDI=; b=E A0O7K1GOxSjckrkXn3M//o9GfbpRUVUmpbjHt4OMMrXpswBK44LdadDZdTY9qj2K 372geEL8DZUk9Wgl06VG1i/1MloICfEOfAdtP708NZyG93iFJxloeeD4DTL9H4lo 83k5iz54zQnFrvzI3PQEdsOFCrIBOFMDwg4bkPdtPgCb1SduBWyn3zFV9LmRYsN+ waS+pw+1JJ30Ec4KPDhYyKzNxnw36cjCEAePOnq3eOL8+Sk+dle4sWaDDHStVWyG uS8AybCmYzXkNmYtoCKS2sK0ZEt0ra5KpvvC4vTfpePbGpxIgeaL3KAehqEUHyhs pY29Drc4Flx70W0kJqq+g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeegkedgudegkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ejredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhepgeehleevueehhffggfetteffieffhfduteduteeuvdehvd fhffdvtefhffejjedvnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihurhhisegrvghtvg hrnhdrohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 11 May 2023 16:16:09 -0400 (EDT) Message-ID: <0066785e-4200-9f93-8c16-b57efe2c700e@aetern.org> Date: Thu, 11 May 2023 22:16:07 +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: git: c16e08e5f324 - main - stand/efi: Retire i386 support Content-Language: en-US To: Warner Losh , current@freebsd.org References: <202305112006.34BK6sca019665@gitrepo.freebsd.org> From: Yuri In-Reply-To: <202305112006.34BK6sca019665@gitrepo.freebsd.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QHNSr3RDqz3rxS X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Warner Losh wrote: > The branch main has been updated by imp: > > URL: https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > Author: Warner Losh > AuthorDate: 2023-05-11 20:04:12 +0000 > Commit: Warner Losh > CommitDate: 2023-05-11 20:06:03 +0000 > > stand/efi: Retire i386 support > > Remove the i386 ifdefs and files. It never worked. > > Sponsored by: Netflix > Reviewed by: manu, tsoome, kevans > Differential Revision: https://reviews.freebsd.org/D40012 As this question seems to be asked a lot on the forums, does this mean we will never support the 32bit efi booting 64bit OS? From nobody Thu May 11 20:28:12 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 4QHNkx5PhKz49yhZ for ; Thu, 11 May 2023 20:28:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHNkx4xhBz3vZP for ; Thu, 11 May 2023 20:28:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-50bc25f0c7dso16435843a12.3 for ; Thu, 11 May 2023 13:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683836904; x=1686428904; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KJhmUmFcE4mCgck6wkrF+jXsrf/A/dNyrCIMbPi+hlE=; b=hbJr6MYUL9fuS7OwYm/pbrRaEi8Y+Q1iY+pyawJLvqQ7BwUy2c63AoHuvbxIa6Q9dh IbxZG5il2G5g+yNA4w2mt39A4JFZbVe+63rWK8I5YmuS1UqufaraKxm06tqYuUx9wzH1 tqXNaJDqrvhjpG4UAQxmARNaJy1oW7+xEDBZufCG7N58WJrCrMr7wq3ZOZJit7Sito15 0MDlo1J+ifxVFRw5kHGG92omSQuYu6V0P3r+wKTgzNXNOF9HIgN/zu/g3ojxzg/UixW4 /vlT+kYyysAnFT3bLh3YPXM2Nek4aTWHJsvh1o4KyJIou5VUyGb6IlYqKM+Y8e8oReq+ gu6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683836904; x=1686428904; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KJhmUmFcE4mCgck6wkrF+jXsrf/A/dNyrCIMbPi+hlE=; b=KWnE1P7CBJkY24ixvDLE6TfK+ryYU2F6bmcwLx2IEZ/pAsKGT5WvoRAFYJH7XZ+Yvr mJAS2j7IZmSKQ5AOIShPGCj4Q0VeK5e9GkB0v0cqUmo/huZ87k4NGWr50ZHz015Q7cHO Ht+6MHgPdkwzkTKS1wpNXApIMbU2gcSE4fsakPSVup69XmHLffPFliq16ClHHKltUr5N hf58r+R9dc/bGpHshm5aJInhT8zQV85hAS4oDH8ijBrbcxbCRVNhRbJ1qugkThDVEtps 6vIYpfKOOxSX1CEYbUP+miKJ/f5RR16BfpcnBfhv9rVDaHLrqm+Pom1FlODSD7UYkhbE GqIw== X-Gm-Message-State: AC+VfDzZXpzkuR1Jkif7ks9Pf36JuuAbG+eLGuYXl4VTS1Myhd5GDsX8 KNBuGTbB0Uc+Nkj/G2cRnJ+M+ipqsYxtt05m+WWnbw== X-Google-Smtp-Source: ACHHUZ7bcQcZmIWwZ26LVZulhic9vRhJQRrt1Mo00fOUteT4jJ4dBPD2k17kwecPJC3i9ZBUHb6aNVIYm6Uf0yxP87o= X-Received: by 2002:a17:907:1c03:b0:94e:4489:f24d with SMTP id nc3-20020a1709071c0300b0094e4489f24dmr21637351ejc.61.1683836903795; Thu, 11 May 2023 13:28:23 -0700 (PDT) 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 References: <202305112006.34BK6sca019665@gitrepo.freebsd.org> <0066785e-4200-9f93-8c16-b57efe2c700e@aetern.org> In-Reply-To: <0066785e-4200-9f93-8c16-b57efe2c700e@aetern.org> From: Warner Losh Date: Thu, 11 May 2023 14:28:12 -0600 Message-ID: Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support To: Yuri Cc: Warner Losh , FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000082c0b305fb70d48d" X-Rspamd-Queue-Id: 4QHNkx4xhBz3vZP X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000082c0b305fb70d48d Content-Type: text/plain; charset="UTF-8" On Thu, May 11, 2023, 2:16 PM Yuri wrote: > Warner Losh wrote: > > The branch main has been updated by imp: > > > > URL: > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > Author: Warner Losh > > AuthorDate: 2023-05-11 20:04:12 +0000 > > Commit: Warner Losh > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > stand/efi: Retire i386 support > > > > Remove the i386 ifdefs and files. It never worked. > > > > Sponsored by: Netflix > > Reviewed by: manu, tsoome, kevans > > Differential Revision: https://reviews.freebsd.org/D40012 > > As this question seems to be asked a lot on the forums, does this mean > we will never support the 32bit efi booting 64bit OS? > Yes. It means we've given up on that. Such environments are rare these days, as far as I know, so unless someone shows up with something that works perfectly with a qemu testing recipe that we can roll it into out test bed. Plus some kind of info on real hardware that does this that's popular enough to justify inclusion. Warner > --00000000000082c0b305fb70d48d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, May 11, 2023, 2:16 PM Yuri <yuri@aetern.org> wrote:

Warner Losh wrote:
> The branch main has been updated by imp:
>
> URL: https://cgit.FreeBSD.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacb= d2abdb40e0
>
> commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> Author:=C2=A0 =C2=A0 =C2=A0Warner Losh <imp@FreeBSD.org>
> AuthorDate: 2023-05-11 20:04:12 +0000
> Commit:=C2=A0 =C2=A0 =C2=A0Warner Losh <imp@FreeBSD.org>
> CommitDate: 2023-05-11 20:06:03 +0000
>
>=C2=A0 =C2=A0 =C2=A0stand/efi: Retire i386 support
>=C2=A0 =C2=A0 =C2=A0
>=C2=A0 =C2=A0 =C2=A0Remove the i386 ifdefs and files. It never worked.<= br> >=C2=A0 =C2=A0 =C2=A0
>=C2=A0 =C2=A0 =C2=A0Sponsored by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0Netflix
>=C2=A0 =C2=A0 =C2=A0Reviewed by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 manu, tsoome, kevans
>=C2=A0 =C2=A0 =C2=A0Differential Revision:=C2=A0 ht= tps://reviews.freebsd.org/D40012

As this question seems to be asked a lot on the forums, does this mean
we will never support the 32bit efi booting 64bit OS?

Yes. It means we'v= e given up on that. Such environments are rare these days, as far as I know= , so unless someone shows up with something that works perfectly with a qem= u testing recipe that we can roll it into out test bed. Plus some kind of i= nfo on real hardware that does this that's popular enough to justify in= clusion.=C2=A0

Warner

--00000000000082c0b305fb70d48d-- From nobody Thu May 11 20:49:56 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 4QHPCz10rlz4B18g for ; Thu, 11 May 2023 20:50:07 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHPCy2qzxz40P2; Thu, 11 May 2023 20:50:05 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 34BKnu8q060305; Thu, 11 May 2023 13:49:56 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 34BKnuJK060304; Thu, 11 May 2023 13:49:56 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202305112049.34BKnuJK060304@gndrsh.dnsmgr.net> Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support In-Reply-To: To: Warner Losh Date: Thu, 11 May 2023 13:49:56 -0700 (PDT) CC: Yuri , Warner Losh , FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] 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 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4QHPCy2qzxz40P2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On Thu, May 11, 2023, 2:16 PM Yuri wrote: > > > Warner Losh wrote: > > > The branch main has been updated by imp: > > > > > > URL: > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > Author: Warner Losh > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > Commit: Warner Losh > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > stand/efi: Retire i386 support > > > > > > Remove the i386 ifdefs and files. It never worked. > > > > > > Sponsored by: Netflix > > > Reviewed by: manu, tsoome, kevans > > > Differential Revision: https://reviews.freebsd.org/D40012 > > > > As this question seems to be asked a lot on the forums, does this mean > > we will never support the 32bit efi booting 64bit OS? > > > > Yes. It means we've given up on that. Such environments are rare these > days, as far as I know, so unless someone shows up with something that > works perfectly with a qemu testing recipe that we can roll it into out > test bed. Plus some kind of info on real hardware that does this that's > popular enough to justify inclusion. I have only ever seen 1 implementation of x86 32bit efi, and it was such a pile of turds I just scrapped the machine. > Warner -- Rod Grimes rgrimes@freebsd.org From nobody Thu May 11 21:04:33 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 4QHPXt06Crz4B1nF for ; Thu, 11 May 2023 21:04:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHPXs6mh6z42Z7 for ; Thu, 11 May 2023 21:04:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-50bc075d6b2so16820367a12.0 for ; Thu, 11 May 2023 14:04:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683839084; x=1686431084; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+t0p4QSgVIuiETfDZFBcn1fIZgEwTpZvJ3nrbtuY+PM=; b=0EnAKT3FghH3rxC8Lo4WM8AI9iIDYNQdm37vQAGLn4piPBde9TFSoT2Bl8QBi0k2tZ kB17iVnea1vT5Va2vj9LoH14dTfWGfwR4q/uVtOD0SsjY2uVUfR8vIfW4JCf86Q0wQKZ ccRXWQWj4wLwMJhlRm5K41gJan7jyffvaoa4NZamMytDAcMtB8CQpO+Ngry5WVTdSIvx +nJpf2FljuVB0A9QF4ulAurIM4lvsxBi46NTE40lQqSzX3HxIhyg3AlZQp8BIwr95Pg4 JFE4cKl702jW6Oio25JzF8qwbZO2HcrPEI4TCmyVVdlgXBR62M9iSQqNErOESbU6TfIs FVew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683839084; x=1686431084; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+t0p4QSgVIuiETfDZFBcn1fIZgEwTpZvJ3nrbtuY+PM=; b=AfJE3KwTI2dgXj9/2+5HTsZUOWBD1lANpiV/ELWAE825pFeQeYdnEX02Cahd383dXa /bYhataohZpp8oy8qvO6qdsZUdqza9h1/SDD5Zef0WMIh8am8lXqCV5nYRxbD1HF0SwD 3SsyDGAeckj/oDMIAgOPpSmkLAHIP6apE3+7eAHLqmAA/xZBfixrLFE1SQCZUmpACDap cuNPsbtYt742lyyybs3ev5ixAIle8TLqaGRcomR3cXLUrmMkrKeWvU9IVfh2gSCRtn9x /y0zUx9JZ8st6pTybfX7VnnZOrTdeswGA3S2cPQx+YkUhbs0ppRplc/cW/Ebd7h/jYcv nweg== X-Gm-Message-State: AC+VfDzvIPdcri3fsE+R3e3lA5S0+hlXJqaNje0cujZyoMVJQZLEkUkt 2irE7fd971saHb84Ea4t/k0SUgcKu4AOlCY9Eg/93A== X-Google-Smtp-Source: ACHHUZ5vbiC1AfNB+Hx64gYTutZQEHB1lyyp+oPuBKrreGnw1/AtbXY+PK7X8rXfoJKBm5zgL1AFgNRm+BgB5XGhRyI= X-Received: by 2002:a17:907:96a0:b0:96a:1022:eca0 with SMTP id hd32-20020a17090796a000b0096a1022eca0mr9133607ejc.23.1683839084541; Thu, 11 May 2023 14:04:44 -0700 (PDT) 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 References: <202305112049.34BKnuJK060304@gndrsh.dnsmgr.net> In-Reply-To: <202305112049.34BKnuJK060304@gndrsh.dnsmgr.net> From: Warner Losh Date: Thu, 11 May 2023 15:04:33 -0600 Message-ID: Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support To: "Rodney W. Grimes" Cc: Yuri , Warner Losh , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000007e4a8105fb7156c8" X-Rspamd-Queue-Id: 4QHPXs6mh6z42Z7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000007e4a8105fb7156c8 Content-Type: text/plain; charset="UTF-8" On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > On Thu, May 11, 2023, 2:16 PM Yuri wrote: > > > > > Warner Losh wrote: > > > > The branch main has been updated by imp: > > > > > > > > URL: > > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > Author: Warner Losh > > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > > Commit: Warner Losh > > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > > > stand/efi: Retire i386 support > > > > > > > > Remove the i386 ifdefs and files. It never worked. > > > > > > > > Sponsored by: Netflix > > > > Reviewed by: manu, tsoome, kevans > > > > Differential Revision: https://reviews.freebsd.org/D40012 > > > > > > As this question seems to be asked a lot on the forums, does this mean > > > we will never support the 32bit efi booting 64bit OS? > > > > > > > Yes. It means we've given up on that. Such environments are rare these > > days, as far as I know, so unless someone shows up with something that > > works perfectly with a qemu testing recipe that we can roll it into out > > test bed. Plus some kind of info on real hardware that does this that's > > popular enough to justify inclusion. > > I have only ever seen 1 implementation of x86 32bit efi, and it was > such a pile of turds I just scrapped the machine. > That was my experience as well, so I biased my action towards just removing it. If it turns out my experience was somehow atypical and these are popular and very much robust, I'm open to learning about it. Warner > Warner > > -- > Rod Grimes > rgrimes@freebsd.org > --0000000000007e4a8105fb7156c8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net= > wrote:

> On Thu, May 11= , 2023, 2:16 PM Yuri <yuri@aetern.org> wrote:
>
> > Warner Losh wrote:
> > > The branch main has been updated by imp:
> > >
> > > URL:
> > https://cgit.FreeBSD.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacb= d2abdb40e0
> > >
> > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0
> > > Author:=C2=A0 =C2=A0 =C2=A0Warner Losh <imp@FreeBSD.org&g= t;
> > > AuthorDate: 2023-05-11 20:04:12 +0000
> > > Commit:=C2=A0 =C2=A0 =C2=A0Warner Losh <imp@FreeBSD.org&g= t;
> > > CommitDate: 2023-05-11 20:06:03 +0000
> > >
> > >=C2=A0 =C2=A0 =C2=A0stand/efi: Retire i386 support
> > >
> > >=C2=A0 =C2=A0 =C2=A0Remove the i386 ifdefs and files. It neve= r worked.
> > >
> > >=C2=A0 =C2=A0 =C2=A0Sponsored by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0Netflix
> > >=C2=A0 =C2=A0 =C2=A0Reviewed by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 manu, tsoome, kevans
> > >=C2=A0 =C2=A0 =C2=A0Differential Revision:=C2=A0 https://reviews.freebsd.org/D40012
> >
> > As this question seems to be asked a lot on the forums, does this= mean
> > we will never support the 32bit efi booting 64bit OS?
> >
>
> Yes. It means we've given up on that. Such environments are rare t= hese
> days, as far as I know, so unless someone shows up with something that=
> works perfectly with a qemu testing recipe that we can roll it into ou= t
> test bed. Plus some kind of info on real hardware that does this that&= #39;s
> popular enough to justify inclusion.

I have only ever seen 1 implementation of x86 32bit efi, and it was
such a pile of turds I just scrapped the machine.

That was my experience as = well, so I biased my action towards just removing it. If it turns out my ex= perience was somehow atypical and these are popular and very much robust, I= 'm open to learning about it.

Warner=C2=A0

<= div class=3D"gmail_quote">

> Warner

--
Rod Grimes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rgrimes@freebsd.org

--0000000000007e4a8105fb7156c8-- From nobody Thu May 11 21:08:30 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 4QHPdJ4cK3z4B272 for ; Thu, 11 May 2023 21:08:36 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHPdJ1r7Bz44H5 for ; Thu, 11 May 2023 21:08:36 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=nNfkkhoB; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="i nDY7ev"; 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 compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id D116832001FC for ; Thu, 11 May 2023 17:08:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 11 May 2023 17:08:34 -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= 1683839314; x=1683925714; bh=FQ2nMPMnhZwLedR33NPbvK09LsC/WVqo/oy hsYiOzks=; b=nNfkkhoBeWiZ7F3Hh7QtlsaEbIXG+foHNHxwUH3vcMwhmShBHTD QqS+2bVk5q0TCp0kNo+YugV81RzmIgyPFgc5jYwt9gzx88e35Z3MbYNgStG65jXv 52+hkcNLMcsOeUtRRckqDed/xgFluUXc3iq26S6sVKZdYQwrNUZ9M61bYXieJHzE Yhb9Zulno9/JPdAfBoG5E9MLSwNGTjUohfsKGBtFF9WlcVGtge1/2Sp+lk12IQWU IniTjLNJaW4tPzcaxgsVKXUCAgMVqZiRkQorcqnO/ZXeUzZfmuDjNDskAixvmWDg 4IKOatfu/Lt6peTbaTLD/FoXas+JU4phF9g== 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=fm3; t=1683839314; x= 1683925714; bh=FQ2nMPMnhZwLedR33NPbvK09LsC/WVqo/oyhsYiOzks=; b=i nDY7evbzfqxkXMm+MdWz0TjcM53dWEPbPZVG9nTBkaOPVeyaC7pWM1goVcuHbQmv bW/DA0Q0NXuEc/Ttwuqwj1tGg6qJCcVKZ4Qbp3hD+CHWJ798f1f4Yx74WyoBuc2+ DtvLJAG2Hi7bZ1T2mpArtGgA+SzPpWE1hIJ/R9n0UTGh7zdcPHiDFhKNsQm3spBz OcWI349msIbXiX1BQ+XaYbSjoU7x71WqsacWNwyTZO2QTMgc34c5hUgWZzsPxOd2 2PRbgJqpSxBdgo5NXujy2ah2Hk8IkOpiP7cJ8LQZ+28Ds1lwnhrA61wYcGu+cpkB l2nNxkUDkrQSd65b7r6rw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeegkedgudehlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttdefjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheq necuggftrfgrthhtvghrnhepieevgfeikeejtefgteeiffegudetheehhfduueefhfejhe egffetveelffffgfegnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihurhhisegrvghtvg hrnhdrohhrgh X-ME-Proxy:

Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 11 May 2023 17:08:33 -0400 (EDT) Message-ID: Date: Thu, 11 May 2023 23:08:30 +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: git: c16e08e5f324 - main - stand/efi: Retire i386 support Content-Language: en-US To: current@freebsd.org References: <202305112049.34BKnuJK060304@gndrsh.dnsmgr.net> From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4QHPdJ1r7Bz44H5 X-Spamd-Bar: / X-Spamd-Result: default: False [-0.40 / 15.00]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-ThisMailContainsUnwantedMimeParts: N Warner Losh wrote: > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes > > > wrote: > > > On Thu, May 11, 2023, 2:16 PM Yuri > wrote: > > > > > Warner Losh wrote: > > > > The branch main has been updated by imp: > > > > > > > > URL: > > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > Author: Warner Losh > > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > > Commit: Warner Losh > > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > > > stand/efi: Retire i386 support > > > > > > > > Remove the i386 ifdefs and files. It never worked. > > > > > > > > Sponsored by: Netflix > > > > Reviewed by: manu, tsoome, kevans > > > > Differential Revision: https://reviews.freebsd.org/D40012 > > > > > > > As this question seems to be asked a lot on the forums, does > this mean > > > we will never support the 32bit efi booting 64bit OS? > > > > > > > Yes. It means we've given up on that. Such environments are rare these > > days, as far as I know, so unless someone shows up with something that > > works perfectly with a qemu testing recipe that we can roll it > into out > > test bed. Plus some kind of info on real hardware that does this > that's > > popular enough to justify inclusion. > > I have only ever seen 1 implementation of x86 32bit efi, and it was > such a pile of turds I just scrapped the machine. > > > That was my experience as well, so I biased my action towards just > removing it. If it turns out my experience was somehow atypical and > these are popular and very much robust, I'm open to learning about it. I just noticed that it was asked several times in the last few months trying to use FreeBSD on not-so-modern and rather exotic hardware; I don't think we really need that support, but I simply wasn't aware of efi32 status before this commit, hence I asked :) From nobody Thu May 11 21:11:51 2023 X-Original-To: freebsd-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 4QHPjJ0ppVz4B2LC for ; Thu, 11 May 2023 21:12:04 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHPjH0mSRz45TB for ; Thu, 11 May 2023 21:12:03 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=CiqrV1qA; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::735 as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x735.google.com with SMTP id af79cd13be357-74e4f839ae4so453661985a.0 for ; Thu, 11 May 2023 14:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683839522; x=1686431522; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UFJd/9Qkj7nrXxyaaeGaP3qoj8FLW0T1Yj/0Og3fIgM=; b=CiqrV1qANvJeZs0a80hnQ+7Vez3ohTNB2QBtJIeROBhlemG0JBWVVfR34MObsJjQdt ut4/K5vpv21BHyFJl8/D2Dokhh3d3Ri/k7m4mvBpW57FcU2Ff5Djz8vpSILMRhzaIwfH SKwBKJ7nS2EeWSd4xwN+kSGEBPWM9uAyDXDeb9TQmesKQRzoOCgWQsIa+HlfOZFmDtp3 QVHqBJ97Wyp8VGnO52gZK/bT4hNzGqzO/33WwTK006RbjRxn+jdRlRV8H1xCJ/ynDWAp fGHq+v4Gt5khzKtgYfYfYDHbttcCr6MMa44VgRM19/p38O5rVSIWcfCP4iHnM9ur7RA3 H5gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683839522; x=1686431522; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UFJd/9Qkj7nrXxyaaeGaP3qoj8FLW0T1Yj/0Og3fIgM=; b=kkqdsbBdZKV15z/IYLQff7uptuT1TQ6A//1kx/6BLeiPE5Tp7JeRSmppieYESt7P7P w6rtnCRj97BK1BE61XTaz2VnNj3jsBZCTI6gHik4gCVyZ8FNBrPXqjHrxE+oVQWcgTGo MyuzNH4eNiUBaAL+1d/GkM5B5G5EY8PMWmavZc520ZjY9CdHMDR48gpnZ03rSfCETFSp daJQv8lnjTXG3RbaGO5ommk87EuNegKHtpKrp9ID87NY6bUjz7xUyI63a5oh7id5eEln uCgE5fwpyAMv+tLDu3ZjZJ29FepeTMebCy256nyQWeJvg25ZeZ0IUGd4fM38Ojnzyxz6 ccBg== X-Gm-Message-State: AC+VfDxoB9/pbUvtne6JzMOdoCqP1hVGEKMgrTufsOnLvysVONCtsVxE Nk7tDD6QOwtGycyh39yvCBfIWmuej3UJyOJcssM98KDrH9baNg== X-Google-Smtp-Source: ACHHUZ5jnejTgnHxfjPg/6RA8I5PioBlfvHIReJJWWfqOeNzeCfVEBUQHBawHoOJaoXH0k5zXftcKHAmcBzndiwPZUM= X-Received: by 2002:ad4:5f8e:0:b0:616:5460:aafd with SMTP id jp14-20020ad45f8e000000b006165460aafdmr34872384qvb.3.1683839521764; Thu, 11 May 2023 14:12:01 -0700 (PDT) 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 From: Oleg Lelchuk Date: Thu, 11 May 2023 17:11:51 -0400 Message-ID: Subject: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008dbb3c05fb717006" X-Spamd-Result: default: False [-2.89 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.89)[-0.890]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::735:from]; BLOCKLISTDE_FAIL(0.00)[2607:f8b0:4864:20::735:server fail]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHPjH0mSRz45TB X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000008dbb3c05fb717006 Content-Type: text/plain; charset="UTF-8" Guys, there is something that I find puzzling. Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Is there something quirky about this particular motherboard that forces the FreeBSD EFI loader to display the old style ASCII orb logo in its boot menu? Please explain to me the cause of this problem and if possible, give me a solution to it. --0000000000008dbb3c05fb717006 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Guys, there is something that I find puzzling. Why doesn&#= 39;t the EFI boot loader want to display the graphical orb logo in its boot= menu on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to display t= he old style ASCII orb logo in its boot menu? Please explain to me the caus= e of this problem and if possible, give me a solution to it.

--0000000000008dbb3c05fb717006-- From nobody Thu May 11 21:20:47 2023 X-Original-To: freebsd-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 4QHPvh1NNKz4B2vG for ; Thu, 11 May 2023 21:21:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztbu10011701.me.com (pv50p00im-ztbu10011701.me.com [17.58.6.53]) (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 4QHPvg60bBz470f for ; Thu, 11 May 2023 21:21:03 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1683840060; bh=BLiyMUdfnG+TjecCKqyn0oZ+Ci7pjl6pbq9m5t3HWJo=; h=Content-Type:Mime-Version:Subject:From:Date:Message-Id:To; b=0gnozizM7nJOvvvByoIjRlGNOzwb9qhNoq44JxZZlNuHYy+zsmaKTudPD83R8Mk1J u7HzRfokOw5FOa8WlBXemZ7a3DQnc5B+n8jPO19UuUF+Q75sSEStXYtqNyfKm4EKRt fw5NKeSqR0nXYJhUyqupql027KHKqSeB6RS9OUGTdvqAXaVer+jcDt/kcQwX5gO9LI pMsRQhSDUXBOPIzIBw4u81349pXegaEM/g8gLtOSWI3JmGdsArBsw/8dsqDdhxLO+G P76epJybIRX5pjar/BGYnOv4pn5yoh0lA/BcRqbfE5WMMy3dpi9U19zswP8D/Pz61D ch88CFTODeeEw== Received: from smtpclient.apple (pv50p00im-dlb-asmtp-mailmevip.me.com [17.56.9.10]) by pv50p00im-ztbu10011701.me.com (Postfix) with ESMTPSA id 8887374031C; Thu, 11 May 2023 21:20:59 +0000 (UTC) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 $3731.500.231$) Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? From: Toomas Soome In-Reply-To: Date: Fri, 12 May 2023 00:20:47 +0300 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> References: To: Oleg Lelchuk X-Mailer: Apple Mail (2.3731.500.231) X-Proofpoint-ORIG-GUID: 6RfA6_0ql-wSJDoRiOjjhW-86BGMWaR_ X-Proofpoint-GUID: 6RfA6_0ql-wSJDoRiOjjhW-86BGMWaR_ X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.517,18.0.883,17.11.64.514.0000000_definitions?= =?UTF-8?Q?=3D2022-06-21=5F08:2022-06-21=5F01,2022-06-21=5F08,2022-02-23?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 phishscore=0 mlxscore=0 clxscore=1011 mlxlogscore=999 adultscore=0 suspectscore=0 malwarescore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2305110181 X-Rspamd-Queue-Id: 4QHPvg60bBz470f X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: >=20 > Guys, there is something that I find puzzling. Why doesn't the EFI = boot loader want to display the graphical orb logo in its boot menu on = an Asus Prime 7590-P motherboard? Is there something quirky about this = particular motherboard that forces the FreeBSD EFI loader to display the = old style ASCII orb logo in its boot menu? Please explain to me the = cause of this problem and if possible, give me a solution to it. There can be two reasons. One is that resolution is low and there is no = space to put the image on. Second one is that the screen is forced to = use =E2=80=9Ctext=E2=80=9D mode, which happens when system has = configured to have serial console (redirection). rgds, toomas= From nobody Thu May 11 21:43:22 2023 X-Original-To: freebsd-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 4QHQPh4TdNz4B4Yb for ; Thu, 11 May 2023 21:43:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHQPh0VXwz4DL9 for ; Thu, 11 May 2023 21:43:36 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-50bd2d7ba74so83471740a12.1 for ; Thu, 11 May 2023 14:43:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683841413; x=1686433413; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WdInz2IZYSs7uhop03oexJ7otaWd27U/96c1EP8R2bo=; b=WQFiEdszXyzrEiJIj+rbIlr1ZY+01jhQFBMTGExJOIhUGwkUqXd2N12ckovsaJ1uss vLsIHSGLelwWAIqJyLCI0qAFSmY97k72rEQobb+BfQM2e5HMsL97pReNOSopMHwyHHC+ zC6c55eU1HeVblddHt76HcOSWnHJ1Z2s86UIP+hR88XVC9YAH1GAxek5YgPKmFJXK3W9 G5GeWDQZRUIdXGXewg9OOE7dLlUgt2gXwBu1FV8eD11e+PDAEsEH/r48DpYjrnGHxgXF pauvEwP3AU8+x96DlKhuWsrGIpQ67v4PpILPhyeFCkkVhziPXsU76EoAPq5WiCAkX0HO LjJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683841413; x=1686433413; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WdInz2IZYSs7uhop03oexJ7otaWd27U/96c1EP8R2bo=; b=VtkxhgGafsAVE3aiQRRF9sKfwAM/GnYxRW2//u+zdC3QnSE940XM3AnxgOP8Zlal28 0VsFsytl+hYILDIShvxrMS3DKezpbcWwCHXRG5fftS2b8xtrLhhAmnVIeLiSNIwPL7ZH UvBPVDxkRnhSnD2yZc9Bgput6bu13YlqYq8CmqYMqguORRLtGSHQOtky6J5T5na1Pt3K 3vY23lO2GIFFkSVG2nRVhK6AkSz+/AGi+acS+Ce37p7efLH3u8NZk3DW40/VHmo9leqb 9LgnuHKvtl8laAaAPAn1XBADOeYI9mzxvpeRfrjiwgKWPYKjyJ5z+7fepikY1JWtQ7vW qJSw== X-Gm-Message-State: AC+VfDxug7o4gKpdvWXSDdvcatq46LVgsLycbsI0XQOei2b5IBmuXtpJ pLCvD2g6FHK3Ih+7ytI2UgWirocmphYWjLG520RQYr302vPJlF9V6vk= X-Google-Smtp-Source: ACHHUZ7jCd/XZ2gQSyQwjx5IVILpfBCY9ax7sG9AD4YYr0E4uFWPYwzOLx/r9Jh+cY7lF0tKvPDX2seIfkzBuhYrv+w= X-Received: by 2002:a17:907:3f22:b0:96a:2b4:eb69 with SMTP id hq34-20020a1709073f2200b0096a02b4eb69mr9411445ejc.31.1683841413233; Thu, 11 May 2023 14:43:33 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> In-Reply-To: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> From: Warner Losh Date: Thu, 11 May 2023 15:43:22 -0600 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Oleg Lelchuk , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004b4ff605fb71e1d2" X-Rspamd-Queue-Id: 4QHQPh0VXwz4DL9 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000004b4ff605fb71e1d2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome wrote: > > > > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: > > > > Guys, there is something that I find puzzling. Why doesn't the EFI boot > loader want to display the graphical orb logo in its boot menu on an Asus > Prime 7590-P motherboard? Is there something quirky about this particular > motherboard that forces the FreeBSD EFI loader to display the old style > ASCII orb logo in its boot menu? Please explain to me the cause of this > problem and if possible, give me a solution to it. > > There can be two reasons. One is that resolution is low and there is no > space to put the image on. Second one is that the screen is forced to use > =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured to = have serial > console (redirection). > I think the latter isn't the case (based on earlier email with Oleg), but we can be sure if he provides: (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf) (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut It should show something like: 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/Pc= iRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardwa= re)/VenVt100Plus() if there's redirect or something like 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100) if not. Warner --0000000000004b4ff605fb71e1d2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, May 11, 2023 at 3:21=E2=80=AF= PM Toomas Soome <tsoome@me.com> = wrote:

> On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>
> Guys, there is something that I find puzzling. Why doesn't the EFI= boot loader want to display the graphical orb logo in its boot menu on an = Asus Prime 7590-P motherboard? Is there something quirky about this particu= lar motherboard that forces the FreeBSD EFI loader to display the old style= ASCII orb logo in its boot menu? Please explain to me the cause of this pr= oblem and if possible, give me a solution to it.

There can be two reasons. One is that resolution is low and there is no spa= ce to put the image on. Second one is that the screen is forced to use =E2= =80=9Ctext=E2=80=9D mode, which happens when system has configured to have = serial console (redirection).

I think t= he latter isn't the case (based on earlier email with Oleg), but we can= be sure if he provides:

(1) kenv (to make sure boot_xxx are set,= maybe via a stray loader.conf)

(2) sudo efivar --device-path 8be= 4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should= show something like:

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut=

: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8= 0010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlo= wCtrl(Hardware)/VenVt100Plus()

=C2=A0

if there's redi= rect or something like

8be4df61-93ca-11d2-aa0d-00e= 098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/A= cpiAdr(0x80010100)

if not.

Warner

--0000000000004b4ff605fb71e1d2-- From nobody Thu May 11 21:57:55 2023 X-Original-To: freebsd-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 4QHQkS1PnBz4B5HL for ; Thu, 11 May 2023 21:58:08 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHQkR6sF4z4G6r for ; Thu, 11 May 2023 21:58:07 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x729.google.com with SMTP id af79cd13be357-757742c2e5fso490148285a.1 for ; Thu, 11 May 2023 14:58:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683842286; x=1686434286; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qJtv9sYAa9nPQBQGPUUeEtNTa/Th4INGDNXrj9/wlmg=; b=kuT7FzgcGOjgr0D6/maEG9nVV8wWawQuB1G8/WOP5ZCEiuVKsreZO9W0IGqZf2LdLq /LGbGI8ytN+ztzM81nCUP2XbMNwkD9C21bo4peJrTnfq8gBaMlnj8+G0YXQoWQzWw4n9 F/cFJouylylNw4fArSOlPPYXRoT5d3xoPH0KHXUMICv/tj62JNpfCAFjzRfEkrluP7qd 1bXtS0aCzP80jlM0tVnJWsXkuqYrmE8OXPLk71u86qXh+2ee8GCQsGAUoDOHJ81Vbeyn PN5DRru/+LK/mziY3K7C+dgZhvdq6Kb9V+XPW3qPYYcvxo72DKs5qokRT7IXpSwtD+6j v8Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683842286; x=1686434286; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qJtv9sYAa9nPQBQGPUUeEtNTa/Th4INGDNXrj9/wlmg=; b=HOFp4OPppVvLZuyTYQGKuK13OSDl3SHcOHdK3z6MERW7hCBK5FYvZNuHXgoF9y0Kof HkMyZdr9iqlGDhdi+UjqGFEolNOut1CrGiE0rn6cSGBe+ItyiEitm/a2fckvoWlxrJBZ T6lB5wyaZhkHg81KQitOpVr4O5e2XQ4eKaNrRQiA2WbAsNuYehxutkUfcbaY7cGjWzEx SGjHm7EFQqoiKWnke+0XOmoPCMcM1tmWmA6FTT1P2EFAfoxihrsNr2BIOk4I2qv6OQh6 uQ9c3cg5ODpd7h+GHrn/ZiJDwduHKMcOhh7yYCoGkJk1YXycwupcGg9TcomkaDmWOtRI jtjg== X-Gm-Message-State: AC+VfDyt2KQPtps0Rhb3MbxoXVmvQDCCsAVBWfSy1EwoXW9i9hzIDCFg 22elarxkPFi65XT/QsPKlsAMonFhovy5LEyMuVg= X-Google-Smtp-Source: ACHHUZ5JS+snoInYfUHhABvp77bDDPOGCs9vFk+U2TunpfK2s6Y2ysJyssyKbOxYf35gFNgemMfZT1QGo2c9R8JaygE= X-Received: by 2002:ad4:5f8e:0:b0:5ef:8909:9b43 with SMTP id jp14-20020ad45f8e000000b005ef89099b43mr36648701qvb.36.1683842286474; Thu, 11 May 2023 14:58:06 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 17:57:55 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Warner Losh Cc: Toomas Soome , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000057d84205fb72159c" X-Rspamd-Queue-Id: 4QHQkR6sF4z4G6r X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000057d84205fb72159c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable kenv | grep boot shows me this: acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" boot_verbose=3D"YES" bootenv_autolist=3D"YES" bootenvs[0]=3D"zfs:DESKTOP/poudriere" bootenvs_count=3D"1" bootfile=3D"kernel" cpu_microcode_name=3D"/boot/firmware/ucode.bin" entropy_cache_name=3D"/boot/entropy" entropy_cache_type=3D"boot_entropy_cache" if_re_name=3D"/boot/modules/if_re.ko" kernel_path=3D"/boot/kernel" kernelname=3D"/boot/kernel/kernel" loader_conf_dirs=3D"/boot/loader.conf.d" module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" nextboot_conf=3D"/boot/nextboot.conf" ram_blacklist_name=3D"/boot/blacklist.txt" The efivar command shows me: efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such file or directory On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh wrote: > > > On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome wrot= e: > >> >> >> > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: >> > >> > Guys, there is something that I find puzzling. Why doesn't the EFI boo= t >> loader want to display the graphical orb logo in its boot menu on an Asu= s >> Prime 7590-P motherboard? Is there something quirky about this particula= r >> motherboard that forces the FreeBSD EFI loader to display the old style >> ASCII orb logo in its boot menu? Please explain to me the cause of this >> problem and if possible, give me a solution to it. >> >> There can be two reasons. One is that resolution is low and there is no >> space to put the image on. Second one is that the screen is forced to us= e >> =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured to= have serial >> console (redirection). >> > > I think the latter isn't the case (based on earlier email with Oleg), but > we can be sure if he provides: > (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf) > (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > > It should show something like: > 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > : > PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/= PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus() > > if there's redirect or something like > > 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100) > > if not. > > Warner > --00000000000057d84205fb72159c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

kenv | grep boot shows me this:

=C2=A0
acpi_dsdt_na= me=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"
b= ootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/poudri= ere"
bootenvs_count=3D"1"
bootfile=3D"kernel"= ;
cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entropy_c= ache_name=3D"/boot/entropy"
entropy_cache_type=3D"boot_en= tropy_cache"
if_re_name=3D"/boot/modules/if_re.ko"
ker= nel_path=3D"/boot/kernel"
kernelname=3D"/boot/kernel/kern= el"
loader_conf_dirs=3D"/boot/loader.conf.d"
module_pa= th=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"nextboot_conf=3D"/boot/nextboot.conf"
ram_blacklist_name=3D&q= uot;/boot/blacklist.txt"

The efivar comma= nd shows me:

efivar --device-path 8be4df61-93ca-11= d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0d-00e= 098032b8c-ConOut: No such file or directory

On Thu, May 11, 2023= at 5:43=E2=80=AFPM Warner Losh <imp@b= sdimp.com> wrote:

On Thu, May 11, 2023 at 3:= 21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

> On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>
> Guys, there is something that I find puzzling. Why doesn't the EFI= boot loader want to display the graphical orb logo in its boot menu on an = Asus Prime 7590-P motherboard? Is there something quirky about this particu= lar motherboard that forces the FreeBSD EFI loader to display the old style= ASCII orb logo in its boot menu? Please explain to me the cause of this pr= oblem and if possible, give me a solution to it.

There can be two reasons. One is that resolution is low and there is no spa= ce to put the image on. Second one is that the screen is forced to use =E2= =80=9Ctext=E2=80=9D mode, which happens when system has configured to have = serial console (redirection).

I think t= he latter isn't the case (based on earlier email with Oleg), but we can= be sure if he provides:
(1) kenv (to make sure boot_xxx are set,= maybe via a stray loader.conf)
(2) sudo efivar --device-path 8be= 4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should= show something like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut=
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8= 0010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlo= wCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there's redi= rect or something like

8be4df61-93ca-11d2-aa0d-00e= 098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/A= cpiAdr(0x80010100)

if not.

Warner

--00000000000057d84205fb72159c-- From nobody Thu May 11 22:01:34 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 4QHQpX2RdNz4B5J9 for ; Thu, 11 May 2023 22:01:40 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4QHQpV5KZtz4HB6 for ; Thu, 11 May 2023 22:01:38 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 34BM1YLN064636 for ; Fri, 12 May 2023 07:01:34 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 12 May 2023 07:01:34 +0900 From: Tomoaki AOKI To: current@freebsd.org Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support Message-Id: <20230512070134.eb633400d68cf7c0813d7fde@dec.sakura.ne.jp> In-Reply-To: References: <202305112049.34BKnuJK060304@gndrsh.dnsmgr.net>

Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-1.45 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.97)[-0.965]; NEURAL_HAM_LONG(-0.89)[-0.891]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[current@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; BLOCKLISTDE_FAIL(0.00)[153.125.133.21:server fail,123.1.88.210:server fail]; DMARC_NA(0.00)[sakura.ne.jp]; HAS_ORG_HEADER(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QHQpV5KZtz4HB6 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Thu, 11 May 2023 23:08:30 +0200 Yuri wrote: > Warner Losh wrote: > > > > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes > > > > > wrote: > > > > > On Thu, May 11, 2023, 2:16 PM Yuri > > wrote: > > > > > > > Warner Losh wrote: > > > > > The branch main has been updated by imp: > > > > > > > > > > URL: > > > > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > Author: Warner Losh > > > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > > > Commit: Warner Losh > > > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > > > > > stand/efi: Retire i386 support > > > > > > > > > > Remove the i386 ifdefs and files. It never worked. > > > > > > > > > > Sponsored by: Netflix > > > > > Reviewed by: manu, tsoome, kevans > > > > > Differential Revision: https://reviews.freebsd.org/D40012 > > > > > > > > > > As this question seems to be asked a lot on the forums, does > > this mean > > > > we will never support the 32bit efi booting 64bit OS? > > > > > > > > > > Yes. It means we've given up on that. Such environments are rare these > > > days, as far as I know, so unless someone shows up with something that > > > works perfectly with a qemu testing recipe that we can roll it > > into out > > > test bed. Plus some kind of info on real hardware that does this > > that's > > > popular enough to justify inclusion. > > > > I have only ever seen 1 implementation of x86 32bit efi, and it was > > such a pile of turds I just scrapped the machine. > > > > > > That was my experience as well, so I biased my action towards just > > removing it. If it turns out my experience was somehow atypical and > > these are popular and very much robust, I'm open to learning about it. > > I just noticed that it was asked several times in the last few months > trying to use FreeBSD on not-so-modern and rather exotic hardware; I > don't think we really need that support, but I simply wasn't aware of > efi32 status before this commit, hence I asked :) Just a FYI. A subscriber (not me) tried ASUS EeeBook X205TA (manufactured "2015-04") through Mar.18, 2021 to Apr.13, 2021 without luck on freebsd-usrs-jp ML (in Japanese, started from [1], [2] for April). Atom CPU Z3735F @1.33GHz, 2GB RAM Shipped with "Windows 8.1 with Bing (32bit)" installed. [1] https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-March/001728.html [2] https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-April/001746.html -- Tomoaki AOKI] From nobody Thu May 11 22:05:50 2023 X-Original-To: freebsd-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 4QHQvg1nVGz4B5mH for ; Thu, 11 May 2023 22:06:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10021901.me.com (pv50p00im-ztdg10021901.me.com [17.58.6.55]) (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 4QHQvf5n9Nz4JHY for ; Thu, 11 May 2023 22:06:06 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1683842765; bh=g4Bv4kSxgwoXYfeLxtX7+h5jAmkFxPVWPgghml0Vlvc=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=eeepXn5jN42OGj0ew9XCTYgbZUa8e4ul2wOO4d0UNDG0KJUMqwOUTKGp8OEHt6KFz +zXVb/ZT8Pvn3CR3Jmw3NeZG/woj+76yCvmt4fW7Rc73ySwFO3U2dtojvmqNmjBCoB SUu7a2uc3EbVP/0HtGYUewIRNjmphtDf3OlPUJoRY4dsBBz/+Lzb3VANjUDttftUvb qWdF9XA150pK6IvojLzpQfo2rEXi0Ju1QndsGDUbTQmrMoQfljK5Rp5zVJarYkfrt3 vGHoiKP3ioJ2d/cfUNfTtbocPmJUX4fCuyClX3OVo0LRc72qLPs/eb+v9i5DuKeEQY 01drSsujV4pOQ== Received: from smtpclient.apple (pv50p00im-dlb-asmtp-mailmevip.me.com [17.56.9.10]) by pv50p00im-ztdg10021901.me.com (Postfix) with ESMTPSA id B3A4E8171B; Thu, 11 May 2023 22:06:03 +0000 (UTC) From: Toomas Soome Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_5C324978-9547-4854-8930-1FC6B3F0799A" 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 (Mac OS X Mail 16.0 $3731.500.231$) Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Date: Fri, 12 May 2023 01:05:50 +0300 In-Reply-To: Cc: Warner Losh , freebsd-current@freebsd.org To: Oleg Lelchuk References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> X-Mailer: Apple Mail (2.3731.500.231) X-Proofpoint-GUID: 313S4RsYjF_QjU7gqjATsccvz5V4i2r9 X-Proofpoint-ORIG-GUID: 313S4RsYjF_QjU7gqjATsccvz5V4i2r9 X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.517,18.0.883,17.11.64.514.0000000_definitions?= =?UTF-8?Q?=3D2022-06-21=5F08:2022-06-21=5F01,2022-06-21=5F08,2022-02-23?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 clxscore=1015 mlxlogscore=999 phishscore=0 spamscore=0 malwarescore=0 adultscore=0 bulkscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2305110187 X-Rspamd-Queue-Id: 4QHQvf5n9Nz4JHY X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_5C324978-9547-4854-8930-1FC6B3F0799A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 12. May 2023, at 00:57, Oleg Lelchuk wrote: >=20 > kenv | grep boot shows me this: Can you run kenv | grep screen ? in gfx mode, you should see = screen.depth, screen.height and screen.width rgds, toomas > =20 > acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" > boot_verbose=3D"YES" > bootenv_autolist=3D"YES" > bootenvs[0]=3D"zfs:DESKTOP/poudriere" > bootenvs_count=3D"1" > bootfile=3D"kernel" > cpu_microcode_name=3D"/boot/firmware/ucode.bin" > entropy_cache_name=3D"/boot/entropy" > entropy_cache_type=3D"boot_entropy_cache" > if_re_name=3D"/boot/modules/if_re.ko" > kernel_path=3D"/boot/kernel" > kernelname=3D"/boot/kernel/kernel" > loader_conf_dirs=3D"/boot/loader.conf.d" > module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" > nextboot_conf=3D"/boot/nextboot.conf" > ram_blacklist_name=3D"/boot/blacklist.txt" >=20 > The efivar command shows me: >=20 > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such = file or directory >=20 > On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh > wrote: >>=20 >>=20 >> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome > wrote: >>>=20 >>>=20 >>> > On 12. May 2023, at 00:11, Oleg Lelchuk > wrote: >>> >=20 >>> > Guys, there is something that I find puzzling. Why doesn't the EFI = boot loader want to display the graphical orb logo in its boot menu on = an Asus Prime 7590-P motherboard? Is there something quirky about this = particular motherboard that forces the FreeBSD EFI loader to display the = old style ASCII orb logo in its boot menu? Please explain to me the = cause of this problem and if possible, give me a solution to it. >>>=20 >>> There can be two reasons. One is that resolution is low and there is = no space to put the image on. Second one is that the screen is forced to = use =E2=80=9Ctext=E2=80=9D mode, which happens when system has = configured to have serial console (redirection). >>=20 >> I think the latter isn't the case (based on earlier email with Oleg), = but we can be sure if he provides: >> (1) kenv (to make sure boot_xxx are set, maybe via a stray = loader.conf) >> (2) sudo efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>=20 >> It should show something like: >> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus() >> =20 >> if there's redirect or something like >>=20 >> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100) >>=20 >> if not. >>=20 >> Warner --Apple-Mail=_5C324978-9547-4854-8930-1FC6B3F0799A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 12. = May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

kenv | grep boot shows me = this:

Can you run kenv | = grep screen ? in gfx mode, you should see screen.depth, screen.height = and = screen.width

rgds,

toomas

acpi_dsdt_name=3D"/boot/acpi_dsdt.aml"
boot_verbo= se=3D"YES"
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/poudr= iere"
bootenvs_count=3D"1"
bootfile=3D"kernel"
cpu_microcode_name= =3D"/boot/firmware/ucode.bin"
entropy_cache_name=3D"/boot/entropy"
e= ntropy_cache_type=3D"boot_entropy_cache"
if_re_name=3D"/boot/modules/if= _re.ko"
kernel_path=3D"/boot/kernel"
kernelname=3D"/boot/kernel/kern= el"
loader_conf_dirs=3D"/boot/loader.conf.d"
module_path=3D"/boot/ke= rnel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf=3D"/boot= /nextboot.conf"
ram_blacklist_name=3D"/boot/blacklist.txt"

The efivar command shows = me:

efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such file or = directory

On Thu, = May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> = wrote:

On Thu, May 11, 2023 at 3:21=E2=80=AFPM = Toomas Soome <tsoome@me.com> wrote:

> On 12. May 2023, at = 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>
> Guys, there is = something that I find puzzling. Why doesn't the EFI boot loader want to = display the graphical orb logo in its boot menu on an Asus Prime 7590-P = motherboard? Is there something quirky about this particular motherboard = that forces the FreeBSD EFI loader to display the old style ASCII orb = logo in its boot menu? Please explain to me the cause of this problem = and if possible, give me a solution to it.

There can be two = reasons. One is that resolution is low and there is no space to put the = image on. Second one is that the screen is forced to use =E2=80=9Ctext=E2=80= =9D mode, which happens when system has configured to have serial = console (redirection).

I think the = latter isn't the case (based on earlier email with Oleg), but we can be = sure if he provides:
(1) kenv (to make sure boot_xxx are set, = maybe via a stray loader.conf)
(2) sudo efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It = should show something = like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus()

if there's redirect or = something = like

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut<= br>: = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)

if = not.

Warner

<= /div>

= --Apple-Mail=_5C324978-9547-4854-8930-1FC6B3F0799A-- From nobody Thu May 11 22:09:37 2023 X-Original-To: freebsd-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 4QHQzx6TQPz4B68f for ; Thu, 11 May 2023 22:09:49 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHQzx4SjKz4KVs for ; Thu, 11 May 2023 22:09:49 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x731.google.com with SMTP id af79cd13be357-75131c2997bso3145222485a.1 for ; Thu, 11 May 2023 15:09:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683842988; x=1686434988; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=V2F5KvFWFD7VPOwX0aL5cAPe764ei+4ZXs7W6hZhHWE=; b=Jag/Tl+9aKKYqCLqKOwXG/Y6+mcUK0L9LJNp4ck/X4tD0SivvfPMWnOgqDzJ3lWJoK 4uY7NXHxsLdoFxxqAGqHnnzt4lW2QaZqwPNpgnjwiJV3U2YYz5EVwgW2QUxWsFBVtKKo TAhu1w3NhwyDhQuyheXNX6z0jF4OTf5IJ7tibpEVzqpgBRTwbyHmz1EMma2T9HH1KAhH sgTlHtn6i/JOAGvEulahyuEXxS2uPPBGXpxGh7SQ32uiAIIn/YY2hCuPsOM8+TFqsqmd Ku83+qwUDDLnb8Y20/xvezDNpSCipkG+U95e8xiQnEdHKeOqDA87jEVZLdTTvhMJ7AKC /F7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683842988; x=1686434988; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=V2F5KvFWFD7VPOwX0aL5cAPe764ei+4ZXs7W6hZhHWE=; b=hgB3tzFmhRuZGrFdstpTL2sOa/mTjlokYZ88wzTr7WM2MNXBcgn0Q0dmhDu00QV09P HME90+KgYeHFT7EduOW/NF/YlVcE8VupIx/6Ezy2keTC9omllGrMzHSVbGNdjWrNboL/ PrWxsa6Sq98/D/wc8/rQOm5JlUQXxgevk7YecbR9xVMAvzeGOFdWD8cqQqcyiWiMBEd9 EUc6x6Yqa1r3CUWPFJ9PSmCeTvD0oaxMcxOltju9SxsB28bSi0e9IGuieQKBTTniY2gj HGHLLEVBCY5KHx+uWO+lg9z3JieVKT/O4C4r9lTj/X0cI+ygL2DVqbK5JNfxYl1AeeCO m8wA== X-Gm-Message-State: AC+VfDxaSHdkdw3UWYijudnVuEsUpCZ2th4B3yn4+MIJwP3sEd3PzpKN /WNCa+my0VHr0dR9EXSCht6EHtGEEP06DAOfCck= X-Google-Smtp-Source: ACHHUZ4XP5XqyCvdzXuLvyXZ3NQxODutnnp0MvTWUO2qcIlcMkOGTUrSJ5OsegkVEAgJIkUE7ucpasWN1hTAAhUC0OQ= X-Received: by 2002:a05:6214:5297:b0:61b:58ec:24c8 with SMTP id kj23-20020a056214529700b0061b58ec24c8mr36742295qvb.10.1683842988030; Thu, 11 May 2023 15:09:48 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 18:09:37 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Warner Losh , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000028bfc405fb723fa7" X-Rspamd-Queue-Id: 4QHQzx4SjKz4KVs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000028bfc405fb723fa7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable kenv | grep screen produces this output: screensave_load=3D"NO" screensave_name=3D"green_saver" On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome wrote: > > > On 12. May 2023, at 00:57, Oleg Lelchuk wrote: > > kenv | grep boot shows me this: > > > Can you run kenv | grep screen ? in gfx mode, you should see screen.depth= , > screen.height and screen.width > > rgds, > toomas > > > acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" > boot_verbose=3D"YES" > bootenv_autolist=3D"YES" > bootenvs[0]=3D"zfs:DESKTOP/poudriere" > bootenvs_count=3D"1" > bootfile=3D"kernel" > cpu_microcode_name=3D"/boot/firmware/ucode.bin" > entropy_cache_name=3D"/boot/entropy" > entropy_cache_type=3D"boot_entropy_cache" > if_re_name=3D"/boot/modules/if_re.ko" > kernel_path=3D"/boot/kernel" > kernelname=3D"/boot/kernel/kernel" > loader_conf_dirs=3D"/boot/loader.conf.d" > module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" > nextboot_conf=3D"/boot/nextboot.conf" > ram_blacklist_name=3D"/boot/blacklist.txt" > > The efivar command shows me: > > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such fil= e > or directory > > On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh wrot= e: > >> >> >> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome wro= te: >> >>> >>> >>> > On 12. May 2023, at 00:11, Oleg Lelchuk wrote= : >>> > >>> > Guys, there is something that I find puzzling. Why doesn't the EFI >>> boot loader want to display the graphical orb logo in its boot menu on = an >>> Asus Prime 7590-P motherboard? Is there something quirky about this >>> particular motherboard that forces the FreeBSD EFI loader to display th= e >>> old style ASCII orb logo in its boot menu? Please explain to me the cau= se >>> of this problem and if possible, give me a solution to it. >>> >>> There can be two reasons. One is that resolution is low and there is no >>> space to put the image on. Second one is that the screen is forced to u= se >>> =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured t= o have serial >>> console (redirection). >>> >> >> I think the latter isn't the case (based on earlier email with Oleg), bu= t >> we can be sure if he provides: >> (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf) >> (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOu= t >> >> It should show something like: >> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >> : >> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),= /PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Har= dware)/VenVt100Plus() >> >> if there's redirect or something like >> >> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >> : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100= ) >> >> if not. >> >> Warner >> > > --00000000000028bfc405fb723fa7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

kenv | grep screen produces this output:

screensave_load=3D"NO"
screensave_name=3D"green_saver&q= uot;

On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com>= wrote:

kenv | grep boot shows = me this:

Can you run kenv | gre= p screen ? in gfx mode, you should see screen.depth, screen.height and scre= en.width

rgds,

toomas

=C2=A0
acpi_dsd= t_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"<= br>bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/po= udriere"
bootenvs_count=3D"1"
bootfile=3D"kernel&= quot;
cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entro= py_cache_name=3D"/boot/entropy"
entropy_cache_type=3D"boo= t_entropy_cache"
if_re_name=3D"/boot/modules/if_re.ko"kernel_path=3D"/boot/kernel"
kernelname=3D"/boot/kernel/= kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"
modul= e_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"= ;
nextboot_conf=3D"/boot/nextboot.conf"
ram_blacklist_name= =3D"/boot/blacklist.txt"

The efivar = command shows me:

efivar --device-path 8be4df61-93= ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0= d-00e098032b8c-ConOut: No such file or directory

On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:<= br>

On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome = <tsoome@me.com>= ; wrote:

> On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
&= gt;=C2=A0
> Guys, there is something that I find puzzlin= g. Why doesn't the EFI boot loader want to display the graphical orb lo= go in its boot menu on an Asus Prime 7590-P motherboard? Is there something= quirky about this particular motherboard that forces the FreeBSD EFI loade= r to display the old style ASCII orb logo in its boot menu? Please explain = to me the cause of this problem and if possible, give me a solution to it.<= br>
There can be two reasons. One is that resolution is low and there is= no space to put the image on. Second one is that the screen is forced to u= se =E2=80=9Ctext=E2=80=9D mode, which happens when system has configured to= have serial console (redirection).

I t= hink the latter isn't the case (based on earlier email with Oleg), but = we can be sure if he provides:
(1) kenv (to make sure boot_xxx ar= e set, maybe via a stray loader.conf)
(2) sudo efivar --device-pa= th 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It = should show something like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-= ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiA= dr(0x80010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/U= artFlowCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there'= s redirect or something like

8be4df61-93ca-11d2-aa= 0d-00e098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,= 0x0)/AcpiAdr(0x80010100)

if not.
Warner

<= /div>

--00000000000028bfc405fb723fa7-- From nobody Thu May 11 22:20:45 2023 X-Original-To: freebsd-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 4QHRDs23xwz4B6ky for ; Thu, 11 May 2023 22:21:01 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-ztdg06021701.me.com (mr85p00im-ztdg06021701.me.com [17.58.23.196]) (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 4QHRDr57D6z4MQN for ; Thu, 11 May 2023 22:21:00 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1683843659; bh=oQq+72W0LODiH6sg3+sqd87OLjo8a+tKBCV+MgctZd4=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=CwllpBR0oAYrYQHAekvz2ftC2CIb++RbDRgQsck/Dw6zZGW727BsnI18qKuAnh6bK s8cucqlZ1YeKqXnUQWHf0kjAx1z1sNm3ch2WynnSmimCdIBOIXNEDzUlwp29JxfSEM LgROiphDmahXAnqepQmnKqElosCpPbnzz6jB51Yht+3nd9dujHKDrvSjnPiNvwlKVS xba9tG2SwoVxJqxnMe5rEKOXlUMlLo8VbQNxlEsuPDCYuYJqThEFJ2G2Hd8lG4Ogys tF99R/ybvu+MomSjEv+gstQLE/QshCBckRyNlEwsP8fIuWQiaCmlAYwrvOo6IuND+v Qd0ZjW4BGYmAg== Received: from smtpclient.apple (mr38p00im-dlb-asmtp-mailmevip.me.com [17.57.152.18]) by mr85p00im-ztdg06021701.me.com (Postfix) with ESMTPSA id F10A926337DE; Thu, 11 May 2023 22:20:57 +0000 (UTC) From: Toomas Soome Message-Id: <252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862" 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 (Mac OS X Mail 16.0 $3731.500.231$) Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Date: Fri, 12 May 2023 01:20:45 +0300 In-Reply-To: Cc: Warner Losh , freebsd-current@freebsd.org To: Oleg Lelchuk References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

X-Mailer: Apple Mail (2.3731.500.231) X-Proofpoint-GUID: xXHVZOHYztDPJiMY1eOYFBFBzkEX_1M_ X-Proofpoint-ORIG-GUID: xXHVZOHYztDPJiMY1eOYFBFBzkEX_1M_ X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.425,18.0.816,17.11.62.513.0000000_definitions?= =?UTF-8?Q?=3D2022-01-18=5F01:2022-01-14=5F01,2022-01-18=5F01,2021-12-02?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 clxscore=1015 mlxlogscore=999 spamscore=0 suspectscore=0 malwarescore=0 mlxscore=0 adultscore=0 bulkscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2305110189 X-Rspamd-Queue-Id: 4QHRDr57D6z4MQN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 12. May 2023, at 01:09, Oleg Lelchuk wrote: >=20 > kenv | grep screen produces this output: >=20 > screensave_load=3D"NO" > screensave_name=3D"green_saver" Yep, the screen is considered to be in text mode and only ascii art is = used (see drawer.lua). on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list=E2=80= =99 output anything? if gop does output reasonable data, make sure your loader.efi on ESP is = up to date; if you have no ConOut and ConOutDev variables set (by = firmware), older loader did default to serial port, recent loader does = default to efi,comconsole (see show console on loader prompt).=20 rgds, toomas >=20 > On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome > wrote: >>=20 >>=20 >>> On 12. May 2023, at 00:57, Oleg Lelchuk > wrote: >>>=20 >>> kenv | grep boot shows me this: >>=20 >> Can you run kenv | grep screen ? in gfx mode, you should see = screen.depth, screen.height and screen.width >>=20 >> rgds, >> toomas >>=20 >>> =20 >>> acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" >>> boot_verbose=3D"YES" >>> bootenv_autolist=3D"YES" >>> bootenvs[0]=3D"zfs:DESKTOP/poudriere" >>> bootenvs_count=3D"1" >>> bootfile=3D"kernel" >>> cpu_microcode_name=3D"/boot/firmware/ucode.bin" >>> entropy_cache_name=3D"/boot/entropy" >>> entropy_cache_type=3D"boot_entropy_cache" >>> if_re_name=3D"/boot/modules/if_re.ko" >>> kernel_path=3D"/boot/kernel" >>> kernelname=3D"/boot/kernel/kernel" >>> loader_conf_dirs=3D"/boot/loader.conf.d" >>> = module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" >>> nextboot_conf=3D"/boot/nextboot.conf" >>> ram_blacklist_name=3D"/boot/blacklist.txt" >>>=20 >>> The efivar command shows me: >>>=20 >>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No = such file or directory >>>=20 >>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh > wrote: >>>>=20 >>>>=20 >>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome > wrote: >>>>>=20 >>>>>=20 >>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk > wrote: >>>>> >=20 >>>>> > Guys, there is something that I find puzzling. Why doesn't the = EFI boot loader want to display the graphical orb logo in its boot menu = on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to = display the old style ASCII orb logo in its boot menu? Please explain to = me the cause of this problem and if possible, give me a solution to it. >>>>>=20 >>>>> There can be two reasons. One is that resolution is low and there = is no space to put the image on. Second one is that the screen is forced = to use =E2=80=9Ctext=E2=80=9D mode, which happens when system has = configured to have serial console (redirection). >>>>=20 >>>> I think the latter isn't the case (based on earlier email with = Oleg), but we can be sure if he provides: >>>> (1) kenv (to make sure boot_xxx are set, maybe via a stray = loader.conf) >>>> (2) sudo efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>=20 >>>> It should show something like: >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus() >>>> =20 >>>> if there's redirect or something like >>>>=20 >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100) >>>>=20 >>>> if not. >>>>=20 >>>> Warner >>=20 --Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On 12. = May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

kenv | grep screen produces this = output:

screensave_load=3D"NO"
screensave_name=3D"gr= een_saver"

Yep, = the screen is considered to be in text mode and only ascii art is used = (see drawer.lua).

on loader prompt, does =E2=80=98= gop get=E2=80=99 or =E2=80=98gop list=E2=80=99 output = anything?

if gop does output reasonable data, = make sure your loader.efi on ESP is up to date; if you have no ConOut = and ConOutDev variables set (by firmware), older loader did default to = serial port, recent loader does default to efi,comconsole (see show = console on loader = prompt).

rgds,

toomas

<= br>

On Thu, May = 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.com> = wrote:

On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

kenv | grep boot shows me = this:

Can you run kenv | = grep screen ? in gfx mode, you should see screen.depth, screen.height = and = screen.width

rgds,
toomas

acpi_dsdt_name=3D"/boot/acpi_dsdt.aml"
b= oot_verbose=3D"YES"
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESK= TOP/poudriere"
bootenvs_count=3D"1"
bootfile=3D"kernel"
cpu_micro= code_name=3D"/boot/firmware/ucode.bin"
entropy_cache_name=3D"/boot/entr= opy"
entropy_cache_type=3D"boot_entropy_cache"
if_re_name=3D"/boot/m= odules/if_re.ko"
kernel_path=3D"/boot/kernel"
kernelname=3D"/boot/ke= rnel/kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"
module_path=3D= "/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf= =3D"/boot/nextboot.conf"
ram_blacklist_name=3D"/boot/blacklist.txt"
=

The efivar command shows = me:

efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such file or = directory

On Thu, May 11, = 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:

On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas = Soome <tsoome@me.com> wrote:

> On 12. May 2023, = at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:
>
> Guys, there is something that = I find puzzling. Why doesn't the EFI boot loader want to display the = graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? = Is there something quirky about this particular motherboard that forces = the FreeBSD EFI loader to display the old style ASCII orb logo in its = boot menu? Please explain to me the cause of this problem and if = possible, give me a solution to it.

There can be two reasons. One = is that resolution is low and there is no space to put the image on. = Second one is that the screen is forced to use =E2=80=9Ctext=E2=80=9D = mode, which happens when system has configured to have serial console = (redirection).

I think the latter = isn't the case (based on earlier email with Oleg), but we can be sure if = he provides:
(1) kenv (to make sure boot_xxx are set, maybe = via a stray loader.conf)
(2) sudo efivar --device-path = 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It = should show something = like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/P= ciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hard= ware)/VenVt100Plus()

if there's redirect or = something = like

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut<= br>: = PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)

if = not.

Warner
<= /div>

= --Apple-Mail=_F350D337-8EBA-43F1-BD14-4E4E648D5862-- From nobody Thu May 11 22:49:07 2023 X-Original-To: freebsd-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 4QHRsX1QVvz4B7p8 for ; Thu, 11 May 2023 22:49:20 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHRsW075cz4QSk for ; Thu, 11 May 2023 22:49:19 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=h9ZlfMYP; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::72a as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7577a91cfd6so294500185a.3 for ; Thu, 11 May 2023 15:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683845358; x=1686437358; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lXOGe2t14E/NYGRxAHxUunslrb6eCydXN44Q/9kuZTk=; b=h9ZlfMYPUF0yibkFshmqDAIX9XnWv+VNrwlmMSBYetcO3HkfxIz4eyFTPuyit5JqIM Byyq2gmm5FYj8FMcEfnw/tYP4UebwNeFHaHNXS4geHAlEhv2PleFvLNdZ2ioWUC7BCIm pBDXA1ZWWdYQbbtpw4mgRDYtX+gXH8pOmZS+v8IFPwAm0GUFLNNe9kzslYBKYm3hbIhB KjWHMMXsHW4UadSmXDt8kCDlFOREOWsUWjulOmxQDkbvIHrycmdjJAiNcZcG/O5UwNW5 uJp4V7bvP78aPDeSiZxpEZOa9QRJCn4NvELdGKdRoPj7tR8iScyZWKqJmGUUrCT8sQma H2Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683845358; x=1686437358; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lXOGe2t14E/NYGRxAHxUunslrb6eCydXN44Q/9kuZTk=; b=l2JNm9OK8Xns3lVShCF0C+WZPlDkFpjuAC082e0PHG4rObDXWGAyGrPpNiVuc/XFLH 9BnAY0fIvwdjdx1h+WFOBterfY1OVEQNH2PtZjVQsY70Pw+J9rkUbWy4fCLyqew4f6a3 AAaVAFjH8MSm5zZQUdPzFSzRYQACxK7tihhwrzmeFAFE0gjsAhQ8QOYYQWe4Q0XHblIY 6QP+X9+yoFeuoRJDgo9Xpe1qVLWaBVyjRMVyFw9FwduQjQ2n+6nLytZPjGVGwHCGmQ4u dTkUQ9nTO39bwdCPIF7z13/cSAuz799SJHd2CWnUBzph79hqEqAVPmvm0npqfElR2hlm Sf/Q== X-Gm-Message-State: AC+VfDzyxmVzbBEm8dxxX8HNJImPZWHQmR84B3GJGI3Qs62mUYPsfGg7 fiS+QqXlZ5xK9soGjZfc2Kg52kCI7kPy8WVX84bj5S+X+Tg= X-Google-Smtp-Source: ACHHUZ6149wpW1BjvF0fFyr87VxpOdlTBoSyGu9+mFWcJtH0LX34X8Gnz98NYkvRRkN0RmSyeeaczIpV5nLDCwrNtIY= X-Received: by 2002:a05:6214:1cc4:b0:5e9:2bad:c8fa with SMTP id g4-20020a0562141cc400b005e92badc8famr34480045qvd.33.1683845358171; Thu, 11 May 2023 15:49:18 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

<252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 18:49:07 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Warner Losh , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006e37e905fb72cc8d" X-Spamd-Result: default: False [-2.92 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.922]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72a:from]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_TO(0.00)[me.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHRsW075cz4QSk X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000006e37e905fb72cc8d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Any, by the way, "show console" also shows "efi,comconsole", just like "kenv | grep efi" does. On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk wrote: > My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to > EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added to > the main branch: > https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd= 2abdb40e0 > . > I get this output: > kenv | grep efi > console=3D"efi,comconsole" > efi-version=3D"2.70" > efi_com_port=3D"0" > efi_com_speed=3D"0" > efi_max_resolution=3D"1x1" > entropy_efi_seed=3D"YES" > loader.efi=3D"1" > > And in the attachment, you can see the output from the loader prompt. > > > On Thu, May 11, 2023 at 6:20=E2=80=AFPM Toomas Soome wrot= e: > >> >> >> On 12. May 2023, at 01:09, Oleg Lelchuk wrote: >> >> kenv | grep screen produces this output: >> >> screensave_load=3D"NO" >> screensave_name=3D"green_saver" >> >> >> Yep, the screen is considered to be in text mode and only ascii art is >> used (see drawer.lua). >> >> on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list=E2= =80=99 output anything? >> >> if gop does output reasonable data, make sure your loader.efi on ESP is >> up to date; if you have no ConOut and ConOutDev variables set (by >> firmware), older loader did default to serial port, recent loader does >> default to efi,comconsole (see show console on loader prompt). >> >> rgds, >> toomas >> >> >> On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome wro= te: >> >>> >>> >>> On 12. May 2023, at 00:57, Oleg Lelchuk wrote: >>> >>> kenv | grep boot shows me this: >>> >>> >>> Can you run kenv | grep screen ? in gfx mode, you should see >>> screen.depth, screen.height and screen.width >>> >>> rgds, >>> toomas >>> >>> >>> acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" >>> boot_verbose=3D"YES" >>> bootenv_autolist=3D"YES" >>> bootenvs[0]=3D"zfs:DESKTOP/poudriere" >>> bootenvs_count=3D"1" >>> bootfile=3D"kernel" >>> cpu_microcode_name=3D"/boot/firmware/ucode.bin" >>> entropy_cache_name=3D"/boot/entropy" >>> entropy_cache_type=3D"boot_entropy_cache" >>> if_re_name=3D"/boot/modules/if_re.ko" >>> kernel_path=3D"/boot/kernel" >>> kernelname=3D"/boot/kernel/kernel" >>> loader_conf_dirs=3D"/boot/loader.conf.d" >>> module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays" >>> nextboot_conf=3D"/boot/nextboot.conf" >>> ram_blacklist_name=3D"/boot/blacklist.txt" >>> >>> The efivar command shows me: >>> >>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such >>> file or directory >>> >>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh wr= ote: >>> >>>> >>>> >>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome w= rote: >>>> >>>>> >>>>> >>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>>> wrote: >>>>> > >>>>> > Guys, there is something that I find puzzling. Why doesn't the EFI >>>>> boot loader want to display the graphical orb logo in its boot menu o= n an >>>>> Asus Prime 7590-P motherboard? Is there something quirky about this >>>>> particular motherboard that forces the FreeBSD EFI loader to display = the >>>>> old style ASCII orb logo in its boot menu? Please explain to me the c= ause >>>>> of this problem and if possible, give me a solution to it. >>>>> >>>>> There can be two reasons. One is that resolution is low and there is >>>>> no space to put the image on. Second one is that the screen is forced= to >>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has config= ured to have serial >>>>> console (redirection). >>>>> >>>> >>>> I think the latter isn't the case (based on earlier email with Oleg), >>>> but we can be sure if he provides: >>>> (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.conf= ) >>>> (2) sudo efivar --device-path >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> >>>> It should show something like: >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : >>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100= ),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(H= ardware)/VenVt100Plus() >>>> >>>> if there's redirect or something like >>>> >>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> : >>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100= ) >>>> >>>> if not. >>>> >>>> Warner >>>> >>> >>> >> --0000000000006e37e905fb72cc8d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Any, by the way, "show console" also shows "= ;efi,comconsole", just like "kenv | grep efi" does.

On Thu, M= ay 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

My ESP partition has EF= I/BOOT/BOOTX64.efi . I copied /boot/loader.efi to EFI/BOOT/BOOTX64.efi when= I compiled stand after this commit was added to the main branch:=C2=A0https://cgit.freebsd.org/src/commit/?id= =3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 .=C2=A0=C2=A0=C2=A0
I g= et this output:
kenv | grep efi
console=3D"efi,comconsole= "
efi-version=3D"2.70"
efi_com_port=3D"0"efi_com_speed=3D"0"
efi_max_resolution=3D"1x1"
e= ntropy_efi_seed=3D"YES"
loader.efi=3D"1"
<= br>
And in the attachment, you can see the output from the loader= prompt.

On Thu, May 11, 2023 at 6:20=E2=80=AFPM Tooma= s Soome <tsoome@me.co= m> wrote:

On 12. May 2023, at 01:09= , Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

kenv= | grep screen produces this output:

screensave_load=3D&= quot;NO"
screensave_name=3D"green_saver"
<= /div>

Yep, the screen is considered to be i= n text mode and only ascii art is used (see drawer.lua).

on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop lis= t=E2=80=99 output anything?

if gop does output rea= sonable data, make sure your loader.efi on ESP is up to date; if you have n= o ConOut and ConOutDev variables set (by firmware), older loader did defaul= t to serial port, recent loader does default to efi,comconsole (see show co= nsole on loader prompt).=C2=A0

rgds,
too= mas

On Thu, May 11, 2023 at 6:= 06=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12.= May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

kenv | grep boot shows me this:

Can you run kenv | grep screen ? in gfx mode, = you should see screen.depth, screen.height and screen.width

<= /div>
rgds,
toomas

=C2=A0
acpi_dsdt_name=3D"/boot/acp= i_dsdt.aml"
boot_verbose=3D"YES"
bootenv_autolist=3D&q= uot;YES"
bootenvs[0]=3D"zfs:DESKTOP/poudriere"
bootenv= s_count=3D"1"
bootfile=3D"kernel"
cpu_microcode_n= ame=3D"/boot/firmware/ucode.bin"
entropy_cache_name=3D"/b= oot/entropy"
entropy_cache_type=3D"boot_entropy_cache"if_re_name=3D"/boot/modules/if_re.ko"
kernel_path=3D"/bo= ot/kernel"
kernelname=3D"/boot/kernel/kernel"
loader_c= onf_dirs=3D"/boot/loader.conf.d"
module_path=3D"/boot/ker= nel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
nextboot_conf=3D&qu= ot;/boot/nextboot.conf"
ram_blacklist_name=3D"/boot/blacklist.= txt"

The efivar command shows me:

efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c= -ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No= such file or directory

On Thu, May 11, = 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:

On T= hu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

> On 12. May 2023, at = 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>=C2=A0
= > Guys, there is something that I find puzzling. Why doesn't the EFI= boot loader want to display the graphical orb logo in its boot menu on an = Asus Prime 7590-P motherboard? Is there something quirky about this particu= lar motherboard that forces the FreeBSD EFI loader to display the old style= ASCII orb logo in its boot menu? Please explain to me the cause of this pr= oblem and if possible, give me a solution to it.

There can be two re= asons. One is that resolution is low and there is no space to put the image= on. Second one is that the screen is forced to use =E2=80=9Ctext=E2=80=9D = mode, which happens when system has configured to have serial console (redi= rection).

I think the latter isn't = the case (based on earlier email with Oleg), but we can be sure if he provi= des:
(1) kenv (to make sure boot_xxx are set, maybe via a stray l= oader.conf)
(2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d= -00e098032b8c-ConOut

It should show something like= :
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: PciRoot(= 0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/PciRoot(0x= 0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenV= t100Plus()
=C2=A0
if there's redirect or something li= ke

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
= : PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100)

if not.

Warner

--0000000000006e37e905fb72cc8d-- From nobody Thu May 11 23:14:13 2023 X-Original-To: freebsd-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 4QHSQW1l9Zz4B9SV for ; Thu, 11 May 2023 23:14:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHSQV0kXdz3FSQ for ; Thu, 11 May 2023 23:14:26 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=rO5848Fs; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::730 as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-757741ca000so586624885a.2 for ; Thu, 11 May 2023 16:14:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683846865; x=1686438865; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FKhuAnnYdJmOj2sxYcs18CM/XwH2TshU5Uqq2vW7bbk=; b=rO5848FsYl62SHjLtcGFDa5XLuPPfcfEDDzz0j+cVdgx4YDV2AePfe3C4OCFmkWgzT ItPPD5k7nSeY+lw015gzBYZGx7CRkdENQ4zBGQ64vXevQVo/CDApi8rUt9qrAjpl/EM2 DN31LFHqzLIxYOyenoda7sg7LCYOsZc+sL4xexvaLUp57LIYCt5OmlzfjILoBA5W4ACX 3ysR5XivJRbMFGAZBu7iJiiJ6Fk5Hv7jr88Q3DtVrTqmeEwo6vtfL9v6YNSc4TbyIcSz Zk1u7eLE/vZWaqwemT3TeMnnOks3WoSMLBy+GvG9Zm5FwKP/A3fhFK5MybmMnPAgFCTG 1RuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683846865; x=1686438865; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FKhuAnnYdJmOj2sxYcs18CM/XwH2TshU5Uqq2vW7bbk=; b=DgFT3uVriirzW56zCUHIl2Vi6t8s0LbYj6E/I7MQOEi/yx3OaX+7bP27hGtlCxZi6L gzdzDx/a9lHVNOGR3d86hrZrGAGeqGb6fRZ3TNvnv2+5NMtH8wm3XfqoI1BUIuYNFXuT ZNpN8zdIOiXUNZ5fl5csckcFPlI8JSJLVZZWRkQXw4TXtjd6ZWDA4FzeGHVmheV2NT6/ vg3wJykE1GDJGLoWaFr5HoUUSO8/EFesTiSurSIfGCgBDrevE820EXx8mYq2ElLPtcP0 /FdTowb1M8Z2CYXHwtc0JFNrw2wXjBFfc4+He4O1sQ/N2jsWEXQsSk5FsJ0ga9oatObO zGPw== X-Gm-Message-State: AC+VfDzSTDaxImT/kTOiIkEZJVR/PGFJ24foQ1KYfSr3ingk0WP1Qxu4 Y6PfPzbMrG3bnQshnKBNnSMhH1KU6RVhXvPyEG76B7X5YhY= X-Google-Smtp-Source: ACHHUZ61Ma5DiheawSe9u1/2ZnUvOTdGRfapFI384H7HihJ1ybMRBo5UndSUQiIuIPmESaF+WbJ5XEUYhsgzM7KzRlY= X-Received: by 2002:a05:6214:d82:b0:5b5:9c2:8c29 with SMTP id e2-20020a0562140d8200b005b509c28c29mr30184784qve.12.1683846865007; Thu, 11 May 2023 16:14:25 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

<252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 19:14:13 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Warner Losh , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000003eb70105fb7326c7" X-Spamd-Result: default: False [-2.93 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.926]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::730:from]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_TO(0.00)[me.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHSQV0kXdz3FSQ X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000003eb70105fb7326c7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I meant to say "And", not "Any", at the start of the previous sentence. On Thu, May 11, 2023, 6:49 PM Oleg Lelchuk wrote: > Any, by the way, "show console" also shows "efi,comconsole", just like > "kenv | grep efi" does. > > On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk > wrote: > >> My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to >> EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added t= o >> the main branch: >> https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacb= d2abdb40e0 >> . >> I get this output: >> kenv | grep efi >> console=3D"efi,comconsole" >> efi-version=3D"2.70" >> efi_com_port=3D"0" >> efi_com_speed=3D"0" >> efi_max_resolution=3D"1x1" >> entropy_efi_seed=3D"YES" >> loader.efi=3D"1" >> >> And in the attachment, you can see the output from the loader prompt. >> >> >> On Thu, May 11, 2023 at 6:20=E2=80=AFPM Toomas Soome wro= te: >> >>> >>> >>> On 12. May 2023, at 01:09, Oleg Lelchuk wrote: >>> >>> kenv | grep screen produces this output: >>> >>> screensave_load=3D"NO" >>> screensave_name=3D"green_saver" >>> >>> >>> Yep, the screen is considered to be in text mode and only ascii art is >>> used (see drawer.lua). >>> >>> on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list= =E2=80=99 output anything? >>> >>> if gop does output reasonable data, make sure your loader.efi on ESP is >>> up to date; if you have no ConOut and ConOutDev variables set (by >>> firmware), older loader did default to serial port, recent loader does >>> default to efi,comconsole (see show console on loader prompt). >>> >>> rgds, >>> toomas >>> >>> >>> On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome wr= ote: >>> >>>> >>>> >>>> On 12. May 2023, at 00:57, Oleg Lelchuk wrote: >>>> >>>> kenv | grep boot shows me this: >>>> >>>> >>>> Can you run kenv | grep screen ? in gfx mode, you should see >>>> screen.depth, screen.height and screen.width >>>> >>>> rgds, >>>> toomas >>>> >>>> >>>> acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" >>>> boot_verbose=3D"YES" >>>> bootenv_autolist=3D"YES" >>>> bootenvs[0]=3D"zfs:DESKTOP/poudriere" >>>> bootenvs_count=3D"1" >>>> bootfile=3D"kernel" >>>> cpu_microcode_name=3D"/boot/firmware/ucode.bin" >>>> entropy_cache_name=3D"/boot/entropy" >>>> entropy_cache_type=3D"boot_entropy_cache" >>>> if_re_name=3D"/boot/modules/if_re.ko" >>>> kernel_path=3D"/boot/kernel" >>>> kernelname=3D"/boot/kernel/kernel" >>>> loader_conf_dirs=3D"/boot/loader.conf.d" >>>> module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays= " >>>> nextboot_conf=3D"/boot/nextboot.conf" >>>> ram_blacklist_name=3D"/boot/blacklist.txt" >>>> >>>> The efivar command shows me: >>>> >>>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such >>>> file or directory >>>> >>>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh w= rote: >>>> >>>>> >>>>> >>>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome = wrote: >>>>> >>>>>> >>>>>> >>>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>>>> wrote: >>>>>> > >>>>>> > Guys, there is something that I find puzzling. Why doesn't the EFI >>>>>> boot loader want to display the graphical orb logo in its boot menu = on an >>>>>> Asus Prime 7590-P motherboard? Is there something quirky about this >>>>>> particular motherboard that forces the FreeBSD EFI loader to display= the >>>>>> old style ASCII orb logo in its boot menu? Please explain to me the = cause >>>>>> of this problem and if possible, give me a solution to it. >>>>>> >>>>>> There can be two reasons. One is that resolution is low and there is >>>>>> no space to put the image on. Second one is that the screen is force= d to >>>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has confi= gured to have serial >>>>>> console (redirection). >>>>>> >>>>> >>>>> I think the latter isn't the case (based on earlier email with Oleg), >>>>> but we can be sure if he provides: >>>>> (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.con= f) >>>>> (2) sudo efivar --device-path >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> >>>>> It should show something like: >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> : >>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001010= 0),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(= Hardware)/VenVt100Plus() >>>>> >>>>> if there's redirect or something like >>>>> >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> : >>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001010= 0) >>>>> >>>>> if not. >>>>> >>>>> Warner >>>>> >>>> >>>> >>> --0000000000003eb70105fb7326c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I meant to say "And", not "Any", at t= he start of the previous sentence.

On Thu, May 11, 2023, 6:49 PM Oleg Lelchu= k <oleglelchuk@gmail.com>= ; wrote:

Any, by t= he way, "show console" also shows "efi,comconsole", jus= t like "kenv | grep efi" does.

On Thu, May 11, 2023 at 6:40=E2=80= =AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
My ESP part= ition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to EFI/BOOT/BOOT= X64.efi when I compiled stand after this commit was added to the main branc= h:=C2=A0https://cg= it.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 .=C2=A0=C2=A0=C2=A0
I get this output:
kenv | grep efi
c= onsole=3D"efi,comconsole"
efi-version=3D"2.70"
ef= i_com_port=3D"0"
efi_com_speed=3D"0"
efi_max_reso= lution=3D"1x1"
entropy_efi_seed=3D"YES"
loader.ef= i=3D"1"

And in the attachment, you can s= ee the output from the loader prompt.

On Thu, May 11, 2= 023 at 6:20=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 01:09, Oleg Lelchuk <oleg= lelchuk@gmail.com> wrote:

kenv | grep= screen produces this output:

screensave_load=3D"NO= "
screensave_name=3D"green_saver"

Yep, the screen is considered to be in text = mode and only ascii art is used (see drawer.lua).

= on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list=E2=80= =99 output anything?

if gop does output reasonable= data, make sure your loader.efi on ESP is up to date; if you have no ConOu= t and ConOutDev variables set (by firmware), older loader did default to se= rial port, recent loader does default to efi,comconsole (see show console o= n loader prompt).=C2=A0

rgds,
toomas

On Thu, May 11, 2023 at 6:06=E2= =80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.co= m> wrote:

kenv | grep bo= ot shows me this:

Can you run k= env | grep screen ? in gfx mode, you should see screen.depth, screen.height= and screen.width

rgds,
toomas

=
=C2=A0acpi_dsdt_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"Y= ES"
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:D= ESKTOP/poudriere"
bootenvs_count=3D"1"
bootfile=3D&quo= t;kernel"
cpu_microcode_name=3D"/boot/firmware/ucode.bin"=
entropy_cache_name=3D"/boot/entropy"
entropy_cache_type=3D= "boot_entropy_cache"
if_re_name=3D"/boot/modules/if_re.ko= "
kernel_path=3D"/boot/kernel"
kernelname=3D"/boo= t/kernel/kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"=
module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/over= lays"
nextboot_conf=3D"/boot/nextboot.conf"
ram_blackl= ist_name=3D"/boot/blacklist.txt"

The= efivar command shows me:

efivar --device-path 8be= 4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-= 11d2-aa0d-00e098032b8c-ConOut: No such file or directory
On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bs= dimp.com> wrote:

On Thu, May 11, 2023 at 3:21= =E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

> On 12. May 2023, at 00:11= , Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>=C2= =A0
> Guys, there is something that I find puzzling. Why doesn= 't the EFI boot loader want to display the graphical orb logo in its bo= ot menu on an Asus Prime 7590-P motherboard? Is there something quirky abou= t this particular motherboard that forces the FreeBSD EFI loader to display= the old style ASCII orb logo in its boot menu? Please explain to me the ca= use of this problem and if possible, give me a solution to it.

There= can be two reasons. One is that resolution is low and there is no space to= put the image on. Second one is that the screen is forced to use =E2=80=9C= text=E2=80=9D mode, which happens when system has configured to have serial= console (redirection).

I think the lat= ter isn't the case (based on earlier email with Oleg), but we can be su= re if he provides:
(1) kenv (to make sure boot_xxx are set, maybe= via a stray loader.conf)
(2) sudo efivar --device-path 8be4df61-= 93ca-11d2-aa0d-00e098032b8c-ConOut

It should show = something like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001010= 0),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(= Hardware)/VenVt100Plus()
=C2=A0
if there's redirect o= r something like

8be4df61-93ca-11d2-aa0d-00e098032= b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr= (0x80010100)

if not.

= Warner

--0000000000003eb70105fb7326c7-- From nobody Fri May 12 01:54:20 2023 X-Original-To: freebsd-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 4QHWzD0S5nz4BLCl for ; Fri, 12 May 2023 01:54:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHWzC65KWz3pY7 for ; Fri, 12 May 2023 01:54:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-956ff2399b1so1769711066b.3 for ; Thu, 11 May 2023 18:54:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683856468; x=1686448468; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8NdwP2oAusSqiBd87qouNIbkn+u2L3vqRUFv+7K12hM=; b=Gwo1/qjygUG0DhnaqsY7H7pK7WtteUUJDvl13GaVnJP6crDxDCcrCHXn0i+xuZf4Bg l+uX1H0UI055mEnajspnbYqbN7AJlK9O8xrZaHxT5a26pEXW6wgS420rVWFRSVpRBRMp lIO/zQpFDrzqfLkQOVYXSetpqCnd/SXrtINse7oOdAdOUXP1DAY7gH4JVV/wpYuo/0Q4 bfbLZdKj3QtWJ8PxO+INOpe/4Z9kSMqhDB07E4gRq3+twMjNZL3FW0uc/IBHz4tSEDFH kNo9RT0VILSWMTVoqPG7v1awInJzON7ZOp8vFRmIeppsSN1bShzVrlZHVkP/QYo22NEN Ppiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683856468; x=1686448468; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8NdwP2oAusSqiBd87qouNIbkn+u2L3vqRUFv+7K12hM=; b=C+ysf9DjRFxhmai3XcQG10XV+QoLbGlDfl6iHkuIh/L1mDAP2mrZcILVSUlY8k079w rCsP6coWVSppdCWgKM15WcNHVa2h2neZX00pMbL8nBTNYzny3d2/Q4RAEpG0dFat15/r FowMOoR17Lt/g+yUCHX+zMDb6YvikQe3jj6nmG0jRzbr84c5OY68hcFUdFGXIrlKzrLb 5P5n2nkD/c7oROV95ddZv1qQrX82i0k2PMXzDvNLBAbxOLHnNA8mjLVIAts0uebmn2xS Rk583hZ0dx0UIoB4a/QTSnVR6O85S04Uhm9/AOEX0inPQtrtCJDU98a9zVmQ0XwnnwhJ r/Fw== X-Gm-Message-State: AC+VfDwh9bCm/Jl0kJmT6eRMjEm7ZpfeqYj9b4jxbtfUNHvUk44yB+w3 Ry3nH3OqClyySn9ypCa69dPaoRVDKHiCZnG8fLX18Q== X-Google-Smtp-Source: ACHHUZ7rz5y24lJmmGJFBKkuOMPSUi1tBTVHiTCA5M+gJps1YnP3A9lLqXztX3UGAgJ8uoVwJNo/Vf8OVwcBnFlVtu0= X-Received: by 2002:a17:907:9454:b0:953:291a:6705 with SMTP id dl20-20020a170907945400b00953291a6705mr21458912ejc.17.1683856468446; Thu, 11 May 2023 18:54:28 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

<252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: From: Warner Losh Date: Thu, 11 May 2023 19:54:20 -0600 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Oleg Lelchuk Cc: Toomas Soome , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000a79fa805fb75627d" X-Rspamd-Queue-Id: 4QHWzC65KWz3pY7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000a79fa805fb75627d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No ConOut variable -> we assume the widest possible amount of hardware. which is why you see efi comconsole as the console. Can you send me the output of efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn It should look like: 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn : PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/Ac= pi(PNP0303,0x1) I've been putting-off falling back to ConIn to determine the default console device. I'd like to collect a few more examples before I start. Warner On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lelchuk wrote: > Any, by the way, "show console" also shows "efi,comconsole", just like > "kenv | grep efi" does. > > On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk > wrote: > >> My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to >> EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added t= o >> the main branch: >> https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacb= d2abdb40e0 >> . >> I get this output: >> kenv | grep efi >> console=3D"efi,comconsole" >> efi-version=3D"2.70" >> efi_com_port=3D"0" >> efi_com_speed=3D"0" >> efi_max_resolution=3D"1x1" >> entropy_efi_seed=3D"YES" >> loader.efi=3D"1" >> >> And in the attachment, you can see the output from the loader prompt. >> >> >> On Thu, May 11, 2023 at 6:20=E2=80=AFPM Toomas Soome wro= te: >> >>> >>> >>> On 12. May 2023, at 01:09, Oleg Lelchuk wrote: >>> >>> kenv | grep screen produces this output: >>> >>> screensave_load=3D"NO" >>> screensave_name=3D"green_saver" >>> >>> >>> Yep, the screen is considered to be in text mode and only ascii art is >>> used (see drawer.lua). >>> >>> on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list= =E2=80=99 output anything? >>> >>> if gop does output reasonable data, make sure your loader.efi on ESP is >>> up to date; if you have no ConOut and ConOutDev variables set (by >>> firmware), older loader did default to serial port, recent loader does >>> default to efi,comconsole (see show console on loader prompt). >>> >>> rgds, >>> toomas >>> >>> >>> On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome wr= ote: >>> >>>> >>>> >>>> On 12. May 2023, at 00:57, Oleg Lelchuk wrote: >>>> >>>> kenv | grep boot shows me this: >>>> >>>> >>>> Can you run kenv | grep screen ? in gfx mode, you should see >>>> screen.depth, screen.height and screen.width >>>> >>>> rgds, >>>> toomas >>>> >>>> >>>> acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" >>>> boot_verbose=3D"YES" >>>> bootenv_autolist=3D"YES" >>>> bootenvs[0]=3D"zfs:DESKTOP/poudriere" >>>> bootenvs_count=3D"1" >>>> bootfile=3D"kernel" >>>> cpu_microcode_name=3D"/boot/firmware/ucode.bin" >>>> entropy_cache_name=3D"/boot/entropy" >>>> entropy_cache_type=3D"boot_entropy_cache" >>>> if_re_name=3D"/boot/modules/if_re.ko" >>>> kernel_path=3D"/boot/kernel" >>>> kernelname=3D"/boot/kernel/kernel" >>>> loader_conf_dirs=3D"/boot/loader.conf.d" >>>> module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays= " >>>> nextboot_conf=3D"/boot/nextboot.conf" >>>> ram_blacklist_name=3D"/boot/blacklist.txt" >>>> >>>> The efivar command shows me: >>>> >>>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such >>>> file or directory >>>> >>>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh w= rote: >>>> >>>>> >>>>> >>>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome = wrote: >>>>> >>>>>> >>>>>> >>>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>>>> wrote: >>>>>> > >>>>>> > Guys, there is something that I find puzzling. Why doesn't the EFI >>>>>> boot loader want to display the graphical orb logo in its boot menu = on an >>>>>> Asus Prime 7590-P motherboard? Is there something quirky about this >>>>>> particular motherboard that forces the FreeBSD EFI loader to display= the >>>>>> old style ASCII orb logo in its boot menu? Please explain to me the = cause >>>>>> of this problem and if possible, give me a solution to it. >>>>>> >>>>>> There can be two reasons. One is that resolution is low and there is >>>>>> no space to put the image on. Second one is that the screen is force= d to >>>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has confi= gured to have serial >>>>>> console (redirection). >>>>>> >>>>> >>>>> I think the latter isn't the case (based on earlier email with Oleg), >>>>> but we can be sure if he provides: >>>>> (1) kenv (to make sure boot_xxx are set, maybe via a stray loader.con= f) >>>>> (2) sudo efivar --device-path >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> >>>>> It should show something like: >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> : >>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001010= 0),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(= Hardware)/VenVt100Plus() >>>>> >>>>> if there's redirect or something like >>>>> >>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> : >>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001010= 0) >>>>> >>>>> if not. >>>>> >>>>> Warner >>>>> >>>> >>>> >>> --000000000000a79fa805fb75627d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

No ConOut variable -> we assume the widest possibl= e amount of hardware. which is why you see efi comconsole as the console.

Can you send me the output of

efivar --de= vice-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn

It should look like:

8be4df61-93ca-11d2-aa0d-00e098032b8c-ConI= n
: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,= 0x0)/Acpi(PNP0303,0x1)

I've been putting-off f= alling back to ConIn to determine the default console device. I'd like<= /div>

to collect a few more examples before I start.

Warner

On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lel= chuk <oleglelchuk@gmail.com= > wrote:

Any, by the way, "show console" also shows "efi= ,comconsole", just like "kenv | grep efi" does.

On Thu, May 1= 1, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

My ESP pa= rtition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi to EFI/BOOT/BO= OTX64.efi when I compiled stand after this commit was added to the main bra= nch:=C2=A0https://cgit.freebsd.org/sr= c/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 .=C2=A0=C2=A0= =C2=A0

I get this output:

kenv | grep efi
console=3D"= efi,comconsole"
efi-version=3D"2.70"
efi_com_port=3D&q= uot;0"
efi_com_speed=3D"0"
efi_max_resolution=3D"= 1x1"
entropy_efi_seed=3D"YES"
loader.efi=3D"1&quo= t;

And in the attachment, you can see the output f= rom the loader prompt.

On Thu, May 11, 2023 at 6:20=E2= =80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May = 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

kenv | grep screen produces this output:

scree= nsave_load=3D"NO"
screensave_name=3D"green_saver"

Yep, the screen is cons= idered to be in text mode and only ascii art is used (see drawer.lua).

on loader prompt, does =E2=80=98gop get=E2=80=99 or = =E2=80=98gop list=E2=80=99 output anything?

if gop= does output reasonable data, make sure your loader.efi on ESP is up to dat= e; if you have no ConOut and ConOutDev variables set (by firmware), older l= oader did default to serial port, recent loader does default to efi,comcons= ole (see show console on loader prompt).=C2=A0

rgd= s,
toomas

=
On Thu, Ma= y 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:<= /div>
kenv | grep boot shows me this:=

Can you run kenv | grep screen= ? in gfx mode, you should see screen.depth, screen.height and screen.width=

rgds,
toomas

=C2=A0
acpi_dsdt_name= =3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES"
boo= tenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESKTOP/poudrier= e"
bootenvs_count=3D"1"
bootfile=3D"kernel"<= br>cpu_microcode_name=3D"/boot/firmware/ucode.bin"
entropy_cac= he_name=3D"/boot/entropy"
entropy_cache_type=3D"boot_entr= opy_cache"
if_re_name=3D"/boot/modules/if_re.ko"
kerne= l_path=3D"/boot/kernel"
kernelname=3D"/boot/kernel/kernel= "
loader_conf_dirs=3D"/boot/loader.conf.d"
module_path= =3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays"
n= extboot_conf=3D"/boot/nextboot.conf"
ram_blacklist_name=3D&quo= t;/boot/blacklist.txt"

The efivar command= shows me:

efivar --device-path 8be4df61-93ca-11d2= -aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d2-aa0d-00e09= 8032b8c-ConOut: No such file or directory

<= div class=3D"gmail_quote" style=3D"font-family:Helvetica;font-size:14px;fon= t-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:norm= al;text-align:start;text-indent:0px;text-transform:none;white-space:normal;= word-spacing:0px;text-decoration:none">
On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:<= br>

> On = 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>= =C2=A0
> Guys, there is something that I find puzzling. Why do= esn't the EFI boot loader want to display the graphical orb logo in its= boot menu on an Asus Prime 7590-P motherboard? Is there something quirky a= bout this particular motherboard that forces the FreeBSD EFI loader to disp= lay the old style ASCII orb logo in its boot menu? Please explain to me the= cause of this problem and if possible, give me a solution to it.

Th= ere can be two reasons. One is that resolution is low and there is no space= to put the image on. Second one is that the screen is forced to use =E2=80= =9Ctext=E2=80=9D mode, which happens when system has configured to have ser= ial console (redirection).

I think the = latter isn't the case (based on earlier email with Oleg), but we can be= sure if he provides:
(1) kenv (to make sure boot_xxx are set, ma= ybe via a stray loader.conf)
(2) sudo efivar --device-path 8be4df= 61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should sh= ow something like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x8001= 0100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCt= rl(Hardware)/VenVt100Plus()
=C2=A0
if there's redirec= t or something like

8be4df61-93ca-11d2-aa0d-00e098= 032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/Acpi= Adr(0x80010100)

if not.

Warner

=

--000000000000a79fa805fb75627d-- From nobody Fri May 12 02:21:52 2023 X-Original-To: freebsd-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 4QHXb23bDxz4BMXR for ; Fri, 12 May 2023 02:22:06 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHXb13K5Gz3rn1 for ; Fri, 12 May 2023 02:22:05 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Gm4AskwR; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::f2b as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-61b6101a1b9so42932316d6.3 for ; Thu, 11 May 2023 19:22:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683858123; x=1686450123; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=0HkE9Gyj1sB1OoR3RsUiaeeABQ9RWJGuvwQI7qSH8jA=; b=Gm4AskwR4PtydebP7MrGT3zIGVgH/DrRnaks8S1A48rmDueuDazLGIAvLoSQAsWzi8 Io4UdvQEumEnit8ie/CBrtTK3Hn3jxjory6h0zkUEzJK+Y1KN+nV0ZaDIqdJ7dM7CTPb +QUNwUdGBT8XL7OWO2eL/zLkRJjygAWxltP+ZUnxPCheABeQ5AZYKw0XuPl3YDMEnBSk asybQAHT+AhWourqJP4Z2qliySi3u0ORpEc9uL2UeLR5XzY96Lkhl9VGDIPZla/Y8bOu 1jWO/Br8zFK1pOS102HY31WLm1Trno2rGNEf3kQVyGzbnixHoB6+pSK3wrMPSuiiz+Cq DGKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683858123; x=1686450123; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=0HkE9Gyj1sB1OoR3RsUiaeeABQ9RWJGuvwQI7qSH8jA=; b=e7S1f+fkHcX2bKvWZjUAYC0JT+gkvzJgr6kDmN4lqdVIckwUrmpyl4iaibVgJu9JjM gahLRgkjrFexf2E5yXXmu4smWemzoIfKeQ+0Cd5usFogigFPvpX3vviLBoyk5aMn7M14 nyilDukszCZQYIto4JNfp660h+mgb3o7b2POuhVP+nH6dW5GjeCTNA6pcJx60yfHx0Wr nKkudzB75cXv4hmRZoI3owaVC0hv1VVrAg7HX+lwWV+4zQ+BbALI64TKxLkvlHekEBuL 9dhV+XDLawkBivJF+rJEPa/zjxJlsGiJ3NYaEXkRO07M4ps5maD6SCZp8grmB8W1FCnz OH0Q== X-Gm-Message-State: AC+VfDwfJZuU2ZM47VrBkJPoyYraF+hWFI4Gd4Oj+IgOs9vz4HsFYHLK Lm/AskAgEzLt4tfQwkEOfhVSOGE2z00qGQ5cABCyyEPKSn0= X-Google-Smtp-Source: ACHHUZ7lMNljEeRcYnzlk387x01EkxoTVgKjT9/dznrqWZidAfnpxAizW2UMkoZdQl9Q7CsUk4pa9b/hRLVaqxDfMsg= X-Received: by 2002:a05:6214:cc2:b0:5ed:ddf0:7c2d with SMTP id 2-20020a0562140cc200b005edddf07c2dmr43723817qvx.25.1683858123386; Thu, 11 May 2023 19:22:03 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com>

<252DD208-79A1-4F0A-8F98-B2F56770CD49@me.com> In-Reply-To: From: Oleg Lelchuk Date: Thu, 11 May 2023 22:21:52 -0400 Message-ID: Subject: Fwd: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004bf25305fb75c58c" X-Spamd-Result: default: False [-2.03 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_SHORT(-0.03)[-0.031]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f2b:from]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QHXb13K5Gz3rn1 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000004bf25305fb75c58c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message --------- From: Oleg Lelchuk Date: Thu, May 11, 2023 at 10:19=E2=80=AFPM Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Warner Losh I see this output: efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn : PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0)/US= B(0x2,0x0) On Thu, May 11, 2023 at 9:54=E2=80=AFPM Warner Losh wrote: > No ConOut variable -> we assume the widest possible amount of hardware. > which is why you see efi comconsole as the console. > > Can you send me the output of > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn > > It should look like: > 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn > : > PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)/= Acpi(PNP0303,0x1) > > I've been putting-off falling back to ConIn to determine the default > console device. I'd like > to collect a few more examples before I start. > > Warner > > On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lelchuk > wrote: > >> Any, by the way, "show console" also shows "efi,comconsole", just like >> "kenv | grep efi" does. >> >> On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk >> wrote: >> >>> My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi t= o >>> EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added = to >>> the main branch: >>> https://cgit.freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabac= bd2abdb40e0 >>> . >>> I get this output: >>> kenv | grep efi >>> console=3D"efi,comconsole" >>> efi-version=3D"2.70" >>> efi_com_port=3D"0" >>> efi_com_speed=3D"0" >>> efi_max_resolution=3D"1x1" >>> entropy_efi_seed=3D"YES" >>> loader.efi=3D"1" >>> >>> And in the attachment, you can see the output from the loader prompt. >>> >>> >>> On Thu, May 11, 2023 at 6:20=E2=80=AFPM Toomas Soome wr= ote: >>> >>>> >>>> >>>> On 12. May 2023, at 01:09, Oleg Lelchuk wrote: >>>> >>>> kenv | grep screen produces this output: >>>> >>>> screensave_load=3D"NO" >>>> screensave_name=3D"green_saver" >>>> >>>> >>>> Yep, the screen is considered to be in text mode and only ascii art is >>>> used (see drawer.lua). >>>> >>>> on loader prompt, does =E2=80=98gop get=E2=80=99 or =E2=80=98gop list= =E2=80=99 output anything? >>>> >>>> if gop does output reasonable data, make sure your loader.efi on ESP i= s >>>> up to date; if you have no ConOut and ConOutDev variables set (by >>>> firmware), older loader did default to serial port, recent loader does >>>> default to efi,comconsole (see show console on loader prompt). >>>> >>>> rgds, >>>> toomas >>>> >>>> >>>> On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome w= rote: >>>> >>>>> >>>>> >>>>> On 12. May 2023, at 00:57, Oleg Lelchuk wrote= : >>>>> >>>>> kenv | grep boot shows me this: >>>>> >>>>> >>>>> Can you run kenv | grep screen ? in gfx mode, you should see >>>>> screen.depth, screen.height and screen.width >>>>> >>>>> rgds, >>>>> toomas >>>>> >>>>> >>>>> acpi_dsdt_name=3D"/boot/acpi_dsdt.aml" >>>>> boot_verbose=3D"YES" >>>>> bootenv_autolist=3D"YES" >>>>> bootenvs[0]=3D"zfs:DESKTOP/poudriere" >>>>> bootenvs_count=3D"1" >>>>> bootfile=3D"kernel" >>>>> cpu_microcode_name=3D"/boot/firmware/ucode.bin" >>>>> entropy_cache_name=3D"/boot/entropy" >>>>> entropy_cache_type=3D"boot_entropy_cache" >>>>> if_re_name=3D"/boot/modules/if_re.ko" >>>>> kernel_path=3D"/boot/kernel" >>>>> kernelname=3D"/boot/kernel/kernel" >>>>> loader_conf_dirs=3D"/boot/loader.conf.d" >>>>> module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlay= s" >>>>> nextboot_conf=3D"/boot/nextboot.conf" >>>>> ram_blacklist_name=3D"/boot/blacklist.txt" >>>>> >>>>> The efivar command shows me: >>>>> >>>>> efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>> efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut: No such >>>>> file or directory >>>>> >>>>> On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh = wrote: >>>>> >>>>>> >>>>>> >>>>>> On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas Soome = wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> > On 12. May 2023, at 00:11, Oleg Lelchuk >>>>>>> wrote: >>>>>>> > >>>>>>> > Guys, there is something that I find puzzling. Why doesn't the EF= I >>>>>>> boot loader want to display the graphical orb logo in its boot menu= on an >>>>>>> Asus Prime 7590-P motherboard? Is there something quirky about this >>>>>>> particular motherboard that forces the FreeBSD EFI loader to displa= y the >>>>>>> old style ASCII orb logo in its boot menu? Please explain to me the= cause >>>>>>> of this problem and if possible, give me a solution to it. >>>>>>> >>>>>>> There can be two reasons. One is that resolution is low and there i= s >>>>>>> no space to put the image on. Second one is that the screen is forc= ed to >>>>>>> use =E2=80=9Ctext=E2=80=9D mode, which happens when system has conf= igured to have serial >>>>>>> console (redirection). >>>>>>> >>>>>> >>>>>> I think the latter isn't the case (based on earlier email with Oleg)= , >>>>>> but we can be sure if he provides: >>>>>> (1) kenv (to make sure boot_xxx are set, maybe via a stray >>>>>> loader.conf) >>>>>> (2) sudo efivar --device-path >>>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>>> >>>>>> It should show something like: >>>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>>> : >>>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x800101= 00),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl= (Hardware)/VenVt100Plus() >>>>>> >>>>>> if there's redirect or something like >>>>>> >>>>>> 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut >>>>>> : >>>>>> PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x800101= 00) >>>>>> >>>>>> if not. >>>>>> >>>>>> Warner >>>>>> >>>>> >>>>> >>>> --0000000000004bf25305fb75c58c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ---------
From: Oleg Lelchuk <oleglelchuk@gmail.com&g= t;
Date: Thu, May 11, 2023 at 10:19=E2=80=AFPM
Subject: Re: Wh= y doesn't the EFI boot loader want to display the graphical orb logo in= its boot menu on an Asus Prime 7590-P motherboard?
To: Warner Losh <= imp@bsdimp.com>

<= div dir=3D"ltr">I see this output:

efivar --device-path 8be4df61-93ca-1= 1d2-aa0d-00e098032b8c-ConIn
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x14,0x0= )/USB(0x2,0x0)

On Thu, May 11, 2023 at 9:54=E2=80=AFPM Warner Losh= <imp@bsdimp.com= > wrote:

No ConOut variable -> we assume the widest possible am= ount of hardware. which is why you see efi comconsole as the console.
=

Can you send me the output of
efivar --device= -path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn

I= t should look like:
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn: PciRoot(0x0)/Pci(0x1f,0x0)/Acpi(PNP0303,0x0),/PciRoot(0x0)/Pci(0x1f,0x0)= /Acpi(PNP0303,0x1)

I've been putting-off falli= ng back to ConIn to determine the default console device. I'd like
to collect a few more examples before I start.

Warner

On Thu, May 11, 2023 at 4:49=E2=80=AFPM Oleg Lelchuk= <oleglelchuk= @gmail.com> wrote:
Any, by the way, "show console" also = shows "efi,comconsole", just like "kenv | grep efi" doe= s.

On Thu, May 11, 2023 at 6:40=E2=80=AFPM Oleg Lelchuk <oleglelchuk@gmail.com> wr= ote:
My ESP partition has EFI/BOOT/BOOTX64.efi . I copied /boot/loader.efi= to EFI/BOOT/BOOTX64.efi when I compiled stand after this commit was added = to the main branch:=C2=A0https://cgit= .freebsd.org/src/commit/?id=3Dc16e08e5f324aa119c85e10eaabacbd2abdb40e0 = .=C2=A0=C2=A0=C2=A0
I get this output:
kenv | grep efi
con= sole=3D"efi,comconsole"
efi-version=3D"2.70"
efi_= com_port=3D"0"
efi_com_speed=3D"0"
efi_max_resolu= tion=3D"1x1"
entropy_efi_seed=3D"YES"
loader.efi= =3D"1"

And in the attachment, you can se= e the output from the loader prompt.

On Thu, May 11, 20= 23 at 6:20=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 01:09, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
kenv | grep screen produces this output:

screensave_load=3D"NO"
screensave_name=3D"green_s= aver"

Yep, the s= creen is considered to be in text mode and only ascii art is used (see draw= er.lua).

on loader prompt, does =E2=80=98gop get= =E2=80=99 or =E2=80=98gop list=E2=80=99 output anything?

if gop does output reasonable data, make sure your loader.efi on ESP= is up to date; if you have no ConOut and ConOutDev variables set (by firmw= are), older loader did default to serial port, recent loader does default t= o efi,comconsole (see show console on loader prompt).=C2=A0

<= /div>
rgds,
toomas

On Thu, May 11, 2023 at 6:06=E2=80=AFPM Toomas Soome <tsoome@me.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">

On 12. May 2023, at 00:57, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

kenv | grep boot = shows me this:

Can you run kenv= | grep screen ? in gfx mode, you should see screen.depth, screen.height an= d screen.width

rgds,
toomas

=C2=A0
ac= pi_dsdt_name=3D"/boot/acpi_dsdt.aml"
boot_verbose=3D"YES&= quot;
bootenv_autolist=3D"YES"
bootenvs[0]=3D"zfs:DESK= TOP/poudriere"
bootenvs_count=3D"1"
bootfile=3D"k= ernel"
cpu_microcode_name=3D"/boot/firmware/ucode.bin"entropy_cache_name=3D"/boot/entropy"
entropy_cache_type=3D&qu= ot;boot_entropy_cache"
if_re_name=3D"/boot/modules/if_re.ko&qu= ot;
kernel_path=3D"/boot/kernel"
kernelname=3D"/boot/k= ernel/kernel"
loader_conf_dirs=3D"/boot/loader.conf.d"module_path=3D"/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlay= s"
nextboot_conf=3D"/boot/nextboot.conf"
ram_blacklist= _name=3D"/boot/blacklist.txt"

The ef= ivar command shows me:

efivar --device-path 8be4df= 61-93ca-11d2-aa0d-00e098032b8c-ConOut
efivar: fetching 8be4df61-93ca-11d= 2-aa0d-00e098032b8c-ConOut: No such file or directory

On Thu, May 11, 2023 at 5:43=E2=80=AFPM Warner Losh <imp@bsdimp.com> wro= te:

On Thu, May 11, 2023 at 3:21=E2=80=AFPM Toomas So= ome <tsoome@me.com> wrote:

> On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:<= br>>=C2=A0
> Guys, there is something that I find puz= zling. Why doesn't the EFI boot loader want to display the graphical or= b logo in its boot menu on an Asus Prime 7590-P motherboard? Is there somet= hing quirky about this particular motherboard that forces the FreeBSD EFI l= oader to display the old style ASCII orb logo in its boot menu? Please expl= ain to me the cause of this problem and if possible, give me a solution to = it.

There can be two reasons. One is that resolution is low and ther= e is no space to put the image on. Second one is that the screen is forced = to use =E2=80=9Ctext=E2=80=9D mode, which happens when system has configure= d to have serial console (redirection).

I think the latter isn't the case (based on earlier email with Oleg), = but we can be sure if he provides:
(1) kenv (to make sure boot_xx= x are set, maybe via a stray loader.conf)
(2) sudo efivar --devic= e-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut

It should show something like:
8be4df61-93ca-11d2-aa0d-00e098032= b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/A= cpiAdr(0x80010100),/PciRoot(0x0)/Pci(0x14,0x3)/Serial(0x1)/Uart(115200,8,N,= 1)/UartFlowCtrl(Hardware)/VenVt100Plus()
=C2=A0
if there&= #39;s redirect or something like

8be4df61-93ca-11d= 2-aa0d-00e098032b8c-ConOut
: PciRoot(0x2)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(= 0x0,0x0)/AcpiAdr(0x80010100)

if not.

Warner

--0000000000004bf25305fb75c58c-- From nobody Fri May 12 05:05:57 2023 X-Original-To: freebsd-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 4QHcDC6Hslz4BWHL for ; Fri, 12 May 2023 05:06:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHcDC2mj7z47kB for ; Fri, 12 May 2023 05:06:03 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1683867961; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zCSOtNiCbHf4bRE+VQq1OD/dxJOGTadQhfXp3Kx9A+4=; b=nbheXUhVFCy0e4cplnP3URurASIYbSdNfQHoBAqrW6pkJ87rSoTNVzoYX/hLTY5JpSb7MX hZ8wEanRY6eShB3efmjjS/bq3CPX26tFKGC+R8KNMwvePqryLiXrfBj4AoiQXYrjf+4zUH TlBxoV2v/TjizGHbN8EgcfwykB36/6M= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 3a88c3fb (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 12 May 2023 05:05:58 +0000 (UTC) Date: Fri, 12 May 2023 07:05:57 +0200 From: Emmanuel Vadot To: Toomas Soome Cc: Oleg Lelchuk , freebsd-current@freebsd.org Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Message-Id: <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> In-Reply-To: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QHcDC2mj7z47kB X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, 12 May 2023 00:20:47 +0300 Toomas Soome wrote: >=20 >=20 > > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: > >=20 > > Guys, there is something that I find puzzling. Why doesn't the EFI boot= loader want to display the graphical orb logo in its boot menu on an Asus = Prime 7590-P motherboard? Is there something quirky about this particular m= otherboard that forces the FreeBSD EFI loader to display the old style ASCI= I orb logo in its boot menu? Please explain to me the cause of this problem= and if possible, give me a solution to it. >=20 > There can be two reasons. One is that resolution is low and there is no s= pace to put the image on. Second one is that the screen is forced to use ?t= ext? mode, which happens when system has configured to have serial console = (redirection). >=20 > rgds, > toomas There is a third reason : you have multiple screens and EFI firmware output on all of them. Never took the time to dig into this one. --=20 Emmanuel Vadot From nobody Fri May 12 10:41:07 2023 X-Original-To: freebsd-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 4QHlg36Y6Wz4Br03 for ; Fri, 12 May 2023 10:41:19 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHlg34jjgz3Q9w for ; Fri, 12 May 2023 10:41:19 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qv1-xf2f.google.com with SMTP id 6a1803df08f44-61b5a6865dfso77528076d6.3 for ; Fri, 12 May 2023 03:41:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683888079; x=1686480079; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qkDIKuoRmenYK20Opy/CzCxLqZjJtr8Z2dODVW7BVV4=; b=bK224qlR0s6C7TS9wLGh1QEm6YmsI8v/eRNjmZN1YifE8irVT6y2yQvPXOyH6sRhhJ hWhpUwYJJkOVnjMOR6kseHDLnn8FWsL/fGZWEkfWDcdaQXdZQ+kglp2gGQaV6Eku2ilY HwKlzjXlq0rd0e+PrQnOq0wy44I3g28udkK43RRNOVdBAk0WxovQSH84Y2zuFSWs/rbs fnKRtIcWOx6P3nT4O8pheS+PhzcpWDaxo0rpMI2s4ChUJuItUvhIHlsvuVW40iJY9BBA FWv8+kM+48zVndgc8AhadUE8kaV/ttd/L20VfBcNeggEDaskqdHQiz8lCMWmNoopljPl wYxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683888079; x=1686480079; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qkDIKuoRmenYK20Opy/CzCxLqZjJtr8Z2dODVW7BVV4=; b=Iy2FCyiZtz05i9+eKGfhJSDpYyzRr7aTzSHdra58O1udwfo+hzdvGD21hhMvgtLLPi 2da9RpQR9dOiafHsavzZBH2AoP/Efe8fOcIF6xgxbrqyx6gZ5pJkn/EiDSE1qp/x58UM lkjQ0xtjxXjBj+7LEtNu7wR7EH7hGTzRlg/ImdFDnClhUob/48lG58UXo81XCUFbIGLR uDcAwvm3QOCyvhmEon54uCuaf969opMCgk/dA28/BQWINd0AH5DowFDSBFZaigi8PkOG fzuAb0vCL4mdIS1rYs0zhyYKz6LeTp8OIdLaZ63NfPztUouGvFGfPBy3zCk7AoJtloXE bgbA== X-Gm-Message-State: AC+VfDyx6a7iiZ5LPvJb15Es44WGeY+8GVwpuUNaIdP2cEhVY5bANHmV v93EilpivDOkgkeOh2yQu+9+mGDMhV+1QFVMsOI= X-Google-Smtp-Source: ACHHUZ5LWqchi7vPzHGnFjIL3+ExnU6kiGMD7ofDmoZ+wtVrRfMg8nNR4YaEiN/TtENgT5gwj6oQqCqB5KpIghhVxgI= X-Received: by 2002:a05:6214:509c:b0:621:363c:ea94 with SMTP id kk28-20020a056214509c00b00621363cea94mr19973997qvb.31.1683888078758; Fri, 12 May 2023 03:41:18 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> In-Reply-To: <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> From: Oleg Lelchuk Date: Fri, 12 May 2023 06:41:07 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Emmanuel Vadot Cc: Toomas Soome , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c6a94905fb7cbeb7" X-Rspamd-Queue-Id: 4QHlg34jjgz3Q9w X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000c6a94905fb7cbeb7 Content-Type: text/plain; charset="UTF-8" There is only one monitor connected to my PC. On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot wrote: > On Fri, 12 May 2023 00:20:47 +0300 > Toomas Soome wrote: > > > > > > > > On 12. May 2023, at 00:11, Oleg Lelchuk wrote: > > > > > > Guys, there is something that I find puzzling. Why doesn't the EFI > boot loader want to display the graphical orb logo in its boot menu on an > Asus Prime 7590-P motherboard? Is there something quirky about this > particular motherboard that forces the FreeBSD EFI loader to display the > old style ASCII orb logo in its boot menu? Please explain to me the cause > of this problem and if possible, give me a solution to it. > > > > There can be two reasons. One is that resolution is low and there is no > space to put the image on. Second one is that the screen is forced to use > ?text? mode, which happens when system has configured to have serial > console (redirection). > > > > rgds, > > toomas > > There is a third reason : you have multiple screens and EFI firmware > output on all of them. Never took the time to dig into this one. > > -- > Emmanuel Vadot > --000000000000c6a94905fb7cbeb7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

There is only one monitor connected to my PC.

On Fri, May = 12, 2023, 1:06 AM Emmanuel Vadot <manu@bidouilliste.com> wrote:

On Fri, 12 May 2023 00:20:47 +0300
Toomas Soome <tsoome@me.com> wrote:

>
>
> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.= com> wrote:
> >
> > Guys, there is something that I find puzzling. Why doesn't th= e EFI boot loader want to display the graphical orb logo in its boot menu o= n an Asus Prime 7590-P motherboard? Is there something quirky about this pa= rticular motherboard that forces the FreeBSD EFI loader to display the old = style ASCII orb logo in its boot menu? Please explain to me the cause of th= is problem and if possible, give me a solution to it.
>
> There can be two reasons. One is that resolution is low and there is n= o space to put the image on. Second one is that the screen is forced to use= ?text? mode, which happens when system has configured to have serial conso= le (redirection).
>
> rgds,
> toomas

=C2=A0There is a third reason : you have multiple screens and EFI firmware<= br> output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org&= gt;

--000000000000c6a94905fb7cbeb7-- From nobody Fri May 12 10:55:10 2023 X-Original-To: freebsd-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 4QHlzM0Vbkz4BrK1 for ; Fri, 12 May 2023 10:55:27 +0000 (UTC) (envelope-from tsoome@me.com) Received: from pv50p00im-ztdg10012001.me.com (pv50p00im-ztdg10012001.me.com [17.58.6.51]) (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 4QHlzL333mz3hYH for ; Fri, 12 May 2023 10:55:26 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1683888924; bh=VTkOEVfYdEFr8PiXmukHQAYRkzqnFO/pbRU8jweZzGw=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=kpSbi0WjaJcg3a/GlCwSnlYj7mKmeqhh2PzHjI8yjsws/MTzkaXwlGa3WHyaMoP2h vTjBrtXYjsWqU0kdGpNqSgxcsu8O/vqqX5Cq0Ol1ti4zRA8yqRnUSpnDgTgFU6hd2X 5K6WowhlIuFJRTTAdfWoNHhxORv8XRRYzfH+zsflEVXwTzrxNwnKt0U0RuJsPpwf66 0l3kkXYXi6ifPTg31k0ZH6Hl4EfBYS06uB538HOho31HMKt6ibclXFgzQ9ginq0/cN i0SCIpzDSOO2xiWhk2tFuKGkFvjvOKsKP5bQO569atvFMDThAUhVSuBVZbL9+4iEEL LrUale7Wi2FQg== Received: from smtpclient.apple (pv50p00im-dlb-asmtp-mailmevip.me.com [17.56.9.10]) by pv50p00im-ztdg10012001.me.com (Postfix) with ESMTPSA id 5F4BAA056C; Fri, 12 May 2023 10:55:22 +0000 (UTC) From: Toomas Soome Message-Id: <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_D52B09E6-58E8-4541-9B98-825589EA3D2D" 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 (Mac OS X Mail 16.0 $3731.500.231$) Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Date: Fri, 12 May 2023 13:55:10 +0300 In-Reply-To: Cc: Emmanuel Vadot , freebsd-current@freebsd.org To: Oleg Lelchuk References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> X-Mailer: Apple Mail (2.3731.500.231) X-Proofpoint-GUID: Kwef41ec6l52IvrWSZDTWnfsPnUgQAkV X-Proofpoint-ORIG-GUID: Kwef41ec6l52IvrWSZDTWnfsPnUgQAkV X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.517,18.0.572,17.11.64.514.0000000_definitions?= =?UTF-8?Q?=3D2022-06-21=5F01:2022-06-21=5F01,2020-02-14=5F11,2022-02-23?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 phishscore=0 mlxscore=0 spamscore=0 suspectscore=0 bulkscore=0 clxscore=1011 adultscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2305120090 X-Rspamd-Queue-Id: 4QHlzL333mz3hYH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.0.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_D52B09E6-58E8-4541-9B98-825589EA3D2D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 12. May 2023, at 13:41, Oleg Lelchuk wrote: >=20 > There is only one monitor connected to my PC. Multiple monitors is definitely not an issue in your case (the missing = ConOut and the decision chain based on it is the root cause). What you = can do, is to check if there is firmware update from system vendor, that = may fix the missing ConOut. rgds, toomas >=20 > On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot > wrote: >> On Fri, 12 May 2023 00:20:47 +0300 >> Toomas Soome > wrote: >>=20 >> >=20 >> >=20 >> > > On 12. May 2023, at 00:11, Oleg Lelchuk > wrote: >> > >=20 >> > > Guys, there is something that I find puzzling. Why doesn't the = EFI boot loader want to display the graphical orb logo in its boot menu = on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to = display the old style ASCII orb logo in its boot menu? Please explain to = me the cause of this problem and if possible, give me a solution to it. >> >=20 >> > There can be two reasons. One is that resolution is low and there = is no space to put the image on. Second one is that the screen is forced = to use ?text? mode, which happens when system has configured to have = serial console (redirection). >> >=20 >> > rgds, >> > toomas >>=20 >> There is a third reason : you have multiple screens and EFI firmware >> output on all of them. Never took the time to dig into this one. >>=20 >> --=20 >> Emmanuel Vadot > = > --Apple-Mail=_D52B09E6-58E8-4541-9B98-825589EA3D2D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On 12. = May 2023, at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

There is only one monitor connected to my = PC.

Multiple monitors is = definitely not an issue in your case (the missing ConOut and the = decision chain based on it is the root cause). What you can do, is to = check if there is firmware update from system vendor, that may fix the = missing = ConOut.

rgds,

toomas

On Fri, May 12, 2023, 1:06 AM Emmanuel = Vadot <manu@bidouilliste.com> = wrote:
On Fri, 12 May 2023 = 00:20:47 +0300
Toomas Soome <tsoome@me.com> wrote:

>
>
> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
> >
> > Guys, there is something that I find puzzling. Why doesn't the = EFI boot loader want to display the graphical orb logo in its boot menu = on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to = display the old style ASCII orb logo in its boot menu? Please explain to = me the cause of this problem and if possible, give me a solution to = it.
>
> There can be two reasons. One is that resolution is low and there = is no space to put the image on. Second one is that the screen is forced = to use ?text? mode, which happens when system has configured to have = serial console (redirection).
>
> rgds,
> toomas

There is a third reason : you have multiple screens and EFI = firmware
output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> = <manu@freebsd.org>

= --Apple-Mail=_D52B09E6-58E8-4541-9B98-825589EA3D2D-- From nobody Fri May 12 11:45:59 2023 X-Original-To: freebsd-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 4QHn5v54Cfz49vL9 for ; Fri, 12 May 2023 11:46:11 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHn5v32wVz3nDN for ; Fri, 12 May 2023 11:46:11 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-757741ca000so657875185a.2 for ; Fri, 12 May 2023 04:46:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683891970; x=1686483970; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fahHinsVGbao94RoCqWeobdlXhEOsp074Zbua2qDJAk=; b=WaWXIxJY9MJ1NPIzcjN9NC1asVCFyVaeYGN4o65KO9d8ESTb+GZo842zFSjXY8SWHr tlxiGyBcmTqrMEfokzN0MW3gMh4p8MA/wt/iTBerwQNsMZeKyIOmyBZYJbUeveQW4MQk Qs5TdsIuw+eBLApfuaeJ0m1f3Q1rKZ3jsH5hWn0tqh+H74NJ3oFzkXgME8GOPUtBUHmr 3ztBo8Kr2BjpLU1ZgYc3ktvA3ouk/ExUcawPSXtJH4qU4ZAQWiHtVQowenK3C/zpgItY V2ia5h3K2jw0JsUhlW0JgSNFLhjGEuY2YlYrrFNX9w/olWKCzY62rr56OU10xLIncxNj 2xhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683891970; x=1686483970; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fahHinsVGbao94RoCqWeobdlXhEOsp074Zbua2qDJAk=; b=GS5rpuDn/KcMf5GhH8lT2MCw2ymiG3PtOduvqVRE3bY6h7uL3d0Bctp/ew55kqHPn4 qAs6W+hIim/xTbtcZ9aHSVBiXZZ56qcVk0O05T7EjaDkfH6vhRGHIaA8Acw1PVIW2315 FFjLM8AJ7X9N/YSbnBAf3JEiyv+6EZcOFVafPaZ5WMqO73aj9cS2qzTZpnWUexdotqVj Xa+GPrT+fFo3Jk4PfXS95r8jKuMeZBEdiZsqjNkjIR+dNXbl8cDOSY2BkhOnKgT6zarT Y8ZgNtmRqknNnXSgCDUFRtSwAfwL0aO7ttQgcPSE1K7Sh/MEGr3voB0XQqe7prHRFQnb gwPg== X-Gm-Message-State: AC+VfDxJELCECg1iJnJVdWKAjojQOXDqRJZ8CECO1OgQgzQI/8Y2lkLM MsyPmRHdeKMsfYklr0SmRB2YuibUUAzabjcDWstm7HWpVqzsoQ== X-Google-Smtp-Source: ACHHUZ5TKjDgLi5F2Eklo3KYjm9Nj5Fq/Sn8O6J31uEKym1dtaAZgZI4G9d73ZQYl8lq69uA7yy7b/wvcW6jY+CBeuA= X-Received: by 2002:a05:6214:76a:b0:5f1:606b:a9c8 with SMTP id f10-20020a056214076a00b005f1606ba9c8mr34598315qvz.22.1683891970471; Fri, 12 May 2023 04:46:10 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> In-Reply-To: <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> From: Oleg Lelchuk Date: Fri, 12 May 2023 07:45:59 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000bd7b5e05fb7da619" X-Rspamd-Queue-Id: 4QHn5v32wVz3nDN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000bd7b5e05fb7da619 Content-Type: text/plain; charset="UTF-8" I run the latest uefi bios firmware available for my motherboard. So, in your opinion, there is something wrong with it? Is this problem somehow related to this problem: https://www.mail-archive.com/stable@freebsd.org/msg00235.html ? As I mentioned earlier, my motherboard is Asus Prime 7590-P Wifi. The PC is connected to my monitor and there is absolutely nothing connected to the PC's serial port. If there is a bug in my motherboard's UEFI implementation, is it possible to add code to the stand implementation of FreeBSD that will find a way around this bug?.. Please think of something... I definitely want to see the graphical orb logo in the FreeBSD boot menu! On Fri, May 12, 2023, 6:55 AM Toomas Soome wrote: > > > On 12. May 2023, at 13:41, Oleg Lelchuk wrote: > > There is only one monitor connected to my PC. > > > Multiple monitors is definitely not an issue in your case (the missing > ConOut and the decision chain based on it is the root cause). What you can > do, is to check if there is firmware update from system vendor, that may > fix the missing ConOut. > > rgds, > toomas > > > > On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot > wrote: > >> On Fri, 12 May 2023 00:20:47 +0300 >> Toomas Soome wrote: >> >> > >> > >> > > On 12. May 2023, at 00:11, Oleg Lelchuk >> wrote: >> > > >> > > Guys, there is something that I find puzzling. Why doesn't the EFI >> boot loader want to display the graphical orb logo in its boot menu on an >> Asus Prime 7590-P motherboard? Is there something quirky about this >> particular motherboard that forces the FreeBSD EFI loader to display the >> old style ASCII orb logo in its boot menu? Please explain to me the cause >> of this problem and if possible, give me a solution to it. >> > >> > There can be two reasons. One is that resolution is low and there is no >> space to put the image on. Second one is that the screen is forced to use >> ?text? mode, which happens when system has configured to have serial >> console (redirection). >> > >> > rgds, >> > toomas >> >> There is a third reason : you have multiple screens and EFI firmware >> output on all of them. Never took the time to dig into this one. >> >> -- >> Emmanuel Vadot >> > > --000000000000bd7b5e05fb7da619 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I run the latest uefi bios firmware avai= lable for my motherboard. So, in your opinion, there is something wrong wit= h it? Is this problem somehow related to this problem:=C2=A0https://www.mail= -archive.com/stable@freebsd.org/msg00235.html ? As I mentioned earlier,= my motherboard is Asus Prime 7590-P Wifi. The PC is connected to my monito= r and there is absolutely nothing connected to the PC's serial port. If= there is a bug in my motherboard's UEFI implementation, is it possible= to add code to the stand implementation of FreeBSD that will find a way ar= ound this bug?.. Please think of something... I definitely want to see the = graphical orb logo in the FreeBSD boot menu!

On Fri, May 12, 2023, 6:5= 5 AM Toomas Soome <ts= oome@me.com> wrote:

On 12. May 2023= , at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
There is only one monitor connected to my PC.

Multiple monitors is definitely = not an issue in your case (the missing ConOut and the decision chain based = on it is the root cause). What you can do, is to check if there is firmware= update from system vendor, that may fix the missing ConOut.

=
rgds,
toomas

On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot <manu@bidouilli= ste.com> wrote:
On Fri, 12 May 2023 00:20:47 +0300
Toomas Soome <tsoome@me.com> wrote:

>
>
> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglel= chuk@gmail.com> wrote:
> >
> > Guys, there is something that I find puzzling. Why doesn't th= e EFI boot loader want to display the graphical orb logo in its boot menu o= n an Asus Prime 7590-P motherboard? Is there something quirky about this pa= rticular motherboard that forces the FreeBSD EFI loader to display the old = style ASCII orb logo in its boot menu? Please explain to me the cause of th= is problem and if possible, give me a solution to it.
>
> There can be two reasons. One is that resolution is low and there is n= o space to put the image on. Second one is that the screen is forced to use= ?text? mode, which happens when system has configured to have serial conso= le (redirection).
>
> rgds,
> toomas

=C2=A0There is a third reason : you have multiple screens and EFI firmware<= br> output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>

--000000000000bd7b5e05fb7da619-- From nobody Fri May 12 12:01:53 2023 X-Original-To: freebsd-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 4QHnSS17zbz49vt4 for ; Fri, 12 May 2023 12:02:16 +0000 (UTC) (envelope-from tsoome@me.com) Received: from mr85p00im-zteg06021601.me.com (mr85p00im-zteg06021601.me.com [17.58.23.187]) (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 4QHnSR4858z3prs for ; Fri, 12 May 2023 12:02:15 +0000 (UTC) (envelope-from tsoome@me.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1683892933; bh=uymoikoyuWrmwgE7XqcqEqjZqCaYAMRDE4XaWVnwdu8=; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; b=XvCCuPYNrboNeBaVkjNnsq5FITL9wMxZc+7Y3EkU97Q0gVw/7+VhfApk/4DTcN3Ql zJ+3thTeovnefZqFGhXnOqpq1TqfZ+SnSen8Wp8+SIhN/BMGmOPvDAY6N/DQX7s057 sKUfno726oaD0muABUWCsiWswogq0KsASbJg0oQ9Om6SRpyGqQ0sPjG0/ppunWom+4 WOOQUn6X/Oc9/TGtptWos9L5AXAev5Xw5PeeUM5BtvH6J+1qBblOKSal7BO2T7JkCI FtWhOiGYWkofy9A2yeZhDxsMf6rK8CMtxp//jjK6XH03FaHshWa2NXuhHtHtKKl55v yKC+Ad+WmmwRg== Received: from smtpclient.apple (mr38p00im-dlb-asmtp-mailmevip.me.com [17.57.152.18]) by mr85p00im-zteg06021601.me.com (Postfix) with ESMTPSA id 71293305890F; Fri, 12 May 2023 12:02:08 +0000 (UTC) From: Toomas Soome Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_859E6A1A-4558-4D38-8F66-4C102BBFE8B3" 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 (Mac OS X Mail 16.0 $3731.500.231$) Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? Date: Fri, 12 May 2023 15:01:53 +0300 In-Reply-To: Cc: Emmanuel Vadot , freebsd-current@freebsd.org To: Oleg Lelchuk References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> X-Mailer: Apple Mail (2.3731.500.231) X-Proofpoint-GUID: gLYnLcQeUuLtRMK1BqWgbG5ugC2A43rj X-Proofpoint-ORIG-GUID: gLYnLcQeUuLtRMK1BqWgbG5ugC2A43rj X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.138,18.0.572,17.11.62.513.0000000_definitions?= =?UTF-8?Q?=3D2020-02-14=5F11:2020-02-14=5F02,2020-02-14=5F11,2021-12-02?= =?UTF-8?Q?=5F01_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 bulkscore=0 suspectscore=0 spamscore=0 phishscore=0 mlxlogscore=999 adultscore=0 mlxscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2305120100 X-Rspamd-Queue-Id: 4QHnSR4858z3prs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:17.58.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_859E6A1A-4558-4D38-8F66-4C102BBFE8B3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 12. May 2023, at 14:45, Oleg Lelchuk wrote: >=20 > I run the latest uefi bios firmware available for my motherboard. So, = in your opinion, there is something wrong with it? Is this problem = somehow related to this problem: = https://www.mail-archive.com/stable@freebsd.org/msg00235.html ? As I = mentioned earlier, my motherboard is Asus Prime 7590-P Wifi. The PC is = connected to my monitor and there is absolutely nothing connected to the = PC's serial port. If there is a bug in my motherboard's UEFI = implementation, is it possible to add code to the stand implementation = of FreeBSD that will find a way around this bug?.. Please think of = something... I definitely want to see the graphical orb logo in the = FreeBSD boot menu! >=20 The UEFI specification does describe those variables, but I have not = seen them noted to be required to be present. They *usually* are = present. So, if you have latest firmware and have option to file the bug = with vendor, it is good idea to do so. Anyhow, as Warner already wrote, we actually have option to check ConIn = for presence of serial port too, so we should do that - it will just = take a bit of time. rgds, toomas > On Fri, May 12, 2023, 6:55 AM Toomas Soome > wrote: >>=20 >>=20 >>> On 12. May 2023, at 13:41, Oleg Lelchuk > wrote: >>>=20 >>> There is only one monitor connected to my PC. >>=20 >> Multiple monitors is definitely not an issue in your case (the = missing ConOut and the decision chain based on it is the root cause). = What you can do, is to check if there is firmware update from system = vendor, that may fix the missing ConOut. >>=20 >> rgds, >> toomas >>=20 >>=20 >>>=20 >>> On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot > wrote: >>>> On Fri, 12 May 2023 00:20:47 +0300 >>>> Toomas Soome > wrote: >>>>=20 >>>> >=20 >>>> >=20 >>>> > > On 12. May 2023, at 00:11, Oleg Lelchuk > wrote: >>>> > >=20 >>>> > > Guys, there is something that I find puzzling. Why doesn't the = EFI boot loader want to display the graphical orb logo in its boot menu = on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to = display the old style ASCII orb logo in its boot menu? Please explain to = me the cause of this problem and if possible, give me a solution to it. >>>> >=20 >>>> > There can be two reasons. One is that resolution is low and there = is no space to put the image on. Second one is that the screen is forced = to use ?text? mode, which happens when system has configured to have = serial console (redirection). >>>> >=20 >>>> > rgds, >>>> > toomas >>>>=20 >>>> There is a third reason : you have multiple screens and EFI = firmware >>>> output on all of them. Never took the time to dig into this one. >>>>=20 >>>> --=20 >>>> Emmanuel Vadot > > >>=20 --Apple-Mail=_859E6A1A-4558-4D38-8F66-4C102BBFE8B3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On 12. = May 2023, at 14:45, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

I run the latest uefi bios firmware = available for my motherboard. So, in your opinion, there is something = wrong with it? Is this problem somehow related to this problem: htt= ps://www.mail-archive.com/stable@freebsd.org/msg00235.html ? As I = mentioned earlier, my motherboard is Asus Prime 7590-P Wifi. The PC is = connected to my monitor and there is absolutely nothing connected to the = PC's serial port. If there is a bug in my motherboard's UEFI = implementation, is it possible to add code to the stand implementation = of FreeBSD that will find a way around this bug?.. Please think of = something... I definitely want to see the graphical orb logo in the = FreeBSD boot = menu!

The UEFI = specification does describe those variables, but I have not seen them = noted to be required to be present. They *usually* are present. So, if = you have latest firmware and have option to file the bug with vendor, it = is good idea to do so.

Anyhow, as Warner = already wrote, we actually have option to check ConIn for presence of = serial port too, so we should do that - it will just take a bit of = time.

rgds,

toomas

On Fri, May 12, 2023, 6:55 AM Toomas Soome <tsoome@me.com> = wrote:

On 12. May 2023, at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com> = wrote:

There is only one monitor = connected to my PC.

Multiple = monitors is definitely not an issue in your case (the missing ConOut and = the decision chain based on it is the root cause). What you can do, is = to check if there is firmware update from system vendor, that may fix = the missing = ConOut.

rgds,
toomas

On Fri, May 12, 2023, 1:06 AM Emmanuel = Vadot <manu@bidouilliste.com> = wrote:
On Fri, 12 May 2023 00:20:47 = +0300
Toomas Soome <tsoome@me.com> wrote:

>
>
> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
> >
> > Guys, there is something that I find puzzling. Why doesn't the = EFI boot loader want to display the graphical orb logo in its boot menu = on an Asus Prime 7590-P motherboard? Is there something quirky about = this particular motherboard that forces the FreeBSD EFI loader to = display the old style ASCII orb logo in its boot menu? Please explain to = me the cause of this problem and if possible, give me a solution to = it.
>
> There can be two reasons. One is that resolution is low and there = is no space to put the image on. Second one is that the screen is forced = to use ?text? mode, which happens when system has configured to have = serial console (redirection).
>
> rgds,
> toomas

There is a third reason : you have multiple screens and EFI = firmware
output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>

= --Apple-Mail=_859E6A1A-4558-4D38-8F66-4C102BBFE8B3-- From nobody Fri May 12 13:26:14 2023 X-Original-To: freebsd-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 4QHqKb5BW9z4B1bg for ; Fri, 12 May 2023 13:26:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHqKb2YcBz3wt0 for ; Fri, 12 May 2023 13:26:27 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-62135cf0adcso23831186d6.1 for ; Fri, 12 May 2023 06:26:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683897986; x=1686489986; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VbNFZtFoylK4mDhQ73TF9bjYMfoeXUhdey+7uBT4aZc=; b=K6HgC+QTGEmtFnuwraN0E3uu3z02/pHT7QLmIrZM/+M5JVsb4BVHBsDrtEeva7g9kc Xn82pgqKQKux9QvRs7718xs9QISUjNof/Rw87OM82gxYLY1DjvSX9FzwIVcspGHwn/xp 4iIeyv98JMblDMgsWI+/sXys+m1Vset5OgUpeXMjTI6Biqf2+nO+VYpZrIajjfVtKv2L rvgxNdOepToMJhGn1VA/Iq4Rr2CzJKIafZsbyeemb6C4+6xJ/UStPQUVxZoNHoIzV4Sr M2w5/Zrz93LUOqxI2Odsj8UNWvPM4x0J9xySt9W1bbKCB2ntwGk7HSiVtibAP5ePzvS1 G3nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683897986; x=1686489986; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VbNFZtFoylK4mDhQ73TF9bjYMfoeXUhdey+7uBT4aZc=; b=NT7Ee3JX6Cqk1AXoQlAUVNXYIZ3qQnjGZolUqjEEmua3VEM+FnIhob1kx7fnQNope5 YTJHSN1JDH0LQs+h3LQhGu1uoUzJkG0wblV6bTRnqxbTHzXjEPayaRhaOUenXog7+3xv Y6juQGbajwhyTPJXepjrX6HTzjDj02g4gjLMAfqG6JHws8JF9a+zLnNRpL/Do5DD2ff8 qB4NAL8qwZz87jp33+1xvMKZw1ghLcO0r/hfJ1T2ED2D1f89nHi7ncBfSu7jvXQ68lUQ ZLoy4qhmn0YEeGPEHB/8VAk/0A0UWk7nRYin2GsMGG8e1pAezYW4N6cl6FJnCt6u3y+O Wn5g== X-Gm-Message-State: AC+VfDxHW3FZv8pQeNIBBK7miVNgcipn1eeRYhOJg2AyCvM+IJSUbFtX Q/Yv4vIsNpmX694N9f1BWf8qWvL0xUndvG6CplE= X-Google-Smtp-Source: ACHHUZ6xwgHLuuPCLCvcJSV38/261+VHN8R7/gS3EmdqZOzFJgIx21bHJ8y5KjgyWehPaF+eMPxbbbMEpipUuINNuKk= X-Received: by 2002:ad4:5f0c:0:b0:61b:58f5:5dc3 with SMTP id fo12-20020ad45f0c000000b0061b58f55dc3mr37807728qvb.43.1683897986413; Fri, 12 May 2023 06:26:26 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com>

In-Reply-To: From: Oleg Lelchuk Date: Fri, 12 May 2023 09:26:14 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Toomas Soome Cc: Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000051761205fb7f0d54" X-Rspamd-Queue-Id: 4QHqKb2YcBz3wt0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000051761205fb7f0d54 Content-Type: text/plain; charset="UTF-8" I don't want to go through the hassle of filling a bug with my vendor. I will just wait for you, guys, to update the stand implementation. Thank you for explaining to me what causes this issue. On Fri, May 12, 2023, 8:02 AM Toomas Soome wrote: > > > On 12. May 2023, at 14:45, Oleg Lelchuk wrote: > > I run the latest uefi bios firmware available for my motherboard. So, in > your opinion, there is something wrong with it? Is this problem somehow > related to this problem: > https://www.mail-archive.com/stable@freebsd.org/msg00235.html ? As I > mentioned earlier, my motherboard is Asus Prime 7590-P Wifi. The PC is > connected to my monitor and there is absolutely nothing connected to the > PC's serial port. If there is a bug in my motherboard's UEFI > implementation, is it possible to add code to the stand implementation of > FreeBSD that will find a way around this bug?.. Please think of > something... I definitely want to see the graphical orb logo in the FreeBSD > boot menu! > > > The UEFI specification does describe those variables, but I have not seen > them noted to be required to be present. They *usually* are present. So, if > you have latest firmware and have option to file the bug with vendor, it is > good idea to do so. > > Anyhow, as Warner already wrote, we actually have option to check ConIn > for presence of serial port too, so we should do that - it will just take a > bit of time. > > rgds, > toomas > > On Fri, May 12, 2023, 6:55 AM Toomas Soome wrote: > >> >> >> On 12. May 2023, at 13:41, Oleg Lelchuk wrote: >> >> There is only one monitor connected to my PC. >> >> >> Multiple monitors is definitely not an issue in your case (the missing >> ConOut and the decision chain based on it is the root cause). What you can >> do, is to check if there is firmware update from system vendor, that may >> fix the missing ConOut. >> >> rgds, >> toomas >> >> >> >> On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot >> wrote: >> >>> On Fri, 12 May 2023 00:20:47 +0300 >>> Toomas Soome wrote: >>> >>> > >>> > >>> > > On 12. May 2023, at 00:11, Oleg Lelchuk >>> wrote: >>> > > >>> > > Guys, there is something that I find puzzling. Why doesn't the EFI >>> boot loader want to display the graphical orb logo in its boot menu on an >>> Asus Prime 7590-P motherboard? Is there something quirky about this >>> particular motherboard that forces the FreeBSD EFI loader to display the >>> old style ASCII orb logo in its boot menu? Please explain to me the cause >>> of this problem and if possible, give me a solution to it. >>> > >>> > There can be two reasons. One is that resolution is low and there is >>> no space to put the image on. Second one is that the screen is forced to >>> use ?text? mode, which happens when system has configured to have serial >>> console (redirection). >>> > >>> > rgds, >>> > toomas >>> >>> There is a third reason : you have multiple screens and EFI firmware >>> output on all of them. Never took the time to dig into this one. >>> >>> -- >>> Emmanuel Vadot >>> >> >> > --00000000000051761205fb7f0d54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I don't want to go through the hassle of filling a bu= g with my vendor. I will just wait for you, guys, to update the stand imple= mentation. Thank you for explaining to me what causes this issue.

On Fri, Ma= y 12, 2023, 8:02 AM Toomas Soome <tsoom= e@me.com> wrote:

On 12. May 2023, at 14:45, Oleg Lelchuk <oleglelchuk@gmail.com= > wrote:

I run the late= st uefi bios firmware available for my motherboard. So, in your opinion, th= ere is something wrong with it? Is this problem somehow related to this pro= blem:=C2=A0https://www.mail-archive.com= /stable@freebsd.org/msg00235.html ? As I mentioned earlier, my motherbo= ard is Asus Prime 7590-P Wifi. The PC is connected to my monitor and there = is absolutely nothing connected to the PC's serial port. If there is a = bug in my motherboard's UEFI implementation, is it possible to add code= to the stand implementation of FreeBSD that will find a way around this bu= g?.. Please think of something... I definitely want to see the graphical or= b logo in the FreeBSD boot menu!

The UEFI specification does describe those variables, but I hav= e not seen them noted to be required to be present. They *usually* are pres= ent. So, if you have latest firmware and have option to file the bug with v= endor, it is good idea to do so.

Anyhow, as Warner= already wrote, we actually have option to check ConIn for presence of seri= al port too, so we should do that - it will just take a bit of time.

<= div>

rgds,

toomas

On = Fri, May 12, 2023, 6:55 AM Toomas Soome <tsoome@me.com> wrote:

On 12. May 2023, at 13:41, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

There is only one monitor connected to my PC.

Multiple monitors is definitely not an issue in your case= (the missing ConOut and the decision chain based on it is the root cause).= What you can do, is to check if there is firmware update from system vendo= r, that may fix the missing ConOut.

rgds,
toomas

On Fri, May 12, 2= 023, 1:06 AM Emmanuel Vadot <manu@bidouilliste.com>= wrote:
On Fri, = 12 May 2023 00:20:47 +0300
Toomas Soome <tsoome@me.com> wrote:

>
>
> > On 12. May 2023, at 00:11, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
> >
> > Guys, there is something that I find puzzling. Why doesn't th= e EFI boot loader want to display the graphical orb logo in its boot menu o= n an Asus Prime 7590-P motherboard? Is there something quirky about this pa= rticular motherboard that forces the FreeBSD EFI loader to display the old = style ASCII orb logo in its boot menu? Please explain to me the cause of th= is problem and if possible, give me a solution to it.
>
> There can be two reasons. One is that resolution is low and there is n= o space to put the image on. Second one is that the screen is forced to use= ?text? mode, which happens when system has configured to have serial conso= le (redirection).
>
> rgds,
> toomas

=C2=A0There is a third reason : you have multiple screens and EFI firmware<= br> output on all of them. Never took the time to dig into this one.

--
Emmanuel Vadot <manu@bidouilliste.com> &= lt;manu@freebsd.org>

--00000000000051761205fb7f0d54-- From nobody Fri May 12 14:05:37 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 4QHrBy6PByz4B3fg for ; Fri, 12 May 2023 14:05:46 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4QHrBy1VDyz412r for ; Fri, 12 May 2023 14:05:45 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Authentication-Results: mx1.freebsd.org; none Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 34CE5cwM063531; Fri, 12 May 2023 07:05:38 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 34CE5bUi063530; Fri, 12 May 2023 07:05:37 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <202305121405.34CE5bUi063530@gndrsh.dnsmgr.net> Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support In-Reply-To: <20230512070134.eb633400d68cf7c0813d7fde@dec.sakura.ne.jp> To: Tomoaki AOKI Date: Fri, 12 May 2023 07:05:37 -0700 (PDT) CC: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] 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 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4QHrBy1VDyz412r X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On Thu, 11 May 2023 23:08:30 +0200 > Yuri wrote: > > > Warner Losh wrote: > > > > > > > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes > > > > > > > wrote: > > > > > > > On Thu, May 11, 2023, 2:16 PM Yuri > > > wrote: > > > > > > > > > Warner Losh wrote: > > > > > > The branch main has been updated by imp: > > > > > > > > > > > > URL: > > > > > > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > Author:? ? ?Warner Losh > > > > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > > > > Commit:? ? ?Warner Losh > > > > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > > > > > > >? ? ?stand/efi: Retire i386 support > > > > > > > > > > > >? ? ?Remove the i386 ifdefs and files. It never worked. > > > > > > > > > > > >? ? ?Sponsored by:? ? ? ? ? ?Netflix > > > > > >? ? ?Reviewed by:? ? ? ? ? ? manu, tsoome, kevans > > > > > >? ? ?Differential Revision:? https://reviews.freebsd.org/D40012 > > > > > > > > > > > > > As this question seems to be asked a lot on the forums, does > > > this mean > > > > > we will never support the 32bit efi booting 64bit OS? > > > > > > > > > > > > > Yes. It means we've given up on that. Such environments are rare these > > > > days, as far as I know, so unless someone shows up with something that > > > > works perfectly with a qemu testing recipe that we can roll it > > > into out > > > > test bed. Plus some kind of info on real hardware that does this > > > that's > > > > popular enough to justify inclusion. > > > > > > I have only ever seen 1 implementation of x86 32bit efi, and it was > > > such a pile of turds I just scrapped the machine. > > > > > > > > > That was my experience as well, so I biased my action towards just > > > removing it. If it turns out my experience was somehow atypical and > > > these are popular and very much robust, I'm open to learning about it. > > > > I just noticed that it was asked several times in the last few months > > trying to use FreeBSD on not-so-modern and rather exotic hardware; I > > don't think we really need that support, but I simply wasn't aware of > > efi32 status before this commit, hence I asked :) > > Just a FYI. > > A subscriber (not me) tried ASUS EeeBook X205TA (manufactured "2015-04") > through Mar.18, 2021 to Apr.13, 2021 without luck on freebsd-usrs-jp ML > (in Japanese, started from [1], [2] for April). > > Atom CPU Z3735F @1.33GHz, 2GB RAM That is a 4 core 64 bit CPU, it most likely has a 64bit efi implementation. > Shipped with "Windows 8.1 with Bing (32bit)" installed. Probably a good choice to use a 32 bit OS on a machine with only 2GB as there is no need for a 64 bit pointer. This pretty much applies to any machine with 4GB or less of memory > > [1] > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-March/001728.html > > [2] > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-April/001746.html > > > -- > Tomoaki AOKI] > > -- Rod Grimes rgrimes@freebsd.org From nobody Fri May 12 22:37:14 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 4QJ3YM1X38z4BXjR for ; Fri, 12 May 2023 22:37:27 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4QJ3YL3nNYz3hmN for ; Fri, 12 May 2023 22:37:25 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 34CMbFmm073554; Sat, 13 May 2023 07:37:16 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 13 May 2023 07:37:14 +0900 From: Tomoaki AOKI To: current@freebsd.org Cc: "Rodney W. Grimes" Subject: Re: git: c16e08e5f324 - main - stand/efi: Retire i386 support Message-Id: <20230513073714.e3be89cf140dce567aff2505@dec.sakura.ne.jp> In-Reply-To: <202305121405.34CE5bUi063530@gndrsh.dnsmgr.net> References: <20230512070134.eb633400d68cf7c0813d7fde@dec.sakura.ne.jp> <202305121405.34CE5bUi063530@gndrsh.dnsmgr.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QJ3YL3nNYz3hmN X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, 12 May 2023 07:05:37 -0700 (PDT) "Rodney W. Grimes" wrote: > > On Thu, 11 May 2023 23:08:30 +0200 > > Yuri wrote: > > > > > Warner Losh wrote: > > > > > > > > > > > > On Thu, May 11, 2023, 2:50 PM Rodney W. Grimes > > > > > > > > > wrote: > > > > > > > > > On Thu, May 11, 2023, 2:16 PM Yuri > > > > wrote: > > > > > > > > > > > Warner Losh wrote: > > > > > > > The branch main has been updated by imp: > > > > > > > > > > > > > > URL: > > > > > > > > > > https://cgit.FreeBSD.org/src/commit/?id=c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > > > > > > > > commit c16e08e5f324aa119c85e10eaabacbd2abdb40e0 > > > > > > > Author:? ? ?Warner Losh > > > > > > > AuthorDate: 2023-05-11 20:04:12 +0000 > > > > > > > Commit:? ? ?Warner Losh > > > > > > > CommitDate: 2023-05-11 20:06:03 +0000 > > > > > > > > > > > > > >? ? ?stand/efi: Retire i386 support > > > > > > > > > > > > > >? ? ?Remove the i386 ifdefs and files. It never worked. > > > > > > > > > > > > > >? ? ?Sponsored by:? ? ? ? ? ?Netflix > > > > > > >? ? ?Reviewed by:? ? ? ? ? ? manu, tsoome, kevans > > > > > > >? ? ?Differential Revision:? https://reviews.freebsd.org/D40012 > > > > > > > > > > > > > > > > As this question seems to be asked a lot on the forums, does > > > > this mean > > > > > > we will never support the 32bit efi booting 64bit OS? > > > > > > > > > > > > > > > > Yes. It means we've given up on that. Such environments are rare these > > > > > days, as far as I know, so unless someone shows up with something that > > > > > works perfectly with a qemu testing recipe that we can roll it > > > > into out > > > > > test bed. Plus some kind of info on real hardware that does this > > > > that's > > > > > popular enough to justify inclusion. > > > > > > > > I have only ever seen 1 implementation of x86 32bit efi, and it was > > > > such a pile of turds I just scrapped the machine. > > > > > > > > > > > > That was my experience as well, so I biased my action towards just > > > > removing it. If it turns out my experience was somehow atypical and > > > > these are popular and very much robust, I'm open to learning about it. > > > > > > I just noticed that it was asked several times in the last few months > > > trying to use FreeBSD on not-so-modern and rather exotic hardware; I > > > don't think we really need that support, but I simply wasn't aware of > > > efi32 status before this commit, hence I asked :) > > > > Just a FYI. > > > > A subscriber (not me) tried ASUS EeeBook X205TA (manufactured "2015-04") > > through Mar.18, 2021 to Apr.13, 2021 without luck on freebsd-usrs-jp ML > > (in Japanese, started from [1], [2] for April). > > > > Atom CPU Z3735F @1.33GHz, 2GB RAM > > That is a 4 core 64 bit CPU, it most likely has a 64bit efi > implementation. Exactly. I'd found the info while discussing with the reporter on freebsd-uses-jp ML at Intel site. Note that neither boot1.efi nor loader.efi shipped with FreeBSD i386 distribution couldn't boot kernel successfully (built but not working). So I have no objection for discontinueing the support. > > Shipped with "Windows 8.1 with Bing (32bit)" installed. > > Probably a good choice to use a 32 bit OS on a machine > with only 2GB as there is no need for a 64 bit pointer. > This pretty much applies to any machine with 4GB or > less of memory IIRC, I've read somewhere describing that ASUS EeeBook X205TA has 32bit UEFI to boot 32bit Windoze, and supports 32bit UEFI boot only. I've found folowing pages now, different pages I read ATM, though. https://github.com/filirnd/x205ta https://forums.linuxmint.com/viewtopic.php?t=380177 > > > > > [1] > > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-March/001728.html > > > > [2] > > https://lists.freebsd.org/pipermail/freebsd-users-jp/2021-April/001746.html > > > > > > -- > > Tomoaki AOKI] > > > > > > -- > Rod Grimes rgrimes@freebsd.org > -- Tomoaki AOKI From nobody Fri May 12 23:45:46 2023 X-Original-To: freebsd-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 4QJ54S52Z9z4Bbpc for ; Fri, 12 May 2023 23:46:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QJ54S1VQVz3mmH for ; Fri, 12 May 2023 23:46:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-f42.google.com with SMTP id 2adb3069b0e04-4f004cc54f4so11946147e87.3 for ; Fri, 12 May 2023 16:46:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683935158; x=1686527158; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+TspVb1MjOKkQJQEavwSrAmp27eo4LvTjLWMaE73PTs=; b=iQWmqRvtrrecGntIQeF1k6ontzEHIVlGIx4ljXXJsSYPjX9lStBuxmQtjv4edCuOLT XjOFIzE0UzjVT+EEJ9DxMhNR8FqVNycBuQXXh0Xeagl7ZxLvCTteXcD8fqdupxu1xERS 7NGMG8hJBupe6yjaHPT9OWAQ6ye5PShc7AbGwXY20HNpGDmTK5XonsWwjWRmc7SI8Fo3 ykEvQXmG5m22UdDoLtJFsBiFhKPzNsktIXbiTBMD9i0G/yzk53NVNqFlcUz6ld3gmYe7 m5rB897gKpbBIdbF5jkEs+qUwz0yGc4kirMkf0cB2mePVzebaG/8b81cM9fY+Jn65xz+ ltFQ== X-Gm-Message-State: AC+VfDwV8vVlI7W96dMz6PGmVVYZM7k21hmby15ocd4so0hOjakOlLUe ClraLwteB1mmyZx/eb3Fhu+PxrUto8lgjeZIvCE= X-Google-Smtp-Source: ACHHUZ4gAV6JribK7LUY2u5/yvZmVeTBZWpfLpgpIka+2bHvRDyXQCLXjj6QCebYISzGlj/Ct9/tleK22uwD7EOh/HA= X-Received: by 2002:a19:a40f:0:b0:4d1:3d1d:4914 with SMTP id q15-20020a19a40f000000b004d13d1d4914mr4329617lfc.33.1683935157957; Fri, 12 May 2023 16:45:57 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com>

In-Reply-To: From: Ed Maste Date: Fri, 12 May 2023 19:45:46 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Oleg Lelchuk Cc: Toomas Soome , Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4QJ54S1VQVz3mmH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, 12 May 2023 at 09:26, Oleg Lelchuk wrote: > > I don't want to go through the hassle of filling a bug with my vendor. I will just wait for you, guys, to update the stand implementation. Thank you for explaining to me what causes this issue. This issue is tracked in PR 265980 if you want to follow it. https://bugs.freebsd.org/265980 From nobody Fri May 12 23:55:58 2023 X-Original-To: freebsd-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 4QJ5JC1Krjz4Bc6C for ; Fri, 12 May 2023 23:56:11 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QJ5JB5mDkz3pDX; Fri, 12 May 2023 23:56:10 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qv1-xf31.google.com with SMTP id 6a1803df08f44-61b58b6e864so92201676d6.3; Fri, 12 May 2023 16:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683935769; x=1686527769; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BCasJzn6VrPPAJT8GGerA6Y0SXlg5nxyr4IZHPEUwcE=; b=IOaBdu1DHbFnDaGIqcdg9UVK9wCYnZmK3HPm9VHMSeiNtNznQ4I/5YpO2KSQ4LxcNj Gksmle437RvtxRgJYRkD74866nPJf7WY2YxAX7FE+0o3ExvkV7sL0Jed4jIukGMF6W57 xfPqiBYFI0arEj0XT/tYKiyaTOKxXAlBMv/096nNbzFmvweT2AeFSS74WB1B5WW9u6OO xwktvhetcVt5TaQ0guVma55FTJ0J1isAG3lY7PJdO3+W9xwopWJsX6GPd50M9M/ffixb 1tF1SOdRFDnPE71HhbKh5tC1OzM16t40R1pI9/AeCIi7cqFjtM46yrZQegCs+c3nG2Lo F1zA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683935769; x=1686527769; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BCasJzn6VrPPAJT8GGerA6Y0SXlg5nxyr4IZHPEUwcE=; b=W4vjzCk5ska8PPHjIFRFzadSi6rebP0w28kVGF/VVHbgi7SIO+hsUQsnQWM9xLsu0R 1//GNkk1BOZO4d5hD2T/A5TPshbN17TcZgj/jwbVEv1kx5TcrTtMyHCqB/K6xegujI2o CpQJmB1NLBbNUfkgVp53Fk3ypmqnj+Sr8mjKVQl6eHG7FMV/IzhBbRoriZvjmDCb0SsC zT1VzMp3g4ot4+ACu8nBYjwYK8MumwallsVMq9IGgvG5SRBpNizv9GAWo4Gorb3LTLcn 86RBl0rRg2nyobJ1YtO1UGXb7Ayrd20lhiDWljn7fTM/4yaw/Cr0kDgvd9TWOmNjJ13z 9zXQ== X-Gm-Message-State: AC+VfDyAeS9UZFuMVn9YJAC6IBfw+8eqMPYqkYG6wLVgUZaKC7y2j3Be t/WXk1xMqIsbALrxok9c6BDqdRLIPJbpOXXPp5jsBK+aGjUQqA== X-Google-Smtp-Source: ACHHUZ7EYSZ0D9Y/c1pqylMkxkve0t4Bw9+bRkLIk9mR1IuDfPay22l4OdMfnPABFNNe47L1jg2pHqTEH/iI0ucxY+k= X-Received: by 2002:a05:6214:501b:b0:5ef:45a7:a3c0 with SMTP id jo27-20020a056214501b00b005ef45a7a3c0mr40156485qvb.27.1683935769189; Fri, 12 May 2023 16:56:09 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com>

In-Reply-To: From: Oleg Lelchuk Date: Fri, 12 May 2023 19:55:58 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Ed Maste Cc: Toomas Soome , Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000058e00505fb87d970" X-Rspamd-Queue-Id: 4QJ5JB5mDkz3pDX X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000058e00505fb87d970 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I got it. Thanks. On Fri, May 12, 2023 at 7:45=E2=80=AFPM Ed Maste wrote= : > On Fri, 12 May 2023 at 09:26, Oleg Lelchuk wrote: > > > > I don't want to go through the hassle of filling a bug with my vendor. = I > will just wait for you, guys, to update the stand implementation. Thank y= ou > for explaining to me what causes this issue. > > This issue is tracked in PR 265980 if you want to follow it. > https://bugs.freebsd.org/265980 > --00000000000058e00505fb87d970 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I got it. Thanks.

On Fri, May 12, 2023 at 7:45=E2=80=AFPM E= d Maste <emaste@freebsd.org>= ; wrote:

On Fri,= 12 May 2023 at 09:26, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
>
> I don't want to go through the hassle of filling a bug with my ven= dor. I will just wait for you, guys, to update the stand implementation. Th= ank you for explaining to me what causes this issue.

This issue is tracked in PR 265980 if you want to follow it.
https://bugs.freebsd.org/265980

--00000000000058e00505fb87d970-- From nobody Sat May 13 12:26:24 2023 X-Original-To: freebsd-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 4QJPy5466Zz4BKlx for ; Sat, 13 May 2023 12:26:37 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QJPy43NK8z40XD; Sat, 13 May 2023 12:26:36 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=QnSDC5HU; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::72a as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-757756e2eefso392649185a.3; Sat, 13 May 2023 05:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683980795; x=1686572795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9hXk/fFg4WnEslfkG4j5T/bs7yMM3Z4PMKcotaOiSzg=; b=QnSDC5HUbnH7gLFf4sVNGQ36tMvQHm+aNrBNGlJV+i5Fqd2KEtqDroihlbs3/mJUWt blk9ahcai97Xm6ng46xPGogj5aP000emmi8AJrxRF/euzN2Rue+y67rNwo0G6b6uVRo5 zFQger4UDLB+aYyywEBgyEpwvCfFpTSTB5B+HvQNo65fc35NumKinPtsafM3GN7D0/42 cfkzLweGdi1s1ICQW+Cj2eaYfVnLFaYcmifnmvhFTqAN5KMCWt3vgAtLrbGult04OJOP d1zpz2OYphQ9tVuoKM4kralIyMIOW9qIypIWmLguGlsl24Ue+njrrPRfO8xRHfJmwZDq c8mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683980795; x=1686572795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9hXk/fFg4WnEslfkG4j5T/bs7yMM3Z4PMKcotaOiSzg=; b=h+mPFIlasMr1qtQhMxi+rlfy8dHMuOUe8YM/hHw2eKJPY3Aurho2jGk3wukiSd/pf9 +gsYqHvV4FSIcTx/6mXAHSBhm6IEQICd+DA7Df1/QzynPybBen5DePy7EK7cd9JaoZ9n cW3B0W7bgX/nF039XAMeFfUlBWDLGojmSKz2VJ0yYU/kE5FOVJe5OQmExEM75rx16Jnn FqfCpOJL+zY8kHUAKFFzPEh7jeyzu1E4hbGdsFxHlzFpOJQ2063/HfSq/BWy59Umx4NP UZc6Hfo/NpaLEyAuf5oLn/n9IAWLEsK74JmgH96yStWH/mRbtG1NYMPAt1T9Y13nrlSH QPyA== X-Gm-Message-State: AC+VfDyJKbvPOY5A/glGi0kIs8QanONWqKNxjI8UfH36Fr3fX08kIdiQ 6oMt2MmVnxx3xFYECK+oHedA5Dz4PuXnlpsgQICf9DZDceSv4EWe X-Google-Smtp-Source: ACHHUZ5kmUBmhuX3W7SMQvBSmc9LWL3hSabL7fX+QUvFpdH8Jhe2f3Z65bhoZcxkqoYKmPpsYrTpeBISHDkQQ5P78wo= X-Received: by 2002:a05:6214:4018:b0:5df:4d3e:b8e0 with SMTP id kd24-20020a056214401800b005df4d3eb8e0mr36631129qvb.4.1683980795142; Sat, 13 May 2023 05:26:35 -0700 (PDT) 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 References: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com>

In-Reply-To: From: Oleg Lelchuk Date: Sat, 13 May 2023 08:26:24 -0400 Message-ID: Subject: Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard? To: Ed Maste Cc: Toomas Soome , Emmanuel Vadot , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001a670705fb9255b6" X-Spamd-Result: default: False [-2.99 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72a:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_CC(0.00)[me.com,bidouilliste.com,freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QJPy43NK8z40XD X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000001a670705fb9255b6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I've been reading the documentation for loader.efi and it says this: "If there is no ConOut variable, both serial and video are attempted. loader.efi uses the "efi" console for the video (which may or may not work) and "comconsole" for the serial on COM1 at the default baud rate= . The kernel will use a dual console, with the video console primary if = a UEFI graphics device is detected, or the serial console as primary if not." I find this language confusing because I don't know what is meant by "a UEFI graphics device". In my situation, is my Intel Integrated Graphics card an UEFI graphics device? Does it mean that once i915kms is loaded, I no longer deal with UEFI graphics? I think lots of people whose native language is English will find the documentation describing loader.efi confusing. The documentation page also mentions this: "BUGS Systems that do not have a ConOut variable set are not conformant with the standard, and likely have unexpected results." But I think you guys already implied that the UEFI specification doesn't mandate having such a variable. On Fri, May 12, 2023 at 7:55=E2=80=AFPM Oleg Lelchuk wrote: > I got it. Thanks. > > On Fri, May 12, 2023 at 7:45=E2=80=AFPM Ed Maste wro= te: > >> On Fri, 12 May 2023 at 09:26, Oleg Lelchuk wrote= : >> > >> > I don't want to go through the hassle of filling a bug with my vendor. >> I will just wait for you, guys, to update the stand implementation. Than= k >> you for explaining to me what causes this issue. >> >> This issue is tracked in PR 265980 if you want to follow it. >> https://bugs.freebsd.org/265980 >> > --0000000000001a670705fb9255b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I've been reading the documentation for loader.efi and= it says this: "If there is no ConOut variable, both serial and video = are attempted.
=C2=A0 =C2=A0 =C2=A0loader.efi uses the "efi" c= onsole for the video (which may or may not
=C2=A0 =C2=A0 =C2=A0work) and= "comconsole" for the serial on COM1 at the default baud rate.=C2=A0 =C2=A0 =C2=A0The kernel will use a dual console, with the video con= sole primary if a
=C2=A0 =C2=A0 =C2=A0UEFI graphics device is detected, = or the serial console as primary if
=C2=A0 =C2=A0 =C2=A0not."

I= find this language confusing because I don't know what is meant by &qu= ot;a UEFI graphics device". In my situation, is my Intel Integrated Gr= aphics card an UEFI graphics device? Does it mean that once i915kms is load= ed, I no longer deal with UEFI graphics? I think lots of people whose nativ= e language is English will find the documentation describing loader.efi con= fusing. The documentation page also mentions this: "BUGS

=C2=A0 = =C2=A0 =C2=A0Systems that do not have a ConOut variable set are not conform= ant with
=C2=A0 =C2=A0 =C2=A0the standard, and likely have unexpected re= sults." But I think you guys already implied that the UEFI specificati= on doesn't mandate having such a variable.

On Fri, May 12, 2023 at 7:55= =E2=80=AFPM Oleg Lelchuk <olegl= elchuk@gmail.com> wrote:

I got it. Thanks.

On Fri, May 12, 2023 at 7= :45=E2=80=AFPM Ed Maste <emaste@freebsd.org> wrote:
On Fri, 12 May 2023 at 09:26, Oleg Lelchuk <<= a href=3D"mailto:oleglelchuk@gmail.com" target=3D"_blank">oleglelchuk@gmail= .com> wrote:
>
> I don't want to go through the hassle of filling a bug with my ven= dor. I will just wait for you, guys, to update the stand implementation. Th= ank you for explaining to me what causes this issue.

This issue is tracked in PR 265980 if you want to follow it.
https://bugs.freebsd.org/265980

--0000000000001a670705fb9255b6--