Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!aardvark.ucs.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.clark.edu!spool.mu.edu!howland.reston.ans.net!pipex!uunet!emba-news.uvm.edu!trantor.emba.uvm.edu!wollman Newsgroups: comp.os.386bsd.questions Subject: FAQ: Device not configured Message-ID: <1993Oct4.164559.2187@emba.uvm.edu> From: wollman@trantor.emba.uvm.edu (Garrett Wollman) Date: Mon, 4 Oct 1993 16:45:59 GMT Sender: news@emba.uvm.edu References: <9310041624.AA0109@havoc.ns.doe.gov> <O5VHBMDH@math.fu-berlin.de> Organization: University of Vermont, EMBA Computer Facility Keywords: FAQ ENXIO Lines: 45 [This is really a generic answer... to what should be an FAQ question.] In article <O5VHBMDH@math.fu-berlin.de>, Robert A. Wheeler <pipes@knock1.mgh.harvard.edu> wrote: > "tcpdump", distributed with FB, initially complained that bpf0 >did not exist. I politely created it via "sh MAKEDEV bpf0". Invoking >tcpdump now says "Device not configured". When any program tells you ``Device not configured'', it's trying to tell you something very important about what you tried to do: namely, that the device you tried to access is not configured into the running operating system. This is the error message corresponding to ENXIO. There are three major causes for this error: 1) The kind of device you requested was not configured into the system. This is Robert Wheeler's problem; the generic kernels are not distributed with the Berkeley Packet Filter enabled by default. To correct this, you must add the appropriate device or pseudo-device to your kernel configuration file and recompile. (In this particular case, `pseudo-device bpfilter number-of-network-interfaces'.) 2) The kind of device you requested was configured into the system, but either the device you requested is would use more than the maximum you configured into the system, or if a physical device, was not found during autoconfiguration. To solve this, either change your configuration file, or change the I/O settings on the device to match what the file says. 3) The major or minor device number specified by the device's entry(ies) in /dev is incorrect. To solve this, re-MAKEDEV the device (read the MAKEDEV script for more details). Hopefully whatever change caused the kernel's internal device tables to get changed also updated your MAKEDEV script; otherwise, you will have to grovel through the kernel to see what is going on. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@emba.uvm.edu | Shashish is the bonding of hearts in spite of distance. uvm-gen!wollman | It is a bond more powerful than absence. We like people UVM disagrees. | who like Shashish. - Claude McKenzie + Florent Vollant