Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!pith.uoregon.edu!cliffs.rs.itd.umich.edu!howland.erols.net!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!newsfeed.internetmci.com!in1.uu.net!160.45.4.4!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: [2.2-ALPHA] ADAPTEC 2940 problems Date: 22 Dec 1996 10:28:34 GMT Organization: Private BSD site, Dresden Lines: 33 Message-ID: <59j2gi$cmg@uriah.heep.sax.de> References: <58ln55$lrl@mark.ucdavis.edu> 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:32988 ccjason@quadrophenia.ucdavis.edu (Jason Gabler) wrote: > ahc0:A:5: refuses WIDE negotiation. Using 8bit transfers I haven't seen a `wide' CD-ROM drive yet. :-) So this is OK. > (ahc0:5:0): "NEC CD-ROM DRIVE:462 1.14" type 5 removable SCSI 2 > cd0(ahc0:5:0): CD-ROM cd present [285226 x 2048 byte records] > [...] > > in 2.2-SNAP the problem was so bad it would lock up the machine. However, > what is this with the 8bit transfers? I have the sneaking feeling > this is the reason why my cd-device may not be work working well with > audio cd's (even with "cdplayer" !!). Your sneaking feeling is wrong. The bus size is unimportant. That's the good point with SCSI: you can put a narrow target onto a wide bus, and it will correctly negotiate the bus size with the controller. I don't know what's wrong with the NEC drives, however somebody posted a message to a FreeBSD list that he's got an ``Illegal mode for this track'' from the drive when trying to play an audio CD. You could investigate this a little further. If the drive _really_ responds with that error to a PLAY request, and the disk is indeed an audio one, the drive is nothing else but broken. (Subsequent timeouts are probably a sign of brokeness in the ahc driver.) -- 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. ;-)