public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Subject: Re: A more complete log about my disk access errors
Date: Sun, 3 Jun 2001 00:14:09 +0200	[thread overview]
Message-ID: <000801c0ebbe$c8c54920$b621fea9@cybertsar> (raw)
In-Reply-To: <Pine.LNX.4.21.0106021648560.5777-100000@ignatious>

Hi, Kirk!
That sheds some light. I will probably end up downloading a diag diskette
for Western Digital drives and see whether they detect DMA capabilities. OK,
if it turns out that I was fooled by Windows during all this time, do you
know of any parameter which I could use to tell Linux to fall to PIO mode
right away?
Best,
Victor

----- Original Message -----
From: "Kirk Wood" <cpt.kirk@1tree.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, June 02, 2001 11:53 PM
Subject: Re: A more complete log about my disk access errors


> First, understand why Windows 2000 doesn't complain about the DMA. If the
> drive times out twice (ever) then it no longer uses DMA ever. So it won't
> complain. It won't tell you. In fact, win winclows 98 they burried any
> indication that this had happened. It happens more often them many people
> realize.
>
> Having said that, if you didn't have DMA support compiled into the kernel
> you wouldn't get the errors. Yes, it must be compiled in if it is to be
> used. (DMA falls back to PIO in case of failure and PIO always remains
> available.)
>
> As for fixing this, it is either the motherboard or the drive. I know that
> doesn't help. You might check to see that DMA is turned on in the
> BIOS. (Linux will try anyway, winblows just acts like it is using DMA and
> doesn't really.) Otherwise try another DMA drive and see if the problem
> resolves.
>
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
>
> Nothing is hard if you know the answer or are used to doing it.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Victor Tsaran
 ` Gregory Nowak
   ` Victor Tsaran
     ` Kirk Wood
     ` Gregory Nowak
     ` Kerry Hoath
     ` Shaun Oliver
       ` Kirk Wood
         ` Shaun Oliver
   ` Kirk Wood
 ` Kirk Wood
   ` Victor Tsaran [this message]
     ` Kerry Hoath
       ` Kirk Wood
       ` Victor Tsaran
   ` Kerry Hoath
     ` Shaun Oliver
     ` Victor Tsaran
       ` Kerry Hoath
     ` John Covici
       ` Victor Tsaran
 ` Shaun Oliver

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='000801c0ebbe$c8c54920$b621fea9@cybertsar' \
    --to=tsar@sylaba.poznan.pl \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).