From owner-freebsd-current@freebsd.org Thu Jan 14 21:34:29 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C016B4EE65F for ; Thu, 14 Jan 2021 21:34:29 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DGyJ466JVz3GMG for ; Thu, 14 Jan 2021 21:34:28 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f51.google.com with SMTP id i6so6622490otr.2 for ; Thu, 14 Jan 2021 13:34:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+Gk6EUWcFvWyjl4qFQlU0/j7vP4P9lUfIfaW72g+eFk=; b=BRqcLvHewMMTzzm3c1iLQsqp3gUdmKftwpB/Jx02dw3ViTa2BWDN2QRTWy0HjRr2Uj ZykA2fxRyzJBB4bilFPjOhMownPpHDpO6DytPuee1TF919bTCsEqtIMTznrLs1avklxH JZXlaF5Jd8cBetGpyAa4HoX2o3A0N6hiQNHEMZxZA6CQ0jlZ/Kh+Cbvmq6ziH+ASrkIX Pw+RHyxzs08FGt0M7M4qr5CBSjS8gnCx4PKj5rWjaiq4VzrsDY5mfsS+OPeGXh0kn9b1 PEVQIeCG+nYvLxCcAnuDlWl2UKNnTDnnIRNRynF3KpaVoWVPS9eQ4b9CQJxbtKgMo53r j95A== X-Gm-Message-State: AOAM532qNkKPBLB3ytJQ3GjHJptlJ+RaBfRgsr42rEgpMLe44/z2wW8N 3+DMpJaSJEXYKHwJuHSLK7tdyXFjj8ukk7v6gTUWC/2TNWo= X-Google-Smtp-Source: ABdhPJweomVwxZm96HhCyYp2OWy5PXDrgDwVjVQtr3/aIEn1v4jnTjg3ymxLHstfRAUfbXYg3TFuV1ZfAL8rYHUUYUM= X-Received: by 2002:a05:6830:30a8:: with SMTP id g8mr5775605ots.291.1610660067454; Thu, 14 Jan 2021 13:34:27 -0800 (PST) MIME-Version: 1.0 References: <83EB3B04-EAE8-4EC3-820B-2F5C3BADE948@me.com> <66908803-BA6F-4538-9D93-6F85A95108C9@me.com> <831788F9-F97F-4A02-A6F9-AE05219DA2E9@me.com> In-Reply-To: From: Alan Somers Date: Thu, 14 Jan 2021 14:34:16 -0700 Message-ID: Subject: Re: boot loader blank screen To: Jakob Alvermark Cc: FreeBSD CURRENT X-Rspamd-Queue-Id: 4DGyJ466JVz3GMG X-Spamd-Bar: / X-Spamd-Result: default: False [-1.00 / 15.00]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.51:from]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.51:from]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; SPAMHAUS_ZRD(0.00)[209.85.210.51:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.51:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Thu, 14 Jan 2021 21:34:29 -0000 Is there a bugzilla issue for this yet? It's affecting a lot of people, and it will be easier for us to monitor progress with Bugzilla than with the mailing list. -Alan On Thu, Jan 14, 2021 at 12:15 AM Jakob Alvermark wrote: > > On 1/14/21 4:49 AM, monochrome wrote: > > I should add my experience to this since its different and haven't > > seen anyone else mention it. > > I see the new boot loader, it's not blank, but its large text, and > > it's very SLOW. > > I can see each char drawn, and then when it gets to the bottom and has > > to redraw all the lines to scroll up for new lines, it loads so slowly > > it's like watching an 8086 on a 300 baud modem, or slower! Takes like > > an extra 30 seconds to get through all the loaded modules, then back > > to normal speed boot with the same large font. > > > > added these lines and everything is back to normal with new appearance > > and small font like before, and at normal speed. > > hw.vga.textmode="0" > > vbe_max_resolution=1280x800 > > > > also removed the old lines for the amdgpu efi problem with no effect > > so I assume those are no longer necessary and why I'm seeing this change? > > #hw.syscons.disable=1 > > #kern.vty=vt > > #hw.vga.textmode=1 > > > > am using X and everything seems fine for now > > > > system: > > AMD Ryzen 5 2400G, using integrated vega GPU > > ASRock B450M Pro4 > > 13-current > > > > > > > > On 1/5/21 8:54 PM, David Wolfskill wrote: > >> On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > >>> ... > >>>> the 58661b3ba9eb should hopefully fix the loader text mode issue, > >>>> it would be cool if you can verify:) > >>>> > >>>> thanks, > >>>> toomas > >>> > >>> I think, I got it fixed (at least idwer did confirm for his system, > >>> thanks). If you can test this patch: > >>> > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch > >>> < > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch> > > >>> it would be really nice. > >>> > >>> thanks, > >>> toomas > >> > >> I tested with each of the following "stanzas' in /boot/loader.conf, > >> using vt (vs. syscons) in each case (though that breaks video reset > >> on resume after suspend): > >> > >> # hw.vga.textmode="0" > >> vbe_max_resolution=1280x800 > >> > >> This works, and provides a graphical console (depth 32). > >> > >> > >> hw.vga.textmode="0" > >> # vbe_max_resolution=1280x800 > >> > >> This also works, and provides a low-resolution (and depth 16) > >> graphical console (800x320 or something similar, IIRC). > >> > >> > >> # hw.vga.textmode="0" > >> # vbe_max_resolution=1280x800 > >> > >> (That is, not specifying anything for hw.vga.textmode or > >> vbe_max_resolution.) > >> > >> This boots OK, but I see no kernel probe messages or single- to > >> multi-user mode messages. I can use (e.g.) Ctl+Alt+F2 to switch to > >> vty1, see a "login: " prompt, and that (also) works. (This is the > >> initial symptom I had reported.) > >> > >> > >> hw.vga.textmode="1" > >> # vbe_max_resolution=1280x800 > >> > >> This works -- boots OK, and I see kernel probe (&c.) messages; this is a > >> text console (mostly blue text; some white, against a dark background. > >> It's a medium-light blue, so it's easy enough to read (unlike a navy > >> blue, for example). > >> > >> > >> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #113 > >> main-c255601-g9fd96b416c45-dirty: Tue Jan 5 17:24:45 PST 2021 > >> root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > >> amd64 > > > +1 on the slowness. > > I like the graphics mode, it's very pretty. > > But slow. It seems to depend a lot on the screen resolution. On my small > laptop, 1366x768, it's fairly OK. On the 1080p laptop it is very much > slower, it takes about 35 seconds longer compared to the old loader. > > Booting on a 4K monitor, well, I didn't time it... > > > Jakob > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >