From: Flameeyes <daps_mls@libero.it>
To: Cédric <cedriccsm2@ifrance.com>
Cc: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 cd-writer problem
Date: 02 Jul 2003 18:11:06 +0200 [thread overview]
Message-ID: <1057162265.9026.3.camel@laurelin> (raw)
In-Reply-To: <3F02FA3E.2080004@ifrance.com>
On Wed, 2003-07-02 at 17:29, Cédric wrote:
> I've tried 2.4.20, and got the same freeze.
> I didn't try 2.4.19.
>
> My IDE chipset is VIA® VT8233A (associed with VIA® KT333)
Have you a 40c or 80c cable on the cd-writer?
I have the same problem using a 40c cable. Also if Bios (and windows)
reports on my system that the UDMA is present only in the first channel,
linux kernel activate it also in the second channel (and it works
great!).
--
Flameeyes <dgp85@users.sf.net>
next prev parent reply other threads:[~2003-07-02 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307012029.h61KTUZk001416@81-2-122-30.bradfords.org.uk>
2003-07-02 15:29 ` 2.4.21 cd-writer problem Cédric
2003-07-02 16:11 ` Flameeyes [this message]
2003-07-02 19:59 ` Cédric
2003-07-01 20:13 Cédric
2003-07-01 20:38 ` Stan Bubrouski
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=1057162265.9026.3.camel@laurelin \
--to=daps_mls@libero.it \
--cc=cedriccsm2@ifrance.com \
--cc=john@grabjohn.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