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?
Thanks
--
-Steven
Never ask a geek why, just nod your head and slowly back away.
> 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.
No dmesg chunk attached. ALso does 2.4.2ac3 work ?
> 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.
Xmcd works fine here. 2.4.2
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.
Here, xmcd and cda both work perfectly.
Linux elfie 2.4.2 #1 Thu Feb 22 10:52:17 CET 2001 i586 unknown
Kernel modules 2.4.2
Gnu C 2.95.2
Gnu Make 3.79
Binutils 2.10.91.0.2
Linux C Library 2.2.2
Dynamic linker ldd (GNU libc) 2.2.2
Linux C++ Library 2.9.0
Procps 2.0.2
Mount 2.10r
Net-tools 1.46
Kbd 0.96
Sh-utils 1.12
Modules Loaded serial
--
# Heinz Diehl, 68259 Mannheim, Germany
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