If this is really a problem to you, look in the linux driver code and -glue of the oskit sources. For some reason, parts of the SCSI stack are linked with the binary. Maybe you can safe some bytes by splitting the appropriate object.
This is a combined problem with fiasco and the output routines. To collect all the screen-output at one place, an to allow serial debugging of the kernel at the same console that gets the user output, the logserver uses the kernel-debug interface to output characters. With fiasco, there is a problem when using the kernel debugger while beeing "exregs'd" by another thread. The result is that you observed.
A workaround is to remove the 'console.c' from the SRC_C -variable in the file lib/src/Makefile of the oskit10_support package, rebuild the package and relink the logserver.
Look into the oskit10 sources,
linux/src/drivers/net. If a suitable driver is listed there, enable it in the LOG server,
server/src/tcpip.c:init_ethernet(). If not, you must write your own driver.
