View previous topic :: View next topic |
Author |
Message |
aceFruchtsaft Guru
Joined: 16 May 2004 Posts: 438 Location: Vienna, Austria
|
Posted: Mon Jun 13, 2011 9:21 am Post subject: KDM + grub + reboot into specific OS not working |
|
|
I'm wondering whether anyone has a working installation where you can select into which OS to reboot to with KDE/KDM 4.6.4 and grub 0.97.
I have selected "grub" as the boot manager in the KDM config, but still I see no list of OS's in the reboot dialog.
It works on my openSUSE installation on different hardware though, with exactly the same package versions and no discernible differences in configuration.
Does it work for you, and if so, how did you get it working?
Thanks. |
|
Back to top |
|
|
SLBMEH Apprentice
Joined: 16 Aug 2003 Posts: 299 Location: Pittsburgh, PA
|
Posted: Thu Jun 23, 2011 10:54 am Post subject: |
|
|
Never tried to configure it. Would it require access to your menu.lst? Is your /boot on a separate partition? Does that mount at boot time? _________________ Steve - Semper Fi |
|
Back to top |
|
|
aceFruchtsaft Guru
Joined: 16 May 2004 Posts: 438 Location: Vienna, Austria
|
Posted: Sat Jun 25, 2011 10:44 am Post subject: |
|
|
Pretty good suggestion, as this was indeed the case an I would think that an accessible menu.lst is a necessary condition for this to work at all. However, now that I've fixed this there are still no reboot options shown, so something else is also missing.
But thanks anyway!
// Edit: Looking further into this, it seems that suse has a grubonce executable which allows it to boot a specific OS once. I guess this is called by KDM. Gentoo neither has grubonce nor grub-reboot, so I guess this is the reason it does not work. |
|
Back to top |
|
|
Spidey Apprentice
Joined: 07 Sep 2006 Posts: 269
|
Posted: Sun Jul 10, 2011 12:35 am Post subject: |
|
|
There is a grub-set-default binary, that sets the last "saved default" on grub. On you grub.conf or menu.lst, you have to use the "default saved" command, so that KDM can correctly set your next OS after boot.
But the problem is that the menu isn't even show, right? |
|
Back to top |
|
|
wrc1944 Advocate
Joined: 15 Aug 2002 Posts: 3435 Location: Gainesville, Florida
|
Posted: Sun Jul 10, 2011 12:44 pm Post subject: |
|
|
I always use grub legacy (0.97) from my Gentoo installations to boot into other distros (whether they are grub 2, or legacy grub), which works fine.
For me, grub 2 and UUID's is a PITA, and overkill, plus I've never figured out reliable a way to chainload from grub2 into a legacy grub distro. For that reason, I find it much simpler to use grub legacy for the controlling grub.
You only use the kernel /boot/grub/core.img and savedefault lines to chainload into grub 2 distros, where their own grub is installed on their own root partition.
In the case the chainloading into other distros doesn't work, and you're SURE you have no typos or wrong stanza entries, you can try reinstalling their grub (the one you are trying to chainload into), or as a last resort create a stanza in your Gentoo controlling grub pointing to the specific kernel and partition found in the other distro's grub.conf, grub.cfg, or menu.lst file. If need be, you can mount the other distro's partition from Gentoo, and check its grub file so you can put the correct entry in your gentoo controlling grub file.
Here's one of my grub.conf files. Use the format shown for Linux Mint if the distro you wish to chainload into is using grub2, otherwise use the short legacy format for 0.97 distros. If you don't have a grub.conf, create one and reinstall grub legacy on your Gentoo distro that you are using for your controlling grub. Need to get that grub working correctly first, before setting up the chainloader stanzas for other distros.
Code: | # This is a sample grub.conf for use with Genkernel, per the Gentoo handbook
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=10#doc_chap2
# If you are not using Genkernel and you need help creating this file, you
# should consult the handbook. Alternatively, consult the grub.conf.sample that
# is included with the Grub documentation.
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Gentoo Linux 3.0.0-rc4 32bit kde-4.6.4
root (hd0,0)
kernel /boot/3.0.0-rc4 root=/dev/sda1 rootflags=commit=5 acpi_enforce_resources=lax
title Gentoo Linux 2.6.39-ck1 32bit kde-4.6.4
root (hd0,0)
kernel /boot/2.6.39-ck1 root=/dev/sda1 rootflags=commit=5 acpi_enforce_resources=lax
title Gentoo Linux 2.6.39 Cgroups & KMS 32bit kde-4.6.4
root (hd0,0)
kernel /boot/2.6.39 root=/dev/sda1 rootflags=commit=5 acpi_enforce_resources=lax
title Gentoo-Audio 32-bit Cgoups & KMS Chainloader
rootnoverify (hd0,5)
chainloader +1
title Gentoo-amd64 multilib kde-testing + Cgoups & KMS Chainloader
rootnoverify (hd0,10)
chainloader +1
title Linux Mint11 32-bit Chainloader
root (hd0,4)
kernel /boot/grub/core.img
savedefault
boot
title Ubuntu-Studio Chainloader
root (hd0,9)
kernel /boot/grub/core.img
savedefault
boot
title Pclos 32-bit Chainloader
rootnoverify (hd0,6)
chainloader +1
title Mandriva Cooker Chainloader amd64
rootnoverify (hd0,7)
chainloader +1
title Arch Linux Chainloader amd64
rootnoverify (hd0,8)
chainloader +1 |
BTW, remember that for example in grub2, hd0,4 is really sda4, and not sda5 as in grub legacy. However, you still use the legacy numbering scheme in legacy grub.conf files, but the grub2 file it's pointing to will use the new scheme, i.e. hd0,4 is really sda4.
In other words, to chainload to a grub2 distro's grub in the sda4 partition where in grub2 it's referred to as hd0,4 in grub.cfg, you still would use hd0,3 in your controlling grub legacy stanza. _________________ Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11 |
|
Back to top |
|
|
Randy Andy Veteran
Joined: 19 Jun 2007 Posts: 1148 Location: /dev/koelsch
|
Posted: Tue Jul 12, 2011 11:08 am Post subject: |
|
|
Hi Folks.
Today i stumbled on this website which shows (visualize the menue enty) the grub2 support of KDM, as mentioned above.
For anyone who are interested how it looks like: http://ksmanis.wordpress.com/2011/04/21/hello-planet-and-grub2-support-for-kdm/
No, i'm not a Fan of grub2. I prefer grub legacy too.
Regards, Andy. _________________ If you want to see a Distro done right, compile it yourself! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|