Re: FreeBSD OS installation stuck after selecting Boot installer
Andrew Turner <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
> On 26 Jun 2024, at 02:18, Mark Millard <[email protected]> wrote: > > > On Jun 25, 2024, at 17:44, Anantharam, Arjun <[email protected]> wrote: > >> I was able to make some more progress with the boot loader cmd: >> >> set hw.uart.console="mm:0x2058400000,rs:2" >> However, with the .iso image i ran into this issue: >> >> <image.png> Your emails don’t seem to be making it to the list as it’s likely the images are too large. > > That .png showed that you are tryin got boot 13_2_RELEASE_AARCH64_CD, > which has its 13.2 EoL on: June 30, 2024 > > 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.) > >> And with the .img (memstick image) file, kernel panics were seen: > > 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. > >> OK boot >> Loading kernel... >> /boot/kernel/kernel text=0x318 text=0x97e6d8 text=0x2b4130 data=0x166e60 data=0x >> 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 >> Reserved 004400000000 000000000000 00000700 WC WT WB >> 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 “efi.rt.disabled=1” in loader to disable the use of these services. Andrew