Hi William,

>I'd boot the Sarge install CD, go into "expert setup", and look for
>something like "Make System Bootable.", to recreate the contents of the
>MBR.

At this very moment, I'm reinstalling in expert mode (expert26), as per your
advice. After going through most of the process, though, it seemed that I
had already made the system bootable in the previous install. During the
partitioning process, you are able to set the boot flag on and off, which I
did for the /boot partition. Here is the (last) partition table I included
in my original email:

>>So my current partitioning scheme is thus:
>>IDE5 (hde) FREE SPACE

>>IDE6 (hdg)
>>Device     Boot     Start       End     Blocks      Id      System
>>/dev/hdg1   *        1          31      248967      83      Linux
>>/dev/hdg2           32         274    1951897+      82      Linux swap
>>/dev/hdg3          275       19457  154087447+      83      Linux

I'm assuming that the asterisk in column boot\row dev/hdg1 is what you were
referring to. As you can see the boot partition was already marked with a
bootable flag. Let me know if I'm totally out of touch on this.

Oh, also...

Installing in expert mode, I received this warning:

"Linux kernel modules needed to drive some of your hardware are not
available yet. Simply porceeding with the install may make these modules
available later.

The unavailable modules, and the deviceds that need them are:
forcedeth (NVIDIA Corporation nForce2 Ethernet Controle3r), sk981in (Galileo
Technology, Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter), medley
(CMD Technology Inc Silicon Image Serial ATARaid Controller [CMD/Sil
3112/3112A ]), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe
driver), ide-detect (Linux IDE detection), ide-floppy (Linux IDE floppy),
eth1394 (Firewire ethernet)"

Are these based on actual hardware detection, or are they the result of my
choosing to load all the drivers I was given the option for (not knowing
which were unnecessary)?

----------------------

Another thing... In a post I found on the debian-users list, I noticed that
someone running SATA drives mentioned that the drives were successfully
recognized as sd, not hd. Perhaps the problem's related to this.

BTTDB (back-to-the-drawing-board)

My best,

Jon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to