From: "Nick Evgeniev" <nick@octet.com>
To: "Andre Hedrick" <andre@linux-ide.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.4.19-preX IDE bugs
Date: Fri, 14 Jun 2002 11:44:21 +0400 [thread overview]
Message-ID: <014201c21377$4bbcde20$baefb0d4@nick> (raw)
In-Reply-To: <Pine.LNX.4.10.10206132354020.21513-100000@master.linux-ide.org>
Hi,
> > And I have no kernel errors. Hence I conclude that it's a DRIVER bug.
>
> If you had connected them correct the first time like they are now, you
> would not have had a complaint. Next, maybe spend more money to get
> quality hardware, since VIA hardware has a history of being poorly
> intergrated.
What are you talking about?! My system was working perfectly for more than 1
year...
And then after changing kernel, my cabels magically becomes "wrong
plugged"?!
WONDERFULL explanation :-/.
>
> Now think for two seconds or longer if needed.
>
> It now works and the driver has not changed.
Yeah... Best driver is not used... wait a second... even not compiled
driver. Am I right?
Well anyway, I plan to change hardware shortly to avoid participation in
never-ending
promise driver testing cycle.
next prev parent reply other threads:[~2002-06-14 7:53 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 [this message]
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
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='014201c21377$4bbcde20$baefb0d4@nick' \
--to=nick@octet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.