[CLUE-Tech] Fedora CD Audio Issues
Collins Richey
crichey at gmail.com
Fri Sep 3 11:57:10 MDT 2004
On Fri, 3 Sep 2004 10:58:20 -0600, Jesse William <jwilliam at gmail.com> wrote:
> that is indeed what i meant. i'm not quite sure how that would work,
> i'm not at all familiar with GRUB and i've been away from linux for
> some time. it wrote to the mbr on the windows drive, and i had
> supplied an option to boot windows or linux during that install,
> however when you pick either of them i get a funky error and a "press
> any key" promt. then the screen would get all funky with horizontal
> lines running thru everything(this is all in text mode).
>
Hmm, I've never seen anything like that.
The way grub works is basically this, and it does not matter whether
you have one or multiple drives with bootable os.
1) grub needs a /boot/grub structure (can be in a separate partition).
The grub directory contains "stage2 executables" and a configuration
file (grub.conf or menu.lst, your choice) to define the bootable os.
2) grub writes the initial booting code to the mbr of the selected
drive during a "setup" procedure, and the initial booting code knows
where to find the /boot/grub directory (on any accessible drive) to
complete the booting procedure. There is also a grub "install"
procedure to perform similar action. The mbr is not a part of any
partition, and grub does not actually modify the partitions referenced
in its grub.conf file, so nothing should have affected your windows
partition.
3. During installation of the grub software, the "stage2 executables"
should have been copied to /boot/grub, or your installation package is
broken.
4. Installation does not accomplish the "setup" action. You do this
manually, or it is done under the covers by your os installer (i,e.
fedora). You must do this
a. Create a /boot/grub/grub.conf (see sample below).
b. executed grub and enter the following:
(1) root (hdn,n) (This is grub notation for the partition
containing /boot/grub)
(2) setup (hd0) (This is grub drive notation for where to write the mbr)
(3) quit
Assuming that you have windows on hda1 (linux notation) or hd0,0 (grub
notation) and linux on hdb with hdb1 (hd1,0) as swap and hdb2 (hd1,1)
as the linux / partition, the above root statement would be root
(hd1,1)
5. Your /boot/grub/grub.conf would contain the following at a minimum;
there are other grub parameters.
## optional
default 0
timeout 25
## optional
title desired-linux-title
root (hd1,1)
kernel (hd1,1)/boot/nameofyourkernel root=/dev/hdb2 ro
# if you have a separate /boot partion, say hdb2 = /boot, hdb3 = /
#title desired-linux-title
# root (hd1,1)
# kernel (hd1,1)/nameofyourkernel root=/dev/hdb3 ro
title desired-windows-title
root (hd0,0)
chainloader +1
You may need to reinstall grub and verify that /boot/grub looks
approximately like this
-rw-r--r-- 1 root root 11488 Aug 25 08:12 e2fs_stage1_5
-rw-r--r-- 1 root root 10480 Aug 25 08:12 fat_stage1_5
-rw-r--r-- 1 root root 9408 Aug 25 08:12 ffs_stage1_5
-rw-r--r-- 1 root root 1164 Sep 1 17:00 grub.conf
-rw-r--r-- 1 root root 1624 Aug 25 08:12 grub.conf.sample
-rw-r--r-- 1 root root 9568 Aug 25 08:12 iso9660_stage1_5
-rw-r--r-- 1 root root 11648 Aug 25 08:12 jfs_stage1_5
lrwxrwxrwx 1 root root 9 Jul 17 16:38 menu.lst -> grub.conf
-rw-r--r-- 1 root root 9792 Aug 25 08:12 minix_stage1_5
-rwxr-xr-x 1 root root 201124 Aug 25 08:12 nbgrub
-rwxr-xr-x 1 root root 202148 Aug 25 08:12 pxegrub
-rw-r--r-- 1 root root 13152 Aug 25 08:12 reiserfs_stage1_5
-rw-r--r-- 1 root root 33856 Aug 25 08:12 splash.xpm.gz
-rw-r--r-- 1 root root 512 Aug 25 08:12 stage1
-rw-r--r-- 1 root root 142060 Aug 25 08:12 stage2
-rwxr-xr-x 1 root root 201732 Aug 25 08:12 stage2.netboot
-rw-r--r-- 1 root root 133004 Feb 27 2004 stage2.old
-rw-r--r-- 1 root root 142060 Aug 25 08:12 stage2_eltorito
-rw-r--r-- 1 root root 9876 Aug 25 08:12 ufs2_stage1_5
-rw-r--r-- 1 root root 9088 Aug 25 08:12 vstafs_stage1_5
-rw-r--r-- 1 root root 13032 Aug 25 08:12 xfs_stage1_5
Then issue the "setup" procedure listed above, reboot, and enjoy.
HTH,
--
/\/\
(CR) Collins Richey
\/\/ 20 minutes is the average that a Windows based PC lasts
before it's compromised.
- according to the Internet Storm Center.
More information about the clue-tech
mailing list