Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!usenet.eel.ufl.edu!spool.mu.edu!howland.reston.ans.net!news.cac.psu.edu!news.math.psu.edu!chi-news.cic.net!newsfeed.internetmci.com!news.sprintlink.net!dfw.nkn.net!rowdy.lonestar.org!nemesis!uhclem From: uhclem@nemesis.lonestar.org (Frank Durda IV) Subject: Re: FBSD SP Pro CD-ROM problem X-Newsreader: Tin 1.1 PL5 Organization: The Big Blue Box Message-ID: <DGKJno.Bww@nemesis.lonestar.org> References: <45r7ef$md1@lugnut.stu.rpi.edu> Date: Tue, 17 Oct 1995 01:19:00 GMT Lines: 54 [1]Geert Bosch <geert@fozzie.sun3.iaf.nl> wrote: [1]Only Panasonic 56x is supported. The info I got on FreeBSD before I bought [1]bought the CD from Walnut Creek was that Panasonic drives on SoundBlaster [1]Pro adapters were supported. It turned out my Panasonic drive on my [1]SB Pro was not supported, A simple mistake for someone to make as the 56x drives were sold with SoundBlaster PRO and SoundBlaster 16 and SoundBlaster 32 sound cards. They just didn't know that an even older drive generation (the 52x series) was also sound with SoundBlaster PRO systems prior to 1993. [0]Damien Neil (damien@lugnut.stu.rpi.edu) wrote: [0]I have been having problems with my Panasonic CD-ROM and playing audio [0]CDs. After playing a CD for a while, the kernel appears to hang in some [0]system call; whatever program I was using to control the CD will lock up [0](and cannot be killed, even by a kill -9). [0] [0]Occasionally, but not always, this will be followed by a message in the [0]system logs reading something like: ``matcd0: get_stat: After reading [0]status byte, bus didn't go idle f2 fd 230''. [0] [0]The CD-ROM's ID string (as returned by the kernel) reads: CR-56225.00 [0] [0]Is this likely to be caused by the lack of support of some Panasonic drives, [0]or is it more likely a bug in the driver? Well, the firmware you have is *REAL* old, older than what came with the hand-built drive samples I have. The earliest version I have is CR-562.55. Most drives made in 1993 were 562.73 or 563.73. You should do two things. First, make sure you have the latest driver. There have been two releases since 2.0.5 came out, and there was a bug related to using xcdplayer on heavily-loaded systems and/or slower systems (486DX-33 or slower). In these conditions, if you constantly poke at the controls in xcdplayer and/or open and close the tray door while issuing commands to xcdplayer, you can get the driver to go to sleep forever. So, get the newer driver and see if that helps. It is available from freebsd.cdrom.com. Look in the "current" or "stable" trees for 2.1.0 development. If it doesn't help, all I can suggest is to get newer firmware. The firmware is socketed in the drive, and is annoying but not impossible to replace. As always, remove power before removing the covers on a device containing a laser. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983