OK. I managed to work it out (eventually). I had somehow managed to get a non-ascii character in the '40_custom' based file in its parameters. This screwed up the planet.
The correct way to pass parameters to the kernel via grub2 for a specific menu item only IS to append them to the 'linux /boot/linux'... line. Sorted. Unrelated Grub2 observation 1: I also needed to be extra careful that none of grub2's '*_LINUX' directives clash. They kept silently adding 'quiet' which confused an idiot. Humpth.. seems odd.. *GFX*_LINUX options not showing up in /proc/cmdline, yet seem to have an effect. Wonder why that is? Oh-well, doesn't matter a jot to me. Unrelated Grub2 observation 2: I found vbeinfo to be completely unusable. On my mobo (with an i3 APU) the output was very long. The entries at the end of the list (the only ones I could see) were the least useful. I was too stupid to work out how to scroll back or to use a 'pager'. Nothing 'obvious' worked. Perhaps more people will have this problem in the future. Thanks for listening! --- > OK. I give up. I need help. > > How do I append an item to the linux kernel boot parameters > for *just*one* menu item in GRUB2? I want to have two > linux menu items. Same partition, same kernel, just with > different kernel command lines. > > GRUB_CMDLINE_LINUX doesn't help me since it applies to all > standard linux menu lines. > > I have created a new custom menu item based on 40_custom. > Text appended to its 'linux /boot/linux'... line does not > seem to get through. > > > The option I am trying to pass is > 'init=/sbin/special_init'. I want to run a non-default init > while retaining the ability to revert to the standard one. I > am obviously being stupid, but I just can't see how. > _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
