Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 May 2023 16:30:00 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        freebsd-hardware@freebsd.org
Subject:   Mini PC does not like FreeBSD
Message-ID:  <CAN6yY1vx06=U-MgM%2Beb3YXZcwSoAC_GxeP-rryPOxfGdyfNJNw@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
--00000000000091ba2605fca11eb2
Content-Type: text/plain; charset="UTF-8"

First, can anyone recommend a small, inexpensive mini-PC that will work
with FreeBSD? I do need one with a VGA monitor connection. (That limits
options quite a bit.)

My decade-old server, an ASUS mini-PC, died a couple of weeks ago and I
bought a Kamrui replacement. Looked good. low-end Alder Lake processor, 16
GB RAM and 512GB SSD.
This looked like a great $200 option for me.

The SSD is m.2, but not nVME. It has a SATA interface. I started seeing odd
corruptions and missing files (like my ld-elf hints file). Decided that the
SSD was bad, so returned the unit and got a replacement. It crashed and
stopped booting when I was installing a number of packages. I see the
following messages:

OK boot -s
staging 0x5fc00000 (not copying) tramp 0x6e4c60000 PT4 0x6e4bd000
Start @ 0xffffffff803b000 ...
EFI framebuffer information:
addr, size       0x4000000000, 0x1d4c00
dimensions     800 x 600
stride             800
masks            0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000

IS there an issue with this hardware (which has probably never run FreeBSD)
or did I just step into a bad batch of SSDs?

-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

--00000000000091ba2605fca11eb2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif;font-size:small">First, can anyone recommend a small, inexpensive=
 mini-PC that will work with FreeBSD? I do need one with a VGA monitor conn=
ection. (That limits options quite a bit.)<br></div><div class=3D"gmail_def=
ault" style=3D"font-family:tahoma,sans-serif;font-size:small"><br></div><di=
v class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:=
small">My decade-old server, an ASUS mini-PC, died a couple of weeks ago an=
d I bought a Kamrui replacement. Looked good. low-end Alder Lake processor,=
 16 GB RAM and 512GB SSD.</div><div class=3D"gmail_default" style=3D"font-f=
amily:tahoma,sans-serif;font-size:small">This looked like a great $200 opti=
on for me.</div><div class=3D"gmail_default" style=3D"font-family:tahoma,sa=
ns-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-family:tahoma,sans-serif;font-size:small">The SSD is m.2, but not nVME.=
 It has a SATA interface. I started seeing odd corruptions and missing file=
s (like my ld-elf hints file). Decided that the SSD was bad, so returned th=
e unit and got a replacement. It crashed and stopped booting when I was ins=
talling a number of packages. I see the following messages:</div><div class=
=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if;font-size:small">OK boot -s</div><div class=3D"gmail_default" style=3D"f=
ont-family:tahoma,sans-serif;font-size:small">staging 0x5fc00000 (not copyi=
ng) tramp 0x6e4c60000 PT4 0x6e4bd000</div><div class=3D"gmail_default" styl=
e=3D"font-family:tahoma,sans-serif;font-size:small">Start @ 0xffffffff803b0=
00 ...</div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-s=
erif;font-size:small">EFI framebuffer information:</div><div class=3D"gmail=
_default" style=3D"font-family:tahoma,sans-serif;font-size:small">addr, siz=
e=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0x4000000000, 0x1d4c00</div><div clas=
s=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:small"=
>dimensions =C2=A0 =C2=A0 800 x 600 <br></div><div class=3D"gmail_default" =
style=3D"font-family:tahoma,sans-serif;font-size:small">stride=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 800</div><div =
class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-size:sm=
all">masks=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000</div><div class=3D"gmail=
_default" style=3D"font-family:tahoma,sans-serif;font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-s=
ize:small">IS there an issue with this hardware (which has probably never r=
un FreeBSD) or did I just step into a bad batch of SSDs?<br clear=3D"all"><=
/div><br><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"l=
tr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">=
Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail:=
 <a href=3D"mailto:rkoberman@gmail.com" target=3D"_blank">rkoberman@gmail.c=
om</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055=
683</div></div></div></div></div></div></div></div></div>

--00000000000091ba2605fca11eb2--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vx06=U-MgM%2Beb3YXZcwSoAC_GxeP-rryPOxfGdyfNJNw>