> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/