[opensuse] Yast & Grub bootloader different.
Hello SuSE people, No answer on my last request so I'll state the problem differently this time. My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why? How can I fix it ? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On November 25, 2008 08:52:52 pm Bob S wrote:
Hello SuSE people,
No answer on my last request so I'll state the problem differently this time.
My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why? How can I fix it ?
Bob S
As I recall you have several versions of suse installed. I would guess that grub is reading the files from one of those other installations instead of the one you are modifying/looking at in YaST. You can read those files (either mount the appropriate partition and look at them that way or simply boot into those installations and have a look using YaST) to see if that is the case. If so, I believe you can change which one of these grub configurations gets used (I'm not clear on the details how however) or modify the grub files that *are* getting used to meet your requirements. Of course this could be all wrong, but you didn't get any responses the first time so a guess can't hurt. -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSE people,
No answer on my last request so I'll state the problem differently this time.
My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why? How can I fix it ?
Bob S
Post: cat /proc/partitions cat /boot/grub/menu.lst cat /etc/fstab This will give us some idea of what your current install is seeing and potentially what else is there to be booted. It will allow for a much more educated guess. -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSE people,
No answer on my last request so I'll state the problem differently this time.
My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why? How can I fix it ?
Bob S
OK, Now I found the first part: <quote> Hello SuSE people, I haave three different versions of SuSE and each containing at least two different kernels. Ijust added a jen kernel to 10.3 and 11.0. I checked the menu.lst file for each distro and they are correct. Going into Yast bootloader all of my desired options are there. Trouble is, that when I reboot the menu doesn't have half the options it shows in Yast. Am I doing something wrong? Bob S </quote> Bob, Same answer, send the info requested in my first reply so we can be sure, but here is what I suspect is going on. First you have more than one /boot partition. (probably one for each version -- which is 100% OK). Grub, or any boot loader for that matter, can only operate on one /boot partition at a time and only one is the primary /boot partition called after the BIOS passes control to the boot loader. (somebody has got to be first -- Right?) To boot all of your operating systems, grub, for lack of better words, daisey chains the various /boot partitions together. It starts with which ever one is configured to get control first and then, if it isn't booting the OS associated with that /boot partition, grub will pass control to the next /boot partition associated with the menu entry you chose from the first menu. Basically: BIOS passes control to the first /boot partition | | [grub: 1st /boot menu] | boot my OS? -- yes --> load the OS | no, pass control to next /boot | [grub: next /boot menu] | boot my OS? -- yes --> load the 2nd OS | no, pass control to next /boot | [grub: next /boot menu] and so on.... At any stage in the game, you are only going to see the menu entries associated with the /boot/grub/menu.lst file that is on the /boot partition that has control. Grub doesn't scour the all hard drives on each install collecting menu entries from every boot partition it finds. It just installs, configures it self to boot the OS it is installing and then creates an entry to point to the /boot partition that was primary before the current install. So, what I bet happened in your case is that, whatever your last installed OS was, you are looking at the "menu" created by the yast installer that sits on the /boot partition for that install. You don't see all the choices on every menu because you are only looking at the --- last installed --- menu. The other /boot partitions have their own "menu" and when control is passed to them, you will see the remaining choices. That also explains why when you boot to another of your OS's and check the grub menu with Yast, you will see all of your choices for each install. It's normal, at first perplexing, but normal none the least. If you want to go check each one individually from any of your OS's, since you have individual /boot partitions, it's pretty easy to do. First, just do a: cat /proc/partitions Now just look at the sizes. When the installer creates separate boot partitions, it usually creates them approximately 75Meg in size. So just note the /dev/hdc2 or whatever device name is associated with the 75 meg partitions and create mount points (as root), say: mkdir /mnt/boot1 mkdir /mnt/boot2 .. and so on Then mount the boot partitions there (also as root) and take a look: ** using hdc2 and hdd2 as examples of the 75 meg partitions.. mount /dev/hdc2 /mnt/boot1 mount /dev/hdd2 /mnt/boo2 And confirm: cat /mnt/boot1/boot/grub/menu.lst cat /mnt/boot2/boot/grub/menu.lst Then to unmount them, just use umount: umount /mnt/boot1 umount /mnt/boot2 You only hope and pray that the last installed OS configured grub properly to pass control to the previous install correctly. Otherwise, things get real interesting. Throw fake RAID in there and it gets down-right fun: https://bugzilla.novell.com/show_bug.cgi?id=445602 -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 26 November 2008 02:45:03 am David C. Rankin wrote:
Bob S wrote:
Hello SuSE people,
No answer on my last request so I'll state the problem differently this time.
My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why? How can I fix it ?
Bob S
OK,
Now I found the first part:
<quote>
Hello SuSE people,
I haave three different versions of SuSE and each containing at least two different kernels. Ijust added a jen kernel to 10.3 and 11.0. I checked the menu.lst file for each distro and they are correct. Going into Yast bootloader all of my desired options are there.
Trouble is, that when I reboot the menu doesn't have half the options it shows in Yast. Am I doing something wrong?
Bob S
</quote>
Bob,
Same answer, send the info requested in my first reply so we can be sure,
OK David, here you go but you will need some explanation as to what you see. bob@Easystreet:~> cat /proc/partitions major minor #blocks name 8 0 78150744 sda 8 1 5116671 sda1 8 2 26218080 sda2 8 3 26218080 sda3 8 4 1 sda4 8 5 10490413 sda5 8 6 5245191 sda6 8 7 4851598 sda7 8 16 29316672 sdb 8 17 10241406 sdb1 8 18 14972580 sdb2 8 19 2048287 sdb3 8 20 2048287 sdb4 8 32 244198584 sdc 8 33 10490413 sdc1 8 34 15735667 sdc2 8 35 2104515 sdc3 8 36 1 sdc4 8 37 5245191 sdc5 8 38 5245191 sdc6 8 39 10490413 sdc7 8 40 15735636 sdc8 8 41 15735636 sdc9 8 42 10490413 sdc10 8 43 10490413 sdc11 8 44 10490413 sdc12 bob@Easystreet:~> As you can see, I do not use separate /boot partitions. bob@Easystreet:~> cat /boot/grub/menu.lst cat: /boot/grub/menu.lst: Permission denied bob@Easystreet:~> cat /etc/fstab LABEL=11.0 /11.0 ext3 acl,user_xattr 1 2 LABEL=11.0tmp /11.0tmp ext3 acl,user_xattr 1 2 LABEL=11.0var /11.0var ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part3 swap swap defaults 0 0 LABEL=10.3 / ext3 defaults 1 1 LABEL=11.0home /11.0home ext3 defaults 1 2 LABEL=backup /backup ext3 defaults 1 2 LABEL=datastorage /datastorage ext3 defaults 1 2 /dev/sdc7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 LABEL=10.3home /home ext3 defaults 1 2 LABEL=mediadata /mediadata ext3 defaults 1 2 LABEL=storage /stoarge ext3 defaults 1 2 LABEL=10.3tmp /tmp ext3 defaults 1 2 LABEL=10.3usr /usr ext3 defaults 1 2 LABEL=10.3var /var ext3 defaults 1 2 /dev/sda1 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0 LABEL=workspace /workspace ext3 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 LABEL=10.2 /10.2 ext3 defaults 1 2 LABEL=10.2home /10.2home ext3 defaults 1 0 LABEL=10.2var /10.2var ext3 defaults 1 0 usbfs /proc/bus/usb usbfs noauto 0 0 LABEL=10.2tmp /10.2tmp ext3 defaults 1 0 bob@Easystreet:~> As you can see, I mount all of my active partitions which allows me to jump back and forth between the distros to look at and/or change things. Easystreet:/ # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sun Nov 23 23:16:46 EST 2008 default 1 timeout 8 gfxmenu (hd2,7)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Regular -- openSUSE 11.0 - 2.6.25.7-jen67 root (hd2,7) kernel /boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/11.0 resume=/dev/sdc3 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.25.7-jen67-regular ###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3 root (hd2,7) kernel /boot/vmlinuz-2.6.22.18-0.2-default root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.22.18-0.2-default ###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3-jen root (hd2,7) kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.25.7-jen67-regular ###Don't change this comment - YaST2 identifier: Original name: linux-2.6.25.11-0.1-default### title openSUSE 11.0 - 2.6.25.11-0.1 root (hd2,7) kernel /boot/vmlinuz-2.6.25.11-0.1-default root=/dev/disk/by-label/11.0 resume=/dev/sdc3 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.25.11-0.1-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.0 - 2.6.25.11-0.1 root (hd2,7) kernel /boot/vmlinuz-2.6.25.11-0.1-default root=/dev/disk/by-label/11.0 showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe vga=0x31a initrd /boot/initrd-2.6.25.11-0.1-default ###Don't change this comment - YaST2 identifier: Original name: linux-2.6.18.2-34-default### title openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/disk/by-label/10.2 resume=/dev/sdc3 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd2,7) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd2,7) chainloader (hd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.2 root (hd2,0) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/disk/by-label/10.2 showopts ide=nodma apm=off acpi=off noresume edd=off 3 vga=normal initrd /boot/initrd-2.6.18.2-34-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd2,7) kernel /boot/vmlinuz-2.6.22.18-0.2-default root=/dev/disk/by-label/10.3 showopts ide=nodma apm=off acpi=off noresume edd=off 3 initrd /boot/initrd-2.6.22.18-0.2-default title Kernel-2.6.18.8-0.10-default root (hd2,0) kernel /boot/vmlinuz-2.6.18.8-0.10-default root=/dev/disk/by-label/10.2 resume=/dev/sdc3 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.18.8-0.10-default Easystreet:/ # This is the menu that shows up in Yast. It is correct, but ios not the one that shows up on the logon screen aat boot time.
but here is what I suspect is going on. First you have more than one /boot partition. (probably one for each version -- which is 100% OK). Grub, or any boot loader for that matter, can only operate on one /boot partition at a time and only one is the primary /boot partition called after the BIOS passes control to the boot loader. (somebody has got to be first -- Right?)
Right
To boot all of your operating systems, grub, for lack of better words, daisey chains the various /boot partitions together. It starts with which ever one is configured to get control first and then, if it isn't booting the OS associated with that /boot partition, grub will pass control to the next /boot partition associated with the menu entry you chose from the first menu.
Welllll....yes, but as in the menu.lst shown above Grub is directed where to go. Correct me if I am wrong.
Basically:
...<Cut explanation>....
At any stage in the game, you are only going to see the menu entries associated with the /boot/grub/menu.lst file that is on the /boot partition that has control. Grub doesn't scour the all hard drives on each install collecting menu entries from every boot partition it finds. It just installs, configures it self to boot the OS it is installing and then creates an entry to point to the /boot partition that was primary before the current install.
Theortically, I suppose that is correct, but I have never seen Grub come up with a correct menu.lst; You must instruct it to go look and half the time it doesn't find everything and I end up editing by hand. Maybe because of the way I have set everything up. But, I never had trouble making it work properly until now. I just don't know where the menu at boot up time is coming from.
So, what I bet happened in your case is that, whatever your last installed OS was, you are looking at the "menu" created by the yast installer that sits on the /boot partition for that install.
No, you would probably lose that bet because the last install was 11.0 and the menu.lst for 11.0 is not like the menu that comes up at boot time.
You don't see all the choices on every menu because you are only looking at the --- last installed --- menu. The other /boot partitions have their own "menu" and when control is passed to them, you will see the remaining choices.
If you mean that cliccking on another OS in the primary menu.lst that it would bring up another menu.lst for that OS then you would be correct. That used to happen for 10.0, 10.1, and 10.2 after I switched from LILO.
That also explains why when you boot to another of your OS's and check the grub menu with Yast, you will see all of your choices for each install. It's normal, at first perplexing, but normal none the least.
Wellll...I guess that is correct. I never had reason to check the boot loader for each individual OS because it worked properly. After a new OS was installed and I clicked on an older OS it would bring up the older menu.lst where I would again make my choice.
If you want to go check each one individually from any of your OS's, since you have individual /boot partitions, it's pretty easy to do. First, just do a:
cat /proc/partitions
.....
You only hope and pray that the last installed OS configured grub properly to pass control to the previous install correctly. Otherwise, things get real interesting. Throw fake RAID in there and it gets down-right fun:
Don' have RAID but I guess 11.0 didn't hear my prayers. Need to find out why the menu that comes up at boot time is not the proper one and doesn't emulate any of the installedOS's and/or why it's behavior is not as previously. I guess that I just can't grasp how Grub works. Supposed to be simple, rright? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2008-11-28 at 00:25 -0500, Bob S wrote: ...
I just don't know where the menu at boot up time is coming from.
Just edit the first entry on each different menu.lst file, so that you know which is which. By the way, this entry: title To grub in hda8 root (hd0,7) configfile /boot/grub/menu.lst passes control to another grub. When I install another suse, I don't let it take control of grub. I tell it to install grub on its root partition instead. Only one of the linuxes I tell it to install grub in the MBR, and that grub is the master one, and this one has entries to boot the different grub menus of each install. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkv3UYACgkQtTMYHG2NR9Uc+QCgjE7drB2IZXvmbiqMJPamdJjU K+AAoIqtOzJTmHdw8Q8oeUGbddpyyoPA =AeoB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 28 November 2008 06:59:55 am Carlos E. R. wrote:
On Friday, 2008-11-28 at 00:25 -0500, Bob S wrote:
I just don't know where the menu at boot up time is coming from.
Just edit the first entry on each different menu.lst file, so that you know which is which.
You mean the "title"name? Sorry Carlos, I am a little confused.
By the way, this entry:
title To grub in hda8 root (hd0,7) configfile /boot/grub/menu.lst
Ummm..where is that? But it really doesn't matter, and I don't need to edit it because you are telling me that on a new install don't let that happen?
passes control to another grub. When I install another suse, I don't let it take control of grub. I tell it to install grub on its root partition instead. Only one of the linuxes I tell it to install grub in the MBR, and that grub is the master one, and this one has entries to boot the different grub menus of each install.
So you are telling me that you have the one master grub menu and when you click on another OS it brings up a replacement menu for the OS that you selected? And if that is correct, what do you do? Edit the "master" by hand to get the new OS on it? And to solve my immediate problem I just need to select a menu as the "master" and write it to the MBR? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2008-11-28 at 23:09 -0500, Bob S wrote:
Just edit the first entry on each different menu.lst file, so that you know which is which.
You mean the "title"name? Sorry Carlos, I am a little confused.
Yes, the tittle of the first entry. Pity there is no main title. You could change the background picture, though.
By the way, this entry:
title To grub in hda8 root (hd0,7) configfile /boot/grub/menu.lst
Ummm..where is that?
In my grub :-) It's an example of what I do.
passes control to another grub. When I install another suse, I don't let it take control of grub. I tell it to install grub on its root partition instead. Only one of the linuxes I tell it to install grub in the MBR, and that grub is the master one, and this one has entries to boot the different grub menus of each install.
So you are telling me that you have the one master grub menu and when you click on another OS it brings up a replacement menu for the OS that you selected? And if that is correct, what do you do? Edit the "master" by hand to get the new OS on it?
Correct, that's what I do. I edit it by hand. It happens to be also the grub menu of one of the installs, so YaST can touch it, too. No problem.
And to solve my immediate problem I just need to select a menu as the "master" and write it to the MBR?
It is probably the least confusing :-) Yes, only one can be in the MBR, the rest have to be on the respective main partition of each install. And you have to keep track of them, in paper perhaps :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkxUj4ACgkQtTMYHG2NR9XWoACZAQRXpZuGBZ4VK4uyaRlkNGgV 0qwAniinWsvK9uWYW8cpOTpvPTQh8+iN =cII6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On November 27, 2008 10:25:24 pm Bob S wrote:
I haave three different versions of SuSE and each containing at least two different kernels. Ijust added a jen kernel to 10.3 and 11.0. I checked the menu.lst file for each distro and they are correct. Going into Yast bootloader all of my desired options are there.
Trouble is, that when I reboot the menu doesn't have half the options it shows in Yast. Am I doing something wrong?
Just to be clear, What shows up when you boot does not match *any* of the menu.lst entries you have, correct? < snip >
Easystreet:/ # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sun Nov 23 23:16:46 EST 2008
< snip >
###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3-jen root (hd2,7) kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.25.7-jen67-regular
"kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular" ? Is that really correct? Shouldn't that just be kernel /boot/vmlinuz-2.6.25.7-jen67-regular -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 28 November 2008 06:34:24 am Don Raboud wrote:
kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.25.7-jen67-regular
"kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular" ?
Looks like too much of copy-paste from file manager (Konqueror?) to YaST Bootloader. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 28 November 2008 11:59:43 am Rajko M. wrote:
On Friday 28 November 2008 06:34:24 am Don Raboud wrote:
kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.25.7-jen67-regular
"kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular" ?
Looks like too much of copy-paste from file manager (Konqueror?) to YaST Bootloader.
Thanks Rajko. You could be right. But I copied from menu.lst to menu.lst. Hmmm,,,,? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 28 November 2008 07:34:24 am Don Raboud wrote:
On November 27, 2008 10:25:24 pm Bob S wrote:
I haave three different versions of SuSE and each containing at least two different kernels. Ijust added a jen kernel to 10.3 and 11.0. I checked the menu.lst file for each distro and they are correct. Going into Yast bootloader all of my desired options are there.
Trouble is, that when I reboot the menu doesn't have half the options it shows in Yast. Am I doing something wrong?
Just to be clear, What shows up when you boot does not match *any* of the menu.lst entries you have, correct?
< snip >
Hello Don, thanks for more input. You got me thinking and checking and scratching my head and comparing line by line. Seems that the menu presented at boot is the menu for 11.0. Excuse the confusion from the doddering old guy. At least that is settled.
Easystreet:/ # cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Sun Nov 23 23:16:46 EST 2008
< snip >
###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3-jen root (hd2,7) kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.25.7-jen67-regular
"kernel /boot/file:/boot/vmlinuz-2.6.25.7-jen67-regular" ?
Is that really correct? Shouldn't that just be
kernel /boot/vmlinuz-2.6.25.7-jen67-regular
No that is not really correct. Thanks for catching that for me. That would have been another head scratcher. Didn't matter at this point because that menu wasn't being used. Now remains the problem of getting the proper menu used. (The 10.3 one instead of the 11.0 one) Do you know? Gonna have to check with Carlos for a little clarification on what he does. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On November 28, 2008 08:35:42 pm Bob S wrote:
Seems that the menu presented at boot is the menu for 11.0. Excuse the confusion from the doddering old guy. At least that is settled.
Glad to hear it.
Now remains the problem of getting the proper menu used. (The 10.3 one instead of the 11.0 one) Do you know?
One approach is just to modify the menu.list file now that you know which one is being booted. That should work, even if it is not very satisfying. Since you are currently booting into 11.0, I think that is where you should make changes. Check YaST->System->Boot Loader and look around. Under the Boot Loader Installation you can select a custom boot partiton. If you point that to your 10.3 root partition I *think* that should achieve what you want. That at least is my understanding of how that particular setting should work. I haven't tested it, so ...
Gonna have to check with Carlos for a little clarification on what he does.
I'm sure that is an excellent idea. -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2008/11/25 22:52 (GMT-0500) Bob S composed:
My Grub bootup menu is different ( many less entries) than the bootloader menu as shown in Yast. Why?
Because the one you see in YaST is not the one being used for boot. Your last install probably installed its Grub to its / partition, leaving a Grub from another installation actually in control.
How can I fix it ?
Several ways: 1 - find the one actually being used, and modify it with your favorite text editor to include whatever it lacks that you wish it to include. 2 - exit the menu, then use the Grub command line to boot the OS you wish used, then cause its Grub to replace the one actually being used. 3 - other, which depends on knowing what is actually installed where. Give us the output from fdisk -l, augmented with descriptions what is installed where. -- "Love is not easily angered. Love does not demand its own way." 1 Corinthians 13:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Bob S
-
Carlos E. R.
-
David C. Rankin
-
Don Raboud
-
Felix Miata
-
Rajko M.