-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The following 40_custom in /etc/grub.d/ fixed the issue for me:
> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> menuentry "D-Testing-32 (on /dev/mmcblk0p1) custom" {
> set root='(hd0,msdos3)'
> linux /vmlinuz-3.16-3-686-pae root=/dev/mmcblk0p1
> initrd /initrd.img-3.16-3-686-pae
> }
I am quite pleased with this actually, this is enough success for me today.
As far as I understand things, the first set-root actually names the
/boot/-partition to
load the kernel and initrd from. It is not identical with the other root:
root=/dev/mmcblk0p1, which seems to name the filesystem-root that is used upon
loading
the kernel.
All I need to do now is make the custom entry the default to boot first
in /etc/default/grub and/or using grub-set-default.
I am going to remove other, non-workable entries pointing at mmcblk0p1 by
removing
the content of /boot/ on the SD-card, also see attachments.
I hope it will continue working upon the next kernel-update without manual
interference.
Probably it is worth, having another look at the scripts in /etc/grub.d/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlT23Z8ACgkQ5+rBHyUt5wuyIACgoSQgKd+/Hm2500yLOH3DFhqh
yzYAn0HoIx8stolo5xURDRabw1Kdli2t
=D2Hl
-----END PGP SIGNATURE-----
grub.cfg.xz
Description: application/xz
40_custom.xz
Description: application/xz
