From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: lost interrupt hell - Plea for Help
Date: Sun, 19 May 2002 17:35:14 -0700 [thread overview]
Message-ID: <00c001c1ff96$357371a0$6caca8c0@kpfhome> (raw)
In-Reply-To: <200205192026.WAA27881@harpo.it.uu.se>
----- Original Message -----
From: "Mikael Pettersson" <mikpe@csd.uu.se>
To: <kevin@labsysgrp.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Sunday, May 19, 2002 01:26 PM
Subject: Re: lost interrupt hell - Plea for Help
>
> 1. It's been stated here on LKML several times that optical drives
> should NOT be connected to Promise chips. It may work with Promise's
> Windows drivers, but that doesn't help here. A better strategy is to
> connect your CD-ROMs and Zip drive to the KT266A, and any IDE disks
> either to the FastTrak or the Ultra66 add-on card (though from your
> `lspci` I suppose your disks are SCSI).
>
I've now switched the CD drives over to the VIA IDE interfaces, and am no
longer getting "lost interrupt" messages. However, I can't succesfully rip
audio from CDs, because I get continual "packet command errors" while
cdda2wav is doing its thing. This results in extremely slow rip speeds...
This is occurring with both 2.4.19-pre8 and 2.4.19-pre8-ac4 (which I believe
has a number of Andre's latest IDE updates included). Also, trying to rip
from my first drive (/dev/cdroms/cdrom0 since I'm using devfs) produces
"cooked: Read TOC: not implemented". For some reason the ide-cd driver
thinks this drive is incapable of doing audio ripping; this may be due to
the fact that it's the master drive on the first IDE channel on the
motherboard and the BIOS left it in some strange mode...
I can mount ISO9660 CDs without apparent problems now, though, so it does
appear that there was some bad Promise/CD drive interaction before. Strange.
What else can be done to work on these audio ripping problems?
next prev parent reply other threads:[~2002-05-20 0:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 20:26 Mikael Pettersson
2002-05-19 22:19 ` Kevin P. Fleming
2002-05-20 0:35 ` Kevin P. Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-19 12:25 Mikael Pettersson
2002-05-20 8:42 ` Erik Steffl
2002-05-07 18:01 mikeH
2002-05-09 11:34 ` Tomasz Rola
2002-05-10 16:15 ` Denis Vlasenko
2002-05-10 21:28 ` Erik Steffl
2002-05-11 8:32 ` mikeH
2002-05-11 8:38 ` Rudmer van Dijk
2002-05-11 8:53 ` mikeH
2002-05-11 8:48 ` Rudmer van Dijk
2002-05-16 20:50 ` Rudmer van Dijk
2002-05-17 8:49 ` Mike
2002-05-19 7:14 ` Erik Steffl
2002-05-19 18:43 ` Kevin P. Fleming
2002-05-11 8:48 ` Erik Steffl
2002-05-09 11:42 ` Tomasz Rola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00c001c1ff96$357371a0$6caca8c0@kpfhome' \
--to=kevin@labsysgrp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®