From nobody Mon May 15 12:22:12 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 4QKdmL0Hknz4BY7s for ; Mon, 15 May 2023 12:22:26 +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 4QKdmK2TF0z4GPj; Mon, 15 May 2023 12:22:25 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Bke8WtiM; spf=pass (mx1.freebsd.org: domain of oleglelchuk@gmail.com designates 2607:f8b0:4864:20::f30 as permitted sender) smtp.mailfrom=oleglelchuk@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-61b71b7803bso60449136d6.1; Mon, 15 May 2023 05:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684153344; x=1686745344; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Up7TcZl8W/95wZTJ18bIu/9SJuJNw6vfTwiHuzq0nhI=; b=Bke8WtiMpqBTK4kHICEGsd0Eo5IHETSf2tz2Z6N5+VmjFwQLqEtMppEHUUccnsPxJM wBUCMXahf8Cv5rvMeI9sGTgG+Qsaxp4cU3Aq79yXH4at5RJuyzLYj/1tPpDrpwP03C7o equezY9gTx2WoD2o7KCB3MzRjvF99NlQDJz8sgBvcbPtU7fqL8/9EkK08dw4q0EPt4yN 39PygXn5ctCuwDC9HR64f1IqCRQs034NnTIIVtO2vzvLCg6PANFkpX5fqAUogrVXIJKf pGj71xbJieHw86UvnSzfaPXAVxBEbBSEM/Tl4UnYKSz+La4BqicyW39Hj2uRkMA87c8+ s0Cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684153344; x=1686745344; 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=Up7TcZl8W/95wZTJ18bIu/9SJuJNw6vfTwiHuzq0nhI=; b=U911UOyw+haZTdhte3v/2Dmwkl+C5aMHW6vHqeT4e1XAu6ojjNWYydULsSIFBLbwBA dbhwmEklFVdoKtNLnGdhoE5xb1SuLhIuf5nwN6gSeqfiI7v0lcoBfHj+GB8r2hICTFLP DQEoGOSQrtCfhfVLhMx6dWlq0zihjL7V3LNkGhEdQ8TusMAqp6cqKEiGiK1A/jbOd5gk TewqgqGMZDmA/794m936HMqXy6KrHOyF5KiGH21gr+mb8LtZea3rb08U429qmg0YRs/P mr6TvVEv2YO6+2WeclYZO7zTKnPwW4T7lLzkUm/fN3sOZ80HEeVqNYaW/DffiaXgTBI0 2FeQ== X-Gm-Message-State: AC+VfDx57WR4YpXV38vZencKT0bgHV8YzZVUBvrdr+bmbncoeYDGxngN vFfXAOvCgum+mBwFmpmD5XyAdP4XlgYgVifaQixb2KsxKNRKSQ== X-Google-Smtp-Source: ACHHUZ5IVZ84ov6AwkXiXceIAJmcxCKDLRv24UUSo8Liayme5IZ9/dt1MwGKi83zlMa4wMQ6MSiO4KxXFqGAGO+SC00= X-Received: by 2002:a05:6214:27c7:b0:621:712c:fa03 with SMTP id ge7-20020a05621427c700b00621712cfa03mr18091880qvb.44.1684153344468; Mon, 15 May 2023 05:22:24 -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: Mon, 15 May 2023 08:22:12 -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: Ed Maste , Toomas Soome , Emmanuel Vadot , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000d82b4f05fbba817e" X-Spamd-Result: default: False [-2.15 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; 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]; NEURAL_HAM_SHORT(-0.15)[-0.150]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f30:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_CC(0.00)[freebsd.org,me.com,bidouilliste.com] X-Rspamd-Queue-Id: 4QKdmK2TF0z4GPj X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000d82b4f05fbba817e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Adding screen.font=3D"16=C3=9732" to loader.conf fixed that tiny issue ment= ioned in the previous email message... I find it a bit surprising that I only had to make one tiny change to the source code of stand to make the graphical logo appear, to start playing with the EFI resolution, and etc. On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk wrote: > Okay, so I edited /usr/src/stand/efi/loader/main.c , and I replaced ConOu= t > with ConIn in this line: rv =3D efi_global_getenv("ConIn", buf, &sz); . N= ow I > am able to see the beautiful graphical logo in the efi boot menu! But why > are the boot menu and the logo shown in the top left corner of my compute= r > screen? My monitor is 1080p and the setting efi_max_resolution=3D1080p in > loader.conf only affects what happens after the kernel starts booting up, > but it doesn't affect what happens before it: the boot menu and the logo > remain in the top left corner of the screen. Why is this the case? You ca= n > see the photo in the provided attachment... And thank you, guys, for your > work! > > On Sat, May 13, 2023 at 9:35=E2=80=AFAM Warner Losh wrot= e: > >> >> >> On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk wrote= : >> >>> I've been reading the documentation for loader.efi and it says this: "I= f >>> 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. >>> >> >> That's unclear. The standard refers to it many times. Earlier versions >> especially. It doesn't say it's optional, unlike some other variables. Y= et >> later versions don't say it's mandatory. I've yet to own or use a syste= m >> without it... such systems exist but they are quite new... >> >> Warner >> >> 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 = 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 implement= ation. >>>>> 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 >>>>> >>>> --000000000000d82b4f05fbba817e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Adding screen.font=3D"16=C3=9732" to loader.con= f fixed that tiny issue mentioned in the previous email message... I find i= t a bit surprising that I only had to make one tiny change to the source co= de of stand to make the graphical logo appear, to start playing with the EF= I resolution, and etc.

On Sun, May 14, 2023, 8:58 AM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
=
Okay, so I edited /us= r/src/stand/efi/loader/main.c , and I replaced ConOut with ConIn in this li= ne:=C2=A0rv =3D efi_global_getenv("ConIn", buf, &sz); . Now I= am able to see the beautiful graphical logo in the efi boot menu! But why = are the boot menu and the logo shown in the top left corner of my computer = screen? My monitor is 1080p and the setting efi_max_resolution=3D1080p in l= oader.conf only affects what happens after the kernel starts booting up, bu= t it doesn't affect what happens before it: the boot menu and the logo = remain in the top left corner of the screen. Why is this the case? You can = see the photo in the provided attachment... And thank you, guys, for your w= ork!

On Sat, May 13, 2023 at 9:35=E2=80=AFAM Warner Losh <imp@bsdimp.com&= gt; wrote:


On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk <oleglelch= uk@gmail.com> wrote:
I've been reading the documentation for lo= ader.efi and it says this: "If there is no ConOut variable, both seria= l and video are attempted.
=C2=A0 =C2=A0 =C2=A0loader.efi uses the "= ;efi" console for the video (which may or may not
=C2=A0 =C2=A0 =C2= =A0work) and "comconsole" for the serial on COM1 at the default b= aud rate.
=C2=A0 =C2=A0 =C2=A0The kernel will use a dual console, with t= he video console primary if a
=C2=A0 =C2=A0 =C2=A0UEFI graphics device i= s 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 "a UEFI graphics device". In my situation, is my Intel I= ntegrated Graphics card an UEFI graphics device? Does it mean that once i91= 5kms is loaded, I no longer deal with UEFI graphics? I think lots of people= whose native language is English will find the documentation describing lo= ader.efi confusing. The documentation page also mentions this: "BUGS=C2=A0 =C2=A0 =C2=A0Systems that do not have a ConOut variable set are = not conformant with
=C2=A0 =C2=A0 =C2=A0the standard, and likely have un= expected results." But I think you guys already implied that the UEFI = specification doesn't mandate having such a variable.

That's uncle= ar. The standard refers to it many times. Earlier versions especially. It d= oesn't say it's optional, unlike some other variables. Yet later ve= rsions don't say it's mandatory.=C2=A0 I've yet to own or use a= system without it... such systems exist but they are quite new...

Warner
On Fri, May 12, 2023 at 7:55=E2=80=AFPM Oleg Lelchuk <= oleglelchuk@gmail.com> wrote:
I got it. Thanks.
=
On Fri= , May 12, 2023 at 7:45=E2=80=AFPM Ed Maste <emaste@freebsd.or= g> wrote:
On Fri, 12 May 2023 at 09:26, Oleg Lelchuk <oleglelchuk@g= mail.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
--000000000000d82b4f05fbba817e--