[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sound errors on 2.2.14->2.2.17 ??



Had the same problem. Replaced cdplay with cdcd.  Seems there's been a
[possibly] undocumented changed in an interface.  I also had to play
around with some other /etc/modutils/aliases settings.  I didn't find
any clues about this in any of the kernel Documentation.  Kind of a
pisser.

On Mon, Sep 04, 2000 at 10:56:38AM -0700, Kenward Vaughan wrote:
> I just moved from 2.2.14 to 2.2.17pre6.  Additionally, I recompiled the new
> ALSA driver for my card (which I don't believe is part of the problem, but
> thought it should be mentioned).  My system is Woody, updated about 2 weeks
> ago, and the ALSA driver is current Woody.
> 
> On rebooting, I immediately tried cdplay to test the sound driver, and got
> the following error:
> 
> daddy:~# cdplay
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x50
> ATAPI device hdc:
>   Error: Illegal request -- (Sense key=0x05)
>   Invalid command operation code -- (asc=0x20, ascq=0x00)
>   The failed "Play Audio TrackIndex" packet command was:
>   "48 00 00 00 01 01 00 0c 63 00 00 00 "
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x50
> ATAPI device hdc:
>   Error: Illegal request -- (Sense key=0x05)
>   Invalid command operation code -- (asc=0x20, ascq=0x00)
>   The failed "Play Audio TrackIndex" packet command was:
>   "48 00 00 00 01 01 00 0c 01 00 00 00 "
> cdplay: ioctl cdromplaytrkind
> 
> Using Gnome's player works, however.  Does anyone know what the source of
> this is??  Could it be the ATAPI driver for the new kernel or cdplay??  
> Rebooting using the old kernel gives a working cdplay.
> 
> TIA,
> 
> Kenward
> 
> -- 
> Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
> --
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 
> 

-- 
/bin/sh ~/.signature:
Command not found



Reply to: