Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Mar 2024 15:49:53 -0800
From:      Doug Ambrisko <ambrisko@ambrisko.com>
To:        Philipp Ost <pj@smo.de>
Cc:        current@freebsd.org, Klaus-Dieter Ost <kdo@smo.de>
Subject:   Re: Unable to boot -CURRENT on Thinkpad P16s G2
Message-ID:  <ZepSob8RM9W6tCXN@ambrisko.com>
In-Reply-To: <283774ec-156b-4bc8-850d-261ea0e0ed07@smo.de>
References:  <dc14d2de-aeef-434f-823e-9ca69e62e77c@smo.de> <283774ec-156b-4bc8-850d-261ea0e0ed07@smo.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 07, 2024 at 07:15:48PM +0100, Philipp Ost wrote:
| On 2/28/24 21:10, Philipp Ost wrote:
| [boot log stripped]
| > Does anyone have any suggestions on how to proceed at this point? [...]
| 
| Short follow-up: disabling uart0 and uart1 at the loader prompt allowed us
| to boot and install FreeBSD (the -CURRENT snapshot from 2024-02-29 in case
| it matters).

UARTS on AMD can be a bit different.  Some BIOS implementations seem
to set them up to work like legacy ports others do not.  On a Naples
platform I helped add support for them since they were not setup
in the legacy configuration.  The AMD servers I'm using now have them
setup in legacy mode and just work like on other systems.

If I remember right those UARTS were defined in ACPI.  On a laptop they
probably don't have serial ports and the probe is getting stuck on
something.  It might be good to instrument it to see what.

Thanks,

Doug A.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZepSob8RM9W6tCXN>