Re: 2.4.2 broke gcd (or, audio CD's won't play)

[Jens Axboe <axboe@suse.de>]

On Fri, Feb 23 2001, Steven Walter wrote:
> After upgrading to 2.4.2, gcd or any audio CD player will work.  The
> attached chunk of dmesg is the messages produced by attempting to play
> them.  The player just loops through all tracks, playing nothing.
> Ripping CD's a la cdparanoia still works.
> 
> If its any consequence, my CD-ROM is now detected as a CD-ROM/DVD-ROM.
> Is this also a problem, or merely an optimization in the boot-detection
> routines?

That doesn't matter, the boot info just means it could be either
a cdrom or a dvd drive.

But these:

ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid command operation code -- (asc=0x20, ascq=0x00)
  The failed "Play Audio MSF" packet command was:
  "47 00 00 2d 2b 1b 39 38 00 00 00 00 "
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid command operation code -- (asc=0x20, ascq=0x00)
  The failed "Test Unit Ready" packet command was:
  "00 00 00 00 00 00 00 00 00 00 00 00 "
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid command operation code -- (asc=0x20, ascq=0x00)
  The failed "Test Unit Ready" packet command was:
  "00 00 00 00 00 00 00 00 00 00 00 00 "
ATAPI device hdc:
  Error: Illegal request -- (Sense key=0x05)
  Invalid command operation code -- (asc=0x20, ascq=0x00)
  The failed "Play Audio MSF" packet command was:
  "47 00 00 37 04 28 39 38 00 00 00 00 "

look very odd. It's basically saying that these required commands
are not implemented by the drive. 2.4.1 worked fine?!

-- 
Jens Axboe