Re: FreeBSD OS installation stuck after selecting Boot installer

From: Anantharam, Arjun <arjun.anantharam_at_intel.com>
Date: Tue, 02 Jul 2024 00:38:39 UTC
Unfortunately, PXE boot is still not an option on this platform yet. Will have to rely on FreeBSD iso/img installation from NVMe partition(RAMDisk method) untill we can get PXE to work with UEFI on this platform..

Thanks,
Arjun

________________________________
From: owner-freebsd-arm@FreeBSD.org <owner-freebsd-arm@FreeBSD.org> on behalf of Klaus Küchemann <maciphone2@googlemail.com>
Sent: Friday, June 28, 2024 7:35 AM
To: Andrew Turner <andrew@fubar.geek.nz>; Warner Losh <imp@bsdimp.com>; Mark Millard <marklmi@yahoo.com>; freebsd-arm@freebsd.org <freebsd-arm@freebsd.org>; Anantharam, Arjun <arjun.anantharam@intel.com>; kib@freebsd.org <kib@freebsd.org>
Subject: Re: FreeBSD OS installation stuck after selecting Boot installer



> Am 28.06.2024 um 12:09 schrieb Andrew Turner <andrew@fubar.geek.nz>:

> …..What device type is the installer on? e.g. NVMe, USB. I see what look like two NVMe devices on the pci bus, however the nvme driver only attaches to one….
>
>

 what did I typically do at first in the past when hanging on <mountroot>-things  debugging on arm64…..
The following seems to give a very nice option as it seems to indicate that the NIC-driver is working:

> ………...
>> net devices:
>>    net0:
>>    net1:
>>    net2:
>>    net3:
>>

You can compile fbsd-current into a folder at e.g. on net0 ,
 setup an PXE-environment(nice description in the handbook) and then :

OK set currdev=net0

OK load boot/kernel/kernel

OK boot
—

If the uart problem is based on baudrate(not driver/attachment), there are tools like picocom
where you can change the baudrate on the fly ,
That sometimes enlightens the situation..

Regards

K.