Kostas Papadopoulos wrote:

On a freshly installed "clean" SuSE 6.3 setup, the system reports continously (/dev/console and in /var/log/:

Feb 1 02:57:34 hypernet modprobe: modprobe: Can't locate module binfmt-0000

<more messages snipped>

The only thing that has changed, is that we changed the network card from a NE2000 (PCI) compatible (ne2k-pci) one, used for the installation, to an SMC EtherPower (tulip). We did that change from "ne2k" to "tulip" using YaST.

Are you using the stock SuSE kernel? If you have recompiled the kernel yourself, you may have compiled the ne2k driver directly into the kernel.

Also, during boot-up, the system STILL reports a problem in loading the NE2000 PCI driver, which ofcourse is not logged (as I guess that no logging daemon runs at that early point of the systems startup). There is no reference to

The bootup messages are stored in /var/log/boot.msg and can be viewed using dmesg.

"ne2k-pci" in any of the configuration files though ... Lateron in the boot process, Linux loads the "tulip.o" driver and connects without problems to the network.

Short of re-installing from scratch, could someone provide any hints on what is going on? I've searched the Internet on the keyword "binfmt-0000" but none of the stuff I found had any relevance to this situation ...

Sorry, can't really help you here. binfmt usually relates to types of executable. Hope that helps a bit, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/