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--