From: Arne Brutschy <abrutschy@xylon.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re[4]: [PATCH] ide driver 2.4.21-rc6
Date: Fri, 27 Jun 2003 00:01:52 +0200 [thread overview]
Message-ID: <1461514129.20030627000152@xylon.de> (raw)
In-Reply-To: <Pine.SOL.4.30.0306040131330.26979-100000@mion.elka.pw.edu.pl>
Hi,
as I promised, I'm back at home and investigated the problem with the
CONFIG_PDC202XX_FORCE setting further.
The special cas with my setup is, that I have an ICH4 onboard, an
PDC20276 onboard and an PCI SCSI controller. The root filesystem is on
the SCSI disks. I can not boot from the SCSI disks directly, as the
BIOS enables the PDC first. So I have to boot from the IDE disks
connected to the PDC. This didn't work, so I replaced the simple
Promise RAID bios with an normal UDMA bios thats allows you to use the
controller as normal IDE controller. The result is, I can boot from
the IDE disks and I can use the IDE disks as normal disks (used it in
times the CONFIG_PDC202XX_FORCE wasn't in the linux kernel).
I do not know if the PDC 20276 is being sold with such a normal bios.
I think so, as there are serveral users reporting the same error.
The problem is, that the driver thinks the bios/drives didn't get enabled
by the bios end disables the whole controller. I patched the driver to
skip this step. I still have to use the CONFIG_PDC202XX_FORCE setting-
without it the second channel gets disabled.
This is the reason for my patch. I'm not sure, but I this it shouldn't
be a problem for the driver...
Regards,
Arne
PS: please write me if you see any problems related to that patch
Bartlomiej Zolnierkiewicz wrote:
BZ> It MUST work.
BZ> Clean your kernel source with 'make mrproper' (just in case) and compile
BZ> again with Special FastTrak Feature enabled (CONFIG_PDC202XX_FORCE=y).
BZ> If it really won't work contact me.
BZ> --
BZ> Bartlomiej
BZ> On Tue, 3 Jun 2003, Arne Brutschy wrote:
>> Bartlomiej Zolnierkiewicz wrote:
>> BZ> What about turning on "Special FastTrak Feature" instead...
>> Didn't work for me, don't know why.
>>
>> Arne
prev parent reply other threads:[~2003-06-26 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 18:51 [PATCH] ide driver 2.4.21-rc6 Arne Brutschy
2003-06-02 19:41 ` Bartlomiej Zolnierkiewicz
2003-06-03 13:22 ` Re[2]: " Arne Brutschy
2003-06-03 23:49 ` Bartlomiej Zolnierkiewicz
2003-06-26 22:01 ` Arne Brutschy [this message]
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=1461514129.20030627000152@xylon.de \
--to=abrutschy@xylon.de \
--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;
as well as URLs for NNTP newsgroup(s).