Bug #445367 seems like a duplicate of this. As described there,
/etc/grub.d/30_os-prober ignores boot partition reported by os-prober.
/usr/lib/linux-boot-probes/mounted/40grub and /usr/lib/linux-boot-
probes/mounted/40grub2 are the files prepending the /boot to linux
kernel/initrd lines.
--
As a temporary workaround (that only works with setups similar to mine,
since the test for separate /boot is simply wrong) I changed 30_os-
prober as follows:
--- 30_os-prober.orig 2009-11-01 13:26:40.787934691 +0200
+++ 30_os-prober2009-11-01 13:27:21.897932968 +0200
@@ -128,6 +128,11
Or maybe that bug I mentioned above is separate one. But both seem to be
symptoms of missing/broken support for separate /boot -partitions for
kernels found by os-prober.
Also my workaround above doesn't work as-is, so please ignore it.
Since bug db isn't a discussion forum, guess I'll shut up
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
grub not adding correct uuid to grub.cfg
https://bugs.launchpad.net/bugs/392836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am running a system with 1 IDE drive (Intrepid), 1 SATA (Windows XP),
1 SATA (Jaunty) and 1 USB external drive which I am using to test
Karmic. The Windows drive has the Windows MBR and all others have GRUB
with the USB drive having GRUB2. The Jaunty drive also has a separate
Boot partition.
You have to change the UUID in 'root=UUID=89c07ebd-cc8e-4d65-be8d-
e4db7fbfef06 ro quiet splash' to match your Jaunty's UUID. But every
time, your kernel in Karmic gets updated and the grub.cfg is updated as
well, this setting gets lost and is overwritten with Karmic's UUID.
--
grub not adding
Problems here with double boot configuration.
Running Jaunty perfectly (/root at secondary hd0,8). Installed Karmic Beta
(sept/29) at primary partition (hd0,0). Could not boot after install. Still
unable to find out why, (perhaps it did not like my grub[1] at [hd0,8]?). Reset
Grub to previous
Same here, Karmic Alpha 6. I didn't have any problems/errors intalling
Karmic, but in the grub.cfg the uuid for Jaunty was set to Karmic's
uuid. When I updated Karmic today, the manually corrected entry was
overwritten with the wrong uuid again.
--
grub not adding correct uuid to grub.cfg
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
--
grub not adding correct uuid to grub.cfg
https://bugs.launchpad.net/bugs/392836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Steve Langasek wrote:
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
Hi, would it help to see the menu.cfg from Kubuntu Karmic using grub2
and the menu.lst from Kubuntu Jaunty using grub?
I highlighted the problem in red
10 matches
Mail list logo
