From: Benjamin LaHaise <bcrl@redhat.com>
To: "Joseph N. Hall" <joseph@5sigma.com>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
linux-kernel@vger.kernel.org
Subject: Re: IDE-DVD problems [excuse former idiotic topic]
Date: Wed, 4 Sep 2002 13:44:07 -0400 [thread overview]
Message-ID: <20020904134407.H1394@redhat.com> (raw)
In-Reply-To: <200209041553.g84Frl130632@mx1.redhat.com>; from joseph@5sigma.com on Wed, Sep 04, 2002 at 09:11:00AM -0700
On Wed, Sep 04, 2002 at 09:11:00AM -0700, Joseph N. Hall wrote:
> Right, but it will work with or without DMA, for some definition
> of "work." Or it should work, right?
Define "work". hdparm -d1 doesn't just work, it requires making sure that
the drive and interface are properly programmed to the correct transfer rates
first (read as: hdparm -d1 can be Bad). Using the kernel defaults is much
better as the probe code will make sure that everything is setup correctly.
Andre can provide more details and help fix things if it doesn't actually
work for your drive.
> Do you know anyone who has gotten this particular drive to work?
> Or for that matter if there are any troubles with the KT333
> chipset? I wouldn't be surprised if there are some interrupt
> "issues" with KT333 because my plain old IDE performance was
> not good under the stock 2.4.18-3 kernel ... it would do some
> of the same things (lots of system time, temporary "pauses",
> etc.).
You might need to upgrade from the -3 kernel (several errata have
been released) as there were a few known problems with some network
drivers, as well as NFS and ext3. Different drives also have varing
amounts of cache, and it might be this that you're noticing.
> I am also having problems with the C-Media onboard audio +
> ALSA (0.9 rc3) ... it hangs the system (totally) after playing
> for a few seconds. So that is another strike against this
> particular h/w configuration.
Again, try a newer kernel. I'm using a C-Media at home and it works
pretty well for ogg/DVD playback.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next parent reply other threads:[~2002-09-04 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209041553.g84Frl130632@mx1.redhat.com>
2002-09-04 17:44 ` Benjamin LaHaise [this message]
2002-09-04 17:54 IDE-DVD problems [excuse former idiotic topic] Joseph N. Hall
-- strict thread matches above, loose matches on Subject: below --
2002-09-04 16:11 Joseph N. Hall
[not found] <200209041530.g84FUM124938@mx1.redhat.com>
2002-09-04 15:49 ` Benjamin LaHaise
2002-09-04 15:48 Joseph N. Hall
[not found] <200209040542.g845gf100948@mx1.redhat.com>
2002-09-04 14:55 ` Benjamin LaHaise
2002-09-04 6:00 Joseph N. Hall
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=20020904134407.H1394@redhat.com \
--to=bcrl@redhat.com \
--cc=joseph@5sigma.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
/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