On Thu, Oct 29, 2015 at 10:15:26AM -0400, Dewey Hylton wrote: > On Wed, Oct 28, 2015 at 11:35 PM, Jonathan Gray <j...@jsg.id.au> wrote: > > > On Wed, Oct 28, 2015 at 10:18:26PM -0400, Dewey Hylton wrote: > > > i like these little boxes; they are silent and stable and perfect for > > plenty > > > of my projects. this new version promises to be better than the several > > fit2 > > > machines i have scattered around customer sites, affording more cores and > > > memory. > > > > > > the man page for em shows the i211 to be supported. this machine uses > > that > > > chip, and it is even reported by the kernel - but still does not work. > > is it > > > possible that its specific id is simply missing from the driver, or is > > there > > > more to it than that? > > > > > > i booted the computer via pxe, so the ethernet is clearly working. it > > > shipped with linux, and networking worked there too. > > > > > > of course it'd be nice for all the other bits to be in working order as > > > well, but at the moment ethernet is the most important for my purposes. > > > > > > please let me know what i can do to get this working, or how i can assist > > > otherwise. > > > > If you can get the dmesg output of a kernel built with the following > > diff it should indicate where the problem is: > > > > Index: sys/dev/pci/if_em_osdep.h > > =================================================================== > > RCS file: /cvs/src/sys/dev/pci/if_em_osdep.h,v > > retrieving revision 1.12 > > diff -u -p -r1.12 if_em_osdep.h > > --- sys/dev/pci/if_em_osdep.h 5 Oct 2011 02:52:10 -0000 1.12 > > +++ sys/dev/pci/if_em_osdep.h 29 Oct 2015 03:27:36 -0000 > > @@ -44,7 +44,8 @@ POSSIBILITY OF SUCH DAMAGE. > > > > #define MSGOUT(S, A, B) printf(S "\n", A, B) > > #define DEBUGFUNC(F) DEBUGOUT(F); > > -#ifdef DBG > > +//#ifdef DBG > > +#if 1 > > #define DEBUGOUT(S) printf(S "\n") > > #define DEBUGOUT1(S,A) printf(S "\n",A) > > #define DEBUGOUT2(S,A,B) printf(S "\n",A,B) > > > > > > > i'll attempt to build a new bsd.rd with this patch and report back. > > i've never done this, so it may take a bit of time to work out the > details. thanks for the suggestion.
It would be enough to log the serial output and boot a normal kernel with pxe. Though it seems you may have the "fitlet-B" that doesn't have serial unlike the "fitlet-i" and "fitlet-X". Or perhaps the output isn't so verbose that you could transcribe it. If you have a spare usb flash drive you could install to that on a different machine, put the test kernel on it, then boot it on the machine. It takes a while to test changes if you have to run make build and make release every time.
