From nobody Sat May 13 13:35: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 4QJRTT5ZqXz4BNcf for ; Sat, 13 May 2023 13:35:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 4QJRTT38wzz47LF for ; Sat, 13 May 2023 13:35:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-50bcb4a81ceso19330964a12.2 for ; Sat, 13 May 2023 06:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1683984924; x=1686576924; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=R4OoyYzsNdu4CKH6/RyOOvFI7BTf0GoivjaxHjNuGBo=; b=F5CQu7b8KAeizO0rcJiseE9XAdQ8NLV36wZZg+f5AGSO00CnAr9Q76xEDwZIpA8bE0 LaM40xea6XvtBhAuRTW2noL40SJPWgtcfJ/n4FvZnYTCVVESu+fj9/nCQ8RyvUyO0yKk wKbqaOVPpkecQl+4hDwk423VgeR0kGWXackz9/1KajTXMSxrH18oy89x57SknpuazQN1 vtfrn0D7fhitcFZAUm0bwceU62Hmfdou5rirODe2BwxMt7hE4AFQ4TrBwy00ZHiEtemY +X8WZma7Zbyso3WLa/rbXcVCFNlWUftphK9GXnRkEH0t06lUHzi1Y74eb0GFW6jINh+F +PBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683984924; x=1686576924; 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=R4OoyYzsNdu4CKH6/RyOOvFI7BTf0GoivjaxHjNuGBo=; b=fgdWH+UX22b0cdESzyXOPVvffFWOvahad0UWhhzI/Ko8bA460aEJr3VOWUUP1BFvg1 AU3GB7+RCo1IQcx5EY0tXu27+iVjGHUfNgg9X3D+hDAXCzJBAzzqVdYitngE/UfSZqDD sgV/5MzdvRnv+xsXVD83geG0FTnISlrall0J97VfZfY8RXrJzGXBdm6Ps3ekEVGx1R9J dX4dxnXaTxIjJpwekfLgVCCk3ure2DszYdo9chBE4eJh3dJY/k6pQu8UREG4o9QvqUuN nTCxjYX3XbUTnWaMKga+7UWCJaLQhgXuziY2m4Ep6Ad369d2sl4g6izmm6Um14TsIAyA Ckyg== X-Gm-Message-State: AC+VfDyJmhitBp4Sh3xYNh5iQok1jdi9Zen4JKd70aSMPVQV/Q72es3E zcES75GtVfkgvMMa8b0AqaAJklp3DYUQaYkiS9KaLQ== X-Google-Smtp-Source: ACHHUZ7LT7aU/+ZGRTAvXCFa3Ku2rDbKx/pidFl5mjmPsmgyNj9qrVUYqEbPBDk0BJmGpa6H3wOTzqOEcwV5Ks1wc0w= X-Received: by 2002:a17:907:94d3:b0:96a:58a:6cd8 with SMTP id dn19-20020a17090794d300b0096a058a6cd8mr15824796ejc.9.1683984923721; Sat, 13 May 2023 06:35: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: <3B658415-3AD0-4E8B-8CBE-F13FA70CBDC8@me.com> <20230512070557.859671981b7c616c0da7d666@bidouilliste.com> <4F0D21B1-58B6-413D-8499-11AF0E338C78@me.com> In-Reply-To: From: Warner Losh Date: Sat, 13 May 2023 07:35:12 -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: Ed Maste , Toomas Soome , Emmanuel Vadot , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000002f95f405fb934b0f" X-Rspamd-Queue-Id: 4QJRTT38wzz47LF 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 --0000000000002f95f405fb934b0f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk wrote: > 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 no= t > 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 i= f > a > UEFI graphics device is detected, or the serial console as primary i= f > 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 wi= th > 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. Yet later versions don't say it's mandatory. 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 wrote: > >> I got it. Thanks. >> >> On Fri, May 12, 2023 at 7:45=E2=80=AFPM Ed Maste wr= ote: >> >>> 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. Tha= nk >>> 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 >>> >> --0000000000002f95f405fb934b0f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, May 13, 2023, 6:26 AM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:
<= /div>
I've been reading = the documentation for loader.efi and it says this: "If there is no Con= Out variable, both serial and video are attempted.
=C2=A0 =C2=A0 =C2=A0l= oader.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 baud rate.
=C2=A0 =C2=A0 =C2=A0The kernel will us= e a dual console, with the video console 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 "a UEFI graphics device". In my= situation, is my Intel Integrated Graphics card an UEFI graphics device? D= oes it mean that once i915kms is loaded, I no longer deal with UEFI graphic= s? I think lots of people whose native language is English will find the do= cumentation describing loader.efi confusing. The documentation page also me= ntions 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 sta= ndard, and likely have unexpected results." But I think you guys alrea= dy implied that the UEFI specification doesn't mandate having such a va= riable.

That's unclear. The standard refers to it many times. Earlier= versions especially. It doesn't say it's optional, unlike some oth= er variables. Yet later versions don't say it's mandatory.=C2=A0 I&= #39;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 Lelch= uk <oleglelchuk@gmail.com> wrote:
I got it. Thanks.
On Fri, = May 12, 2023 at 7:45=E2=80=AFPM Ed Maste <emaste@freebsd.org> wro= te:
On Fri, 12 M= ay 2023 at 09:26, Oleg Lelchuk <oleglelchuk@gmail.com> wrote:<= br> >
> 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
--0000000000002f95f405fb934b0f--