From owner-freebsd-current@freebsd.org Wed Apr 4 04:23:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0961F8D738 for ; Wed, 4 Apr 2018 04:23:07 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50CEA87684; Wed, 4 Apr 2018 04:23:07 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id d6so22667516iog.1; Tue, 03 Apr 2018 21:23:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+j//cLfi5u6G80UlaN+sYZs9F6Uaser6Gkf4pLIrfZE=; b=BsAHaUrnpruqaEF6LHbG+eX0klkn7pTSy4+Rb+vbR6aDgwgelctHP2raQHvMPFF9Qd q4oFUoW4et/zOMuNrXUYHu6ZdGMuUqoMQGrwZAT3ZHgiq9LldAfM5WVXQWnu9DLO9FPf SeDzz+j6Jya08Yxp5DrSPfqw7V7OJKBUcHXxHfG9TtyJHXc4QsFUScVAemSEH0fya4Kn 8i/dPsmYQx1I/4n8ZE4PJuPyYlMCN6j/MQZQKq2YNNRGLcWaxu3vuotK/81Km+j5FpgZ flE39Tba3zIbqd3arb5gxXF54yipl9fsKqiFXx2LxTsr1GCojZpeVGF3NvA96JOH5KTi SDQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+j//cLfi5u6G80UlaN+sYZs9F6Uaser6Gkf4pLIrfZE=; b=DgP2g+6/C9GABPodQi5ONUpK8CoeRQM0Gulc1zW5Nw8OWbl8XUItJbGoR70aBXwI8T 3xkNC2x/j0i9osgAc4PbhPDz+H9Y3B7gglXFm1gDQC1TPFDHzjk5Dec5W8UGwPD8yteN /4Yn6x2/P+cXyHWaFz7ctM2LAEufFvVcDzMhx7/y7exP00uyFOCWp/KBWdJFoys3pQ0L ArLfQH2nb7eVAfhvnaJXoCglEOgfKPgXZRCfCqgcBGSFWLImmGIC8CftUtFYgP1/mOOj nnSN17uOpDGAndtEH2mdvjsH/LFw0W2NpKKR0d8NAF5HodNowX82miott69ihys9+MnX I8Lg== X-Gm-Message-State: ALQs6tCNDe2boD8IrUi+wDnRO2p3GXrC7TaYz8x1Gjn401iUaW2iQ6d+ heQKWtwzhkvZK/08ryWpUBoDw8+rfYqZbYwY1w== X-Google-Smtp-Source: AIpwx4/uKKRqLy1Rf8/lUSVKjZzmRzjD65xyv4LBCD60z4WiMzR1phFbkm2Tv0kPPRvZFXsdRurrQ30Mzstl9qy2FkE= X-Received: by 10.107.8.32 with SMTP id 32mr14077961ioi.136.1522815786336; Tue, 03 Apr 2018 21:23:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.192.139.243 with HTTP; Tue, 3 Apr 2018 21:23:05 -0700 (PDT) In-Reply-To: References: <5f663141-433c-951d-a350-7369b004415f@alvermark.net> <20180322225644.1480251c4547ce30f3d88de9@dec.sakura.ne.jp> <20180401213831.1535c7511c1d95a258318bc7@dec.sakura.ne.jp> From: Zaphod Beeblebrox Date: Wed, 4 Apr 2018 00:23:05 -0400 Message-ID: Subject: Re: Call for Testing: UEFI Changes To: Kyle Evans Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2018 04:23:08 -0000 If you're thinking on it, you should know that the DVD version works. The difference, AFAICT, is that it simply calls loader.efi directly. Ie: bootx64.efi is loader.efi, not boot1.efi. Loader.efi doesn't seem to change the screen mode when it starts. When the kernel starts afterwards, this all just works. I assume loader.efi works here because CD9660 is a format supported by EFI. Thus loader.efi can directly read it. That and/or loader can work with the device is was started from. When I start boot1.efi on this system, it changes mode, then it continues. ... so if you've got a boot1.efi that doesn't change mode, can you post that binary for me to try ... ? On Tue, Apr 3, 2018 at 4:48 PM, Kyle Evans wrote: > On Tue, Apr 3, 2018 at 3:17 PM, Kyle Evans wrote: > > Hi, > > > > Right- so, `gop set 0` should've immediately cleared your screen and > > put it into 1920x1080, full stop. If it did not, I think that's > > indicative of some kind of interestingly broken firmware... > > > > Regardless! We're clearly bad at trying to set a mode before the > > kernel starts, so r331904 sets the default max resolution in such a > > way that we just don't change the resolution by default anymore and > > interested parties can bump that up if they want to try it. This > > Thursday's snapshots should have this included. > > After reviewing the video again and discussing it with manu, I don't > think that commit's going to solve your problem at all... we'll need > to re-think this one a bit more. > > > I think if we're going to change modes as a default, we should have > > some way for vt/efifb to use EFIRT or be notified by EFIRT of > > supported resolutions so that vt/efifb can hopefully just handle it > > all and do it properly. This approach would be more similar I guess to > > how KMS drivers operate, and less fragile than what we're seeing with > > these different approaches we've taken. > > >