public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Evgeniev" <nick@octet.com>
To: "Andre Hedrick" <andre@linux-ide.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.4.19-preX IDE bugs
Date: Fri, 14 Jun 2002 13:06:13 +0400	[thread overview]
Message-ID: <019c01c21382$bbf7a340$baefb0d4@nick> (raw)
In-Reply-To: <Pine.LNX.4.10.10206140112490.21513-100000@master.linux-ide.org>

Hi,

> Nick,
>
> http://www.tecchannel.de/hardware/817/index.html
>
> Read about the JUNK hardware base you are working with.
> This is one of the reasons people avoid VIA.

Ok. Thanks... But it's not my case. Article talks about ata-133 not
ata-100..

> OIC, it worked perfectly in wonder kernel but not in the latest.

I had 2.4.7 kernel, it was working just fine for me... Then I changed it to
2.4.18/2.4.19-preX
(with all problems I wrote about).

> Did you check to see if there were other changes in the kernel which could
> effect the behavior and operations?

It's a little bit hard for non-kernel developer to track changes between 10
kernel versions, sorry :(

> A real simple test is to undo the changes to the Promise code and does
> the problem still exist?  If it does then it is not the driver it self.

As I wrote already... I'm in process of changing hardware... and office
location.
>
> However the other changes in conjuntion could cause problems, that is a
> fair point to be made.

Sure.. But I reported problem as I've seen it in kernel logs.
>
> So how about including which kernel was the last working version.

2.4.7 Sorry, it's old enough, but usually I don't change kernel till it
works...

>
> For kicks I would back port the driver to prove it is not the driver, or
> allow you to prove it is.
>

Actually, no need to do this. As I wrote I'm changing hardware and will try
to avoid promise, via, and may be ide :)
Hope it solves the problem :) at least for me.



  parent reply	other threads:[~2002-06-14  9:08 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:28 linux 2.4.19-preX IDE bugs Nick Evgeniev
2002-06-04 16:41 ` Alan Cox
2002-06-08 19:52   ` Andre Hedrick
2002-06-11 15:31     ` Nick Evgeniev
2002-06-11 16:52       ` Andre Hedrick
2002-06-13 11:15         ` Nick Evgeniev
2002-06-14  7:01           ` Andre Hedrick
2002-06-14  7:44             ` Nick Evgeniev
2002-06-14  8:20               ` Andre Hedrick
2002-06-14  8:37                 ` Vojtech Pavlik
2002-06-14  8:45                   ` Andre Hedrick
2002-06-14  8:55                     ` Vojtech Pavlik
2002-06-14  8:59                       ` Andre Hedrick
2002-06-14  9:15                         ` Bartlomiej Zolnierkiewicz
2002-06-14  9:19                         ` Bartlomiej Zolnierkiewicz
2002-06-14  8:59                     ` Abraham vd Merwe
2002-06-14  9:08                       ` Andre Hedrick
2002-06-14  9:24                         ` Abraham vd Merwe
2002-06-14  9:06                 ` Nick Evgeniev [this message]
2002-06-11 18:53       ` Jason C. Pion
2002-06-11 19:34         ` Tomas Szepe
2002-06-11 19:47           ` Jason C. Pion
2002-06-14 12:34         ` Bill Davidsen
2002-06-14 14:22           ` Jason C. Pion
2002-06-11 22:49       ` Bill Davidsen
2002-06-12  0:19         ` Andre Hedrick
2002-06-12  7:31         ` Alan Cox
2002-06-12 13:57           ` Bill Davidsen
2002-06-12 18:32             ` Andre Hedrick
2002-06-12 20:30               ` Bill Davidsen
2002-06-12  7:36       ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 18:26 Mikael Pettersson
2002-06-13 20:39 Mikael Pettersson
2002-06-15 17:12 Anssi Saari
2002-06-15 18:51 ` Vojtech Pavlik

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='019c01c21382$bbf7a340$baefb0d4@nick' \
    --to=nick@octet.com \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@octet.spb.ru \
    /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