Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!malgudi.oar.net!news.ans.net!newsgate.watson.ibm.com!watnews.watson.ibm.com!yktnews.watson.ibm.com!chaos!nistler From: nistler@rchland.vnet.ibm.com (John Nistler) Subject: Re: CDROM support Sender: news@rchland.ibm.com Message-ID: <1994Jan11.202742.55580@rchland.ibm.com> Date: Tue, 11 Jan 1994 20:27:42 GMT Reply-To: john_nistler@vnet.ibm.com Disclaimer: This posting represents the poster's views, not necessarily those of IBM References: <CIzI2p.C76@sugar.NeoSoft.COM> <2gd8rc$gi@intergate.swc.cc.ca.us> <1994Jan07.054524.49510@rchland.ibm.com> <1994Jan11.035328.20854@mcshub.dcss.mcmaster.ca> Nntp-Posting-Host: chaos.rchland.ibm.com Organization: IBM Rochester Lines: 19 In article <1994Jan11.035328.20854@mcshub.dcss.mcmaster.ca>, hfraser@maccs.mcmaster.ca (Hugh Fraser) writes: |> Yep. I have a Mitsumi drive that also refuses to be seen. Very frustrating, |> since mine is a "Mitsumi" Mitsumi drive. I too am anxiously awaiting a |> solution. I also have access to the Linux device driver for the Mitsumi, and noticed that some of the for loops which read from the device have much larger loop numbers (like 1000000) instead of 1000. I made a few changes and the probe now successfully finds the device. Only now I can't get it to mount the device. I used: mount -r -t isofs /dev/mcd0a /mnt and Mount reports: >mount: Invalid Argument My first guess is that my kernal is not including the right stuff???? -- John Nistler