From: kaih@khms.westfalen.de (Kai Henningsen)
To: dsrelist@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stream Lined Booting - SCSI Hold Up
Date: 07 Jun 2002 20:08:00 +0200 [thread overview]
Message-ID: <8QRbBdkXw-B@khms.westfalen.de> (raw)
In-Reply-To: <20020607165154.29392.qmail@web20809.mail.yahoo.com>
dsrelist@yahoo.com (Shane Walton) wrote on 07.06.02 in <20020607165154.29392.qmail@web20809.mail.yahoo.com>:
> Thank you all for your replies. Disabling the SCSI
> reset helps much, but not enough. I ended up loading
> a RAM disk to start key binaries to fulfill this
> requirement, afterwards I then load the aic7xxx module
> and pivot_root to the real root. My biggest problem
> is
> the BIOS level resets and POST. Thanks for your time.
* Generic BIOS:
On modern BIOSes, there are usually several options that can be changed
to speed up that part - switching off the memory check, the floppy seek,
and so on.
* Adaptec BIOS:
It's been a while since I saw that, but there's often stuff that can be
switched in a SCSI BIOS as well. Such as which targets and LUNs it will
look at, what options it will try, if those options can be negotiated,
if it will try to spin up disks, and so on. Some of those options also
affect boot speed.
You might need to experiment some to determine the fastest setting.
But beware that *some* settings can at least theoretically make a reboot
hang that's not coming from power-off. (If the boot disk doesn't spin up
by itself, that can usually be changed by a jumper; the BIOS should not
*need* to spin up disks.) And turning off error checks means - just like
one would expect - that some errors aren't checked for.
MfG Kai
next prev parent reply other threads:[~2002-06-07 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 16:51 Stream Lined Booting - SCSI Hold Up Shane Walton
2002-06-07 18:08 ` Kai Henningsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 17:22 Shane Walton
2002-06-06 20:44 ` Patrick Mansfield
2002-06-07 22:55 ` Patrick Mansfield
2002-06-08 3:15 ` Justin T. Gibbs
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=8QRbBdkXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=dsrelist@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox