Intel X553 and Supermicro A2SDi-4C-HLN4F Networking
Hello, For those who are interested, the most recent snapshots contain support for the Intel X553 copper NICs used on the Supermicro A2SDi-4C-HLN4F boards. I have tested this on a couple of systems and I am seeing about 940 Mbps with tcpbench(1) using a direct cable connection. I am guessing that this support is likely to be in the 6.7 release Thanks to all the OpenBSD developers for your great work! dmesg from one of the systems below Richard OpenBSD 6.6-current (GENERIC.MP) #43: Mon Mar 9 20:52:27 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17125621760 (16332MB) avail mem = 16594010112 (15825MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries) bios0: vendor American Megatrends Inc. version "1.2" date 11/05/2019 bios0: Supermicro Super Server acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT APIC BDAT HPET UEFI SSDT DMAR HEST BERT ERST EINJ WSMT acpi0: wakeup devices XHC1(S4) OBL1(S4) LAN1(S4) PEX0(S4) LAN2(S4) LAN3(S4) PEX1(S4) PEX6(S4) PEX7(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.42 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,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 2MB 64b/line 16-way L2 cache cpu0: cannot disable silicon debug cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 25MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE cpu1 at mainbus0: apid 12 (application processor) cpu1: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.02 MHz, 06-5f-01 cpu1: 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,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 2MB 64b/line 16-way L2 cache cpu1: cannot disable silicon debug cpu1: smt 0, core 6, package 0 cpu2 at mainbus0: apid 16 (application processor) cpu2: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.01 MHz, 06-5f-01 cpu2: 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,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 2MB 64b/line 16-way L2 cache cpu2: cannot disable silicon debug cpu2: smt 0, core 8, package 0 cpu3 at mainbus0: apid 24 (application processor) cpu3: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.01 MHz, 06-5f-01 cpu3: 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,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 2MB 64b/line 16-way L2 cache cpu3: cannot disable silicon debug cpu3: smt 0, core 12, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 6 (VRP0) acpiprt2 at acpi0: bus 2 (PEX0) acpiprt3 at acpi0: bus 1 (VRP2) acpiprt4 at acpi0: bus 7 (VRP1) acpiprt5 at acpi0: bus -1 (PEX1) acpiprt6 at acpi0: bus 3 (PEX6) acpiprt7 at acpi0: bus 4 (PEX7) acpiprt8 at acpi0: bus 5 (BR28) acpicpu0 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu1 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu2 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpicpu3 at acpi0: C2(10@50 mwait.1@0x21), C1(1000@1 mwait.1@0x1), PSS acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x "PNP0003" at acpi0 not configured acpicmos0 at acpi0 "IPI0001" at acpi0 not configured "PNP0C33" at acpi0 not configured ipmi at mainbus0 not configured cpu0: E
Re: hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 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 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. >> >> >
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
Sun, 16 Jun 2019 05:23:36 +0200 ms > "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.
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
On 2019-06-15, ms 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.
hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 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. > >
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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.
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
I am sorry for NOT reading my content again before posting it, my fault. On 16.06.19 06:35, li...@wrant.com wrote: Sat, 15 Jun 2019 23:52:18 +0200 ms 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?
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
Sat, 15 Jun 2019 23:52:18 +0200 ms > 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.
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 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.
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 > 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 >dera...@amd64.openbsd.org:/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 0xfe01/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 &
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
On 2019-06-15, ms 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.
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
On Sat, 15 Jun 2019 19:36:23 +1000 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. > 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 dera...@amd64.openbsd.org:/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 0xfee0: 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 0xfec0, 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 0xfe01/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 3
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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
Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 > dera...@amd64.openbsd.org:/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 0xfe01/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)
Installing OpenBSD on Supermicro A2SDi-4C-HLN4F
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 dera...@amd64.openbsd.org:/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 0xfe01/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
Re: SuperMicro A2SDi-4C-HLN4F
On August 25, 2018 1:59:55 PM GMT+02:00, Rupert Gallagher wrote: > wrote: > >> This vendor addresses hardware & firmware faults like the other >enterprise vendors, they DON'T past year two. BIOS and BMC firmwares >are not updated after this even with the long term lifetime products, >you are on your own! > >On bios and ipmi updates, you can download and apply them yourself. For >advanced bios updates, there is a licence you can purchase, as you do >with Dell and HP. > >On warranty, they are in line with the industry standards: > >https://www.supermicro.com/support/Warranty/ > >On open source, they work with the community, well enough to have a >cetified list of compatible systems: > >https://www.supermicro.com/support/faqs/os.cfm > >When you are in business, you do not want to go back to the drawing >board each time. You need a platform where to build your own services. >If you have to develop disk and keyboard drivers, and you are told off >from the support mailing list, then the OS is worth nothing to you. - That there is no current support, does not mean there will never be. - misc@ is not a support mailing list. In fact, there is none. That does not, however, mean that you can't get help from there. >OpenBSD is not ready for enterprise. By some definition of "for enterprise", sure. /Alexander > >Your faithfull troll.
Re: SuperMicro A2SDi-4C-HLN4F
On 2018-08-26, Mihai Popescu wrote: >> OpenBSD is not ready for enterprise. > > Fantastic intuition here [1]. > > [1] https://marc.info/?l=openbsd-misc=153385998722067=2 > > Would you mind fixing your thread headers please? My killfile entry for threads with 'protonmail.com' in references doesn't work very well otherwise ;)
Re: SuperMicro A2SDi-4C-HLN4F
Popescu, obsd does not always work. Hiding the bugs, instead of showing them on git issues or bugzilla, it does not make obsd any better. Sent from ProtonMail Mobile
Re: SuperMicro A2SDi-4C-HLN4F
> OpenBSD is not ready for enterprise. Fantastic intuition here [1]. [1] https://marc.info/?l=openbsd-misc=153385998722067=2
Re: SuperMicro A2SDi-4C-HLN4F
wrote: > This vendor addresses hardware & firmware faults like the other enterprise > vendors, they DON'T past year two. BIOS and BMC firmwares are not updated > after this even with the long term lifetime products, you are on your own! On bios and ipmi updates, you can download and apply them yourself. For advanced bios updates, there is a licence you can purchase, as you do with Dell and HP. On warranty, they are in line with the industry standards: https://www.supermicro.com/support/Warranty/ On open source, they work with the community, well enough to have a cetified list of compatible systems: https://www.supermicro.com/support/faqs/os.cfm When you are in business, you do not want to go back to the drawing board each time. You need a platform where to build your own services. If you have to develop disk and keyboard drivers, and you are told off from the support mailing list, then the OS is worth nothing to you. OpenBSD is not ready for enterprise. Your faithfull troll.
Re: SuperMicro A2SDi-4C-HLN4F
On 2018 Aug 20 (Mon) at 05:29:50 +0300 (+0300), li...@wrant.com wrote: :You get what you ask for. Says much about your original intent, to spread :negative abusive words. You fail to disrupt anything, no one has the time :to read your boot up complaints with offensive language. Get out of here. wrant, Shut up. You are routinely abusive and not helpful. Don't lecture people on tone, or how useful someone is. You have always failed in that comparision. Don't respond, just shut up.
Re: SuperMicro A2SDi-4C-HLN4F
Sun, 19 Aug 2018 08:34:43 + Rupert Gallagher > Troll here... Rupert, > Step out of your nerdiness, and step into the real world with this scenario. A troll mini speaker calls real world their empty words on a mailing list. You are simply ignored. In fact, you send total nonsense all around. And the basis of your miniature demanding pretences has no meaning whatsoever. > A well-known vendor of server boards has an entite product line based on > intel atom C3000 cpus. Windows corporate & assembly shops targeting vendor. "Producing", but not actually carrying (relies on third party selling service and has a smaller global SKU list) boards. They frequently fail before, or near the limited warranty. At this point you better use desktop boards from other vendors. Especially other CPU vendors outside Intel's dominating position of FAILS. > Each product has a list of certified operating systems, including windows, > freebsd, red hat linux enterprise, esxi. You speak of the self proclaimed Enterprise segment, that is mostly vendor locked hardware fault addressing extra cost. You can not push your demand and your wishes to have support where vendors try to exclude free systems. Why don't you just ask direct the vendor instead, see what they give you?! > The list does not include openbsd. How are you helping this process, Rupert? At this point, you are throwing offence past simply comparing with sponsored software "other OS" versions. > You spend a few days testing the server with various oss. Minimum effort it is. That is your own fault, everything else is ignored. > It turns out that the server *works* with everything linux, including debian, > proxmox, centos. As in "works past the hardware faults", boots up. You should rather use a board that is more popular, has been tested out thoroughly, has seen wider market adoption, bugs caught, with new revision of CPU and firmware fixes. This vendor addresses hardware & firmware faults like the other enterprise vendors, they DON'T past year two. BIOS and BMC firmwares are not updated after this even with the long term lifetime products, you are on your own! > It also turns out that openbsd fails to recognise the devices, including the > disks, and the keyboard. You should really put some more effort into this to see how it progresses. > Then you post its dmesg, because obsd folks really like it, together with a > positive dmesg from centos. So you dictate now which unsupported boards are in use? You are a nobody. Positive-negative is your opinion only, it doesn't matter past your mouth. > Someone intervenes spreading FUD about the server and flaming you are a > troll. You get what you ask for. Says much about your original intent, to spread negative abusive words. You fail to disrupt anything, no one has the time to read your boot up complaints with offensive language. Get out of here. Kind regards, Anton Lazarov > On Sun, Aug 19, 2018 at 00:06, wrote: > > > Sat, 18 Aug 2018 12:28:17 + Rupert Gallagher > >> I am not complaining about obsd. > >> > >> I am complaining about your FUD on C3000 and your request for a > >> post-installation dmesg. No installation is possible for lack of disk > >> drivers. I do not develop/port drivers. The dmesgs I already posted > >> are all I can share. > >> > >> The only way to run obsd at this time is via qemu/proxmox or > >> vmware/esxi. > > > > Rupert, > > > > You would not have to complain if you hadn't spammed your puny pretences. > > The boards and processors have issues to be known, accompanying warnings. > > > > The dmesg you posted does not help anything. It looks like a poorly done > > commercial for other operating systems that "supposedly" work. Only, you > > have not been running anything past boot up. Accept it, you are a troll. > > > > Looks like you point out there are "drivers to be written", for your use. > > I call this helpless whining. I told you how you can help this process.. > > > > Get the boards in the hands of developers with OpenBSD who write drivers. > > And first kindly ask about it whether it is possible to fit in busy work. > > > > Kind regards, > > Anton Lazarov > > > >> On Sat, Aug 18, 2018 at 12:55, wrote: > >> > >> > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher > >> >> Orher architectures are explicitly known for being bugged, but this > >> >> did not stop the developers. > >> > > >> > Hi Rupert, > >> > > >> > Enough already, just post a full dmesg when you can. The hardware is not > >> > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > >> > > >> > They also include a lot more than the CPU where most of the problems are. > >> > So keep an eye on these boards and be a bit more impartial and objective. > >> > > >> > It would be so nice if you could ship new boards like these to developers > >> > or donate some of your excess hardware costs so that they get the boards. > >> > > >> > That might be much more
Re: SuperMicro A2SDi-4C-HLN4F
Troll here... Step out of your nerdiness, and step into the real world with this scenario. A well-known vendor of server boards has an entite product line based on intel atom C3000 cpus. Each product has a list of certified operating systems, including windows, freebsd, red hat linux enterprise, esxi. The list does not include openbsd. You spend a few days testing the server with various oss. It turns out that the server *works* with everything linux, including debian, proxmox, centos. It also turns out that openbsd fails to recognise the devices, including the disks, and the keyboard. Then you post its dmesg, because obsd folks really like it, together with a positive dmesg from centos. Someone intervenes spreading FUD about the server and flaming you are a troll. You know what? Fuck you. Sent from ProtonMail Mobile On Sun, Aug 19, 2018 at 00:06, wrote: > Sat, 18 Aug 2018 12:28:17 + Rupert Gallagher >> I am not complaining about obsd. >> >> I am complaining about your FUD on C3000 and your request for a >> post-installation dmesg. No installation is possible for lack of disk >> drivers. I do not develop/port drivers. The dmesgs I already posted >> are all I can share. >> >> The only way to run obsd at this time is via qemu/proxmox or >> vmware/esxi. > > Rupert, > > You would not have to complain if you hadn't spammed your puny pretences. > The boards and processors have issues to be known, accompanying warnings. > > The dmesg you posted does not help anything. It looks like a poorly done > commercial for other operating systems that "supposedly" work. Only, you > have not been running anything past boot up. Accept it, you are a troll. > > Looks like you point out there are "drivers to be written", for your use. > I call this helpless whining. I told you how you can help this process.. > > Get the boards in the hands of developers with OpenBSD who write drivers. > And first kindly ask about it whether it is possible to fit in busy work. > > Kind regards, > Anton Lazarov > >> On Sat, Aug 18, 2018 at 12:55, wrote: >> >> > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher >> >> Orher architectures are explicitly known for being bugged, but this >> >> did not stop the developers. >> > >> > Hi Rupert, >> > >> > Enough already, just post a full dmesg when you can. The hardware is not >> > perfect, watch out for unfixed CPU bugs as these are soldered down chips. >> > >> > They also include a lot more than the CPU where most of the problems are. >> > So keep an eye on these boards and be a bit more impartial and objective. >> > >> > It would be so nice if you could ship new boards like these to developers >> > or donate some of your excess hardware costs so that they get the boards. >> > >> > That might be much more helpful than complaints over the installer dmesg. >> > >> > Kind regards, >> > Anton Lazarov >> > >> >> On Fri, Aug 17, 2018 at 22:09, wrote: >> >> >> >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> >> >> This is a really nice board at a really nice price, and you should >> >> >> stop scaring people off. These Atoms are cleaner than both Cores and >> >> >> Xeons, and AMDs have have their fair share of problems. Citin g >> >> >> C2000 against the latest C3000 is FUD. You should come clean first, >> >> >> and cite a comparable server board at a comparable cost and clear of >> >> >> bugs. >> >> > >> >> > Rupert, >> >> > >> >> > The publication and processor specifications are about the C3000 CPU >> >> > bug. >> >> > Similar hardware flaws affect the new C3000 CPUs, same >> >> > microarchitecture. >> >> > These Atoms are also fully affected by Intel HW flaws Spectre & >> >> > Meltdown. >> >> > >> >> > With NONE real hardware understanding, you have to rely upon vendor >> >> > spec. >> >> > With NONE single dmesg after installation, you can NOT advise this >> >> > board. >> >> > With NONE real OpenBSD experience, you better ask the developers >> >> > instead. >> >> > >> >> > You are speculatively advertising yet unsupported boards as feature >> >> > sets. >> >> > Not interested reading anything that pops in your visibility on the >> >> > list. >> >> > It takes very little effort to have some opinion and I do NOT want >> >> > yours. >> >> > >> >> > Kind regards, >> >> > Anton Lazarov >> >> > >> >> >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> >> >> >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> >> >> > >> >> >> >> FUD >> >> >> >> >> >> >> >> Sent from total and utter ignorance. >> >> >> > >> >> >> > Rupert, >> >> >> > >> >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> >> >> > kernel. You Should complete an actual OpenBSD installation to get >> >> >> > the full dmesg. >> >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> >> >> > >> >> >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> >> >> and it is possible to
Re: SuperMicro A2SDi-4C-HLN4F
Sat, 18 Aug 2018 12:28:17 + Rupert Gallagher > I am not complaining about obsd. > > I am complaining about your FUD on C3000 and your request for a > post-installation dmesg. No installation is possible for lack of disk > drivers. I do not develop/port drivers. The dmesgs I already posted > are all I can share. > > The only way to run obsd at this time is via qemu/proxmox or > vmware/esxi. Rupert, You would not have to complain if you hadn't spammed your puny pretences. The boards and processors have issues to be known, accompanying warnings. The dmesg you posted does not help anything. It looks like a poorly done commercial for other operating systems that "supposedly" work. Only, you have not been running anything past boot up. Accept it, you are a troll. Looks like you point out there are "drivers to be written", for your use. I call this helpless whining. I told you how you can help this process.. Get the boards in the hands of developers with OpenBSD who write drivers. And first kindly ask about it whether it is possible to fit in busy work. Kind regards, Anton Lazarov > On Sat, Aug 18, 2018 at 12:55, wrote: > > > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher > >> Orher architectures are explicitly known for being bugged, but this > >> did not stop the developers. > > > > Hi Rupert, > > > > Enough already, just post a full dmesg when you can. The hardware is not > > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > > > > They also include a lot more than the CPU where most of the problems are. > > So keep an eye on these boards and be a bit more impartial and objective. > > > > It would be so nice if you could ship new boards like these to developers > > or donate some of your excess hardware costs so that they get the boards. > > > > That might be much more helpful than complaints over the installer dmesg. > > > > Kind regards, > > Anton Lazarov > > > >> On Fri, Aug 17, 2018 at 22:09, wrote: > >> > >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher > >> >> This is a really nice board at a really nice price, and you should > >> >> stop scaring people off. These Atoms are cleaner than both Cores and > >> >> Xeons, and AMDs have have their fair share of problems. Citin g > >> >> C2000 against the latest C3000 is FUD. You should come clean first, > >> >> and cite a comparable server board at a comparable cost and clear of > >> >> bugs. > >> > > >> > Rupert, > >> > > >> > The publication and processor specifications are about the C3000 CPU bug. > >> > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > >> > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > >> > > >> > With NONE real hardware understanding, you have to rely upon vendor spec. > >> > With NONE single dmesg after installation, you can NOT advise this board. > >> > With NONE real OpenBSD experience, you better ask the developers instead. > >> > > >> > You are speculatively advertising yet unsupported boards as feature sets. > >> > Not interested reading anything that pops in your visibility on the list. > >> > It takes very little effort to have some opinion and I do NOT want yours. > >> > > >> > Kind regards, > >> > Anton Lazarov > >> > > >> >> On Fri, Aug 17, 2018 at 17:38, wrote: > >> >> > >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > >> >> > > >> >> >> FUD > >> >> >> > >> >> >> Sent from total and utter ignorance. > >> >> > > >> >> > Rupert, > >> >> > > >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD > >> >> > kernel. You Should complete an actual OpenBSD installation to get > >> >> > the full dmesg. > >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: > >> >> >> > >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> >> >> > > >> >> >> >> Using the serial over lan console, the keyboard keeps working, > >> >> >> >> and it is possible to enter the shell. Using the standard > >> >> >> >> console, the keyboard does not work. There is plenty of drivers > >> >> >> >> that need to be written. No, I do not write/port drivers. > >> >> >> >> > >> >> >> >> By comparison, both freebsd and centos linux just work out of > >> >> >> >> the box. Both dmesgs are attached as reference. > >> >> >> >> > >> >> >> >> The board is really nice. > >> >> >> >> > >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> >> >> >> wrote: > >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > >> >> >> >> > > >> >> >> > > >> >> >> > Hi misc@, > >> >> >> > > >> >> >> > This one is much quieter, the vendors have reacted to the > >> >> >> > previous flaw. As nice as it can get.. before trusting > >> >> >> > non-technical reviews, be aware: > >> >> >> > > >> >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum > >> >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > >> >> >> >
Re: SuperMicro A2SDi-4C-HLN4F
I am not complaining about obsd. I am complaining about your FUD on C3000 and your request for a post-installation dmesg. No installation is possible for lack of disk drivers. I do not develop/port drivers. The dmesgs I already posted are all I can share. The only way to run obsd at this time is via qemu/proxmox or vmware/esxi. On Sat, Aug 18, 2018 at 12:55, wrote: > Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher >> Orher architectures are explicitly known for being bugged, but this >> did not stop the developers. > > Hi Rupert, > > Enough already, just post a full dmesg when you can. The hardware is not > perfect, watch out for unfixed CPU bugs as these are soldered down chips. > > They also include a lot more than the CPU where most of the problems are. > So keep an eye on these boards and be a bit more impartial and objective. > > It would be so nice if you could ship new boards like these to developers > or donate some of your excess hardware costs so that they get the boards. > > That might be much more helpful than complaints over the installer dmesg. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 22:09, wrote: >> >> > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> >> This is a really nice board at a really nice price, and you should >> >> stop scaring people off. These Atoms are cleaner than both Cores and >> >> Xeons, and AMDs have have their fair share of problems. Citin g >> >> C2000 against the latest C3000 is FUD. You should come clean first, >> >> and cite a comparable server board at a comparable cost and clear of >> >> bugs. >> > >> > Rupert, >> > >> > The publication and processor specifications are about the C3000 CPU bug. >> > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. >> > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. >> > >> > With NONE real hardware understanding, you have to rely upon vendor spec. >> > With NONE single dmesg after installation, you can NOT advise this board. >> > With NONE real OpenBSD experience, you better ask the developers instead. >> > >> > You are speculatively advertising yet unsupported boards as feature sets. >> > Not interested reading anything that pops in your visibility on the list. >> > It takes very little effort to have some opinion and I do NOT want yours. >> > >> > Kind regards, >> > Anton Lazarov >> > >> >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> >> > >> >> >> FUD >> >> >> >> >> >> Sent from total and utter ignorance. >> >> > >> >> > Rupert, >> >> > >> >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> >> > kernel. You Should complete an actual OpenBSD installation to get >> >> > the full dmesg. >> >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> >> > >> >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> >> and it is possible to enter the shell. Using the standard >> >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> >> wrote: >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> >> > >> >> >> > Hi misc@, >> >> >> > >> >> >> > This one is much quieter, the vendors have reacted to the >> >> >> > previous flaw. As nice as it can get.. before trusting >> >> >> > non-technical reviews, be aware: >> >> >> > >> >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> >> >> > https://www.google.com/search?q=intel+c3000+bug >> >> >> > >> >> >> > Recurring issue - similar problems were discussed noisily >> >> >> > industry wide: >> >> >> > >> >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> >> >> > https://www.google.com/search?q=intel+c2000+bug >> >> >> > >> >> >> > As with the previous generation processors and main boards, >> >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs >> >> >> > and prepare for RMA. >> >> >> > >> >> >> > Kind regards, >> >> >> > Anton Lazarov >> >> > >> >> > "Similar to previous Silvermont generation design flaws were found >> >> > in processor circuitry resulting in cease of operation when >> >> > processors are actively used for several years. Errata named >> >> > >> >> > APL47 System May Experience Inability to Boot or May Cease Operation >> >> > >> >> > and
Re: SuperMicro A2SDi-4C-HLN4F
Sat, 18 Aug 2018 08:29:33 + Rupert Gallagher > Orher architectures are explicitly known for being bugged, but this > did not stop the developers. Hi Rupert, Enough already, just post a full dmesg when you can. The hardware is not perfect, watch out for unfixed CPU bugs as these are soldered down chips. They also include a lot more than the CPU where most of the problems are. So keep an eye on these boards and be a bit more impartial and objective. It would be so nice if you could ship new boards like these to developers or donate some of your excess hardware costs so that they get the boards. That might be much more helpful than complaints over the installer dmesg. Kind regards, Anton Lazarov > On Fri, Aug 17, 2018 at 22:09, wrote: > > > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher > >> This is a really nice board at a really nice price, and you should > >> stop scaring people off. These Atoms are cleaner than both Cores and > >> Xeons, and AMDs have have their fair share of problems. Citin g > >> C2000 against the latest C3000 is FUD. You should come clean first, > >> and cite a comparable server board at a comparable cost and clear of > >> bugs. > > > > Rupert, > > > > The publication and processor specifications are about the C3000 CPU bug. > > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > > > > With NONE real hardware understanding, you have to rely upon vendor spec. > > With NONE single dmesg after installation, you can NOT advise this board. > > With NONE real OpenBSD experience, you better ask the developers instead. > > > > You are speculatively advertising yet unsupported boards as feature sets. > > Not interested reading anything that pops in your visibility on the list. > > It takes very little effort to have some opinion and I do NOT want yours. > > > > Kind regards, > > Anton Lazarov > > > >> On Fri, Aug 17, 2018 at 17:38, wrote: > >> > >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > >> > > >> >> FUD > >> >> > >> >> Sent from total and utter ignorance. > >> > > >> > Rupert, > >> > > >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD > >> > kernel. You Should complete an actual OpenBSD installation to get > >> > the full dmesg. > >> >> On Fri, Aug 17, 2018 at 12:24, wrote: > >> >> > >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> >> > > >> >> >> Using the serial over lan console, the keyboard keeps working, > >> >> >> and it is possible to enter the shell. Using the standard > >> >> >> console, the keyboard does not work. There is plenty of drivers > >> >> >> that need to be written. No, I do not write/port drivers. > >> >> >> > >> >> >> By comparison, both freebsd and centos linux just work out of > >> >> >> the box. Both dmesgs are attached as reference. > >> >> >> > >> >> >> The board is really nice. > >> >> >> > >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> >> >> wrote: > >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > >> >> >> > > >> >> > > >> >> > Hi misc@, > >> >> > > >> >> > This one is much quieter, the vendors have reacted to the > >> >> > previous flaw. As nice as it can get.. before trusting > >> >> > non-technical reviews, be aware: > >> >> > > >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum > >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > >> >> > https://www.google.com/search?q=intel+c3000+bug > >> >> > > >> >> > Recurring issue - similar problems were discussed noisily > >> >> > industry wide: > >> >> > > >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum > >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > >> >> > https://www.google.com/search?q=intel+c2000+bug > >> >> > > >> >> > As with the previous generation processors and main boards, > >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs > >> >> > and prepare for RMA. > >> >> > > >> >> > Kind regards, > >> >> > Anton Lazarov > >> > > >> > "Similar to previous Silvermont generation design flaws were found > >> > in processor circuitry resulting in cease of operation when > >> > processors are actively used for several years. Errata named > >> > > >> > APL47 System May Experience Inability to Boot or May Cease Operation > >> > > >> > and > >> > > >> > APL48 System May Experience Non-functioning GPIO Weak Pull-up > >> > Circuitry > >> > > >> > were added to documentation in June 2017 stating: > >> > > >> > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) > >> > card and General-Purpose Input/Output (GPIO) interfaces may stop > >> > functioning. > >> > > >> > The documents cited in the Wikipedia article, see for current > >> > versions.. that apply to the later CPU
Re: SuperMicro A2SDi-4C-HLN4F
I can pay you with your same currency. You have no experience installing openbsd on a new architecture: > Available disks are: none Your references are not specific to the C3000 architecture. Orher architectures are explicitly known for being bugged, but this did not stop the developers. On Fri, Aug 17, 2018 at 22:09, wrote: > Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher >> This is a really nice board at a really nice price, and you should >> stop scaring people off. These Atoms are cleaner than both Cores and >> Xeons, and AMDs have have their fair share of problems. Citin g >> C2000 against the latest C3000 is FUD. You should come clean first, >> and cite a comparable server board at a comparable cost and clear of >> bugs. > > Rupert, > > The publication and processor specifications are about the C3000 CPU bug. > Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. > These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. > > With NONE real hardware understanding, you have to rely upon vendor spec. > With NONE single dmesg after installation, you can NOT advise this board. > With NONE real OpenBSD experience, you better ask the developers instead. > > You are speculatively advertising yet unsupported boards as feature sets. > Not interested reading anything that pops in your visibility on the list. > It takes very little effort to have some opinion and I do NOT want yours. > > Kind regards, > Anton Lazarov > >> On Fri, Aug 17, 2018 at 17:38, wrote: >> >> > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> > >> >> FUD >> >> >> >> Sent from total and utter ignorance. >> > >> > Rupert, >> > >> > Plus the dmesg you posted is by the RAM disk installation OpenBSD >> > kernel. You Should complete an actual OpenBSD installation to get >> > the full dmesg. >> >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> > >> >> >> Using the serial over lan console, the keyboard keeps working, >> >> >> and it is possible to enter the shell. Using the standard >> >> >> console, the keyboard does not work. There is plenty of drivers >> >> >> that need to be written. No, I do not write/port drivers. >> >> >> >> >> >> By comparison, both freebsd and centos linux just work out of >> >> >> the box. Both dmesgs are attached as reference. >> >> >> >> >> >> The board is really nice. >> >> >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> >> wrote: >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> >> > >> >> > Hi misc@, >> >> > >> >> > This one is much quieter, the vendors have reacted to the >> >> > previous flaw. As nice as it can get.. before trusting >> >> > non-technical reviews, be aware: >> >> > >> >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> >> > https://www.google.com/search?q=intel+c3000+bug >> >> > >> >> > Recurring issue - similar problems were discussed noisily >> >> > industry wide: >> >> > >> >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> >> > https://www.google.com/search?q=intel+c2000+bug >> >> > >> >> > As with the previous generation processors and main boards, >> >> > Intel FAILS. Wait for updated CPU revision boards, consult techs >> >> > and prepare for RMA. >> >> > >> >> > Kind regards, >> >> > Anton Lazarov >> > >> > "Similar to previous Silvermont generation design flaws were found >> > in processor circuitry resulting in cease of operation when >> > processors are actively used for several years. Errata named >> > >> > APL47 System May Experience Inability to Boot or May Cease Operation >> > >> > and >> > >> > APL48 System May Experience Non-functioning GPIO Weak Pull-up >> > Circuitry >> > >> > were added to documentation in June 2017 stating: >> > >> > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) >> > card and General-Purpose Input/Output (GPIO) interfaces may stop >> > functioning. >> > >> > The documents cited in the Wikipedia article, see for current >> > versions.. that apply to the later CPU stepping models, if any, as >> > time progresses: >> > >> > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf >> > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf >> > >> > APL47 Problem: Under certain conditions LPC, SD card and RTC >> > circuitry may stop functioning in the outer years of use. >> > >> > APL48 Problem: When platform drives the GPIO pin low, GPIOs >> > programmed with weak pull-up circuitry may not maintain a value >> > above VIH when not actively driven in outer years of service."
Re: SuperMicro A2SDi-4C-HLN4F
Fri, 17 Aug 2018 16:48:52 + Rupert Gallagher > This is a really nice board at a really nice price, and you should > stop scaring people off. These Atoms are cleaner than both Cores and > Xeons, and AMDs have have their fair share of problems. Citin g > C2000 against the latest C3000 is FUD. You should come clean first, > and cite a comparable server board at a comparable cost and clear of > bugs. Rupert, The publication and processor specifications are about the C3000 CPU bug. Similar hardware flaws affect the new C3000 CPUs, same microarchitecture. These Atoms are also fully affected by Intel HW flaws Spectre & Meltdown. With NONE real hardware understanding, you have to rely upon vendor spec. With NONE single dmesg after installation, you can NOT advise this board. With NONE real OpenBSD experience, you better ask the developers instead. You are speculatively advertising yet unsupported boards as feature sets. Not interested reading anything that pops in your visibility on the list. It takes very little effort to have some opinion and I do NOT want yours. Kind regards, Anton Lazarov > On Fri, Aug 17, 2018 at 17:38, wrote: > > > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > > > >> FUD > >> > >> Sent from total and utter ignorance. > > > > Rupert, > > > > Plus the dmesg you posted is by the RAM disk installation OpenBSD > > kernel. You Should complete an actual OpenBSD installation to get > > the full dmesg. > >> On Fri, Aug 17, 2018 at 12:24, wrote: > >> > >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> > > >> >> Using the serial over lan console, the keyboard keeps working, > >> >> and it is possible to enter the shell. Using the standard > >> >> console, the keyboard does not work. There is plenty of drivers > >> >> that need to be written. No, I do not write/port drivers. > >> >> > >> >> By comparison, both freebsd and centos linux just work out of > >> >> the box. Both dmesgs are attached as reference. > >> >> > >> >> The board is really nice. > >> >> > >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> >> wrote: > >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > >> >> > > >> > > >> > Hi misc@, > >> > > >> > This one is much quieter, the vendors have reacted to the > >> > previous flaw. As nice as it can get.. before trusting > >> > non-technical reviews, be aware: > >> > > >> > https://en.wikipedia.org/wiki/Goldmont#Erratum > >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > >> > https://www.google.com/search?q=intel+c3000+bug > >> > > >> > Recurring issue - similar problems were discussed noisily > >> > industry wide: > >> > > >> > https://en.wikipedia.org/wiki/Silvermont#Erratum > >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > >> > https://www.google.com/search?q=intel+c2000+bug > >> > > >> > As with the previous generation processors and main boards, > >> > Intel FAILS. Wait for updated CPU revision boards, consult techs > >> > and prepare for RMA. > >> > > >> > Kind regards, > >> > Anton Lazarov > > > > "Similar to previous Silvermont generation design flaws were found > > in processor circuitry resulting in cease of operation when > > processors are actively used for several years. Errata named > > > > APL47 System May Experience Inability to Boot or May Cease Operation > > > > and > > > > APL48 System May Experience Non-functioning GPIO Weak Pull-up > > Circuitry > > > > were added to documentation in June 2017 stating: > > > > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) > > card and General-Purpose Input/Output (GPIO) interfaces may stop > > functioning. > > > > The documents cited in the Wikipedia article, see for current > > versions.. that apply to the later CPU stepping models, if any, as > > time progresses: > > > > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf > > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf > > > > APL47 Problem: Under certain conditions LPC, SD card and RTC > > circuitry may stop functioning in the outer years of use. > > > > APL48 Problem: When platform drives the GPIO pin low, GPIOs > > programmed with weak pull-up circuitry may not maintain a value > > above VIH when not actively driven in outer years of service." > > > > Some other "interesting" errata: > > > > APL23 HD Audio Recording May Experience a Glitch While Opening or > > Closing Audio Streams > > > > APL25 USB Device Controller Incorrectly Interprets U3 Wakeup For > > Warm Reset > > > > APL27 USB 2.0 Timing Responsiveness Degradation > > > > APL50 System May Unexpectedly Shut Down When Software Requests a > > Reset > > > > APL53 Warm Reset May Result in System Hang or
Re: SuperMicro A2SDi-4C-HLN4F
This is a really nice board at a really nice price, and you should stop scaring people off. These Atoms are cleaner than both Cores and Xeons, and AMDs have have their fair share of problems. Citin g C2000 against the latest C3000 is FUD. You should come clean first, and cite a comparable server board at a comparable cost and clear of bugs. On Fri, Aug 17, 2018 at 17:38, wrote: > Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher >> FUD >> >> Sent from total and utter ignorance. > > Rupert, > > Plus the dmesg you posted is by the RAM disk installation OpenBSD kernel. > You Should complete an actual OpenBSD installation to get the full dmesg. > >> On Fri, Aug 17, 2018 at 12:24, wrote: >> >> > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> >> Using the serial over lan console, the keyboard keeps working, and it is >> >> possible to enter the shell. Using the standard console, the keyboard >> >> does not work. There is plenty of drivers that need to be written. No, I >> >> do not write/port drivers. >> >> >> >> By comparison, both freebsd and centos linux just work out of the box. >> >> Both dmesgs are attached as reference. >> >> >> >> The board is really nice. >> >> >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher >> >> wrote: >> >> >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm >> > >> > Hi misc@, >> > >> > This one is much quieter, the vendors have reacted to the previous flaw. >> > As nice as it can get.. before trusting non-technical reviews, be aware: >> > >> > https://en.wikipedia.org/wiki/Goldmont#Erratum >> > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ >> > https://www.google.com/search?q=intel+c3000+bug >> > >> > Recurring issue - similar problems were discussed noisily industry wide: >> > >> > https://en.wikipedia.org/wiki/Silvermont#Erratum >> > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ >> > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ >> > https://www.google.com/search?q=intel+c2000+bug >> > >> > As with the previous generation processors and main boards, Intel FAILS. >> > Wait for updated CPU revision boards, consult techs and prepare for RMA. >> > >> > Kind regards, >> > Anton Lazarov > > "Similar to previous Silvermont generation design flaws were found in > processor circuitry resulting in cease of operation when processors are > actively used for several years. Errata named > > APL47 System May Experience Inability to Boot or May Cease Operation > > and > > APL48 System May Experience Non-functioning GPIO Weak Pull-up Circuitry > > were added to documentation in June 2017 stating: > > The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) card > and General-Purpose Input/Output (GPIO) interfaces may stop functioning. > > The documents cited in the Wikipedia article, see for current versions.. > that apply to the later CPU stepping models, if any, as time progresses: > > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf > https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf > > APL47 Problem: Under certain conditions LPC, SD card and RTC circuitry > may stop functioning in the outer years of use. > > APL48 Problem: When platform drives the GPIO pin low, GPIOs programmed > with weak pull-up circuitry may not maintain a value above VIH when not > actively driven in outer years of service." > > Some other "interesting" errata: > > APL23 HD Audio Recording May Experience a Glitch While Opening or > Closing Audio Streams > > APL25 USB Device Controller Incorrectly Interprets U3 Wakeup For Warm > Reset > > APL27 USB 2.0 Timing Responsiveness Degradation > > APL50 System May Unexpectedly Shut Down When Software Requests a Reset > > APL53 Warm Reset May Result in System Hang or Unexpected System > Behaviour > > Keep your eyes open and.. expect some more technical Atom CPU findings.
Re: SuperMicro A2SDi-4C-HLN4F
Fri, 17 Aug 2018 11:15:32 + Rupert Gallagher > FUD > > Sent from total and utter ignorance. Rupert, Plus the dmesg you posted is by the RAM disk installation OpenBSD kernel. You Should complete an actual OpenBSD installation to get the full dmesg. > On Fri, Aug 17, 2018 at 12:24, wrote: > > > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > >> Using the serial over lan console, the keyboard keeps working, and it is > >> possible to enter the shell. Using the standard console, the keyboard does > >> not work. There is plenty of drivers that need to be written. No, I do not > >> write/port drivers. > >> > >> By comparison, both freebsd and centos linux just work out of the box. > >> Both dmesgs are attached as reference. > >> > >> The board is really nice. > >> > >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher > >> wrote: > >> > >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > > > > Hi misc@, > > > > This one is much quieter, the vendors have reacted to the previous flaw. > > As nice as it can get.. before trusting non-technical reviews, be aware: > > > > https://en.wikipedia.org/wiki/Goldmont#Erratum > > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > > https://www.google.com/search?q=intel+c3000+bug > > > > Recurring issue - similar problems were discussed noisily industry wide: > > > > https://en.wikipedia.org/wiki/Silvermont#Erratum > > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > > https://www.google.com/search?q=intel+c2000+bug > > > > As with the previous generation processors and main boards, Intel FAILS. > > Wait for updated CPU revision boards, consult techs and prepare for RMA. > > > > Kind regards, > > Anton Lazarov "Similar to previous Silvermont generation design flaws were found in processor circuitry resulting in cease of operation when processors are actively used for several years. Errata named APL47 System May Experience Inability to Boot or May Cease Operation and APL48 System May Experience Non-functioning GPIO Weak Pull-up Circuitry were added to documentation in June 2017 stating: The Low Pin Count (LPC), Real-Time Clock (RTC), Secure Digital (SD) card and General-Purpose Input/Output (GPIO) interfaces may stop functioning. The documents cited in the Wikipedia article, see for current versions.. that apply to the later CPU stepping models, if any, as time progresses: https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/pentium-celeron-n-series-j-series-datasheet-spec-update.pdf https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-c3000-family-spec-update.pdf APL47 Problem: Under certain conditions LPC, SD card and RTC circuitry may stop functioning in the outer years of use. APL48 Problem: When platform drives the GPIO pin low, GPIOs programmed with weak pull-up circuitry may not maintain a value above VIH when not actively driven in outer years of service." Some other "interesting" errata: APL23 HD Audio Recording May Experience a Glitch While Opening or Closing Audio Streams APL25 USB Device Controller Incorrectly Interprets U3 Wakeup For Warm Reset APL27 USB 2.0 Timing Responsiveness Degradation APL50 System May Unexpectedly Shut Down When Software Requests a Reset APL53 Warm Reset May Result in System Hang or Unexpected System Behaviour Keep your eyes open and.. expect some more technical Atom CPU findings.
Re: SuperMicro A2SDi-4C-HLN4F
FUD Sent from ProtonMail Mobile On Fri, Aug 17, 2018 at 12:24, wrote: > Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher >> Using the serial over lan console, the keyboard keeps working, and it is >> possible to enter the shell. Using the standard console, the keyboard does >> not work. There is plenty of drivers that need to be written. No, I do not >> write/port drivers. >> >> By comparison, both freebsd and centos linux just work out of the box. Both >> dmesgs are attached as reference. >> >> The board is really nice. >> >> On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher wrote: >> >> > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm > > Hi misc@, > > This one is much quieter, the vendors have reacted to the previous flaw. > As nice as it can get.. before trusting non-technical reviews, be aware: > > https://en.wikipedia.org/wiki/Goldmont#Erratum > https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ > https://www.google.com/search?q=intel+c3000+bug > > Recurring issue - similar problems were discussed noisily industry wide: > > https://en.wikipedia.org/wiki/Silvermont#Erratum > https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ > https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ > https://www.google.com/search?q=intel+c2000+bug > > As with the previous generation processors and main boards, Intel FAILS. > Wait for updated CPU revision boards, consult techs and prepare for RMA. > > Kind regards, > Anton Lazarov
Re: SuperMicro A2SDi-4C-HLN4F
Fri, 17 Aug 2018 06:23:23 + Rupert Gallagher > Using the serial over lan console, the keyboard keeps working, and it is > possible to enter the shell. Using the standard console, the keyboard does > not work. There is plenty of drivers that need to be written. No, I do not > write/port drivers. > > By comparison, both freebsd and centos linux just work out of the box. Both > dmesgs are attached as reference. > > The board is really nice. > > On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher wrote: > > > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm Hi misc@, This one is much quieter, the vendors have reacted to the previous flaw. As nice as it can get.. before trusting non-technical reviews, be aware: https://en.wikipedia.org/wiki/Goldmont#Erratum https://www.servethehome.com/another-atom-bomb-intel-e3800-bay-trail-atom-vli89-bug/ https://www.google.com/search?q=intel+c3000+bug Recurring issue - similar problems were discussed noisily industry wide: https://en.wikipedia.org/wiki/Silvermont#Erratum https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/ https://www.servethehome.com/intel-atom-c2000-c0-stepping-fixing-the-avr54-bug/ https://www.google.com/search?q=intel+c2000+bug As with the previous generation processors and main boards, Intel FAILS. Wait for updated CPU revision boards, consult techs and prepare for RMA. Kind regards, Anton Lazarov
Re: SuperMicro A2SDi-4C-HLN4F
Using the serial over lan console, the keyboard keeps working, and it is possible to enter the shell. Using the standard console, the keyboard does not work. There is plenty of drivers that need to be written. No, I do not write/port drivers. By comparison, both freebsd and centos linux just work out of the box. Both dmesgs are attached as reference. The board is really nice. On Thu, Aug 16, 2018 at 18:04, Rupert Gallagher wrote: > https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm
SuperMicro A2SDi-4C-HLN4F
https://www.supermicro.com/products/motherboard/atom/A2SDi-4C-HLN4F.cfm # OpenBSD 6.3 on SuperMicro SYS-E200-9A /usr/bin/ssh ADMIN@192.168.1.2 ATEN SMASH-CLP System Management Shell, version 1.05 Copyright (c) 2008-2009 by ATEN International CO., Ltd. All Rights Reserved -> cd /system1/sol1 /system1/sol1 -> start /system1/sol1 press , , and then to terminate session (press the keys in sequence, one after the other) [...] probing: pc0 com0 com1 mem[252K 384K 1894M 120M 136K 5M 14336M] disk: hd0 hd1* hd2* >> OpenBSD/amd64 BOOTX64 3.38 boot> stty com1 115200 boot> set tty com1 switching console to com1 >> OpenBSD/amd64 BOOTX64 3.38 boot> boot /bsd booting hd0a:/bsd: 3418091+1467392+3891704+0+598016=0x8f3280 entry point at 0xf000158 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2018 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17136254976 (16342MB) avail mem = 16613122048 (15843MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c7000 (34 entries) bios0: vendor American Megatrends Inc. version "1.0b" date 12/12/2017 bios0: Supermicro A2SDi-4C-HLN4F acpi0 at bios0: rev 2, can't enable ACPI cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.40 MHz 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,SENSOR,ARAT 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 0xfe01/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 (cla
