Date: Fri, 28 Jun 2024 16:35:32 +0200 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Andrew Turner <andrew@fubar.geek.nz>, Warner Losh <imp@bsdimp.com>, Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org, arjun.anantharam@intel.com, kib@freebsd.org Subject: Re: FreeBSD OS installation stuck after selecting Boot installer Message-ID: <29F6FEFD-4DBA-463F-A12A-ADBA85AAA07F@googlemail.com> In-Reply-To: <1DEED962-C5D8-4B6D-8BC9-870A9BFE1176@fubar.geek.nz> 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> <CANCZdfoL0A-Aj21g-E_uPcx%2Bf0U-mhM0s35rja7RNHukCOF6Fg@mail.gmail.com> <MW3PR11MB4761CA9388199BC11600D70B80D72@MW3PR11MB4761.namprd11.prod.outlook.com> <1DEED962-C5D8-4B6D-8BC9-870A9BFE1176@fubar.geek.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 28.06.2024 um 12:09 schrieb Andrew Turner <andrew@fubar.geek.nz>: > =E2=80=A6..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=E2=80=A6. >=20 >=20 what did I typically do at first in the past when hanging on = <mountroot>-things debugging on arm64=E2=80=A6.. The following seems to give a very nice option as it seems to indicate = that the NIC-driver is working: > =E2=80=A6=E2=80=A6=E2=80=A6... >> net devices: >> net0: >> net1: >> net2: >> net3: >>=20 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=3Dnet0 OK load boot/kernel/kernel OK boot =E2=80=94 If the uart problem is based on baudrate(not driver/attachment), there = are tools like picocom=20 where you can change the baudrate on the fly , That sometimes enlightens the situation.. Regards K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29F6FEFD-4DBA-463F-A12A-ADBA85AAA07F>