Return to BSD News archive
#! rnews 1783 bsd Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!newsfeed.internetmci.com!netnews.nwnet.net!news.montana.edu!news From: Dan Dartman <uffda@fubar.cs.montana.edu> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: IDE CDRom help Date: Fri, 12 Jan 1996 11:55:37 -0800 Organization: cs Lines: 25 Message-ID: <30F6BCB9.5137@fubar.cs.montana.edu> References: <4ci43n$8c5@news2.realtime.net> NNTP-Posting-Host: fubar.cs.montana.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b5 (Win95; I; 16bit) To: dhbrown@bga.com > Anyhow, I compiled the kernel with ATAPI CDRom support. Now, when I boot > the kernel, you'd never know it. There's no probe of the wcd0 device. I It's my understanding that since the device is using the wdc controller this is what will be probed, if the address and irq is correct. > tried to do the MAKEDEV wcd0. There's now an entry in the /dev directory > for a wcd0c device, but if I try to do a mount, it says there's no such This is the same thing that happens to me. Jordon suggested that I configure the drive as a slave, but it was already set to slave. You might try it though. > device, or device not configured. When booting, I tried to enable the wcd0 > device for probing, but again, the kernel seems oblivious. It all sounds so > easy in the handbook document. Again, I don't think the wcd0 device is supposed to show up in the kernel configuration or the boot probes, just the wdc0 or wdc1 controllers. At least, it doesn't for me either. Good luck. Let me know if you get it working and how. Dan Dartman Roberts #518 uffda@cs.montana.edu