Date: Wed, 26 Jun 2024 10:02:39 +0100 From: Andrew Turner <andrew@fubar.geek.nz> To: Mark Millard <marklmi@yahoo.com> Cc: "Anantharam, Arjun" <arjun.anantharam@intel.com>, Warner Losh <imp@bsdimp.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD OS installation stuck after selecting Boot installer Message-ID: <9FA9D2D4-E36E-415E-A55F-F711F5E5FAE2@fubar.geek.nz> In-Reply-To: <FCDC489E-03D4-4DB0-85C5-086BDE6FBB18@yahoo.com> References: <9BE6FB50-27DC-453E-B915-131D45C901CD.ref@yahoo.com> <9BE6FB50-27DC-453E-B915-131D45C901CD@yahoo.com> <MW3PR11MB4761B4889AFA6C18AB31BFDE80C92@MW3PR11MB4761.namprd11.prod.outlook.com> <CANCZdfrWofc-e=9_-wf=ose64w1y2fyg8Y%2BVWAC58JJV3q7vuQ@mail.gmail.com> <MW3PR11MB4761223785D1EFC855D7148280C92@MW3PR11MB4761.namprd11.prod.outlook.com> <MW3PR11MB47614BE548FC663F56011C0F80C92@MW3PR11MB4761.namprd11.prod.outlook.com> <MW3PR11MB4761A8E40EA013CA1AE9EA4980CB2@MW3PR11MB4761.namprd11.prod.outlook.com> <MN2PR11MB4758E974AFEA6AAB15DD240B80D62@MN2PR11MB4758.namprd11.prod.outlook.com> <FCDC489E-03D4-4DB0-85C5-086BDE6FBB18@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 26 Jun 2024, at 02:18, Mark Millard <marklmi@yahoo.com> wrote: >=20 >=20 > On Jun 25, 2024, at 17:44, Anantharam, Arjun = <arjun.anantharam@intel.com> wrote: >=20 >> I was able to make some more progress with the boot loader cmd: >>=20 >> set hw.uart.console=3D"mm:0x2058400000,rs:2"=20 >> However, with the .iso image i ran into this issue: >>=20 >> <image.png> Your emails don=E2=80=99t seem to be making it to the list as it=E2=80=99s= likely the images are too large. >=20 > That .png showed that you are tryin got boot 13_2_RELEASE_AARCH64_CD, > which has its 13.2 EoL on: June 30, 2024 >=20 > You may want to try 13.3 or some other Release that has significantly > more time before its EoL (no support). (But you already tried a main > [15] build below.) >=20 >> And with the .img (memstick image) file, kernel panics were seen: >=20 > This is not a boot of the same release, in fact it is a > boot of main [15] from early June, instead of a release. >=20 >> OK boot >> Loading kernel... >> /boot/kernel/kernel text=3D0x318 text=3D0x97e6d8 text=3D0x2b4130 = data=3D0x166e60 data=3D0x >> 0+0x370000 0x8+0x1652e8+0x8+0x196120 >> Loading configured modules... >> can't find '/etc/hostid' >> can't find '/boot/entropy' >> No valid device tree blob found! >> WARNING! Trying to fire up the kernel, but no device tree blob found! >> ---<<BOOT>>--- >> GDB: no debug ports present >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> Type Physical Virtual #Pages Attr >> ConventionalMemory 0040e0000000 000000000000 002a0000 WC WT WB=20 >> Reserved 004400000000 000000000000 00000700 WC WT WB=20 >> RuntimeServicesData 004400700000 004400700000 00000100 WC WT WB = RUNTIME ... >> Reserved 004400700000 004400700000 00000010 WB RUNTIME Why do the ACPI tables list the same address space twice? >> MAP 4400700000 mode 2 pages 256 >> MAP 44b6940000 mode 2 pages 32 >> MAP 44b6b60000 mode 2 pages 128 >> MAP 44b6c20000 mode 2 pages 80 >> MAP 44b6c70000 mode 2 pages 80 >> MAP 44b6cf0000 mode 2 pages 80 >> MAP 44b6d40000 mode 2 pages 80 >> MAP 44b6d90000 mode 2 pages 80 >> MAP 44b6de0000 mode 2 pages 80 >> MAP 44b6e40000 mode 2 pages 80 >> MAP 44b6e90000 mode 2 pages 80 >> MAP 44b6ee0000 mode 2 pages 80 >> MAP 44b6f30000 mode 2 pages 80 >> MAP 44bbf50000 mode 2 pages 64 >> MAP 44bbfa0000 mode 2 pages 80 >> MAP 4400700000 mode 2 pages 16 >> panic: efi_1t1_l3: Already mapped: va 0x4400700000 *pt 0x4400700f0b This is complaining that the kernel is trying to map memory it already = mapped. As a workaround you can disable the EFI runtime you can try = setting =E2=80=9Cefi.rt.disabled=3D1=E2=80=9D in loader to disable the = use of these services. Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9FA9D2D4-E36E-415E-A55F-F711F5E5FAE2>