Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Jul 2024 00:04:55 +0000
From:      "Anantharam, Arjun" <arjun.anantharam@intel.com>
To:        Andrew Turner <andrew@fubar.geek.nz>
Cc:        Warner Losh <imp@bsdimp.com>, Mark Millard <marklmi@yahoo.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: FreeBSD OS installation stuck after selecting Boot installer
Message-ID:  <MW3PR11MB476199009EFF9650069B752980AD2@MW3PR11MB4761.namprd11.prod.outlook.com>
In-Reply-To: <084E63D4-8A02-4E7B-8C26-152ED0D0317A@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> <MW3PR11MB476109F1B8FC134E5BF39CC680D32@MW3PR11MB4761.namprd11.prod.outlook.com> <MW3PR11MB47617F8DD22E17DA3219FC3380D32@MW3PR11MB4761.namprd11.prod.outlook.com> <MW3PR11MB47619F77AE942F17F1762D8A80DD2@MW3PR11MB4761.namprd11.prod.outlook.com> <MW3PR11MB47617D13959F782479FC481280A42@MW3PR11MB4761.namprd11.prod.outlook.com> <084E63D4-8A02-4E7B-8C26-152ED0D0317A@fubar.geek.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
--_000_MW3PR11MB476199009EFF9650069B752980AD2MW3PR11MB4761namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

The location from which we are trying to boot FreeBSD is a VFS or RAMDisk m=
ethod:
OK lsdev
disk devices:
     disk0:    4194304 X 512 blocks
       disk0p1: EFI
      disk0p2: FreeBSD UFS
 http: (unknown)
 net devices:
    net0:
     net1:
     net2:
     net3:


Looks like FreeBSD does not have access to this RAMDisk and hence unable to=
 boot the image. I was digging through FreeBSD forums and found some releva=
nt details. I guess the first step would be to build FreeBSD to prepare it =
as RAMDisk image, so from the links below i could gather something like thi=
s ?
Some Examples:
https://forums.freebsd.org/threads/how-would-i-load-root-image-into-memory-=
backed-fs-and-run-the-system-from-that.78021/
https://www.reddit.com/r/freebsd/comments/tzm2xi/run_from_ram/
https://forums.freebsd.org/threads/mount-memory-disk-on-boot.61090/
https://forums.freebsd.org/threads/questions-about-ramdisk-in-freebsd.20345=
/

mdmfs (https://man.freebsd.org/cgi/man.cgi?query=3Dmdmfs&sektion=3D8&manpat=
h=3Dfreebsd-release-ports#EXAMPLES) and mdconfig(https://man.freebsd.org/cg=
i/man.cgi?query=3Dmdconfig&sektion=3D8&manpath=3Dfreebsd-release-ports):

  1.  Prepare RAMDisk image

mdconfig -a -t vnode -s 10g -u 0
newfs /dev/md0
mount /dev/md0 /mnt
dump -0aLf - / | (cd /mnt && restore -rf -)
dd if=3D/dev/md0 of=3D/path/to/ramdisk.img bs=3D1M
      2. Edit /boot/loader.conf:

initrd_load=3D"YES"
initrd_type=3D"mfs_root"
initrd_name=3D"/boot/ramdisk.img"
vfs.root.mountfrom=3D"ufs:/dev/md0"
vfs.root.mountfrom.options=3D"ro,noatime"

    3. Set Boot Variables in the Bootloader

OK set initrd_load=3D"YES"
OK set initrd_type=3D"mfs_root"
OK set initrd_name=3D"/boot/ramdisk.img"
OK set vfs.root.mountfrom=3D"ufs:/dev/md0"
OK set vfs.root.mountfrom.options=3D"ro,noatime"
OK boot

Can someone please clarify if this is a right approach? Any inputs are appr=
eciated!!

Thanks,
Arjun
________________________________
From: Andrew Turner <andrew@fubar.geek.nz>
Sent: Wednesday, July 10, 2024 11:36 AM
To: Anantharam, Arjun <arjun.anantharam@intel.com>
Cc: Warner Losh <imp@bsdimp.com>; Mark Millard <marklmi@yahoo.com>; freebsd=
-arm@freebsd.org <freebsd-arm@freebsd.org>
Subject: Re: FreeBSD OS installation stuck after selecting Boot installer


On 10 Jul 2024, at 17:03, Anantharam, Arjun <arjun.anantharam@intel.com> wr=
ote:

Hi,

On most of our hardware, i still run into mount issues. Can anyone provide =
some guidance on this ?
This iso/img file boot is the only option right now for us to boot FreeBSD(=
no PXE boot option yet), so any inputs are appreciated!!


The issue appears to be the interface the NVMe provides to the kernel.

found-> vendor=3D0x8086, dev=3D0x1457, revid=3D0x21
        domain=3D0, bus=3D0, slot=3D1, func=3D1
        class=3D01-08-02, hdrtype=3D0x00, mfdev=3D1
        cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D0 (dwords)
        lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)
        intpin=3Da, irq=3D255
        powerspec 3  supports D0 D3  current D0
        MSI supports 1 message, 64 bit, vector masks
        MSI-X supports 257 messages in map 0x18
        map[10]: type Prefetchable Memory, range 64, base 0x2220000000, siz=
e 25, memory disabled

This looks like the NVMe device that the nvme driver attaches to. The class=
=3D01-08-02 indicates it=92s an NVMe device using the enterprise nvmhci.

=85

found-> vendor=3D0x8086, dev=3D0x1458, revid=3D0x21
        domain=3D0, bus=3D0, slot=3D1, func=3D7
        class=3D01-08-00, hdrtype=3D0x00, mfdev=3D1
        cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D0 (dwords)
        lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns)
        intpin=3Da, irq=3D255
        powerspec 3  supports D0 D3  current D0
        MSI-X supports 257 messages in map 0x18
        map[10]: type Prefetchable Memory, range 64, base 0x2224000000, siz=
e 25, memory disabled

This is the NVMe device the nvme driver doesn=92t attach to. As the class i=
s 01-08-00 the driver doesn=92t attach. The problem is the 00 at the end.

I don=92t know the difference between the different interfaces so am unsure=
 how difficult it would be to support this device.

Andrew

--_000_MW3PR11MB476199009EFF9650069B752980AD2MW3PR11MB4761namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
Hi,</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
The location from which we are trying to boot FreeBSD is a VFS or RAMDisk m=
ethod:</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
OK lsdev<br>
<b>disk devices:<br>
&nbsp;&nbsp;&nbsp;&nbsp; disk0:&nbsp;&nbsp;&nbsp; 4194304 X 512 blocks<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; disk0p1: EFI<br>
&nbsp; &nbsp; &nbsp; disk0p2: FreeBSD UFS</b><br>
&nbsp;http: (unknown)<br>
&nbsp;net devices:<br>
&nbsp; &nbsp; net0:<br>
&nbsp;&nbsp;&nbsp;&nbsp; net1:<br>
&nbsp;&nbsp;&nbsp;&nbsp; net2:<br>
&nbsp;&nbsp;&nbsp;&nbsp; net3:</div>
<div id=3D"appendonsend" style=3D"color: inherit;"></div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Looks like FreeBSD does not have access to this RAMDisk and hence unable to=
 boot the image. I was digging through FreeBSD forums and found some releva=
nt details. I guess the first step would be to build FreeBSD to prepare it =
as RAMDisk image, so from the links
 below i could gather something like this ?</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Some Examples:</div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<a href=3D"https://forums.freebsd.org/threads/how-would-i-load-root-image-i=
nto-memory-backed-fs-and-run-the-system-from-that.78021/" target=3D"_blank"=
 id=3D"OWAc29ff825-be05-ce79-3311-e2bb4bbdc50b" class=3D"fui-Link ___1rxvrp=
e f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok=
6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fq=
v5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86=
v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f1=
0aw75t fsle3fq f17ae5zn OWAAutoLink" title=3D"https://forums.freebsd.org/th=
reads/how-would-i-load-root-image-into-memory-backed-fs-and-run-the-system-=
from-that.78021/" rel=3D"noreferrer noopener">https://forums.freebsd.org/th=
reads/how-would-i-load-root-image-into-memory-backed-fs-and-run-the-system-=
from-that.78021/</a></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<a href=3D"https://www.reddit.com/r/freebsd/comments/tzm2xi/run_from_ram/" =
target=3D"_blank" id=3D"OWAd2ea2ed6-c9b5-a1f0-dbb4-db4724b6e9a3" class=3D"f=
ui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fo=
uc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1q=
ch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y=
 f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h=
8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn OWAAutoLink" title=3D"https://www.=
reddit.com/r/freebsd/comments/tzm2xi/run_from_ram/" rel=3D"noreferrer noope=
ner">https://www.reddit.com/r/freebsd/comments/tzm2xi/run_from_ram/</a></di=
v>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<a href=3D"https://forums.freebsd.org/threads/mount-memory-disk-on-boot.610=
90/" target=3D"_blank" id=3D"OWAefa859a8-b2f2-b594-eb99-17870745b1df" class=
=3D"fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv =
fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0=
i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1i=
ds18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41=
a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn OWAAutoLink" title=3D"https:/=
/forums.freebsd.org/threads/mount-memory-disk-on-boot.61090/" rel=3D"norefe=
rrer noopener">https://forums.freebsd.org/threads/mount-memory-disk-on-boot=
.61090/</a></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<a href=3D"https://forums.freebsd.org/threads/questions-about-ramdisk-in-fr=
eebsd.20345/" target=3D"_blank" id=3D"OWAa0ebf105-3ad3-3dd0-c283-497a9a337f=
ab" class=3D"fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh =
f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7=
ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9=
n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93ei=
r f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn OWAAutoLink" title=
=3D"https://forums.freebsd.org/threads/questions-about-ramdisk-in-freebsd.2=
0345/" rel=3D"noreferrer noopener">https://forums.freebsd.org/threads/quest=
ions-about-ramdisk-in-freebsd.20345/</a></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
&nbsp;</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
mdmfs (<a href=3D"https://man.freebsd.org/cgi/man.cgi?query=3Dmdmfs&amp;sek=
tion=3D8&amp;manpath=3Dfreebsd-release-ports#EXAMPLES" target=3D"_blank" id=
=3D"OWAa3eb5b50-0901-26ff-6683-a610d29ebd8c" class=3D"fui-Link ___1rxvrpe f=
2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f=
1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5q=
za f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f=
1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw=
75t fsle3fq f17ae5zn OWAAutoLink" title=3D"https://man.freebsd.org/cgi/man.=
cgi?query=3Dmdmfs&amp;sektion=3D8&amp;manpath=3Dfreebsd-release-ports#examp=
les" rel=3D"noreferrer noopener">https://man.freebsd.org/cgi/man.cgi?query=
=3Dmdmfs&amp;sektion=3D8&amp;manpath=3Dfreebsd-release-ports#EXAMPLES</a>)
 and mdconfig(<a href=3D"https://man.freebsd.org/cgi/man.cgi?query=3Dmdconf=
ig&amp;sektion=3D8&amp;manpath=3Dfreebsd-release-ports" target=3D"_blank" i=
d=3D"OWAb797770d-ef84-9e8a-ffe5-61bea2c83f40" class=3D"fui-Link ___1rxvrpe =
f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 =
f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5=
qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v =
f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10a=
w75t fsle3fq f17ae5zn OWAAutoLink" title=3D"https://man.freebsd.org/cgi/man=
.cgi?query=3Dmdconfig&amp;sektion=3D8&amp;manpath=3Dfreebsd-release-ports" =
rel=3D"noreferrer noopener">https://man.freebsd.org/cgi/man.cgi?query=3Dmdc=
onfig&amp;sektion=3D8&amp;manpath=3Dfreebsd-release-ports</a>):</div>
<ol start=3D"1" data-listchain=3D"__List_Chain_29">
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<b>Prepare RAMDisk image</b></li></ol>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>mdconfig -a -t vnode -s 10g -u 0<br>
newfs /dev/md0<br>
mount /dev/md0 /mnt<br>
dump -0aLf - / | (cd /mnt &amp;&amp; restore -rf -)<br>
dd if=3D/dev/md0 of=3D/path/to/ramdisk.img bs=3D1M</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>&nbsp; &nbsp; &nbsp; 2. Edit /boot/loader.conf:</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>&nbsp;</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>initrd_load=3D&quot;YES&quot;<br>
initrd_type=3D&quot;mfs_root&quot;<br>
initrd_name=3D&quot;/boot/ramdisk.img&quot;<br>
vfs.root.mountfrom=3D&quot;ufs:/dev/md0&quot;<br>
vfs.root.mountfrom.options=3D&quot;ro,noatime&quot;</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>&nbsp;</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>&nbsp; &nbsp; 3. Set Boot Variables in the Bootloader</b></div>
<div style=3D"margin-top: 1em; margin-bottom: 1em; font-family: Aptos, Apto=
s_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-s=
ize: 11pt; color: rgb(0, 0, 0);">
<b>&nbsp;</b></div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<b>OK set initrd_load=3D&quot;YES&quot;<br>
OK set initrd_type=3D&quot;mfs_root&quot;<br>
OK set initrd_name=3D&quot;/boot/ramdisk.img&quot;<br>
OK set vfs.root.mountfrom=3D&quot;ufs:/dev/md0&quot;<br>
OK set vfs.root.mountfrom.options=3D&quot;ro,noatime&quot;<br>
OK boot</b></div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Can someone please clarify if this is a right approach? Any inputs are appr=
eciated!!</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Thanks,</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
 font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Arjun</div>
<hr style=3D"display: inline-block; width: 98%;">
<div id=3D"divRplyFwdMsg" dir=3D"ltr" style=3D"color: inherit;"><span style=
=3D"font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);=
"><b>From:</b>&nbsp;Andrew Turner &lt;andrew@fubar.geek.nz&gt;<br>
<b>Sent:</b>&nbsp;Wednesday, July 10, 2024 11:36 AM<br>
<b>To:</b>&nbsp;Anantharam, Arjun &lt;arjun.anantharam@intel.com&gt;<br>
<b>Cc:</b>&nbsp;Warner Losh &lt;imp@bsdimp.com&gt;; Mark Millard &lt;marklm=
i@yahoo.com&gt;; freebsd-arm@freebsd.org &lt;freebsd-arm@freebsd.org&gt;<br=
>
<b>Subject:</b>&nbsp;Re: FreeBSD OS installation stuck after selecting Boot=
 installer</span>
<div>&nbsp;</div>
</div>
<div><br>
</div>
<blockquote>
<div>On 10 Jul 2024, at 17:03, Anantharam, Arjun &lt;arjun.anantharam@intel=
.com&gt; wrote:</div>
<br>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
Hi,</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
<br>
</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
On most of our hardware, i still run into mount issues. Can anyone provide =
some guidance on this ?</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
This iso/img file boot is the only option right now for us to boot FreeBSD(=
no PXE boot option yet), so any inputs are appreciated!!</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
<br>
</div>
</blockquote>
<div><br>
</div>
<div>The issue appears to be the interface the NVMe provides to the kernel.=
</div>
<br>
<blockquote>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
found-&gt; vendor=3D0x8086, dev=3D0x1457, revid=3D0x21</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; domain=3D0, bus=3D0, slot=3D1, func=3D1</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; class=3D01-08-02, hdrtype=3D0x00, mfdev=3D1</di=
v>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D=
0 (dwords)</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), m=
axlat=3D0x00 (0 ns)</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; intpin=3Da, irq=3D255</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; powerspec 3 &nbsp;supports D0 D3 &nbsp;current =
D0</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; MSI supports 1 message, 64 bit, vector masks</d=
iv>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; MSI-X supports 257 messages in map 0x18</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; map[10]: type Prefetchable Memory, range 64, ba=
se 0x2220000000, size 25, memory disabled</div>
</blockquote>
<div><br>
</div>
<div>This looks like the NVMe device that the nvme driver attaches to. The&=
nbsp;class=3D01-08-02 indicates it=92s an NVMe device using the enterprise =
nvmhci.</div>
<div><br>
</div>
=85
<div><br>
</div>
<blockquote>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
found-&gt; vendor=3D0x8086, dev=3D0x1458, revid=3D0x21</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; domain=3D0, bus=3D0, slot=3D1, func=3D7</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; class=3D01-08-00, hdrtype=3D0x00, mfdev=3D1</di=
v>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D=
0 (dwords)</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), m=
axlat=3D0x00 (0 ns)</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; intpin=3Da, irq=3D255</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; powerspec 3 &nbsp;supports D0 D3 &nbsp;current =
D0</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; MSI-X supports 257 messages in map 0x18</div>
<div style=3D"text-align: left; text-indent: 0px; font-family: Aptos, Aptos=
_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-si=
ze: 11pt;">
&nbsp; &nbsp; &nbsp; &nbsp; map[10]: type Prefetchable Memory, range 64, ba=
se 0x2224000000, size 25, memory disabled</div>
</blockquote>
<div><br>
</div>
<div>This is the NVMe device the nvme driver doesn=92t attach to. As the cl=
ass is 01-08-00 the driver doesn=92t attach. The problem is the 00 at the e=
nd.</div>
<div><br>
</div>
<div>I don=92t know the difference between the different interfaces so am u=
nsure how difficult it would be to support this device.</div>
<br>
<div>Andrew</div>
</body>
</html>

--_000_MW3PR11MB476199009EFF9650069B752980AD2MW3PR11MB4761namp_--



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