Re: FreeBSD OS installation stuck after selecting Boot installer

If the screenshots are not visible, i have included below errors seen in screenshot:

From 1st screenshot(below errors seen during FreeBSD installation after selecting Boot installer):
Loading kernel..
Loading configured modules..
cant find 'etc/hostid'
cant find 'boot/entropy'
No valid device tree blob found!
Warning! Trying to fire up the kernel, but no device tree blob found!

"Garbage displayed"

From 2nd Screenshot:
ACPI option enabled by default in FreeBSD



________________________________
From: Anantharam, Arjun <arjun.anantharam@intel.com>
Sent: Thursday, June 20, 2024 9:51 AM
To: freebsd-arm@freebsd.org <freebsd-arm@freebsd.org>
Subject: FreeBSD OS installation stuck after selecting Boot installer

Hi,


I am trying to install FreeBSD OS(https://download.freebsd.org/releases/ISO-IMAGES/14.1/FreeBSD-14.1-RELEASE-arm64-aarch64-memstick.img or any other FreeBSD version) on Intel IPU E2100 (https://www.intel.com/content/www/us/en/products/details/network-io/ipu/adapter-e2100.html )from UEFI environment.
Installation however fails on Arm Neoverse N1 CPU Cores at up to 3.0GHz with below errors:

[1718737477475.png]

[1718737524958.png]


Since the IPU E2100 does not support device tree, i have tried to disable it with below cmds and also made sure to enable ACPI(which was enabled by default with FreeBSD-above screenshot). As, enabling ACPI should not require device tree
From the BSD Boot Loader Prompt, i did set following options but still ran into install issue(below screenshot):



Code:

set boot_serial="YES"
echo boot_serial is set to ${boot_serial}
set comconsole_speed="115200"
echo comconsole_speed is set to ${comconsole_speed}

set hint.acpi.0.disabled=0
set hint.fdt.0.disabled=1

OK set acpi_load="YES"
OK echo acpi_load is set to ${acpi_load}
acpi_load is set to YES

OK set fdt_enable="NO"
OK echo fdt_enable is set to ${fdt_enable}
fdt_enable is set to NO
OK boot

[1718737456134.png]


Other OS's like Ubuntu, Rocky Linux installed just fine. So, any pointers to solve this FreeBSD issue is much appreciated..
Thanks