Booting Issue

gone15 · #1 26th December 2006, 02:45 PM

I want to be able to use my windows boot loader to come up and then use it to boot my linux... Right now Iam running three OS's on my computer Vista, Xp, & Fedora 6... When I turn my computer on my grub boot loader comes up then if I hit the windows it will take me to the windows boot loader where I have boot options for Fedora, Xp & Vista The Fedora one just brings me back to the grub bootloader which I don't mind but if I could get it to come up after the windows boot laoder then I can set the grub bootloader with a zero second timeout and just boot linux... So if there is anyway I can move the grub bootloader behind the windows one it would help me out... Thanks in advance...

b_martinez · #2 26th December 2006, 04:13 PM

Let me get this straight....
Your GRUB boots, then when you select Windows,you are handed over to the Windows bootloader? You have the option to boot Linux, which returns you to grub? So I am assuming that sometime before now, you configured the Windows bootloader to Load linux. [Correct me if I'm wrong.]
IF this is the case, and if I understand what what you want..... then this is what you need to do.
1) start up the linux OS and log in as root.
2) open a terminal and type in "grub --install /dev/hdX" ( where X=partition number of root partition for Linux OS) [remember..Linux counts from zero (0) ]
3) type in "init 6" but do not hit the 'enter' key yet. First put in the Windows disk so you can use the recovery console when you re-boot. [ This may be un-needed. If you know how to edit the win bootloader, you may have already set up a boot option in windows to boot into recovery console]
4) re-boot into windows and reinstall the windows bootloader.
5) if using the Win installation disk, after booting up, follow the prompts to get to the 'recovery console'
This is what the commands look like in both linux and windows. Hit 'enter' key after each line
Linux

Code:

grub --install /dev/hdX
init 6

Windows

Code:

fixboot
fixmbr
exit
exit

The second 'exit' may not be needed. I haven't used Windows for almost 2 years.
Anyway, what this will do is set your computer to
1] start windows bootloader FIRST
2] when you choose Linux, it will boot from the / (root) partition, enabling you to have a 0 (zero) second delay before booting.
You will need to edit the /boot/grub/grub.conf in Linux to achieve the zero second delay.
Good luck and hth
Bil

edit: use the win bootloader from the win system with the modified boot loader. This is the one you have to use to keep linux.

gone15 · #3 26th December 2006, 08:28 PM

Quote:

Originally Posted by b_martinez

Let me get this straight....
Your GRUB boots, then when you select Windows,you are handed over to the Windows bootloader? You have the option to boot Linux, which returns you to grub? So I am assuming that sometime before now, you configured the Windows bootloader to Load linux. [Correct me if I'm wrong.]
IF this is the case, and if I understand what what you want..... then this is what you need to do.
1) start up the linux OS and log in as root.
2) open a terminal and type in "grub --install /dev/hdX" ( where X=partition number of root partition for Linux OS) [remember..Linux counts from zero (0) ]
3) type in "init 6" but do not hit the 'enter' key yet. First put in the Windows disk so you can use the recovery console when you re-boot. [ This may be un-needed. If you know how to edit the win bootloader, you may have already set up a boot option in windows to boot into recovery console]
4) re-boot into windows and reinstall the windows bootloader.
5) if using the Win installation disk, after booting up, follow the prompts to get to the 'recovery console'
This is what the commands look like in both linux and windows. Hit 'enter' key after each line
Linux

Code:

grub --install /dev/hdX
init 6

Windows

Code:

fixboot
fixmbr
exit
exit

The second 'exit' may not be needed. I haven't used Windows for almost 2 years.
Anyway, what this will do is set your computer to
1] start windows bootloader FIRST
2] when you choose Linux, it will boot from the / (root) partition, enabling you to have a 0 (zero) second delay before booting.
You will need to edit the /boot/grub/grub.conf in Linux to achieve the zero second delay.
Good luck and hth
Bil

edit: use the win bootloader from the win system with the modified boot loader. This is the one you have to use to keep linux.

K your right as far as I configured windows to boot linux... It does point back to the grub loader... I did try your commands I did the "grub --install /dev/hdX" it brought me to a grub screen which basically had a grub prompt... Oh also I have an SD drive so I typed that in instead... sda3 is where the grub.conf says my boot is installed... But when I type init 6 I got unrecognized command and I type tab to see list of possible commands and init is not in there... Don't know where to go from here stuck at the number two of codes to run in linux... Im thinking it has something to do with either me having grub installed already or maybe i am typing the wrong /dev/sda3 drive...

b_martinez · #4 26th December 2006, 09:39 PM

[quote]
K your right as far as I configured windows to boot linux... It does point back to the grub loader... I did try your commands I did the "grub --install /dev/hdX" it brought me to a grub screen which basically had a grub prompt... Oh also I have an SD drive so I typed that in instead... sda3 is where the grub.conf says my boot is installed... But when I type init 6 I got unrecognized command and I type tab to see list of possible commands and init is not in there... Don't know where to go from here stuck at the number two of codes to run in linux... Im thinking it has something to do with either me having grub installed already or maybe i am typing the wrong /dev/sda3 drive...
[endquote]

Exactly how is your windows bootloader set up? When it passes off to grub, where does it pass off to ? The mbr or to /boot/grub/dev/sda3 ? If to the mbr, then you will never get your linux to boot, because the 2nd set of commands will wipe the mbr and re-install the windows bootloader.
To start again.....
1] boot into your linux.
2] if logging on as your user account, open a terminal and type in

Code:

su -
[enter your root password here]
grub --install /dev/hda3
quit 
init 6

It's been a while since I had to re-install grub. forgot that once you install , you are taken to a 'grub' prompt. You need the 'quit' to escape the grub prompt [ might be exit, but try quit first] then do the init 6 to reboot. The 'su -' is needed only if you are in the regular user account (which is a good idea).
Make sure that the Win bootloader calls grub from /dev/sda3 and not the mbr.
Let me know if this works for you.
Bill

gone15 · #5 27th December 2006, 12:27 AM

Quote:

Originally Posted by b_martinez

Exactly how is your windows bootloader set up? When it passes off to grub, where does it pass off to ? The mbr or to /boot/grub/dev/sda3 ? If to the mbr, then you will never get your linux to boot, because the 2nd set of commands will wipe the mbr and re-install the windows bootloader.
To start again.....
1] boot into your linux.
2] if logging on as your user account, open a terminal and type in

Code:

su -
[enter your root password here]
grub --install /dev/hda3
quit 
init 6

It's been a while since I had to re-install grub. forgot that once you install , you are taken to a 'grub' prompt. You need the 'quit' to escape the grub prompt [ might be exit, but try quit first] then do the init 6 to reboot. The 'su -' is needed only if you are in the regular user account (which is a good idea).
Make sure that the Win bootloader calls grub from /dev/sda3 and not the mbr.
Let me know if this works for you.
Bill

When my computer starts up my hp logo comes up... Then it goes to the grub bootloader... Then it goes to the windows bootloader.... The Grub boot loader menu list looks like this...

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,2)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda3
default=1
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.18-1.2798.fc6)
root (hd0,2)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.18-1.2798.fc6.img
title Windows
rootnoverify (hd0,0)
chainloader +1

If I select the Windows Title on there (grub loader) it will take me to the windows boot loader which has a list of Fedora Core 6, Windows Xp, Windows Vista.... If I choose Xp or Vista it will boot either of them... However if I choose Fedora Core 6 from that menu then it will bring me back to the grub boot loader....

If I select Fedora Core (2.6.18-1.2798.fc6) from the grub boot loader it will take me into linux like its suppose too...

Let me know if you still want me to try the commands you last sent me because I want to know that we are on the same page before I try them.... Thanks for you help so far...

b_martinez · #6 27th December 2006, 01:38 AM

What I 'think' is happening is that
1) during the POST (power on self test) phase of booting, you see the HP logo
2) after the "POST", you are in the 'grub' menu list that is on your mbr. When you pass off to Windows, you are taken to it's menu list because you have more than 1 system that it can choose to boot from. [Not on mbr, but part of ntldr system?]
3) If you have grub installed to /dev/sda3 [you should, because you ran the "grub --install /dev/sda3" command], then it likely is necessary to
a] reconfigure grub to immediately boot
b] re-install Windows bootloader to your mbr.
To do this,
a]just change the timeout to 0 (zero)
b]Do the commands previously listed for Windows. [Do this in the Windows Recovery Console]
Prior to doing any of this, go to HP.com and look for information on your system. Find out if they have their own bootloader, because I could be VERY,VERY wrong about the "POST". If not, then 'go for it'.
Bill

gone15 · #7 28th December 2006, 01:00 AM

Quote:

Originally Posted by b_martinez

What I 'think' is happening is that
1) during the POST (power on self test) phase of booting, you see the HP logo
2) after the "POST", you are in the 'grub' menu list that is on your mbr. When you pass off to Windows, you are taken to it's menu list because you have more than 1 system that it can choose to boot from. [Not on mbr, but part of ntldr system?]
3) If you have grub installed to /dev/sda3 [you should, because you ran the "grub --install /dev/sda3" command], then it likely is necessary to
a] reconfigure grub to immediately boot
b] re-install Windows bootloader to your mbr.
To do this,
a]just change the timeout to 0 (zero)
b]Do the commands previously listed for Windows. [Do this in the Windows Recovery Console]
Prior to doing any of this, go to HP.com and look for information on your system. Find out if they have their own bootloader, because I could be VERY,VERY wrong about the "POST". If not, then 'go for it'.
Bill

K I am all set now thanks to your help....

Here's what I did

Code:

su -
[enter your root password here]
grub --install /dev/hda3
quit 
init 6

To be honest I don't think the grub --install thing did anything at all and quit and init 6 seemed to just exit the grub prompt and reboot... I had the same startup issue...

But the

Code:

fixboot 
fixmbr 
exit

Basically took over both the boot loaders I had the Vista Boot Loader & The Grub Boot Loader... Which was fine...

I downloaded and installed Easybcd 1.52... Don't know if you have heard of it but its one of two programs that are used to edit the Windows Vista bootloader... In Easy Bcd I went to Manage Bootloader option and hit rewrite the Vista Bootloader this reinstalls the Windows Vista Bootloader that I had before that I was getting after the grub boot loader... It still had all three Os's like I wanted and when I click my linux distro it now takes me to the grub boot loader like I wanted... I just set the grub boot loader to a zero timeout so it will load Fedora automatically....

Once again thanks for your help now I can start working on doing more things in my linux box... Next thing is to fix that load system beep when my fedora is done loading... Then I got to start working on wireless networking...