Date: Sat, 17 Jun 2023 20:41:51 +0100 From: Nuno Teixeira <eduardo@freebsd.org> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: keyboard doesn't work at Boot Menu Message-ID: <CAFDf7UKZzQ2EO95ac1-tH1jtn9M8R85QrfEoUQUMZRWGvTx6RA@mail.gmail.com> In-Reply-To: <CAFDf7UKZmZZS6aKf=43-A_2eXDHq3%2BPcC3Hqbp1s7umrcJDA_g@mail.gmail.com> References: <CAFDf7ULWff1YNA675-0ZdSgRM-t6RnCHO9RSTshPS0k8xfc6xw@mail.gmail.com> <99542360-6350-4636-A9EA-CA9BBCC93C60@yahoo.com> <CAFDf7U%2B3NR8ETaxg2W9j%2BXkm-sNaCdFSCXNMLA_GmxnRayeZuQ@mail.gmail.com> <5D8D94E2-781D-4945-B721-EDD0BF56A8F2@yahoo.com> <CAFDf7UKZmZZS6aKf=43-A_2eXDHq3%2BPcC3Hqbp1s7umrcJDA_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000e0368505fe587e77 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (...) FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20230615-456c1199d3b3-263574.img doesn't boot either. Same error as above photo. Nuno Teixeira <eduardo@freebsd.org> escreveu no dia s=C3=A1bado, 17/06/2023= =C3=A0(s) 20:19: > I've tryed to boot > FreeBSD-13.2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf4e-255597.img bu= t > it doesn't boot. > Same error as I replace /boot/efi from stable. > > I sent an photo. > > Procedure: > > $ mount | grep msdosfs > $ /dev/gpt/efiboot0 on /boot/efi (msdosfs, local) > > $ mdconfig -t vnode -f > FreeBSD-13.2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf4e-255597.img > $ mount -t msdosfs /dev/md0s1 /mnt > <backup and clean /boot/efi> > $ cd /mnt > $ tar cf - . | ( cd /boot/efi && tar xvf - ) > > (./: Can't restore time: Invalid argument > tar: Error exit delayed from previous errors. > > <cp my config.txt to /boot/efi> > > $ ls -Tld /boot/efi/EFI/*/* > $ -rwxr-xr-x 1 root wheel 1182604 Jun 15 04:47:12 2023 > /boot/efi/EFI/BOOT/bootaa64.efi > > my config.txt: > --- > [all] > arm_64bit=3D1 > #dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don > dtoverlay=3Dmmc > dtoverlay=3Ddisable-bt > device_tree_address=3D0x4000 > kernel=3Du-boot.bin > > [pi4] > hdmi_safe=3D0 > armstub=3Darmstub8-gic.bin > max_framebuffers=3D2 > hdmi_force_hotplug=3D1 > hdmi_group=3D2 > hdmi_drive=3D2 > hdmi_mode=3D82 > disable_overscan=3D1 > # overclock 20210303 > over_voltage=3D6 > arm_freq=3D2000 > sdram_freq_min=3D3200 > force_turbo=3D1 > --- > > Mark Millard <marklmi@yahoo.com> escreveu no dia s=C3=A1bado, 17/06/2023 = =C3=A0(s) > 18:12: > >> On Jun 17, 2023, at 08:52, Nuno Teixeira <eduardo@freebsd.org> wrote: >> >> > Hello Mark! >> >> Hello Nuno. >> >> FYI: My example paths and such are from my main instead of a >> stable/13 context. I may set up a stable/13 snapshot to better >> match your context at some point, but not yet. >> >> >> It is unclear what the context is here: Serial console? No serial >> console? >> >> >> >> What is in /boot/loader.conf ? I've a serial console context and have= : >> >> >> >> boot_multicons=3D"YES" >> >> boot_serial=3D"YES" >> >> >> > rpi4 connected to monitor via hdmi >> > >> > /boot/loader.conf: >> > >> > kern.geom.label.disk_ident.enable=3D"0" >> > kern.geom.label.gptid.enable=3D"0" >> > cryptodev_load=3D"YES" >> > zfs_load=3D"YES" >> > >> >> Is the stable/13 from a specific *.img* file from the likes of: >> >> >> >> http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/?C=3DM&= O=3DD >> >> >> >> ? If yes, which one? If self built, what commit was the build based o= n? >> >> >> >> Has this worked for you before? If yes, based on what commit back whe= n >> >> it last worked? >> >> >> > Instalation is from 13.2-RELEASE and firmware copied from it. >> >> [Note: main has /boot/efi/ as a mount point for the msdosfs. >> Your stable/13 my still have /boot/msdos/ instead. That might >> even depend on the details of how and when the configuration >> was set up. The efi directory in the msdosfs may be named EFI >> or named efi as well. I show/use EFI to make the name distinct >> from main's mount point name, making references clear about >> which.] >> >> The following are from in the msdosfs file system but are >> not from sysutils/rpi-firmware or from >> sysutils/u-boot-rpi-arm64 . (The detailed content, size, >> date, and such will not match any stable/13 details here.) >> >> # ls -Tld /boot/efi/EFI/*/* >> -rwxr-xr-x 1 root wheel 870956 Jun 13 18:24:42 2023 >> /boot/efi/EFI/BOOT/bootaa64.efi >> >> Is your bootaa64.efi the old ones from a 13.2-RELEASE ? >> From a recent stable/13 snapshot? I'll note that: >> >> loader: comconsole: don't unconditionally wipe out hw.uart.console Kyle >> Evans 2023-04-26 >> >> would not be in the old 13.2-RELEASE msdosfs file system >> contents. >> >> In general, you may want to update to be using msdosfs >> content from, say, the most recent stable/13 snaphot >> (preserving any adjustments that you have been making >> to config.txt or the like): >> >> >> http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/FreeBSD-13= .2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf4e-255597.img.xz >> >> But, I'll note that updating BOOT/bootaa64.efi can be >> done just by copying /boot/loader.efi to >> BOOT/bootaa64.efi in the msdosfs. >> >> > I'm tracking STABLE for some time and I'm at >> stable/13-n255602-e6c1e181ba7f >> >> The snapshots contain things in final places that are not >> in those places just by FreeBSD installation or >> installation of ports. Have you been updating bootaa64.efi >> by copying /boot/loader.efi to BOOT/bootaa64.efi in the >> msdosfs? >> >> > Since first instalation that keyboard doesn't work in Boot menu. >> >> Another file that could have relevant content is >> config.txt in the msdosfs. >> >> >> Note: Warner's recent changes to stand/ for the subject area are only >> >> in main [so: 14] so far. So it appears that the only fairly recent >> >> change for such for stable/13 has been: >> >> >> >> loader: comconsole: don't unconditionally wipe out hw.uart.console >> Kyle Evans 2023-04-26 >> >> >> >> =3D=3D=3D >> Mark Millard >> marklmi at yahoo.com >> >> > > -- > Nuno Teixeira > FreeBSD Committer (ports) > --=20 Nuno Teixeira FreeBSD Committer (ports) --000000000000e0368505fe587e77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>(...)</div><div><br></div><div>FreeBSD-14.0-CURRENT-a= rm64-aarch64-RPI-20230615-456c1199d3b3-263574.img doesn't boot either.<= /div><div>Same error as above photo.<br></div></div><br><div class=3D"gmail= _quote"><div dir=3D"ltr" class=3D"gmail_attr">Nuno Teixeira <<a href=3D"= mailto:eduardo@freebsd.org">eduardo@freebsd.org</a>> escreveu no dia s= =C3=A1bado, 17/06/2023 =C3=A0(s) 20:19:<br></div><blockquote class=3D"gmail= _quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204= ,204);padding-left:1ex"><div dir=3D"ltr"><div>I've tryed to boot FreeBS= D-13.2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf4e-255597.img but it doe= sn't boot.</div><div>Same error as I replace /boot/efi from stable.</di= v><div><br></div><div>I sent an photo.<br></div><div><br></div><div>Procedu= re:<br></div><div><br></div><div>$ mount | grep msdosfs<br></div><div>$ /de= v/gpt/efiboot0 on /boot/efi (msdosfs, local)</div><div><br></div><div>$ mdc= onfig -t vnode -f FreeBSD-13.2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf= 4e-255597.img</div><div>$ mount -t msdosfs /dev/md0s1 /mnt</div><div><ba= ckup and clean /boot/efi></div><div>$ cd /mnt<br></div><div>$ tar cf - .= | ( cd /boot/efi && tar xvf - )</div><div><br></div><div>(./: Can&= #39;t restore time: Invalid argument<br>tar: Error exit delayed from previo= us errors.</div><div><br></div><div><cp my config.txt to /boot/efi></= div><div><br></div><div>$ ls -Tld /boot/efi/EFI/*/*<br>$ -rwxr-xr-x =C2=A01= root =C2=A0wheel =C2=A01182604 Jun 15 04:47:12 2023 /boot/efi/EFI/BOOT/boo= taa64.efi</div><div><br></div><div>my config.txt:</div><div>---</div><div>[= all]<br>arm_64bit=3D1<br>#dtparam=3Daudio=3Don,i2c_arm=3Don,spi=3Don<br>dto= verlay=3Dmmc<br>dtoverlay=3Ddisable-bt<br>device_tree_address=3D0x4000<br>k= ernel=3Du-boot.bin<br><br>[pi4]<br>hdmi_safe=3D0<br>armstub=3Darmstub8-gic.= bin<br>max_framebuffers=3D2<br>hdmi_force_hotplug=3D1<br>hdmi_group=3D2<br>= hdmi_drive=3D2<br>hdmi_mode=3D82<br>disable_overscan=3D1<br># overclock 202= 10303<br>over_voltage=3D6<br>arm_freq=3D2000<br>sdram_freq_min=3D3200<br>fo= rce_turbo=3D1</div><div>---<br></div></div><br><div class=3D"gmail_quote"><= div dir=3D"ltr" class=3D"gmail_attr">Mark Millard <<a href=3D"mailto:mar= klmi@yahoo.com" target=3D"_blank">marklmi@yahoo.com</a>> escreveu no dia= s=C3=A1bado, 17/06/2023 =C3=A0(s) 18:12:<br></div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex">On Jun 17, 2023, at 08:52, Nuno Teixeira <<a h= ref=3D"mailto:eduardo@freebsd.org" target=3D"_blank">eduardo@freebsd.org</a= >> wrote:<br> <br> > Hello Mark!<br> <br> Hello=C2=A0 Nuno.<br> <br> FYI: My example paths and such are from my main instead of a<br> stable/13 context. I may set up a stable/13 snapshot to better<br> match your context at some point, but not yet.<br> <br> >> It is unclear what the context is here: Serial console? No serial = console?<br> >> <br> >> What is in /boot/loader.conf ? I've a serial console context a= nd have:<br> >> <br> >> boot_multicons=3D"YES"<br> >> boot_serial=3D"YES"<br> >> <br> > rpi4 connected to monitor via hdmi<br> > <br> > /boot/loader.conf:<br> > <br> > kern.geom.label.disk_ident.enable=3D"0"<br> > kern.geom.label.gptid.enable=3D"0"<br> > cryptodev_load=3D"YES"<br> > zfs_load=3D"YES"<br> >=C2=A0 <br> >> Is the stable/13 from a specific *.img* file from the likes of:<br= > >> <br> >> <a href=3D"http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGE= S/13.2/?C=3DM&O=3DD" rel=3D"noreferrer" target=3D"_blank">http://ftp3.f= reebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/?C=3DM&O=3DD</a><br> >> <br> >> ? If yes, which one? If self built, what commit was the build base= d on?<br> >> <br> >> Has this worked for you before? If yes, based on what commit back = when<br> >> it last worked?<br> >> <br> > Instalation is from 13.2-RELEASE and firmware copied from it.<br> <br> [Note: main has /boot/efi/ as a mount point for the msdosfs.<br> Your stable/13 my still have /boot/msdos/ instead. That might<br> even depend on the details of how and when the configuration<br> was set up. The efi directory in the msdosfs may be named EFI<br> or named efi as well. I show/use EFI to make the name distinct<br> from main's mount point name, making references clear about<br> which.]<br> <br> The following are from in the msdosfs file system but are<br> not from sysutils/rpi-firmware or from<br> sysutils/u-boot-rpi-arm64 . (The detailed content, size,<br> date, and such will not match any stable/13 details here.)<br> <br> # ls -Tld /boot/efi/EFI/*/*<br> -rwxr-xr-x=C2=A0 1 root=C2=A0 wheel=C2=A0 870956 Jun 13 18:24:42 2023 /boot= /efi/EFI/BOOT/bootaa64.efi<br> <br> Is your bootaa64.efi the old ones from a 13.2-RELEASE ?<br> >From a recent stable/13 snapshot? I'll note that:<br> <br> loader: comconsole: don't unconditionally wipe out hw.uart.console Kyle= Evans 2023-04-26<br> <br> would not be in the old 13.2-RELEASE msdosfs file system<br> contents.<br> <br> In general, you may want to update to be using msdosfs<br> content from, say, the most recent stable/13 snaphot<br> (preserving any adjustments that you have been making<br> to config.txt or the like):<br> <br> <a href=3D"http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/Fr= eeBSD-13.2-STABLE-arm64-aarch64-RPI-20230615-894492f5bf4e-255597.img.xz" re= l=3D"noreferrer" target=3D"_blank">http://ftp3.freebsd.org/pub/FreeBSD/snap= shots/ISO-IMAGES/13.2/FreeBSD-13.2-STABLE-arm64-aarch64-RPI-20230615-894492= f5bf4e-255597.img.xz</a><br> <br> But, I'll note that updating BOOT/bootaa64.efi can be<br> done just by copying /boot/loader.efi to<br> BOOT/bootaa64.efi in the msdosfs.<br> <br> > I'm tracking STABLE for some time and I'm at stable/13-n255602= -e6c1e181ba7f <br> <br> The snapshots contain things in final places that are not<br> in those places just by FreeBSD installation or<br> installation of ports. Have you been updating bootaa64.efi<br> by copying /boot/loader.efi to BOOT/bootaa64.efi in the<br> msdosfs?<br> <br> > Since first instalation that keyboard doesn't work in Boot menu.<b= r> <br> Another file that could have relevant content is<br> config.txt in the msdosfs.<br> <br> >> Note: Warner's recent changes to stand/ for the subject area a= re only<br> >> in main [so: 14] so far. So it appears that the only fairly recent= <br> >> change for such for stable/13 has been:<br> >> <br> >> loader: comconsole: don't unconditionally wipe out hw.uart.con= sole Kyle Evans 2023-04-26<br> >> <br> <br> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer" target=3D"_blank= ">yahoo.com</a><br> <br> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l= tr"><span style=3D"color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committ= er (ports)</span></div></div> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"l= tr"><span style=3D"color:rgb(102,102,102)">Nuno Teixeira<br>FreeBSD Committ= er (ports)</span></div></div> --000000000000e0368505fe587e77--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7UKZzQ2EO95ac1-tH1jtn9M8R85QrfEoUQUMZRWGvTx6RA>