Author Topic: Fixing A Tri Boot  (Read 3817 times)

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Fixing A Tri Boot
« on: October 04, 2009, 06:11:42 PM »
I am  tri booting PCLOS KDE3, PCLOS KDE4 and Win 7. Although I can get into each operating system, my first boot screen with pclos K3 brings me to basically the same  when I click to go into pclos K4 in the original screen.
 Is there a way to edit my menu.lst to bring me right into K4?.I am certaintly glad it works, but always open to learn if there is a better way. Thanks very much for any suggestions.

PCLOS K3 menu.lst

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title Windows7
root (hd0,0)
makeactive
chainloader +1

title 2.6.24.7.tex1
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.24.7.tex1 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot


title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
savedefault
boot


title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

  PCLOS KDE4 menu.lst

splashimage (hd0,7)/boot/grub/splashimages/109089-malta-palo.xpm.gz
gfxmenu (hd0,7)/boot/gfxmenu
default 0
timeout 6
color black/cyan yellow/cyan

title PCLinuxOS KDE4
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_KDE4 root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img

title linux-nonfb
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,7)/boot/initrd.img

title failsafe
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a failsafe acpi=on
initrd (hd0,7)/boot/initrd.img

title windows
root (hd0,0)
chainloader +1
makeactive

title linux
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img
« Last Edit: October 04, 2009, 06:16:56 PM by Duvid »

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #1 on: October 04, 2009, 06:38:18 PM »
I am  tri booting PCLOS KDE3, PCLOS KDE4 and Win 7. Although I can get into each operating system, my first boot screen with pclos K3 brings me to basically the same  when I click to go into pclos K4 in the original screen.
 Is there a way to edit my menu.lst to bring me right into K4?.I am certaintly glad it works, but always open to learn if there is a better way. Thanks very much for any suggestions.

PCLOS K3 menu.lst

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title Windows7
root (hd0,0)
makeactive
chainloader +1

title 2.6.24.7.tex1
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.24.7.tex1 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot



title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
savedefault
boot


title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

  PCLOS KDE4 menu.lst

splashimage (hd0,7)/boot/grub/splashimages/109089-malta-palo.xpm.gz
gfxmenu (hd0,7)/boot/gfxmenu
default 0
timeout 6
color black/cyan yellow/cyan

title PCLinuxOS KDE4
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_KDE4 root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img

title linux-nonfb
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,7)/boot/initrd.img

title failsafe
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a failsafe acpi=on
initrd (hd0,7)/boot/initrd.img

title windows
root (hd0,0)
chainloader +1
makeactive

title linux
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img

If the KDE3.5 installation controls grub, the stanza quoted above in blue is very messed up. It might be helpful if you'd tell us more about which grub is controlling the boot process, for sure, which kernels you have installed on each installation, and which you are trying to boot to, so we know exactly what it is you are trying to accomplish. The more details you furnish, the better the advise will be.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #2 on: October 04, 2009, 08:46:06 PM »
I left out the last section of menu.lst which I pounded out so I would have one less entry on my boot screen. This is my default kernel for my first screen which  controls the boot process ( KDE 3.5).  I want to clean up the hand off to KDE 4 if possible.Thanks again for the help. Hope this is what you needed.

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title Windows7
root (hd0,0)
makeactive
chainloader +1

title 2.6.24.7.tex1
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.24.7.tex1 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot


title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
savedefault
boot


title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

#title 2.6.27.31.tex5
kernel (hd0,1)/boot/vmlinuz-2.6.27.31.tex5 BOOT_IMAGE=2.6.27.31.tex5 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd-2.6.27.31.tex5.img
« Last Edit: October 04, 2009, 08:55:22 PM by Duvid »

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #3 on: October 04, 2009, 10:10:46 PM »
I left out the last section of menu.lst which I pounded out so I would have one less entry on my boot screen. This is my default kernel for my first screen which  controls the boot process ( KDE 3.5).  I want to clean up the hand off to KDE 4 if possible.Thanks again for the help. Hope this is what you needed.

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title Windows7
root (hd0,0)
makeactive
chainloader +1

title 2.6.24.7.tex1
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.24.7.tex1 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot


title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
savedefault
boot


title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

#title 2.6.27.31.tex5
kernel (hd0,1)/boot/vmlinuz-2.6.27.31.tex5 BOOT_IMAGE=2.6.27.31.tex5 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd-2.6.27.31.tex5.img


Again I ask, what is the partial stanza, in blue above, attached to the regular stanza immediately above it? You don't mention anything on (hd0,6)

You have two savedefault lines, but can only have one stanza to default to, and one is in the partial stanza.

Are you pressing Enter when the first boot menu choice is highlighted, or waiting for the timer to send you somewhere?

Terminology:

You really need to learn the proper terminology to use when asking for help, or replying with asked for information. If you don't, others have to guess at what you mean, and if the guess is wrong, so is the help they try to provide.

You don't pound out an entry; you comment it, by adding a hash character #.

I have no idea what a default kernel for a first screen is meant to imply.  ???

The initial boot process is controlled by BIOS, which sets up the hardware, and then finds the bootloader on the designated boot drive, (grub, in this case) then grub, using instructions from /boot/grub/menu.lst on one of your partitions. Grub's only purpose is to locate, then load a kernel, and it's accompanying initrd image into memory, so the kernel can then finish loading the rest of the OS.

During the process, grub presents you with a boot menu, then waits a given time. If during that time, you select an entry on the boot menu using the up or down arrow keys, and press the Enter key, your selection is booted. If you wait for the timer to expire, the default entry is booted. Obviously you can have only one default.

Now, try to describe, step by step, what you are doing, what you expect to happen, what actually happens, and how what actually happens differs from what you expect.

Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Xenaflux

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3829
Re: Fixing A Tri Boot
« Reply #4 on: October 04, 2009, 10:15:27 PM »
Quote
I am certaintly glad it works, but always open to learn if there is a better way. Thanks very much for any suggestions.

I boot also into 4 different systems, but instead of getting a headache, I use a boot manager.
My preferred one is GAG

Xena
The great thing in this world is not so much where we stand,
as in what direction we are moving.
                                                    (Oliver Wendell Holmes )

Offline Gnarly

  • New Friend
  • *
  • Posts: 9
Re: Fixing A Tri Boot
« Reply #5 on: October 04, 2009, 11:57:17 PM »
I'm not sure if you can bypass the kde4 grub, but you could edit the timeout in the kde4 menu.lst to 1 or o and speed the process up a little.

You could also in the kde3 menu.lst change the default to 5. That along with the kde4 timeout would speed booting up kde4 a bit.

LOL you could also reinstall grub with kde4 booted up and let it install grub in the mbr, then the kde4 grub would be the first menu you would see and by default it will load up kde4 first.
« Last Edit: October 05, 2009, 12:10:02 AM by Gnarly »

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #6 on: October 05, 2009, 01:44:50 AM »
 I will try again to explain what is happening........ My default kernel 2.6.27.31.tex5, is the kernel to which my system will boot into if I let it go by itself or if I wait 5 seconds as per the first stanza

The first  boot menu gives me these choices:
                                                                                          PCLOS K3
                                                                                          Windows 7
                                                                                          2.6.24.7.tex1
                                                                                          PCLOS K4
                          
  If I click on PCLOS K4 it will bring me to a new boot menu with these choices

                                                                    PCLOS  K3
                                                                    PCLOS safe mode
                                                                    PCLOS K4

 I kept 2.6.24.7.tex1 as a backup kernel "security blanket" that I really haven't really been using. I commented it out, as well as the texted version of the kernel the system is booting into, to keep down the confusion I created.
 What I am trying to find out if there is a way to go to  KDE 4 without having two boot menus, such as when going to Windows 7. Is there a modification in my grub menu that would accomplish this? I don't know how the save default happened. I installed PCLOS K4(hd0,7) on another partition after Win 7 using the bootloader from pclos onto the mbr of Win7 (hd0,0). Then I installed PCLOS with K3(hd0,1) on another partition and used that bootloader and placed it on Windows mbr (hd0,0). My end results is what I have posted.
  Inspite of my method, I can still get into all the operating systems, just figured there was a better way than how I had approached it.
 Hope this better explains the method to my madness.
« Last Edit: October 05, 2009, 01:52:08 AM by Duvid »

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #7 on: October 05, 2009, 02:20:23 AM »
I will try again to explain what is happening........ My default kernel 2.6.27.31.tex5, is the kernel to which my system will boot into if I let it go by itself or if I wait 5 seconds as per the first stanza

The first  boot menu gives me these choices:
                                                                                          PCLOS K3
                                                                                          Windows 7
                                                                                          2.6.24.7.tex1
                                                                                          PCLOS K4
                         
  If I click on PCLOS K4 it will bring me to a new boot menu with these choices

                                                                    PCLOS  K3
                                                                    PCLOS safe mode
                                                                    PCLOS K4

 I kept 2.6.24.7.tex1 as a backup kernel "security blanket" that I really haven't really been using. I commented it out as well as the texted version of the kernel the system is booting into to keep down the confusion.
 What I am trying to find out is there a way to go  KDE 4 without having two boot menus, such as when going to Windows 7. Is there a modification in my grub menu that would accomplish this. I don't know how the save default happened. I first installed PCLOS K4 on top of Win 7 using the bootloader from pclos onto the mbr of Win7. Then I installed PCLOS with K3 on another partition and used that bootloader and placed it on Windows mbr. My end results is what I have posted.
  Inspite of my method, I can still get into all the operating systems, just figured there was a better way than I had approached it.
 Hope this better explains the method to my madness

OK, that describes a normal chainloader stanza operation, but you have no such thing in the two menu.lst files you posted, nor do the boot menu entries match the entries you posted, so you must have another menu.lst somewhere that grub is reading from. That menu.lst is what we must see, or you need to change which menu.lst is to be the master.

There is no such thing as a Windows MBR or Linux MBR, there is just the MBR, and there are also boot sectors on each of your partitions where grub might be installed. Something is still missing from your description of events, as there is no correlation between the menu.lst files you posted and the boot menu entries you posted. Without proper details, we're still left in the dark as to what is actually happening.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #8 on: October 05, 2009, 10:24:27 AM »
  Good Morning OP and all that have helped in my post. As you may have noticed I was on this forum to early morning, so with a fresher brain, and coffee, I will try again to explain what I am trying to accomplish
    I have always liked reading your posts in the last 2 years that I have used PCLOS,the only linux I haved used, learned alot, but I might sometimes misuse the wording. I know to put grub in the windows partition,  (hd0,0) perhaps because I have dual booted many times for several reasons. I know you are the ultimate teacher, and will refine my knowledge at the end of the day, but I am  perplexed what more info I can give you.In this case I could understand and learn, by the solution observed, where I could dissect the end results.
   I did use a chainloader stanza for Windows ( stanza 5)only,and I thought I have explained how I got to where I am today. I first installed Windows, then PCLOS with K4, set up grub in  the Windows partition. Then I installed PCLOS K3 in another partition and set up grub in the Windows partition where the original grub was (hd0,0). What I forgot to mention Window7 was not recognized by grub ( a quirk with Win7) so I put the entry in by hand ( in both Boot Screens) and then it was recognized. The menu.lst that are from  boot > grub > menu.lst are the exact duplicates of what is found in each version KDE3 and KDE4. After the bios screen the computer goes to the first boot menu which gives me a choice of  each version of PCLOS with its respective KDE, an alternate kernel, and Windows7.
  Since I have PCLOS K3 as my default desktop, as it is called in PCC, I press enter usually, or wait 5 seconds. If I wish to go to KDE4 I scroll down to KDE4 which is at the bottom of the list. This brings me to a NEW boot menu with a choice of either PCLOS KDE versions, and Windows 7.
       Is it possible to go directly into PCLOS K4 from the first BOOT SCREEN ? I copied  KDE3 and KDE4 men.lst again below.

 This is my menu.lst from PCLOS KDE4

timeout 6
color black/cyan yellow/cyan
gfxmenu (hd0,7)/boot/gfxmenu
default 0

title PCLinuxOS KDE4
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_KDE4 root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img

title linux-nonfb
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,7)/boot/initrd.img

title failsafe
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a failsafe acpi=on
initrd (hd0,7)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title linux
kernel (hd0,7)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd.img

title 2.6.27.29.tex1
kernel (hd0,7)/boot/vmlinuz-2.6.27.29.tex1 BOOT_IMAGE=2.6.27.29.tex1 root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd-2.6.27.29.tex1.img

title 2.6.27.31.tex5
kernel (hd0,7)/boot/vmlinuz-2.6.27.31.tex5 BOOT_IMAGE=2.6.27.31.tex5 root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,7)/boot/initrd-2.6.27.31.tex5.img

      PCLOS KDE3 menu.lst

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title Windows7
root (hd0,0)
makeactive
chainloader +1

title 2.6.24.7.tex1
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.24.7.tex1 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot


title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
savedefault
boot


title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

#title 2.6.27.31.tex5
kernel (hd0,1)/boot/vmlinuz-2.6.27.31.tex5 BOOT_IMAGE=2.6.27.31.tex5 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd-2.6.27.31.tex5.img




« Last Edit: October 05, 2009, 01:48:39 PM by Duvid »

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #9 on: October 05, 2009, 02:42:08 PM »
 Good Morning OP and all that have helped in my post. As you may have noticed I was on this forum to early morning, so with a fresher brain, and coffee, I will try again to explain what I am trying to accomplish
    I have always liked reading your posts in the last 2 years that I have used PCLOS,the only linux I haved used, learned alot, but I might sometimes misuse the wording. I know to put grub in the windows partition,  (hd0,0) perhaps because I have dual booted many times for several reasons.

It's never proper to install grub to the Windows partition. Grub is installed to the MBR, or to the / partition of it's own installation.

Quote
I know you are the ultimate teacher, and will refine my knowledge at the end of the day, but I am  perplexed what more info I can give you.In this case I could understand and learn, by the solution observed, where I could dissect the end results.
   I did use a chainloader stanza for Windows ( stanza 5)only,and I thought I have explained how I got to where I am today. I first installed Windows, then PCLOS with K4, set up grub in  the Windows partition. Then I installed PCLOS K3 in another partition and set up grub in the Windows partition where the original grub was (hd0,0). What I forgot to mention Window7 was not recognized by grub ( a quirk with Win7) so I put the entry in by hand ( in both Boot Screens) and then it was recognized. The menu.lst that are from  boot > grub > menu.lst are the exact duplicates of what is found in each version KDE3 and KDE4. After the bios screen the computer goes to the first boot menu which gives me a choice of  each version of PCLOS with its respective KDE, an alternate kernel, and Windows7.
  Since I have PCLOS K3 as my default desktop, as it is called in PCC, I press enter usually, or wait 5 seconds. If I wish to go to KDE4 I scroll down to KDE4 which is at the bottom of the list. This brings me to a NEW boot menu with a choice of either PCLOS KDE versions, and Windows 7.
       Is it possible to go directly into PCLOS K4 from the first BOOT SCREEN ? I copied  KDE3 and KDE4 men.lst again below.

As I've said before, you are describing a chainloader entry between whatever you are booting with and the kde4 installation. We're not talking about the Windows chainloader, we're talking about the kde4 chainloader, and you aren't giving some pertinent fact.

Let me guess... You are using some kind or 3rd party bootloader that's causing all your problems, but you didn't want to mention it?

That's my only guess.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #10 on: October 05, 2009, 03:06:06 PM »
 The only bootloader I am using is from our distro that comes up at the end of each installation. Am I wrong in putting the bootloader onto (hd0,0) when there is Windows installed first, then our distro. I have always done it this way with no problems. This time I decided to add our distro with KDE4 and put its bootloader onto (hd0,0) again. It does work, only that it gives me 2 boot screens. I do not know how to explain any differently than I have tried, even after sleep and an ample amount of coffee.
   How would you recommend I approach installing Windows, and 2 versions of our distro. I am more than willing to redo my system, as I have a remaster of our distros, and a copy of Windows.
    My terabyte HD is partitioned as such:
  
   Windows   ntfs     45 gig
   pclos K3   ext3     root 15 gig   home 100 gig
   pclos K4   ext3      root 15 gig   home 30 gig ( used less- data kept on 700 gig partition)
   DATA        ext3     700 gig        use this partition for all my music, pictures, and large files. Shared with all operating systems.I tend to be a data hog, but I backup invaluable stuff to an external as well
   linux swap       2 gig
  
« Last Edit: October 05, 2009, 04:06:50 PM by Duvid »

Offline Gnarly

  • New Friend
  • *
  • Posts: 9
Re: Fixing A Tri Boot
« Reply #11 on: October 05, 2009, 03:29:17 PM »
I currently multiboot several linux distros and xp and win 7.  Windows wants to be on the first partition.   I have my Mepis grub installed in the mbr and then I chainload all the rest.  It is the only way I have ever done it.  If you can point grub to the correct kernel of what ever distro you are wanting to boot up im sure it will work.  But if the are any kernel updates I think you would have to go back and re-edit your menu.lst everytime that happens.  Yes with chainloading I basically see 2 grubs but i dont have to re-edit any of my menu.lst after kernel changes either.  If i where you I would just change the timeouts and or defaults to speed the selection along.
Good luck.

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #12 on: October 05, 2009, 03:32:02 PM »

 The only bootloader I am using is from our distro that comes up at the end of each installation. Am I wrong in putting the bootloader onto (hd0,0) when there is Windows installed first, then our distro. I have always done it this way with no problems. This time I decided to add our distro with KDE4 and put its bootloader onto (hd0,0) again. It does work, only that it gives me 2 boot screens. I do not know how to explain any differently than I have tried, even after sleep and an ample amount of coffee.

It is not correct to install grub to the Windows partition, as explained before. Grub is a bootloader and belongs in the MBR. For special types of booting it can be installed in the boot sector of the partition it is installed on, as a secondary chain bootloader.

Whether you want to believe it or not, you do have some other bootloader in the MBR, or you couldn't get the boot menu that differs from what's in your menu.lsts.

For a fresh start, boot into the KDE3.5 Open a root terminal and do the following;

Pressing the Enter key after each command is a given.

[root@localhost ~]# grub


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> root (hd0,1)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0)"...  15 sectors are embedded.
succeeded
 Running "install /boot/grub/stage1 (hd0) (hd0)1+15 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.

grub> quit

[root@localhost ~]#

At which point you now have grub installed in the MBR.

Reboot and try both the KDE3 and KDE4 entries, You may have to scroll down with the down arrow key to see the KDE4 entry.

If all is working, we can clean up your menu.lst entries later.
« Last Edit: October 05, 2009, 03:35:07 PM by old-polack »
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #13 on: October 05, 2009, 03:58:54 PM »
Thanks for staying with me on this topic. I booted into KDE3, opened a root terminal, typed grub,waited a few minutes and this is where the terminal remains. I am not sure what to do afterward or was something supposed to happen?

GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub>

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11688
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #14 on: October 05, 2009, 04:15:45 PM »
Thanks for staying with me on this topic. I booted into KDE3, opened a root terminal, typed grub,waited a few minutes and this is where the terminal remains. I am not sure what to do afterward or was something supposed to happen?

GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub>


It's waiting for you to enter the first command. Look at my previous post. The grub prompt is shown in blue. The command is in purple. Press the Enter key after each command.

You should see the same output after each command as is shown in that post. I reinstalled my grub to show you exactly what you will see, and what commands to use.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...