From: Phil Dibowitz <phil@ipom.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux IDE bug in 2.4.21 and 2.4.22 ?
Date: Tue, 09 Sep 2003 08:13:39 -0700 [thread overview]
Message-ID: <3F5DEE23.6020106@ipom.com> (raw)
In-Reply-To: <200309091701.48993.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
>>But, what about the case when I built in the generic driver, but made
>>the CMD649 driver a module, and loaded it after boot. That shouldn't
>>have *changed* what ide0 and ide1 are, right? I had ide0 and ide1
>>assigned, did a modprobe, and CMD649 changed what ide0 adn ide1 where,
>>and then forgot about the previous ones.. like all of a sudden it told
>>the generic driver "no, no, you were wrong, there's no VIA chipset here,
>>go back to sleep."
>
>
> Hmm. please send me dmesg.
>
I'm happy to. Assumably you want both a Dmesg of my new working kernel,
and a dmesg of above described kernel? Note that the dmesg from the
later kernel be before loading the CMD64X modules, because when I do
that, I loose my hard drive. Therefore it'll look mostly like my working
one, except with no ide2 and ide3.
I've gone ahead and posted the current working dmesg here:
http://www.phildev.net/dmesg-working
I'll have to do the non-working kernel when I get back from work. I'll
drop a line when I get that posted.
Thanks,
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
next prev parent reply other threads:[~2003-09-09 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 22:51 Linux IDE bug in 2.4.21 and 2.4.22 ? Phil Dibowitz
2003-09-09 12:48 ` Bartlomiej Zolnierkiewicz
2003-09-09 14:33 ` Phil Dibowitz
2003-09-09 15:01 ` Bartlomiej Zolnierkiewicz
2003-09-09 15:13 ` Phil Dibowitz [this message]
2003-09-10 3:52 ` Phil Dibowitz
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=3F5DEE23.6020106@ipom.com \
--to=phil@ipom.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
/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