From: "Andrew Chan" <achan@achan.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Promise 20267 "working" but no UDMA
Date: Mon, 2 Apr 2001 23:35:30 +0800 [thread overview]
Message-ID: <003e01c0bb8a$8cd4a140$3700a8c0@pluto> (raw)
Actually, upon further testing, I found that the MB will move on without an
Fasttrack array. However, it will proceed to boot from PXE because it now
thinks that there is no hard disk attached to the entire system (as reported
by the Promise RAID chip)!
So,
1. Promise driver doesn't support SMP or 2.4.x kernels
2. Linux IDE code won't support the chip in any Promise RAID config, not
even single disk span
3. If not under RAID config, the motherboard thinks it has no hard disk, so
booting from disk is not possible even though the kernel can run the disks
in ATA100 mode
The remaining alternative is to boot from floppy (to load the kernel) and
specify the hard disk as root disk... :-(
I am most disappointed with Promise (not so much with Tyan).
Andrew
> >> FastTrack config: only 1 drive, configured as a SPAN volume
> >> consisting of 1 drive
>
> > No RAIDing allowed in the FTTK Bios.
>
> But my motherboard hangs at boot time (while Fasttrack tests for arrays)
> if there is no array defined! There is a message from the Fasttrack bios
> that says something like "no array found, press some key to continue".
> But I need to remotely reboot these servers!
next reply other threads:[~2001-04-02 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 15:35 Andrew Chan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 11:13 Promise 20267 "working" but no UDMA Andrew Chan
2001-04-02 7:27 ` Andre Hedrick
2001-04-02 9:00 ` Andrew Chan
2001-04-02 16:20 ` Nerijus Baliunas
2001-04-24 5:04 ` Andre Hedrick
2001-04-03 10:58 ` Ruth Ivimey-Cook
2001-04-03 15:57 ` Andrew Chan
2001-04-03 16:30 ` Ruth Ivimey-Cook
2001-04-03 19:10 ` Juhani Rautiainen
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='003e01c0bb8a$8cd4a140$3700a8c0@pluto' \
--to=achan@achan.com \
--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 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.