01-16-2016, 02:48 PM
(This post was last modified: 01-16-2016, 03:13 PM by br1anstorm.)
Okay..... next episode.
Went into LL root, found and re-copied the entry, then re-pasted it via the Mint terminal into the Mint Grub boot menu. Seemed to work this time.
So I then did the "sudo update-grub" in the Mint terminal; and this is what I got in the terminal screen.
I'm posting this before I reboot, so I don't know what, if any, change or update has actually happened in Mint's Grub boot menu. I guess I will discover any change after I reboot. But I do wonder, and worry, about whatever the "syntax error at line 386" and "in the generated Grub config file" might be.
Are these a consequence of the peculiarities or tweaking of the design of the LL Grub, I wonder, and an example of the 'not playing nicely' problem?
EDIT/UPDATE: Well, didn't take long to find out the result. Rebooted, got to Mint's Grub screen, and...... no change. The listing of options (Mint, recovery mode, memtest, Win7 etc) all exactly the same as before. No trace of Linux Lite as an additional option. So the alternative route of inserting LL into Mint's Grub, seems not to have worked, which is a pity. But what puzzles me is why it worked for austin.texas (who suggested it) and isn't working for me. The "syntax error" must surely be part of the reason?
Just in case it helps with the detective work, once I had rebooted into Mint I went into the file manager and had a look into its /boot/grub. In there I noticed two grub (menu?) files, grub.cfg and grub.cfg.new. The latter was modified today. ......and it includes the Linux Lite entry - in fact more than one. And line 386 in that cfg.new file is actually the very last line, not a part of the body of the LL entry. I have no idea what this means....! I can copy and paste the whole of that grub.cfg.new file if that would help to figure out the error.
Went into LL root, found and re-copied the entry, then re-pasted it via the Mint terminal into the Mint Grub boot menu. Seemed to work this time.
So I then did the "sudo update-grub" in the Mint terminal; and this is what I got in the terminal screen.
Quote:Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.19.0-32-generic
Found initrd image: /boot/initrd.img-3.19.0-32-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
No volume groups found
Found Windows 7 (loader) on /dev/sda1
Found Windows Recovery Environment (loader) on /dev/sda4
Found Linux Lite 2.6 (14.04) on /dev/sda7
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 386
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done
I'm posting this before I reboot, so I don't know what, if any, change or update has actually happened in Mint's Grub boot menu. I guess I will discover any change after I reboot. But I do wonder, and worry, about whatever the "syntax error at line 386" and "in the generated Grub config file" might be.
Are these a consequence of the peculiarities or tweaking of the design of the LL Grub, I wonder, and an example of the 'not playing nicely' problem?
EDIT/UPDATE: Well, didn't take long to find out the result. Rebooted, got to Mint's Grub screen, and...... no change. The listing of options (Mint, recovery mode, memtest, Win7 etc) all exactly the same as before. No trace of Linux Lite as an additional option. So the alternative route of inserting LL into Mint's Grub, seems not to have worked, which is a pity. But what puzzles me is why it worked for austin.texas (who suggested it) and isn't working for me. The "syntax error" must surely be part of the reason?
Just in case it helps with the detective work, once I had rebooted into Mint I went into the file manager and had a look into its /boot/grub. In there I noticed two grub (menu?) files, grub.cfg and grub.cfg.new. The latter was modified today. ......and it includes the Linux Lite entry - in fact more than one. And line 386 in that cfg.new file is actually the very last line, not a part of the body of the LL entry. I have no idea what this means....! I can copy and paste the whole of that grub.cfg.new file if that would help to figure out the error.