Re: FreeBSD OS installation stuck after selecting Boot installer
"Anantharam, Arjun" <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <MW3PR11MB4761291C45B60A88956E1B9C80DC2@MW3PR11MB4761.namprd11.prod.outlook.com> |
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: [email protected] <[email protected]> on behalf of Klaus Küchemann <[email protected]> Sent: Friday, June 28, 2024 7:35 AM To: Andrew Turner <[email protected]>; Warner Losh <[email protected]>; Mark Millard <[email protected]>; [email protected] <[email protected]>; Anantharam, Arjun <[email protected]>; [email protected] <[email protected]> Subject: Re: FreeBSD OS installation stuck after selecting Boot installer > Am 28.06.2024 um 12:09 schrieb Andrew Turner <[email protected]>: > …..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.