Date: Tue, 27 Dec 2022 13:47:49 +0000 From: Graham Perrin <grahamperrin@freebsd.org> To: questions@freebsd.org Subject: Re: Unable to boot from internal hard disks on new PC Message-ID: <cba40072-9fe3-b75c-669b-3d7282944d44@freebsd.org> In-Reply-To: <20221227124617.GB11926@localhost.org> References: <20221227110800.GA11926@localhost.org> <45e305f7a1193cd6eac03dd0a1499e638c26ceda.camel@riseup.net> <20221227124617.GB11926@localhost.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------fs0znBMKk5hzQlnq4jk1AVGn
Content-Type: multipart/mixed; boundary="------------0V0gwcgDySi8Hok01yKF0IHU";
protected-headers="v1"
From: Graham Perrin <grahamperrin@freebsd.org>
To: questions@freebsd.org
Message-ID: <cba40072-9fe3-b75c-669b-3d7282944d44@freebsd.org>
Subject: Re: Unable to boot from internal hard disks on new PC
References: <20221227110800.GA11926@localhost.org>
<45e305f7a1193cd6eac03dd0a1499e638c26ceda.camel@riseup.net>
<20221227124617.GB11926@localhost.org>
In-Reply-To: <20221227124617.GB11926@localhost.org>
--------------0V0gwcgDySi8Hok01yKF0IHU
Content-Type: multipart/alternative;
boundary="------------4MUEu1eqyfys1kZAmevK8pp3"
--------------4MUEu1eqyfys1kZAmevK8pp3
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64
T24gMjcvMTIvMjAyMiAxMjo0NiwgSm9oYW5uZXMtTWFyaWEgS2FsdGVuYmFjaCB3cm90ZToN
Cg0KDQo+IOKApg0KPg0KPiBPdXRwdXQgZnJvbSBlZmlib290bWdyOg0KPiArQm9vdDAwMEIq
IFVFRkk6IFVTQiAyLjAgUEVORFJJVkUgMS4wLCBQYXJ0aXRpb24gMQ0KPiAgIEJvb3QwMDA4
KiBVRUZJIE9TDQo+ICAgQm9vdDAwMDIqIFVFRkk6IEhUVFAgSVB2NCBSZWFsdGVrIFBDSWUg
R0JFIEZhbWlseSBDb250cm9sbGVyDQo+ICAgQm9vdDAwMDMqIFVFRkk6IFBYRSBJUHY0IFJl
YWx0ZWsgUENJZSBHQkUgRmFtaWx5IENvbnRyb2xsZXINCj4gICBCb290MDAwNCogVUVGSTog
SFRUUCBJUHY2IFJlYWx0ZWsgUENJZSBHQkUgRmFtaWx5IENvbnRyb2xsZXINCj4gICBCb290
MDAwQSogVUVGSTogUFhFIElQdjYgUmVhbHRlayBQQ0llIEdCRSBGYW1pbHkgQ29udHJvbGxl
cg0KPg0KPiAoLWIgMDAwYiBpcyB0aGUgaW5zdGFsbGF0aW9uIHN0aWNrIGFuZCAwMDA4IHRo
ZSBvdGhlciBzdGljayBJIHRlc3RlZDsgYm90aCBubyBwcm9ibGVtKQ0KPg0KPiDigKYNCg0K
DQpJZiB0aGUgaW50ZW50aW9uIGlzIHRvIHVzZSB0aGUgRUZJIHN5c3RlbSBwYXJ0aXRpb24g
YXQgYWRhMHAyLCBhbmQgaWYgDQp0aGUgb3BlcmF0aW5nIHN5c3RlbSBhdCBhZGEwcDQgaXMg
c3RpbGwgYm9vdGFibGUsIGFuZCBpZiB5b3UnbGwgbm90IGJvb3QgDQpmcm9tIHRoZSBuZXR3
b3JrOiB5b3UgY2FuIHNhZmVseSBkZWxldGUgdW53YW50ZWQgZW50cmllcy4NCg0KSWYgQm9v
dDAwMDggaXMgbXlzdGVyaW91cywgeW91IGNvdWxkIHRyeSBhY3RpdmF0aW5nIGl0IChhbmQg
dGhlbiANCnJlc3RhcnRpbmcgdGhlIGNvbXB1dGVyKSB0byB0ZWxsIHdoZXRoZXIgaXQncyB1
c2FibGUgaW4gcmVsYXRpb24gdG8geW91ciANCmluc3RhbGxhdGlvbiBvZiBGcmVlQlNELg0K
DQpUaGluZ3MgaGVyZSBhcmUgdmVyeSBzcGFyc2UsIGVub3VnaCBmb3IgRnJlZUJTRCB0byBi
b290Og0KDQpyb290QG1vd2EyMTktZ2pwNC04NTcwcC1mcmVlYnNkOn4gIyBlZmlib290bWdy
DQpCb290IHRvIEZXIDogZmFsc2UNCkJvb3RDdXJyZW50OiAwMDAwDQpUaW1lb3V0IMKgwqDC
oDogNSBzZWNvbmRzDQpyb290QG1vd2EyMTktZ2pwNC04NTcwcC1mcmVlYnNkOn4gIw0KDQoN
Cg==
--------------4MUEu1eqyfys1kZAmevK8pp3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html data-lt-installed=3D"true">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
</head>
<body style=3D"padding-bottom: 1px;">
<p>On 27/12/2022 12:46, Johannes-Maria Kaltenbach wrote:<br>
</p>
<div class=3D"moz-cite-prefix"><br>
</div>
<blockquote type=3D"cite"
cite=3D"mid:20221227124617.GB11926@localhost.org">
<pre class=3D"moz-quote-pre" wrap=3D"">=E2=80=A6
Output from efibootmgr:
+Boot000B* UEFI: USB 2.0 PENDRIVE 1.0, Partition 1
Boot0008* UEFI OS
Boot0002* UEFI: HTTP IPv4 Realtek PCIe GBE Family Controller
Boot0003* UEFI: PXE IPv4 Realtek PCIe GBE Family Controller
Boot0004* UEFI: HTTP IPv6 Realtek PCIe GBE Family Controller
Boot000A* UEFI: PXE IPv6 Realtek PCIe GBE Family Controller
(-b 000b is the installation stick and 0008 the other stick I tested; bot=
h no problem)
=E2=80=A6
</pre>
</blockquote>
<p><br>
</p>
<p>If the intention is to use the EFI system partition at ada0p2,
and if the operating system at ada0p4 is still bootable, and if
you'll not boot from the network: you can safely delete unwanted
entries.=C2=A0</p>
<p>If Boot0008 is mysterious, you could try activating it (and then
restarting the computer) to tell whether it's usable in relation
to your installation of FreeBSD.</p>
<p>Things here are very sparse, enough for FreeBSD to boot: <br>
</p>
<p><span style=3D"font-family:monospace"><span
style=3D"color:#000000;background-color:#ffffff;">root@mowa219-=
gjp4-8570p-freebsd:~
# efibootmgr
</span><br>
Boot to FW : false
<br>
BootCurrent: 0000
<br>
Timeout =C2=A0=C2=A0=C2=A0: 5 seconds
<br>
root@mowa219-gjp4-8570p-freebsd:~ # <br>
<br>
<br>
</span></p>
</body>
<lt-container></lt-container>
</html>
--------------4MUEu1eqyfys1kZAmevK8pp3--
--------------0V0gwcgDySi8Hok01yKF0IHU--
--------------fs0znBMKk5hzQlnq4jk1AVGn
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmOq94UFAwAAAAAACgkQt2dIb0oY1Avs
Ig/+PU1azqZFrjtbDZS7QHvYpTRHDR+RjmAakMdeXfDErKIfgXhUlWb3t6AyeijkW3uGW7cVeJZ2
Vj3hIwaYt6TUgNY1Kdcim+wbRqiIhm992pvZWjRkrrmjF01vlh16gd/+GMlztQZWPDtQHANlH7UC
nAnRBzrap8Kj9JjFQw4khFPRvM4VvwlTqq7MDLmgBBJFdEwEyF7jeCz+KXrEg68dEozkMvMJQDEq
aTSQnWGNuoKKqv9zDA6L0U0Fwroc7BDM+Lcqj26ETtOBI838//IcQY0DhMkxLbIgqUCKjDDZWWoH
mFUtsjm+D7FtaEbmwMTctlo0Suviut/amOAmYpCsEg2ANQJiqx7eEg8uO9hlYepslapnO/BObxeO
SEbA09CabKAomvV7UbBZV5UnrfnveEY/pv+rlrxHpwGscm/uuq75c00zl54jSIUHufUNflWkqqES
KTniUjhOCu22SKCGTIghS0pxfKZGmj+MnPv6tqSGQIOzMGVslLPeJ45ko8elNDSI/3T+YGel3pDY
aaquNoZA2VMmbnhbXjK+uaQJtAlj2QEwnBHgwS9mkxKF2uQN5vDtMn8S7rlpW6V0fHwBA762SbUK
OjnnN8qWzpIYXnC4c0t4axOr2aWWQT2qjwtqj8Q91q3nbNSL0ZraxNiPJum6uqZFhyv4i2t6b/t3
ddc=
=2vTv
-----END PGP SIGNATURE-----
--------------fs0znBMKk5hzQlnq4jk1AVGn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cba40072-9fe3-b75c-669b-3d7282944d44>