Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Richard Laysell-2

Hello,

I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
Atom CPU (Denverton).  The board boots but most devices are not
detected because ACPI can't be enabled.

Does anyone know if this is likely to be supported at some point?

Full dmesg is below

OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17125621760 (16332MB)
avail mem = 16602619904 (15833MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
bios0: Supermicro Super Server
acpi0 at bios0: rev 2, can't enable ACPI
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 2MB 64b/line 16-way L2 cache
cpu0: cannot disable silicon debug
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
pci0 at mainbus0 bus 0
0:31:5: mem address conflict 0xfe010000/0x1000
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
vendor "Intel", unknown product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 dev 5 function 0 not configured
ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
pci1 at ppb0 bus 1
vendor "Intel", unknown product 0x19e2 (class processor subclass Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured
ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
pci2 at ppb1 bus 2
ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
pci3 at ppb2 bus 3
ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
pci5 at ppb4 bus 5
"ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not configured
ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 0x11: unable to map interrupt
ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt
xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 0x11: couldn't map interrupt
ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
pci6 at ppb5 bus 6
vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 0 not configured
vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 1 not configured
ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
pci7 at ppb6 bus 7
vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 0 not configured
vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 1 not configured
vendor "Intel", unknown product 0x19d3 (class communications subclass miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) at pci0 dev 31 function 0 not configured
vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, rev 0x11) at pci0 dev 31 function 2 not configured
vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 0x11) at pci0 dev 31 function 4 not configured
vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 0x80, rev 0x11) at pci0 dev 31 function 5 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
efifb0 at mainbus0: 1920x1200, 32bpp
wsdisplay at efifb0 not configured
softraid0 at root
scsibus0 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T

Welcome to the OpenBSD/amd64 6.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?


Regards,

Richard




Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Jonathan Gray-11
On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>
> Hello,
>
> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
> Atom CPU (Denverton).  The board boots but most devices are not
> detected because ACPI can't be enabled.
>
> Does anyone know if this is likely to be supported at some point?

Try a snapshot.  ACPI changes were made for a similiar machine
(Lanner NCA-1510) in May.

However there is no support for the integrated X553 Ethernet at the
moment.

>
> Full dmesg is below
>
> OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
>     [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17125621760 (16332MB)
> avail mem = 16602619904 (15833MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
> bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
> bios0: Supermicro Super Server
> acpi0 at bios0: rev 2, can't enable ACPI
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: cannot disable silicon debug
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> pci0 at mainbus0 bus 0
> 0:31:5: mem address conflict 0xfe010000/0x1000
> pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
> pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
> vendor "Intel", unknown product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 dev 5 function 0 not configured
> ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
> pci1 at ppb0 bus 1
> vendor "Intel", unknown product 0x19e2 (class processor subclass Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured
> ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
> pci3 at ppb2 bus 3
> ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
> pci4 at ppb3 bus 4
> ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
> pci5 at ppb4 bus 5
> "ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not configured
> ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 0x11: unable to map interrupt
> ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt
> xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 0x11: couldn't map interrupt
> ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
> pci6 at ppb5 bus 6
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 1 not configured
> ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
> pci7 at ppb6 bus 7
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 1 not configured
> vendor "Intel", unknown product 0x19d3 (class communications subclass miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
> vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) at pci0 dev 31 function 0 not configured
> vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, rev 0x11) at pci0 dev 31 function 2 not configured
> vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 0x11) at pci0 dev 31 function 4 not configured
> vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 0x80, rev 0x11) at pci0 dev 31 function 5 not configured
> isa0 at mainbus0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> efifb0 at mainbus0: 1920x1200, 32bpp
> wsdisplay at efifb0 not configured
> softraid0 at root
> scsibus0 at softraid0: 256 targets
> root on rd0a swap on rd0b dump on rd0b
> erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>
> Welcome to the OpenBSD/amd64 6.5 installation program.
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
>
>
> Regards,
>
> Richard
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Andrew Luke Nesbit-2
On 15/06/2019 10:36, Jonathan Gray wrote:

> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>>
>> Hello,
>>
>> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
>> Atom CPU (Denverton).  The board boots but most devices are not
>> detected because ACPI can't be enabled.
>>
>> Does anyone know if this is likely to be supported at some point?
>
> Try a snapshot.  ACPI changes were made for a similiar machine
> (Lanner NCA-1510) in May.
>
> However there is no support for the integrated X553 Ethernet at the
> moment.

Jonathan, thank you for the update.

Richard, I am in the market for one of these boards too, or some other
C3000 series model.  I'm a big fan of Supermicro's C2000 boards because
they are so versatile for low-power applications.  They are also
excellent home servers due to this and the correspondingly low heat and
noise.  Of course if you have a C2000 series board you would need to
ensure that it doesn't suffer from the notorious Erratum AVR.54 defect [1].

Please could you keep us updated re: your progress of getting OpenBSD
installed along with the support status of all devices?  If so this
would be greatly appreciated.  Thanks!!

[1] A little-known fact is that if you look through Intel's data sheets
and whitepapers you can find similar defects in the stepping errata for
other SoC's.  In my case I found an almost identical example in a recent
Celeron or Pentium J-series SoC.  To add to my disappointment, I later
discovered, entirely coincidentally, that it was used on the controller
boards for a model of Synology NAS that I was considering purchasing.

Andrew
--
OpenPGP key: EB28 0338 28B7 19DA DAB0  B193 D21D 996E 883B E5B9

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

ms-2
There were some serious security issues with hardware and software from
Supermicro (espionage chips, firmware)

For me a NoGo!



On 15.06.19 12:52, Andrew Luke Nesbit wrote:

> On 15/06/2019 10:36, Jonathan Gray wrote:
>> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>>> Hello,
>>>
>>> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
>>> Atom CPU (Denverton).  The board boots but most devices are not
>>> detected because ACPI can't be enabled.
>>>
>>> Does anyone know if this is likely to be supported at some point?
>> Try a snapshot.  ACPI changes were made for a similiar machine
>> (Lanner NCA-1510) in May.
>>
>> However there is no support for the integrated X553 Ethernet at the
>> moment.
> Jonathan, thank you for the update.
>
> Richard, I am in the market for one of these boards too, or some other
> C3000 series model.  I'm a big fan of Supermicro's C2000 boards because
> they are so versatile for low-power applications.  They are also
> excellent home servers due to this and the correspondingly low heat and
> noise.  Of course if you have a C2000 series board you would need to
> ensure that it doesn't suffer from the notorious Erratum AVR.54 defect [1].
>
> Please could you keep us updated re: your progress of getting OpenBSD
> installed along with the support status of all devices?  If so this
> would be greatly appreciated.  Thanks!!
>
> [1] A little-known fact is that if you look through Intel's data sheets
> and whitepapers you can find similar defects in the stepping errata for
> other SoC's.  In my case I found an almost identical example in a recent
> Celeron or Pentium J-series SoC.  To add to my disappointment, I later
> discovered, entirely coincidentally, that it was used on the controller
> boards for a model of Synology NAS that I was considering purchasing.
>
> Andrew

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Richard Laysell-2
In reply to this post by Jonathan Gray-11
On Sat, 15 Jun 2019 19:36:23 +1000
Jonathan Gray <[hidden email]> wrote:

> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
> >
> > Hello,
> >
> > I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an
> > Intel Atom CPU (Denverton).  The board boots but most devices are
> > not detected because ACPI can't be enabled.
> >
> > Does anyone know if this is likely to be supported at some point?  
>
> Try a snapshot.  ACPI changes were made for a similiar machine
> (Lanner NCA-1510) in May.
>
> However there is no support for the integrated X553 Ethernet at the
> moment.
>

Thanks Jonathan.

For those interested the dmesg from the latest snapshot (2019-06-15) is
below.  Significant improvement, but (as Jonathan mentions) no Ethernet
as yet.

OpenBSD 6.5-current (RAMDISK_CD) #27: Fri Jun 14 22:24:30 MDT 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17125621760 (16332MB)
avail mem = 16602619904 (15833MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
bios0: Supermicro Super Server
acpi0 at bios0: ACPI 6.1
acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT APIC BDAT HPET UEFI SSDT DMAR HEST BERT ERST EINJ WSMT
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 4 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 2MB 64b/line 16-way L2 cache
cpu0: cannot disable silicon debug
cpu0: apic clock running at 25MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (VRP0)
acpiprt2 at acpi0: bus -1 (PEX0)
acpiprt3 at acpi0: bus 1 (VRP2)
acpiprt4 at acpi0: bus 7 (VRP1)
acpiprt5 at acpi0: bus 2 (PEX1)
acpiprt6 at acpi0: bus 3 (PEX6)
acpiprt7 at acpi0: bus 4 (PEX7)
acpiprt8 at acpi0: bus 5 (BR28)
acpicpu at acpi0 not configured
"PNP0A08" at acpi0 not configured
"PNP0003" at acpi0 not configured
acpicmos0 at acpi0
"IPI0001" at acpi0 not configured
"PNP0C33" at acpi0 not configured
pci0 at mainbus0 bus 0
0:31:5: mem address conflict 0xfe010000/0x1000
pchb0 at pci0 dev 0 function 0 "Intel C3000 Host" rev 0x11
pchb1 at pci0 dev 4 function 0 "Intel C3000 GLREG" rev 0x11
"Intel C3000 RCEC" rev 0x11 at pci0 dev 5 function 0 not configured
ppb0 at pci0 dev 6 function 0 "Intel C3000 PCIE" rev 0x11
pci1 at ppb0 bus 1
"Intel C3000 QAT" rev 0x11 at pci1 dev 0 function 0 not configured
ppb1 at pci0 dev 10 function 0 "Intel C3000 PCIE" rev 0x11: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 16 function 0 "Intel C3000 PCIE" rev 0x11
pci3 at ppb2 bus 3
ppb3 at pci0 dev 17 function 0 "Intel C3000 PCIE" rev 0x11
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
pci5 at ppb4 bus 5
"ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
"Intel C3000 SMBus" rev 0x11 at pci0 dev 18 function 0 not configured
ahci0 at pci0 dev 19 function 0 "Intel C3000 AHCI" rev 0x11: msi, AHCI 1.3.1
scsibus0 at ahci0: 32 targets
ahci1 at pci0 dev 20 function 0 "Intel C3000 AHCI" rev 0x11: msi, AHCI 1.3.1
scsibus1 at ahci1: 32 targets
xhci0 at pci0 dev 21 function 0 "Intel C3000 xHCI" rev 0x11: msi, xHCI 1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
ppb5 at pci0 dev 22 function 0 "Intel C3000 PCIE" rev 0x11
pci6 at ppb5 bus 6
"Intel X553 SGMII" rev 0x11 at pci6 dev 0 function 0 not configured
"Intel X553 SGMII" rev 0x11 at pci6 dev 0 function 1 not configured
ppb6 at pci0 dev 23 function 0 "Intel C3000 PCIE" rev 0x11
pci7 at ppb6 bus 7
"Intel X553 SGMII" rev 0x11 at pci7 dev 0 function 0 not configured
"Intel X553 SGMII" rev 0x11 at pci7 dev 0 function 1 not configured
"Intel C3000 ME HECI" rev 0x11 at pci0 dev 24 function 0 not configured
"Intel C3000 LPC" rev 0x11 at pci0 dev 31 function 0 not configured
"Intel C3000 PMC" rev 0x11 at pci0 dev 31 function 2 not configured
"Intel C3000 SMBus" rev 0x11 at pci0 dev 31 function 4 not configured
"Intel C3000 SPI" rev 0x11 at pci0 dev 31 function 5 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
efifb0 at mainbus0: 1920x1200, 32bpp
wsdisplay at efifb0 not configured
uhidev0 at uhub0 port 1 configuration 1 interface 0 "Logitech USB Multimedia Keyboard" rev 1.10/0.70 addr 2
uhidev0: iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0 mux 1
uhidev1 at uhub0 port 1 configuration 1 interface 1 "Logitech USB Multimedia Keyboard" rev 1.10/0.70 addr 2
uhidev1: iclass 3/0, 2 report ids
uhid at uhidev1 reportid 1 not configured
uhid at uhidev1 reportid 2 not configured
uhub1 at uhub0 port 3 configuration 1 interface 0 "vendor 0x05e3 USB2.0 Hub" rev 2.00/32.98 addr 3
uhub2 at uhub1 port 1 configuration 1 interface 0 "vendor 0x0557 product 0x7000" rev 2.00/0.00 addr 4
uhidev2 at uhub2 port 1 configuration 1 interface 0 "vendor 0x0557 product 0x2419" rev 1.10/1.00 addr 5
uhidev2: iclass 3/1
ukbd1 at uhidev2
wskbd1 at ukbd1 mux 1
uhidev3 at uhub2 port 1 configuration 1 interface 1 "vendor 0x0557 product 0x2419" rev 1.10/1.00 addr 5
uhidev3: iclass 3/1
uhid at uhidev3 not configured
uhub3 at uhub1 port 2 configuration 1 interface 0 "vendor 0x05e3 USB2.0 Hub" rev 2.00/32.98 addr 6
umass0 at uhub0 port 4 configuration 1 interface 0 "TrekStor USB-Stick CS TrekStor USB-Stick CS" rev 2.00/0.35 addr 7
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
sd0 at scsibus2 targ 1 lun 0: <TrekStor, TrekStor USB CS, > SCSI2 0/direct removable serial.1e680035000000003923
sd0: 7450MB, 512 bytes/sector, 15257600 sectors
softraid0 at root
scsibus3 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T

Welcome to the OpenBSD/amd64 6.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?


Regards,

Richard

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Stuart Henderson
In reply to this post by ms-2
On 2019-06-15, ms <[hidden email]> wrote:
> There were some serious security issues with hardware and software from
> Supermicro (espionage chips, firmware)

Assuming you mean the allegations in that Bloomberg piece, there was no
evidence found supporting them.

https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc

There are the usual problems with BMC security, cpu bugs, etc, but those
are by no means unique to supermicro.


Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Patrick Dohman-4
In reply to this post by Richard Laysell-2
My understanding is that a well known linux vendor was disabling kernel ACPI APEI & EINJ parameter support by default.

"ACPI provides an error injection mechanism, EINJ, for debugging and testing
the ACPI Platform Error Interface (APEI) and other RAS features. If
supported by the firmware, ACPI specification 5.0 and later provide for a
way to specify a physical memory address to which to inject the error.

Injecting errors through EINJ can produce errors which to the platform are
indistinguishable from real hardware errors. This can have undesirable
side-effects, such as causing the platform to mark hardware as needing
replacement.

While it does not provide a method to load unauthenticated privileged code,
the effect of these errors may persist across reboots and affect trust in
the underlying hardware, so disable error injection through EINJ if
securelevel is set."

Regards
Patrick

> On Jun 15, 2019, at 3:02 AM, Richard Laysell <[hidden email]> wrote:
>
>
> Hello,
>
> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
> Atom CPU (Denverton).  The board boots but most devices are not
> detected because ACPI can't be enabled.
>
> Does anyone know if this is likely to be supported at some point?
>
> Full dmesg is below
>
> OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
>    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17125621760 (16332MB)
> avail mem = 16602619904 (15833MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
> bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
> bios0: Supermicro Super Server
> acpi0 at bios0: rev 2, can't enable ACPI
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: cannot disable silicon debug
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> pci0 at mainbus0 bus 0
> 0:31:5: mem address conflict 0xfe010000/0x1000
> pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
> pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
> vendor "Intel", unknown product 0x19a2 (class system subclass root complex event, rev 0x11) at pci0 dev 5 function 0 not configured
> ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
> pci1 at ppb0 bus 1
> vendor "Intel", unknown product 0x19e2 (class processor subclass Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured
> ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
> pci3 at ppb2 bus 3
> ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
> pci4 at ppb3 bus 4
> ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
> pci5 at ppb4 bus 5
> "ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, rev 0x11) at pci0 dev 18 function 0 not configured
> ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 0x11: unable to map interrupt
> ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 0x11: unable to map interrupt
> xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 0x11: couldn't map interrupt
> ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
> pci6 at ppb5 bus 6
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 0x11) at pci6 dev 0 function 1 not configured
> ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
> pci7 at ppb6 bus 7
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 0x11) at pci7 dev 0 function 1 not configured
> vendor "Intel", unknown product 0x19d3 (class communications subclass miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
> vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) at pci0 dev 31 function 0 not configured
> vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, rev 0x11) at pci0 dev 31 function 2 not configured
> vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 0x11) at pci0 dev 31 function 4 not configured
> vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 0x80, rev 0x11) at pci0 dev 31 function 5 not configured
> isa0 at mainbus0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> efifb0 at mainbus0: 1920x1200, 32bpp
> wsdisplay at efifb0 not configured
> softraid0 at root
> scsibus0 at softraid0: 256 targets
> root on rd0a swap on rd0b dump on rd0b
> erase ^?, werase ^W, kill ^U, intr ^C, status ^T
>
> Welcome to the OpenBSD/amd64 6.5 installation program.
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell?
>
>
> Regards,
>
> Richard
>
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

ms-2
In reply to this post by Stuart Henderson
https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html

https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html

Now a day backdors are already on the silicon level (inside chips). They
are declared as debugging interfaces..


It looks like at least the reengineering of the frimware an it is
analyzing of the code could increase security wholes

https://resources.infosecinstitute.com/reversing-firmware-part-1/#gref


I am curious if someone on this list had tried to do it and had achieved
helpfull results..


On 15.06.19 17:11, Stuart Henderson wrote:

> On 2019-06-15, ms <[hidden email]> wrote:
>> There were some serious security issues with hardware and software from
>> Supermicro (espionage chips, firmware)
> Assuming you mean the allegations in that Bloomberg piece, there was no
> evidence found supporting them.
>
> https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc
>
> There are the usual problems with BMC security, cpu bugs, etc, but those
> are by no means unique to supermicro.
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

lists-2
Sat, 15 Jun 2019 23:52:18 +0200 ms <[hidden email]>
> Now a day backdors are already on the silicon level (inside chips). They
> are declared as debugging interfaces..

Must have happened around the time when school dropouts went to business.

> It looks like at least the reengineering of the frimware an it is
> analyzing of the code could increase security wholes

Wonderful day for some misspelled general Failure statements.. is it not?

> I am curious if someone on this list had tried to do it and had achieved
> helpfull results..

No, but if you need an English textbook, computers are not your strength.

Obviously you missed the topic of the thread and the hardware specifics..

Or at the least just try to say something OpenBSD related for any points.

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

ms-2
I am sorry for NOT reading my content again before posting it, my fault.


On 16.06.19 06:35, [hidden email] wrote:
> Sat, 15 Jun 2019 23:52:18 +0200 ms <[hidden email]>
>> Now a day backdors are already on the silicon level (inside chips). They
>> are declared as debugging interfaces..
> Must have happened around the time when school dropouts went to business.

What do you want to say? Do you have experience in chip design?

Probably not ..


>> It looks like at least the reengineering of the frimware an it is
>> analyzing of the code could increase security wholes
> Wonderful day for some misspelled general Failure statements.. is it not?

"It looks like at least the reengineering of the firmware

and the analysis of the code could increase the security, to avoid
security wholes"


>> I am curious if someone on this list had tried to do it and had achieved
>> helpfull results..
> No, but if you need an English textbook, computers are not your strength.
>
> Obviously you missed the topic of the thread and the hardware specifics..
>
> Or at the least just try to say something OpenBSD related for any points.

The OpenBSD related point is, that people are using OpenBSD because of
security and it does not really make sense to run OpenBSD on unsecure
hardware / firmware.


Have you got it now?


Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Stuart Longland
On 16/6/19 1:23 pm, ms wrote:
>>> Now a day backdors are already on the silicon level (inside chips). They
>>> are declared as debugging interfaces..
>> Must have happened around the time when school dropouts went to business.
>
> What do you want to say? Do you have experience in chip design?

Do you design and make your own x86 chips?  Do you inspect the dies of
all off-the-shelf chips you buy?
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Reply | Threaded
Open this post in threaded view
|

hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Luke Call
In reply to this post by Stuart Henderson
And I think I read that Supermicro is moving production
out of China because of the perceptions of risk (and/or actual
risks) of sensitive electronics manufacturing there.

Forgive/ignore if this question is excessive here, but I
wonder if anyone has knowledge or educated perspective to share
on this:  I have avoided Chinese products (like Lenovo) due to
government history/means/motive/opportunity to put in backdoors
or things with which I might be less comfortable than the
backdoors unfortunately inserted by someone else.  Just like I've
been favoring AMD due to Intel's track record and evident attitude.)
Yes, the US government has been reported to waylay hardware
during shipping, etc., and Bruce Schneier and/or others
have said the problem of vetting hardware is beyond
the ability of individuals or most businesses, given the
extreme economic and technical complexity involved.  (And
I realize that suspicion can be carried too far, and cost/benefit
estimates can sometimes even favor less caution, but one has to
choose whom to work with, given tradeoffs and an imperfect world.
I know Theo has said in efffect that hardware security is not
a problem OBSD can address, and if that is the final answer, OK.)

But I wonder sometimes if anyone knows of a laptop &/or desktop
vendor where the odds seem most favorable, maybe why you
think so, and where they are likely to work with OBSD. (System76,
librem, dell, small/local manufacturers)?  (My audio, video, and
battery needs are minimal, but *quiet* effective thermal management, &
16GB+ RAM are important, and reliability & compilation speed.)  
AMD CPUs preferred, as going exotic sounds like more $ and
harder to get spare parts.  And I probably don't have the ability
now or later to become expert at choosing many individual
components.  Thanks in advance.
--
Luke Call
Things I want to say to many (a lightly-loading site):
http://lukecall.net  (updated 2019-06-09)


On 06-15 15:11, Stuart Henderson wrote:

> On 2019-06-15, ms <[hidden email]> wrote:
> > There were some serious security issues with hardware and software from
> > Supermicro (espionage chips, firmware)
>
> Assuming you mean the allegations in that Bloomberg piece, there was no
> evidence found supporting them.
>
> https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc
>
> There are the usual problems with BMC security, cpu bugs, etc, but those
> are by no means unique to supermicro.
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Stuart Henderson
In reply to this post by ms-2
On 2019-06-15, ms <[hidden email]> wrote:
> https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html
>
> https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html

Those are based on the discredited Bloomberg piece I mentioned.

> Now a day backdors are already on the silicon level (inside chips). They
> are declared as debugging interfaces..

You'll find that sort of crap whichever way you look.


Reply | Threaded
Open this post in threaded view
|

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

lists-2
In reply to this post by ms-2
Sun, 16 Jun 2019 05:23:36 +0200 ms <[hidden email]>
> "It looks like at least the reengineering of the firmware
>
> and the analysis of the code could increase the security, to avoid
> security wholes"
>          ^^^^^^

Your clock is off.  Wrong time is a serious reliability & security flaw.
Before you look for the security problems in firmware, fix obvious ones.

Reply | Threaded
Open this post in threaded view
|

Re: hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

Joseph Borg
In reply to this post by Luke Call
apparently the F-35 project sources motherboards for key instrumentation
from China.

This is a new economic cold war. Do what you feel best but a big part of  
this is politics.

Maybe the list should qualify when a mail thread is verging on personal
politics and out of strictly technical subject the list is supposed to handle.

regards

> On 16 Jun 2019, at 21:28, Luke A. Call <[hidden email]> wrote:
>
> And I think I read that Supermicro is moving production
> out of China because of the perceptions of risk (and/or actual
> risks) of sensitive electronics manufacturing there.
>
> Forgive/ignore if this question is excessive here, but I
> wonder if anyone has knowledge or educated perspective to share
> on this:  I have avoided Chinese products (like Lenovo) due to
> government history/means/motive/opportunity to put in backdoors
> or things with which I might be less comfortable than the
> backdoors unfortunately inserted by someone else.  Just like I've
> been favoring AMD due to Intel's track record and evident attitude.)
> Yes, the US government has been reported to waylay hardware
> during shipping, etc., and Bruce Schneier and/or others
> have said the problem of vetting hardware is beyond
> the ability of individuals or most businesses, given the
> extreme economic and technical complexity involved.  (And
> I realize that suspicion can be carried too far, and cost/benefit
> estimates can sometimes even favor less caution, but one has to
> choose whom to work with, given tradeoffs and an imperfect world.
> I know Theo has said in efffect that hardware security is not
> a problem OBSD can address, and if that is the final answer, OK.)
>
> But I wonder sometimes if anyone knows of a laptop &/or desktop
> vendor where the odds seem most favorable, maybe why you
> think so, and where they are likely to work with OBSD. (System76,
> librem, dell, small/local manufacturers)?  (My audio, video, and
> battery needs are minimal, but *quiet* effective thermal management, &
> 16GB+ RAM are important, and reliability & compilation speed.)  
> AMD CPUs preferred, as going exotic sounds like more $ and
> harder to get spare parts.  And I probably don't have the ability
> now or later to become expert at choosing many individual
> components.  Thanks in advance.
> --
> Luke Call
> Things I want to say to many (a lightly-loading site):
> http://lukecall.net  (updated 2019-06-09)
>
>
> On 06-15 15:11, Stuart Henderson wrote:
>> On 2019-06-15, ms <[hidden email]> wrote:
>>> There were some serious security issues with hardware and software from
>>> Supermicro (espionage chips, firmware)
>>
>> Assuming you mean the allegations in that Bloomberg piece, there was no
>> evidence found supporting them.
>>
>> https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc
>>
>> There are the usual problems with BMC security, cpu bugs, etc, but those
>> are by no means unique to supermicro.
>>
>>
>