Date: Wed, 25 Sep 2024 14:03:33 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Thomas Laus <lausts@acm.org> Cc: freebsd-current@freebsd.org Subject: Re: New console output at boot? Message-ID: <554769221.5417.1727265813478@localhost> In-Reply-To: <34ae041a-fe98-4744-be6b-aeea24e25e7b@acm.org> References: <CAN6yY1unczee8d4jkiok4KObGg%2BJkCShU_1WgpKbMPX2SWkX_g@mail.gmail.com> <CANCZdfqWm6ynaB4h2KwWOrvCxCe-j8iowuZoLdv2j_x3eXygeA@mail.gmail.com> <5ee4b852-f2a3-4c87-bcaa-7341e34f8bfe@acm.org> <CANCZdfrW3kqaFPAH1caDyLWdVXSoZ-rEn=Dv2KexwTJa1o%2B13A@mail.gmail.com> <CANCZdfpvC0EtV0wdn2zF=z3HnyCn-zewLxSX50Cjxs4ESAsXQg@mail.gmail.com> <34ae041a-fe98-4744-be6b-aeea24e25e7b@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_5416_343354515.1727265813464 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, Nice work. I did the video trick also in the past with boot issues. Can you tell us what the errors are? Like what filenames are mentioned. Maybe post the screenshot of the video somewhere. My /boot/fonts on raspberry pi 4 15.0-CURRENT contains. $ ls -l /boot/fonts/ total 187 -r--r--r-- 1 root wheel 15355 Jul 7 2023 10x18.fnt.gz -r--r--r-- 1 root wheel 15579 Jul 7 2023 10x20.fnt.gz -r--r--r-- 1 root wheel 16772 Jul 7 2023 11x22.fnt.gz -r--r--r-- 1 root wheel 17078 Jul 7 2023 12x24.fnt.gz -r--r--r-- 1 root wheel 17158 Jul 7 2023 14x28.fnt.gz -r--r--r-- 1 root wheel 20084 Jul 7 2023 16x32.fnt.gz -r--r--r-- 1 root wheel 5874 Jul 7 2023 6x12.fnt.gz -r--r--r-- 1 root wheel 12452 Jul 7 2023 8x14.fnt.gz -r--r--r-- 1 root wheel 6472 Jul 7 2023 8x14v.fnt.gz -r--r--r-- 1 root wheel 12604 Jul 7 2023 8x16.fnt.gz -r--r--r-- 1 root wheel 6536 Jul 7 2023 8x16b.fnt.gz -r--r--r-- 1 root wheel 6568 Jul 7 2023 8x16v.fnt.gz -r--r--r-- 1 root wheel 2087 Aug 26 2023 INDEX.fonts An RPI3 running 14.1-RELEASE has the same filenames with the same sizes but with a date of May 2022. I didn't compare the content of the files. I'm not sure how they end up in that directory. In the FreeBSD sources I could only find share/syscons/fonts which contains some *.fnt files. I don't know if these are the same files as in /boot/fonts. Regards, Ronald. Van: Thomas Laus <lausts@acm.org> Datum: woensdag, 25 september 2024 13:42 Aan: freebsd-current@freebsd.org Onderwerp: Re: New console output at boot? > > On 9/24/24 15:26, Warner Losh wrote: > > > > Thinking about it, I found a hole. If gptzfsboot picked the wrong BE > this could happen. And updating it might fix a bug that's causing it. > Knowing when your system last updated the gptzfsboot would be useful... > > > After getting a hint to use my cellphone camera to capture the error messages, the errors all indicate missing fonts in /boot/fonts. How does this directory get populated when building world? All of the fonts in this directory date back to July 24, 2023 and nothing newer. > > Tom > > -- > Public Keys: > PGP KeyID = 0x5F22FDC1 > GnuPG KeyID = 0x620836CF > > > > ------=_Part_5416_343354515.1727265813464 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body>Hi,<br> <br> Nice work. I did the video trick also in the past with boot issues.<br> <br> Can you tell us what the errors are? Like what filenames are mentioned. Maybe post the screenshot of the video somewhere.<br> <br> My /boot/fonts on raspberry pi 4 15.0-CURRENT contains.<br> $ ls -l /boot/fonts/<br> total 187<br> -r--r--r-- 1 root wheel 15355 Jul 7 2023 10x18.fnt.gz<br> -r--r--r-- 1 root wheel 15579 Jul 7 2023 10x20.fnt.gz<br> -r--r--r-- 1 root wheel 16772 Jul 7 2023 11x22.fnt.gz<br> -r--r--r-- 1 root wheel 17078 Jul 7 2023 12x24.fnt.gz<br> -r--r--r-- 1 root wheel 17158 Jul 7 2023 14x28.fnt.gz<br> -r--r--r-- 1 root wheel 20084 Jul 7 2023 16x32.fnt.gz<br> -r--r--r-- 1 root wheel 5874 Jul 7 2023 6x12.fnt.gz<br> -r--r--r-- 1 root wheel 12452 Jul 7 2023 8x14.fnt.gz<br> -r--r--r-- 1 root wheel 6472 Jul 7 2023 8x14v.fnt.gz<br> -r--r--r-- 1 root wheel 12604 Jul 7 2023 8x16.fnt.gz<br> -r--r--r-- 1 root wheel 6536 Jul 7 2023 8x16b.fnt.gz<br> -r--r--r-- 1 root wheel 6568 Jul 7 2023 8x16v.fnt.gz<br> -r--r--r-- 1 root wheel 2087 Aug 26 2023 INDEX.fonts<br> <br> An RPI3 running 14.1-RELEASE has the same filenames with the same sizes but with a date of May 2022. I didn't compare the content of the files.<br> I'm not sure how they end up in that directory.<br> <br> In the FreeBSD sources I could only find share/syscons/fonts which contains some *.fnt files. I don't know if these are the same files as in /boot/fonts.<br> <br> Regards,<br> Ronald.<br> <br> <p><strong>Van:</strong> Thomas Laus <lausts@acm.org><br> <strong>Datum:</strong> woensdag, 25 september 2024 13:42<br> <strong>Aan:</strong> freebsd-current@freebsd.org<br> <strong>Onderwerp:</strong> Re: New console output at boot?</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="TextPlainViewer" id="P.P">On 9/24/24 15:26, Warner Losh wrote:<br> ><br> > Thinking about it, I found a hole. If gptzfsboot picked the wrong BE > this could happen. And updating it might fix a bug that's causing it. > Knowing when your system last updated the gptzfsboot would be useful...<br> ><br> After getting a hint to use my cellphone camera to capture the error messages, the errors all indicate missing fonts in /boot/fonts. How does this directory get populated when building world? All of the fonts in this directory date back to July 24, 2023 and nothing newer.<br> <br> Tom<br> <br> -- <br> Public Keys:<br> PGP KeyID = 0x5F22FDC1<br> GnuPG KeyID = 0x620836CF<br> </div> <hr></div> </blockquote> <br> </body></html> ------=_Part_5416_343354515.1727265813464--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?554769221.5417.1727265813478>