Thanks John. None of your suggestions turned up the problem directly,
but they did get me thinking and I tried the same disk on different
connectors and at different settings. I found that I can boot from the
primary slave device and the secondary master device. I didn't try the
secondary slave device. The only one that reliable fails is the primary
master device.
I did try resetting my BIOS settings to the default.
Weird, huh?
Some day I'll come back and try to figure out why this is the case.
Meanwhile, though, I just reconfigured my grub settings and moved on.
Thanks everyone for your suggestions.
Michael
On Sat, 17 Sep 2005, John Myers wrote:
On Saturday 17 September 2005 21:47, Walter Dnes wrote:
Can you check the jumpers on the drive? In the old days, there were
just "master" and "slave". Now there's a 3rd option "cable select",
which may be abbreviated as "CS". It works "automagically" with Windows
but it does *NOT* work with linux. If the jumper is set CS, set it to
master and try booting from it again.
Good thinking, except that it's failing in the BIOS. Linux has nothing to do
with it.
I would suggest checking the jumpers (if it's a PATA disk), unplugging and
replugging the signal cable (at both ends), and unplugging and replugging the
power cable.
If you have access to one, try with a different signal cable, and try with a
different lead from your PSU
Also might check for bad a bad CMOS battery, and check the BIOS settings,
ensuring all your controller hasn't accidentally been turned off.
You might also try wiggling the block of connectors on the drive. I happen to
have a funky SATA Seagate Barracuda 7200.7 which stops my system booting if
the connector block is jostled the wrong way.
--
gentoo-user@gentoo.org mailing list
