Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!swrinde!cs.utexas.edu!geraldo.cc.utexas.edu!piglet.cc.utexas.edu!not-for-mail From: nichols@ccwf.cc.utexas.edu (Stewart Nichols) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: what is MCD0? Date: 15 Jul 1996 10:06:41 -0500 Organization: The University of Texas at Austin Lines: 30 Message-ID: <4sdmq1$9rj@piglet.cc.utexas.edu> References: <4s6pkq$g05@zeus.crosslink.net> <4s8276$n33@uriah.heep.sax.de> NNTP-Posting-Host: piglet.cc.utexas.edu In article <4s8276$n33@uriah.heep.sax.de>, J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote: >moverman@crosslink.net (Marc Overman) wrote: >> When my FreeBSD machine boots up something called MCD0 comes up at IRQ >> 10 and 300h address. Any idea what this is? It is interfering with >> my network card (ix0) which also wants 300h. > RTFM mcd(4) [...] >RTFM boot(8) [...] I've had interference from the mcd driver, also. I think the original poster was actually asking, in effect, "Why does this mcd0 device, which doesn't seem to exist in my machine, mess up my network card driver?". If someone who knows something about how the probes are done would be willing to explain it, I would be interested in knowing how the probes are performed. In my case the network card was an NE2000, and the mcd driver popped up during the startup probing. I knew enough to disable the device and all was well, but it left me curious about why the mcd driver thought that an NE2000 card was a Mitsumi CD card. What does the probe look for, other than simply an interupt (if anything)? stu nichols@ccwf.cc.utexas.edu.