Date: Mon, 15 Apr 2019 14:38:49 +0200 From: Milan Obuch <freebsd-hackers@dino.sk> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Any WAFER-BT users? Message-ID: <20190415143849.0f09eb91@zeta.dino.sk> In-Reply-To: <CANCZdfr0sZe6x25LWKxx_kcs=PbtW-G4wZz6JJ_fGXjXRki=XA@mail.gmail.com> References: <20190409103256.5d095bb5@zeta.dino.sk> <CANCZdfr0sZe6x25LWKxx_kcs=PbtW-G4wZz6JJ_fGXjXRki=XA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 Apr 2019 08:25:03 -0600 Warner Losh <imp@bsdimp.com> wrote: > On Tue, Apr 9, 2019 at 2:39 AM Milan Obuch <freebsd-hackers@dino.sk> > wrote: > > > Hi, > > > > I am testing WAFER-BT-N28071-R20 board, details at > > https://www.ieiworld.com/en/product/model.php?II=637 > > > > I tried installing from mini memstick image for both i386 and amd64 > > architectures, 12.0-RELEASE, both are failing the same way - boot > > loader starts, menu is displayed, selected/timed out, then > > > > Loading kernel... > > /boot/kernel/kernel [text= etc.] > > Loading configured modules... > > can't find '/boot/entropy' > > | > > > > and that's all. No output from kernel, no sign of life :( > > > > This symptom means one of two things: > (1) The boot loader is crashing for some reason, but not reporting it > (way too common on UEFI, sadly) > (2) The boot loader is configuring some crazy thing as console, > loading the kernel and it is dying and reporting the message into > cloud kookoo land. > > > > This board was tested with Windows and Linux, so it could not be > > something totally wrong, just some BIOS settings or somesuch... I > > tried loading without ACPI, but then it fails with 'can't find > > APIC' panic or aomething similar (just from memory). Also, trying > > run kernel manually from loader does not reveal anything, 'boot > > -vs' outputs nothing as well. > > > > If you can get to the stage where it thinks it's booting manually, it > isn't likely (1), though it's still a small possibility while loading > the kernel. It would be really helpful to have a screen shot where it > died. You might also setup a serial console too. > Thanks, that's it - for some reason loader switches to serial console after starting kernel, or is it kernel itself? Does not matter... After installing system, it behaves that way - switch to serial console. I think video is the cullprit - from dmesg: Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-RELEASE r341666 GENERIC i386 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) VT: init without driver. CPU: Intel(R) Celeron(R) CPU N2807 @ 1.58GHz (1583.38-MHz 686-class CPU) Origin="GenuineIntel" Id=0x30679 Family=0x6 Model=0x37 Stepping=9 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x41d8e3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,RDRAND> AMD Features=0x28100000<NX,RDTSCP,LM> AMD Features2=0x101<LAHF,Prefetch> Structured Extended Features=0x2282<TSCADJ,SMEP,ERMS,NFPUSG> Structured Extended Features3=0xc000000<IBPB,STIBP> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics Later: vgapci0: <VGA-compatible display> port 0xe080-0xe087 mem 0xd0000000-0xd03fffff,0xc0000000-0xcfffffff irq 16 at device 2.0 on pci0 vgapci0: Boot video device As this should be a video terminal, it is kind of show stopper for me. I am going to try graphics/drm-kmod port, whether it is of any help... Regards, Milan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190415143849.0f09eb91>