Linux-kernel mailing list archive 1999-37,: audio CDs, and 2.2.13pre8

# audio CDs, and 2.2.13pre8

Tim Keating (tkeating@home.com)
Thu, 16 Sep 1999 23:05:40 -0600 (MDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Dan Kegel: "re: > 15K simultaneous connections EXAMPLE program/OS config needed,"
- Previous message: Zach Brown: "maestro.c 0.05, with kung fu grip."

Built and install a 2.2.13pre8 kernel and once I stuck a audio CD in I
started getting the following error. It would repeat steadily on all the
virtual terminals except the one where X was started from. I boot
into run level 3 so the message was showing up on 5 different virtual
terminals. I tried 3 different audio CD players (wmcdplay, wmsvencd, and
the KDE cd player) and still got the same behaviour. Once I shut the cd
players down, the messages also stop. I could play an audio CD when I
first started the CD players, but if I tried skipping tracks the audio
wouldn't start again. Sound was still working from other utilities. I
do not get the error with data CDs. If I boot a 2.2.12 kernel built
with essentially the same .config file (Used same .config, just did a
"make oldconfig" for the 2.2.13pre8) I do not get the error.

Here is the error I was getting. This was copied by hand, since it
wasn't showing up in any log files.

hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packer command error: statux=0x04 ATAPI device hdc:
Unknown Error Type: No sense data --(Sense key=0x00)
No additional sense information --(asc=0x00, ascq=0x00)
The failed "<NULL>" packet command was:
"42 02 40 01 00 00 00 00 10 00 00 00 "
hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error
}
hdc: request sense failure: status=0x04

VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
ide0: VIA Bus-Master (U)DMA Timing Config Success
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
ide1: VIA Bus-Master (U)DMA Timing Config Success
hda: FUJITSU MPD3064AT, ATA DISK drive
hdc: CDR-CC-24, ATAPI CDROM drive
hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive

hdc: ATAPI 24X CD-ROM drive, 120kB Cache
Uniform CDROM driver Revision: 2.56

ISO 9660 Extensions: Microsoft Joliet Level 1
ISO 9660 Extensions: RRIP_1991A

I'm on a Slackware 6.? beta system using the following.

/usr/src/linux/scripts$ sh ver_linux
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux darkspot 2.2.13pre8 #1 Wed Sep 15 15:27:17 MDT 1999 i586 unknown
Kernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.1.0.25
Linux C Library 2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Procps 2.0.2
Mount 2.9v
Net-tools 1.52
Kbd 0.99
Sh-utils 1.16
Modules Loaded snd-mixer-oss snd-pcm1-oss snd-card-ens1370
snd-ens1370 snd-pcm1 snd-pcm snd-timer snd-ak4531-codec snd-midi
snd-seq-device snd-mixer snd soundcore nls_iso8859-1 binfmt_misc
binfmt_aout dummy tulip ide-floppy ide-cd cdrom lp parport_pc parport

All the snd-* stuff is alsa-project stuff. Below is chipset information
from /proc/pci

/proc$ cat pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies VT 82C597 Apollo VP3 (rev 4).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=16.
Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
Medium devsel. Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies VT 82C586 Apollo ISA (rev 71).
Medium devsel. Master Capable. No bursts.
Bus 0, device 7, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.
I/O at 0xe000 [0xe001].
Bus 0, device 7, function 3:
Host bridge: VIA Technologies VT 82C586B Apollo ACPI (rev 16).
Medium devsel. Fast back-to-back capable.

I realise that I am a "little" out on the bleeding edge, and that the
error I've encountered may not be relevant to main stream Linux, but if
any one would like further information that might help squash this
particular problem, please feel free to ask for more information.

I am not on the mailing list.

Tim Keating.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Dan Kegel: "re: > 15K simultaneous connections EXAMPLE program/OS config needed,"
- Previous message: Zach Brown: "maestro.c 0.05, with kung fu grip."