Return to BSD News archive
Newsgroups: comp.os.386bsd.apps Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!cs.utexas.edu!geraldo.cc.utexas.edu!portal.austin.ibm.com!awdprime.austin.ibm.com!fredriks From: fredriks@austin.ibm.com (Lars Fredriksen) Subject: Re: xcdplayer, is there a port for FreeBSD? Originator: @worf.cet.austin.ibm.com Sender: news@austin.ibm.com (News id) Message-ID: <CGyEG3.2rJ1@austin.ibm.com> Date: Tue, 23 Nov 1993 16:43:14 GMT References: <hastyCGpHwq.6yM@netcom.com> <1993Nov20.190753.6585@mcshub.dcss.mcmaster.ca> <ARG.93Nov22225342@gauss.first.gmd.de> Organization: IBM Austin Lines: 27 In article <ARG.93Nov22225342@gauss.first.gmd.de>, arg@first.gmd.de (Arnulf Guenther) writes: > I did a similar "fix". I ignored the CD_AS_INVALID in > cdrom_getcurtrack() and it returns null. I'm sure that's not the > right way :). My configuration is 1742/Toshiba 3301/FreeBSD 1.0e. > I didn't figure out, why eject don't work and volume control is also > not available (cd0: illegal request). Is there a description of the > structures and #defines in /usr/include/sys/cdio.h? > > -Arnulf > -- To fix the (cd0: illegal request) message add a line that bzeros the vol structure before it is passed in to the CDROM device driver( and before you fill in any fields :-)). That should fix it. Note that as far as I have seen, it doesn't do much for the volume (on/off), but at least the annoying error messages are gone. WRT to eject, the CDROM device driver doesn't have support for that yet. I have a fix for that on its way. Lars -- Regards, ----------------------------------------------------------------------------