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, <li...@wrant.com> wrote: > Sat, 18 Aug 2018 08:29:33 +0000 Rupert Gallagher <r...@protonmail.com> >> 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, <li...@wrant.com> wrote: >> >> > Fri, 17 Aug 2018 16:48:52 +0000 Rupert Gallagher <r...@protonmail.com> >> >> 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, <li...@wrant.com> wrote: >> >> >> >> > Fri, 17 Aug 2018 11:15:32 +0000 Rupert Gallagher >> >> > <r...@protonmail.com> >> >> >> 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, <li...@wrant.com> wrote: >> >> >> >> >> >> > Fri, 17 Aug 2018 06:23:23 +0000 Rupert Gallagher >> >> >> > <r...@protonmail.com> >> >> >> >> 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 >> >> >> >> <r...@protonmail.com> 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
