From: Philip Dodd <phil.lists@two-towers.net>
To: Philip Dodd <phil.lists@two-towers.net>
Cc: linux-kernel@vger.kernel.org,
Hugo Mills <hugo-lkml@carfax.org.uk>, Jens Axboe <axboe@suse.de>,
Daniele Bernardini <db@sqbc.com>
Subject: Re: dma ripping
Date: Thu, 20 May 2004 04:31:05 +0200 [thread overview]
Message-ID: <40AC1869.5090407@two-towers.net> (raw)
In-Reply-To: <40A9377A.70200@two-towers.net>
Philip Dodd wrote:
8<
> Intel i820 Chipset on P3C-D mobo.
> ide0: BM-DMA at 0xa800-0xa807, BIOS settings: hda:DMA, hdb:pio
> hda: ASUS DVD-ROM E616, ATAPI CD/DVD-ROM drive
> hda: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
>
> ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdc:DMA, hdd:pio
> hdc: RICOH CD-R/RW MP7060A, ATAPI CD/DVD-ROM drive
> hdc: ATAPI 24X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
>
> Now hda is the one that bogs out, ripping silence after the "cdrom:
> dropping to single frame dma" error. hdc can rip for hours and hardly
> ever get cdparanoia errors - even on "problematic" CDs that would appear
> to be a declenching factor for the single frame dma switch for hda.
8<
Hi - just a quick update: after ripping 5Gb of oggs hdc "went funny" -
DMA was disabled and after hdc just stopped ripping altogether.
I've moved back to ide-scsi and am using that as a workaround, as it now
appears as the only way of getting this stuff working.
Many thanks;
Phil
next prev parent reply other threads:[~2004-05-20 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 15:29 dma ripping Daniele Bernardini
2004-05-15 10:14 ` Jens Axboe
2004-05-15 8:45 ` Daniele Bernardini
2004-05-15 14:58 ` Jens Axboe
2004-05-15 10:13 ` Daniele Bernardini
2004-05-15 14:03 ` Daniele Bernardini
2004-05-15 21:19 ` Jens Axboe
2004-05-16 15:26 ` Philip Dodd
2004-05-16 15:39 ` Hugo Mills
2004-05-17 22:06 ` Philip Dodd
2004-05-20 2:31 ` Philip Dodd [this message]
2004-05-20 13:34 ` Jens Axboe
2004-05-30 17:36 ` Philip Dodd
2004-05-31 5:19 ` Tvrtko A. Uršulin
2004-05-17 22:12 ` Bill Davidsen
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=40AC1869.5090407@two-towers.net \
--to=phil.lists@two-towers.net \
--cc=axboe@suse.de \
--cc=db@sqbc.com \
--cc=hugo-lkml@carfax.org.uk \
--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