FS#43438 - grub-mkconfig fails to place kernel image in added system in multiboot (grub 1:2.02.beta2-5)

Attached to Project: Arch Linux
Opened by Larry Johnson (keepitsimpleengineer) - Tuesday, 13 January 2015, 19:43 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 16 January 2015, 00:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: when producing /boot/grub/grub.cfg in a system with intel cpu and multiple linux systems, the kernel image is not included in the initrd line of grub.cfg for systems other than the system where "grub-mkconfig -o /boot/grub/grub.cfg" is run.

Additional info:
* package version(s) grub 1:2.02.beta2-5
* config and/or log files etc.

Steps to reproduce:
[root@KISE-007 ~]# pacman -Qe grub
grub 1:2.02.beta2-5
[root@KISE-007 ~]# pacman -Qe intel-ucode
intel-ucode 20140913-1
[root@KISE-007 ~]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found Intel Microcode image
Found linux image: /boot/vmlinuz-linux-ck
Found initrd image: /boot/initramfs-linux-ck.img
Found fallback initramfs image: /boot/initramfs-linux-ck-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found fallback initramfs image: /boot/initramfs-linux-fallback.img
Found Manjaro Linux (0.8.11) on /dev/sda1
done
[root@KISE-007 ~]# cat /boot/grub/grub.cfg | grep initrd
initrd /boot/intel-ucode.img /boot/initramfs-linux-ck.img
initrd /boot/intel-ucode.img /boot/initramfs-linux-ck-fallback.img
initrd /boot/intel-ucode.img /boot/initramfs-linux-ck-fallback.img
initrd /boot/intel-ucode.img /boot/initramfs-linux.img
initrd /boot/intel-ucode.img /boot/initramfs-linux-fallback.img
initrd /boot/intel-ucode.img /boot/initramfs-linux-fallback.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
initrd /boot/intel-ucode.img
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 16 January 2015, 00:20 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#43254 
Comment by Larry Johnson (keepitsimpleengineer) - Tuesday, 13 January 2015, 19:48 GMT
Also see https://bugs.archlinux.org/task/43254?string=os-prober&project=0&search_name=&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=
   grub.cfg (15 KiB)
Comment by Doug Newgard (Scimmia) - Tuesday, 13 January 2015, 22:22 GMT
I'm confused. Why would the kernel image be placed in the initrd line?
Comment by Larry Johnson (keepitsimpleengineer) - Wednesday, 14 January 2015, 17:40 GMT
@Scimmia To use the latest Intel microcode for their CPU, it must be placed there so it will be loaded when the system boots, see
https://wiki.archlinux.org/index.php/Microcode#Grub
Comment by Doug Newgard (Scimmia) - Thursday, 15 January 2015, 02:21 GMT
That link has nothing to do with the kernel image.

I think I see where we went off track here. You're not talking about the kernel image at all, you're talking about the initrd created by mkinitcpio, correct? If so, isn't this the same as  FS#43254  that you linked to?
Comment by Larry Johnson (keepitsimpleengineer) - Thursday, 15 January 2015, 17:20 GMT
@Scimmia Yes it is the same, but that has been patched for use in manjaro.

My error, this is for architecture i686, my error in reporting.

There is a similar but not identical bug for architecture x86_64 reported in  FS#43461 
Comment by Larry Johnson (keepitsimpleengineer) - Thursday, 15 January 2015, 17:26 GMT
grug.cfg for x86_64
   grub.cfg (21.9 KiB)

Loading...