From: Christopher Swope <swopecr@yahoo.com>
To: linux-newbie@vger.kernel.org
Subject: Strange Boot Behavior (cont.)
Date: Thu, 21 Aug 2003 22:49:05 -0700 (PDT) [thread overview]
Message-ID: <20030822054905.11388.qmail@web13804.mail.yahoo.com> (raw)
Hello again,
Can anyone tell me if there is an easy way to reply on-list. Several
people have responded to my first inquiry, and I expected the
reply-to address to be the list email, but it was their personal
emails instead.
Anyway, I would like to address some of the concerns brought up in
those emails. My initial hunch was that there was a problem with the
jumpers, but I checked several times to make sure they were okay.
Nonetheless, after three separate people replied suggesting that I
check the jumpers, I went back just to be sure. Sure enough, the
jumpers were right. I did run a little jumper experiment, however,
and here are the results:
If the settings are any of the following, the drives are not
recognized at all. (These results are not surprising).
Primary -- Master w/ Slave present
Secondary -- Cable Select
Primary -- Master w/ Slave Present
Secondary -- Master
Primary -- Anything other than "Master (Single Drive)"
Secondary -- Not installed
If the settings are any of the following, I get the behavior I
described earlier.
Primary -- Cable Select
Secondary -- Slave
Primary -- Master w/ Slave Present
Secondary -- Slave
Primary -- Master (Single Drive)
Secondary -- Slave
Now, my line of thinking is as follows.
If the second drive is not installed at all, the computer boots
normally. This would indicate the problem stems from connecting the
second drive.
The computer can be successfully booted from a floppy boot disk.
Then, both drives can be read from and written to. This would
indicate that there is nothing wrong with the Cables.
Note also that I have tested nearly every jumper setting for the
secondary drive. The only option I did not try was setting the
secondary drive to master w/ slave present. That setting requires
two jumpers, and I don't have an extra one. I highly doubt, however,
that that configuration would work. Thus, if I were setting the
jumpers on the second drive wrong, one of the other options should
have worked.
Finally, I would like to provide some answers to questions that have
come up or might come up:
How old is the BIOS?
I have the latest revision. It was released sometime in 2000.
Are you sure the BIOS is correct?
Yes.
Do you have confidence in the BIOS?
Not really, but the computer does boot sometimes.
How big is the new hard drive?
80G
The old one?
4G
Have you used two hard drives on the system before?
Yes, but not with this revision of the BIOS.
There is probably more information I could provide still, so if you
want to know, please ask.
Thanks again for your help,
Christopher
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2003-08-22 5:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 5:49 Christopher Swope [this message]
2003-08-22 13:18 ` Strange Boot Behavior (cont.) Ray Olszewski
2003-08-22 15:22 ` Christopher Swope
2003-08-22 15:48 ` Ray Olszewski
2003-08-22 17:25 ` Warren Hrach
2003-08-22 19:00 ` Ken Moffat
2003-08-24 18:26 ` Robert Couture
[not found] ` <20030829135635.A194@lnx2.w8mch.ampr.org>
2003-08-29 19:07 ` Hal MacArgle
-- strict thread matches above, loose matches on Subject: below --
2003-08-22 18:55 beolach
2003-08-22 0:00 Heimo Claasen
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=20030822054905.11388.qmail@web13804.mail.yahoo.com \
--to=swopecr@yahoo.com \
--cc=linux-newbie@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