Page 2 of 2

Re: Mint 17.2 Kernel upgrade issue!

Posted: Fri May 06, 2016 4:01 pm
by blue_bullet
blue_bullet wrote:
Hendrick wrote:Joe,

I once had the same issue when running Mint13 and Mint17 on my pc. It took me not long to found out
that you cannot have two captains on one ship, so to speak. One of the distributions has to be in charge
for updating the Grub boot manager. Laurent85 is absolutely right concerning this matter.

Hendrick
Late to the dance again as usual. Hendrick, thanks for your post. I have a multiboot system with Petra (LM16 KDE) as the 1st choice in the grub menu. I also have LM17.1 KDE (now LM 17.2 KDE), and Windows 8. Today I upgraded from 17.1 to 17.2 quite smoothly I might add. I installed the recommended kernel for 17.2, rebooted, and did the sudo update-grub, rebooted. Nothing changed in the grub menu. I did boot to 17.2 but the menu said 17.1 and uname -a said I was still at the old kernel. I had to log in to LM16 and issue the sudo update-grub. Next I rebooted into 17.2 (appeared correctly in the grub menu now) and uname -a shows the new recommended kernel.

Thanks for your tip. I now need to get rid of LM16 since I no longer use it. Can you tell me how you safely eliminated LM13 when running it with LM17? I want LM17.2 to be the captain.
Here almost a year later and using LM 17.3 KDE since it was released I have been living with Grub listing my default as Rebecca 17.2 (first entry) even though selecting that puts me in Rosa 17.3. I used grub-customizer in Konsole to set my defaults, but they were never displayed properly. This morning I logged into LM 16 and ran 'sudo update-grub", rebooted and now the entries are displaying properly and in LM 17.3 I get the recommended kernel 3.19 instead of 3.16.0-38-Generic.

Here's my questions. How can I remove LM 16 when that is where update-grub works? Am I stuck with LM 16 forever or is there a way to make update-grub work in the most current release of Linux Mint?

I guess the correct title of this post should be "Mint 17.3 Kernel Upgrade Issue" as the problem persists.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Fri May 06, 2016 4:33 pm
by austin.texas
In order to get rid of LM16, you just need to install Mint 17.3's grub to the MBR.
Boot into 17.3, open a terminal and enter

Code: Select all

sudo grub-install /dev/dsX
where X is your hard drive. sda? sdb?

Re: Mint 17.2 Kernel upgrade issue!

Posted: Fri May 06, 2016 6:22 pm
by blue_bullet
austin.texas wrote:In order to get rid of LM16, you just need to install Mint 17.3's grub to the MBR.
Boot into 17.3, open a terminal and enter

Code: Select all

sudo grub-install /dev/dsX
where X is your hard drive. sda? sdb?
Thanks for your suggestion. I think you meant dsX to be sdX.

I tried this. In Konsole in 17.3 "sudo grub-install /dev/sda" got no errors. To see if it worked I entered grub-customizer and moved the
Windows 8 option to be the first in the list, saved the configuration, entered "sudo update-grub" (no errors), and then "sudo reboot".
The order did not change, i.e. Windows 8 was not the first option. So I don't think your suggestion worked for me. How can I tell where grub
is installed? "sudo update-grub" returns no errors in LM 17.3 and LM 16, but LM 16 seems to be the controlling version.

If I go to LM 16 and run grub-customizer to move Windows 8 up in the list as the first option, run "sudo reboot" Windows 8 appears as first in the list.
That tells me LM 16 is still controlling grub.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Fri May 06, 2016 11:37 pm
by austin.texas
Yes, you are right, I meant sdX

When you changed it with grub customizer, and then entered "sudo update-grub" - that would undo the change you made.

I color code my grub menus. The menu for my current Mint is green and the grub menu for my old OS is blue. To do that all you have to do is open /etc/default/grub in your text editor, and add these two lines at the end:

Code: Select all

export GRUB_COLOR_NORMAL="white/blue"
export GRUB_COLOR_HIGHLIGHT="blue/white"
Then update grub. What will give you a very clear picture of which OS is controlling Grub, and you don't have to mess with changing the order with grub customizer.

I can't imagine why sudo grub-install /dev/sda would not work.
Please post the result of the Boot Info Script.
Install boot-info-script:

Code: Select all

sudo apt-get install boot-info-script
Then run the script:

Code: Select all

sudo bootinfoscript --stdout | pastebin
Post the resulting URL link that displays in the terminal.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 12:58 pm
by blue_bullet
Here's the link to output from the bootinfoscript:

http://paste.linuxmint.com/view/ztc1

Thanks for the tip on colors. I changed them via "kdesudo kate /etc/default/grub", ran "sudo update-grub", "sudo reboot" but saw no color change.
Before doing all this I first ran "sudo grub-install /dev/sda" and "sudo update-grub", and got no errors. All this was done in 17.3.

I am going to try your color change in 16 to see if it takes there.

I guess I could remove LM 16 / and /home partitions in partition manager and reinstall grub via live usb, but seems a bit extreme for a simple upgrade.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 3:11 pm
by austin.texas
In looking at your Boot Info, it appears that you have Windows installed in UEFI mode, and quite possibly both Mint 16 and Mint 17.x installed in non-UEFI mode (Legacy mode).
Can you currently boot into Windows?
Please boot both Mint installations and run this command, to verify the mode:

Code: Select all

[ -d /sys/firmware/efi ] && echo "Currently in EFI mode" || echo "Currently in Legacy mode"

By the way, I have to correct myself on the color change.
The better way to do it is to edit /etc/grub.d/06_mint_theme

Code: Select all

kdesudo kate /etc/grub.d/06_mint_theme
And add these lines:

Code: Select all

set menu_color_normal=white/blue
set menu_color_highlight=blue/white
Then update grub.
I have both files edited, but the 06_mint_theme is the one that makes the change happen.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 4:29 pm
by blue_bullet
Response to command [ -d /sys/firmware/efi ] && echo "Currently in EFI mode" || echo "Currently in Legacy mode" is

"Currently in EFI mode"

for LM 17.3 and LM 16. Yes, I can boot into Windows 8.

When I made the color changes you suggested on /etc/grub.d/06_mint_theme followed by a "sudo update-grub" and a "sudo reboot"
on LM 17.3 there was no change in colors. When I did the same thing on LM 16 the colors did change to blue/white so grub is running from LM 16.

BTW the original color change you suggested on /etc/default/grub did not work on LM 17.3 nor LM 16.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 4:38 pm
by austin.texas
OK, now that we know your Mints are both in UEFI mode, we know why the command sudo grub-install /dev/sda is not working.
For UEFI installations, the bootloader (Grub) is installed to the ESP.
In your case, your ESP is /dev/sda2, so the correct command is:

Code: Select all

sudo grub-install /dev/sda2
Reference: viewtopic.php?p=912036
See also: the section titled "Fixing Post-Installation Problems", here →http://www.rodsbooks.com/linux-uefi/

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 5:41 pm
by blue_bullet
"sudo grub-install /dev/sda2" ran without errors in LM 17.3. KDE Partition Manager confirmed that /boot/efi is on /dev/sda2.

Still when I make color changes in LM 17.3 they do not take. They do work in LM 16 so grub is still tied to LM 16.

Thanks for the links on dual booting. I will read them to learn more.

Re: Mint 17.2 Kernel upgrade issue!

Posted: Sat May 07, 2016 7:01 pm
by austin.texas
blue_bullet wrote:Thanks for the links on dual booting. I will read them to learn more.
The first link was just a reference to an explanation of the ESP.

The second link is where you can start to learn about the ways to fix a UEFI boot problem. The first suggestion on that page, in the section I referred you to, "Fixing Post-Installation Problems" is:
Use efibootmgr—You can boot a Linux emergency disc in EFI mode and use the efibootmgr utility to re-register your Linux boot loader, as described here.
This page explains the usage of efibootmgr to alter the boot sequence.

The problem you are dealing with is that both Mint 16 and Mint 17.x appear as "ubuntu" for the UEFI boot, and you have to manually configure the files in your ESP to point to the correct Mint.