Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news-peer.sprintlink.net!news.sprintlink.net!Sprint!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: matcd driver is not working, is there something to do? Date: 8 May 1997 19:28:14 GMT Organization: Private BSD site, Dresden Lines: 36 Message-ID: <5kt9ge$pig@uriah.heep.sax.de> References: <Pine.SUN.3.95-heb-2.07.970501105530.4673A-100000@actcom.co.il> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:40611 Alexander Indenbaum <baum@actcom.co.il> wrote: > # matcd: Matsushita/Panasonic CD-ROM > # for the SoundBlaster 16 multicd - up to 4 devices > controller matcd0 at isa? port 0x230 bio > > Maybe SoundBlaster should be decleared before > matcd in order to tell to kernel not to use controler > but to use SoundBlaster? Nope, it's using a different IO address (0x220, as you've been quoting here). Why don't you start messing with the driver? If you already know that your drive takes an enormous amount of time to get ready, simply try adding DELAY()'s around in the driver's probe routine. It's C code, not black magic, and you are so free to get that C code along with your system. After all, it's just _your_ drive that makes problems, so why do you expect others (who very apparently can't reproduce _your_ problems) to solve them, as opposed to just trying your own luck? ``Ah, but i'm not a programmer...'' No, doesn't count. It doesn't require a programmer to stick a few DELAY()'s or maybe printf()'s into a piece of C code. Hint: the unit of measure for DELAY is microseconds. So if you add DELAY(60 * 1000 * 1000) somewhere, this should give the drive some time to `settle'. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)