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 01:51:40 +0200 [thread overview]
Message-ID: <000e01c0ebbe$ff53f5e0$b621fea9@cybertsar> (raw)
In-Reply-To: <20010602161651.A286@linserver.megsinet.net>
But why UltraDMA? Are DMA and UltraDMA much different from each other?
Vic
----- Original Message -----
From: "Gregory Nowak" <romualt@megsinet.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, June 02, 2001 11:16 PM
Subject: Re: A more complete log about my disk access errors
> Hi Vic,
>
> Yeah, I'd say also to check if you have ultra dma
> support in your kernel.
> Greg
>
>
> On Sat, Jun 02, 2001 at 10:44:19PM -0100, Victor Tsaran wrote:
> Content-Description: message body text
> > Hello, listers!
> > I hope those of you who are experts in kernel bugs or interaction of
kernel
> > with the hardware can help me with this. Since I installed Redhat 7.1 I
> > started to get the messages that RedHat cannot communicate through DMA
with
> > my hard drives. I know for sure that my hard drives can communicate
through
> > DMA, plus I was never getting similar messages before. Shon suggested
for
> > me to check whether UltraDMA support was compiled into my kernel, but I,
> > firstly, do not understand why it should be included into kernel, and
> > secondly, why would Redhat ignore including UltraDMA support in the
first
> > place.
> > Iam therefore attaching the complete log from the messages buffer ring
> > produced by the `dmesg' command.
> > Please let me know if you have any idea and where should I look for
> > possible solutions.
> > WIndows 2000 is very happy about my drives, whereas Linux complains
about
> > them. However, after kernel disables DMA transfer mode, it goes pretty
> > fine. Please ignore any messages about SWAP...
> > Best and thanks in advance,
> > Vic
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
Victor Tsaran
` Gregory Nowak
` Victor Tsaran [this message]
` Kirk Wood
` Gregory Nowak
` Kerry Hoath
` Shaun Oliver
` Kirk Wood
` Shaun Oliver
` Kirk Wood
` Kirk Wood
` Victor Tsaran
` 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='000e01c0ebbe$ff53f5e0$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).