Yeah, good point. I see it when I look at any other booted OS. You are thinking that my grub-mkimage may be missing some key module? I guess that makes sense. I can try that.
I still don't get the difference between grub-mkimage and grub-mkstandalone... On Mon, May 23, 2016 at 8:26 PM, Andrei Borzenkov <[email protected]> wrote: > 20.05.2016 07:43, Avi Deitcher пишет: > > cat /proc/cmdline is empty. > > > > With GRUB command line cannot be empty. It always adds at least > BOOT_IMAGE=/path/to/kernel as the very first parameter. > > ... hmm ... you build custom image with limited selection of modules. It > is possible that some required module is missing but grub skips over > this and continues. Please test with grub-mkrescue first - it created > bootable ISO which contains full grub. > > Using current GIT master (or at least 2.02~beat3) would be additional > bonus. > > > On Friday, May 20, 2016, Andrei Borzenkov <[email protected]> wrote: > > > >> > >>> To keep this thread simple, I set up a gist with the grub.cfg, mkimage, > >> and > >>> build. > >>> > >>> https://gist.github.com/deitch/260bb94ecf7932cb83bdf7024099fdb5 > >>> > >>> Any ideas? > >> > >> Not really. How do you check for kernel params? What is in > /proc/cmdline? > >> > > > > > > -- Avi Deitcher [email protected] Follow me http://twitter.com/avideitcher Read me http://blog.atomicinc.com _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
