Kernel Updates, is it advisable?

Questions about applications and software
Forum rules
Before you post please read how to get help
User avatar
slipstick
Level 5
Level 5
Posts: 807
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Kernel Updates, is it advisable?

Post by slipstick » Thu Mar 29, 2018 7:44 pm

/dev/sda changing from /dev/sdb is likely at the heart of this problem - did that happen when you installed the new drive?

I don't see any attachment. The RESULTS.txt file from bootinfoscript should be a long text file. Please open it, copy all the text (right click - Select All, right click - Copy), then paste it into a reply by left clicking on the icon at the top of the reply box that looks like </>, then right click - Paste).
In theory, theory and practice are the same. In practice, they ain't.

andrewgouw
Level 3
Level 3
Posts: 153
Joined: Sat Nov 29, 2014 11:12 pm

Re: Kernel Updates, is it advisable?

Post by andrewgouw » Thu Mar 29, 2018 9:06 pm

Yes it happened when I installed the new drive and it installed itself in /dev/sda from the get go but then I get an "press S to....." when I bootup and everything goes wrong.
Sorry forgot to upload the attachment. Here it is.
Attachments
Scr5.png

User avatar
slipstick
Level 5
Level 5
Posts: 807
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Kernel Updates, is it advisable?

Post by slipstick » Thu Mar 29, 2018 10:12 pm

I forgot you are on LM17 - bootinfoscript is not in the repository for LM17 (but it is in the repo for LM18). If you want to run it from LM17, you will have to download it from here (click the Download button at that site):
https://sourceforge.net/projects/bootinfoscript/

I realize the following may be a little intimidating if you don't have much experience with the terminal and if you don't want to try it, that's OK. If you do want to try this, then download the file from the above link and then follow these instructions:

Assuming that was downloaded to your ~/Downloads folder, then you can start your file manager and open the Downloads folder, then right click on the downloaded bootinfoscript-061.tar.gz file and select "Extract Here". At this point, you should have a new folder in Downloads named bootinfoscript-061, which contains the bootinfoscript script file and a README file if you want to learn more what it does. To execute it, open a terminal and do

Code: Select all

cd ~/Downloads/bootinfoscript-061
then

Code: Select all

sudo ./bootinfoscript
Now close the terminal and with your file manager, open the ~/Downloads/bootinfoscript-061/RESULTS.txt file and copy all the contents and paste it into a reply here inside code blocks.
In theory, theory and practice are the same. In practice, they ain't.

andrewgouw
Level 3
Level 3
Posts: 153
Joined: Sat Nov 29, 2014 11:12 pm

Re: Kernel Updates, is it advisable?

Post by andrewgouw » Thu Mar 29, 2018 10:38 pm

Thanks. By a stroke of luck I got it. Here is the result.txt
Boot Info Script 0.61 [1 April 2012]


============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 112 for .
=> No known boot loader is installed in the MBR of /dev/sdb.
=> Windows is installed in the MBR of /dev/sdc.
=> Windows is installed in the MBR of /dev/sdd.
=> Windows is installed in the MBR of /dev/sde.

sda1: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg

sda2: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 17.3 Rosa
Boot files: /boot/grub/grub.cfg /etc/fstab

sda3: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: According to the info in the boot sector, sda3 starts
at sector 51050496. But according to the info from
fdisk, sda3 starts at sector 298948608.
Operating System:
Boot files:

sda4: __________________________________________________________________________

File system: Extended Partition
Boot sector type: Unknown
Boot sector info:

sda5: __________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

sda6: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdb1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdb2: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdb3: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdc1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD

sdc2: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe

sdd1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdd3: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sde1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows XP: NTFS
Boot sector info: According to the info in the boot sector, sde1 starts
at sector 0. But according to the info from fdisk,
sde1 starts at sector 2048.
Operating System:
Boot files:

sde2: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 240.1 GB, 240057409536 bytes
255 heads, 63 sectors/track, 29185 cylinders, total 468862128 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 1,953,791 1,951,744 83 Linux
/dev/sda2 1,953,792 31,250,431 29,296,640 83 Linux
/dev/sda3 298,948,608 312,580,095 13,631,488 27 Hidden NTFS (Recovery Environment)
/dev/sda4 31,252,478 298,948,607 267,696,130 5 Extended
/dev/sda5 31,252,480 39,063,551 7,811,072 82 Linux swap / Solaris
/dev/sda6 39,065,600 298,948,607 259,883,008 83 Linux


Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 2,048 904,945,663 904,943,616 7 NTFS / exFAT / HPFS
/dev/sdb2 904,945,664 1,324,374,015 419,428,352 7 NTFS / exFAT / HPFS
/dev/sdb3 1,324,376,064 1,953,521,663 629,145,600 7 NTFS / exFAT / HPFS


Drive: sdc _____________________________________________________________________

Disk /dev/sdc: 180.0 GB, 180045766656 bytes
255 heads, 63 sectors/track, 21889 cylinders, total 351651888 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sdc2 206,848 262,146,047 261,939,200 7 NTFS / exFAT / HPFS


GUID Partition Table detected, but does not seem to be used.

Partition Start Sector End Sector # of Sectors System

Drive: sdd _____________________________________________________________________

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdd1 2,048 1,324,376,063 1,324,374,016 7 NTFS / exFAT / HPFS
/dev/sdd3 1,324,376,064 1,953,521,663 629,145,600 7 NTFS / exFAT / HPFS


Drive: sde _____________________________________________________________________

Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sde1 2,048 1,951,746,047 1,951,744,000 7 NTFS / exFAT / HPFS
/dev/sde2 1,951,746,048 3,907,024,895 1,955,278,848 7 NTFS / exFAT / HPFS


"blkid" output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda1 3415e163-e814-4bf8-902a-5026c2b64730 ext4
/dev/sda2 96b49976-f94b-4a46-b0d0-d658be5e1c5f ext4
/dev/sda3 DEECDABFECDA90DF ntfs Recovery image
/dev/sda5 625a4a07-09ca-459f-b3e2-297c0b0e3f15 swap
/dev/sda6 a187a4d7-1488-42ec-800f-0b98b983f44f ext4
/dev/sdb1 0CA99B7958518E04 ntfs Personal
/dev/sdb2 0D1EEA96B8B44298 ntfs Resource
/dev/sdb3 47F501E3E5B28AEB ntfs Bak2
/dev/sdc1 545855DA5855BB84 ntfs System Reserved
/dev/sdc2 AC1E6C4E1E6C139C ntfs
/dev/sdd1 6628455628452681 ntfs 2-Personal
/dev/sdd3 3ABA3D8D4414172C ntfs 2-Resource
/dev/sde1 8C92DEC0F6E8D57F ntfs Bak
/dev/sde2 24920C84920C5CA4 ntfs RES

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda2 / ext4 (rw,errors=remount-ro)
/dev/sda6 /home ext4 (rw)
/dev/sdb1 /mnt/Personal fuseblk (rw,nosuid,nodev,allow_other,blksize=512)
/dev/sdb2 /mnt/Resource fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sdb3 /mnt/Bak2 fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sdd1 /mnt/2-Personal fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sdd3 /mnt/2-Resource fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/sde1 /media/andrew/Bak fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)
/dev/sde2 /media/andrew/RES fuseblk (rw,nosuid,nodev,allow_other,default_permissions,blksize=4096)


============================= sda1/grub/grub.cfg: ==============================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 96b49976-f94b-4a46-b0d0-d658be5e1c5f
else
search --no-floppy --fs-uuid --set=root 96b49976-f94b-4a46-b0d0-d658be5e1c5f
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="$1"
if [ "$1" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-37-generic (/dev/sda1)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 3415e163-e814-4bf8-902a-5026c2b64730
else
search --no-floppy --fs-uuid --set=root 3415e163-e814-4bf8-902a-5026c2b64730
fi
linux /vmlinuz-3.13.0-37-generic root=UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f ro quiet splash $vt_handoff
initrd /initrd.img-3.13.0-37-generic
}
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-37-generic (/dev/sda1) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 3415e163-e814-4bf8-902a-5026c2b64730
else
search --no-floppy --fs-uuid --set=root 3415e163-e814-4bf8-902a-5026c2b64730
fi
echo 'Loading Linux 3.13.0-37-generic ...'
linux /vmlinuz-3.13.0-37-generic root=UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.13.0-37-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 3415e163-e814-4bf8-902a-5026c2b64730
else
search --no-floppy --fs-uuid --set=root 3415e163-e814-4bf8-902a-5026c2b64730
fi
knetbsd /memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 3415e163-e814-4bf8-902a-5026c2b64730
else
search --no-floppy --fs-uuid --set=root 3415e163-e814-4bf8-902a-5026c2b64730
fi
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

###--### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdb2)' --class windows --class os $menuentry_id_option 'osprober-chain-545855DA5855BB84' {
insmod part_msdos
insmod ntfs
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 545855DA5855BB84
else
search --no-floppy --fs-uuid --set=root 545855DA5855BB84
fi
parttool ${root} hidden-
chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
set timeout=5
fi
###--### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=================== sda1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)


=========================== sda2/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 96b49976-f94b-4a46-b0d0-d658be5e1c5f
else
search --no-floppy --fs-uuid --set=root 96b49976-f94b-4a46-b0d0-d658be5e1c5f
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="$1"
if [ "$1" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
}
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Linux Mint 17.3 Cinnamon 64-bit, 4.4.0-116-generic (/dev/sdb2)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 96b49976-f94b-4a46-b0d0-d658be5e1c5f
else
search --no-floppy --fs-uuid --set=root 96b49976-f94b-4a46-b0d0-d658be5e1c5f
fi
linux /boot/vmlinuz-4.4.0-116-generic root=UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f ro quiet splash $vt_handoff
initrd /boot/initrd.img-4.4.0-116-generic
}
menuentry 'Linux Mint 17.3 Cinnamon 64-bit, 4.4.0-116-generic (/dev/sdb2) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 96b49976-f94b-4a46-b0d0-d658be5e1c5f
else
search --no-floppy --fs-uuid --set=root 96b49976-f94b-4a46-b0d0-d658be5e1c5f
fi
echo 'Loading Linux 4.4.0-116-generic ...'
linux /boot/vmlinuz-4.4.0-116-generic root=UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.4.0-116-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdd1)' --class windows --class os $menuentry_id_option 'osprober-chain-545855DA5855BB84' {
insmod part_msdos
insmod ntfs
set root='hd3,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 545855DA5855BB84
else
search --no-floppy --fs-uuid --set=root 545855DA5855BB84
fi
parttool ${root} hidden-
chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# 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.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sda2/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
#
# / was on /dev/sda2 during installation
# /dev/sdb2
UUID=96b49976-f94b-4a46-b0d0-d658be5e1c5f / ext4 errors=remount-ro, 0 1
# /boot was on /dev/sda1 during installation
# /home was on /dev/sda6 during installation
# /dev/sdb6
UUID=a187a4d7-1488-42ec-800f-0b98b983f44f /home ext4 defaults 0 2
# swap was on /dev/sda5 during installation
# /dev/sdb5
UUID=625a4a07-09ca-459f-b3e2-297c0b0e3f15 none swap sw 0 0
#
# /dev/sda1
# UUID=16765557765538A /mnt/Bak ntfs errors=remount-ro 0 0
# /dev/sda2
# UUID=24920C84920C5CA4 /mnt/RES ntfs errors=remount-ro 0 0
#
LABEL=Personal /mnt/Personal auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Resource /mnt/Resource auto nosuid,nodev,nofail,x-gvfs-show 0 0
# LABEL=Bak /mnt/Bak auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=2-Personal /mnt/2-Personal auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=2-Resource /mnt/2-Resource auto nosuid,nodev,nofail,x-gvfs-show 0 0
# LABEL=RES /mnt/RES auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
#
LABEL=Bak2 /mnt/Bak2 auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
--------------------------------------------------------------------------------

=================== sda2: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)


======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown MBR on /dev/sdb

00000000 e8 12 01 b9 f0 01 be 10 7c bf 10 06 57 f3 a4 c3 |........|...W...|
00000010 8b 4e 14 83 f9 0e 75 08 8d 5e 07 43 02 07 e2 fb |.N....u..^.C....|
00000020 8c 56 0c 8c 56 0e 75 69 8a 56 10 84 d2 79 62 e8 |.V..V.ui.V...yb.|
00000030 f6 00 bb aa 55 cd 13 72 6f 3b 5e 5c 75 6a d1 e9 |....U..ro;^\uj..|
00000040 73 66 b4 42 c6 46 02 01 eb 66 89 b6 f6 fe 8a 44 |sf.B.F...f.....D|
00000050 04 84 c0 74 0f 3c 05 74 0b 3c 0f 74 07 8a 14 80 |...t.<.t.<.t....|
00000060 e2 80 75 cb 83 c6 10 06 c4 5c 08 89 5e 08 8c 46 |..u......\..^..F|
00000070 0a 07 fe 8e f9 fe 75 d2 b0 31 c6 46 d7 50 88 46 |......u..1.F.P.F|
00000080 d4 be 6a 07 ac 84 c0 74 08 b4 0e b3 07 cd 10 eb |..j....t........|
00000090 f3 e8 81 00 88 46 11 be ae 07 3c 05 75 c6 cd 16 |.....F....<.u...|
000000a0 33 d2 89 56 08 89 56 0a e8 7d 00 72 1b b8 01 02 |3..V..V..}.r....|
000000b0 bf 05 00 8b dc 56 50 50 32 e4 cd 13 58 8b f5 cd |.....VPP2...X...|
000000c0 13 58 5e 73 03 4f 75 eb b0 32 72 b2 40 8a 66 11 |.X^s.Ou..2r.@.f.|
000000d0 9e 7b 04 c6 47 02 0e 72 35 75 0c 88 57 40 c4 4e |.{..G..r5u..W@.N|
000000e0 08 89 4f 1c 8c 47 1e 79 06 8a 4e 12 88 4f 25 80 |..O..G.y..N..O%.|
000000f0 c7 02 81 7f fe 55 aa 75 85 81 7f fa cd 19 75 09 |.....U.u......u.|
00000100 c6 47 fa e9 c7 47 fb 94 88 e8 1c 00 ff e4 74 ce |.G...G........t.|
00000110 88 57 24 eb c9 5d 33 c0 8e d8 8e c0 8e d0 bc 00 |.W$..]3.........|
00000120 7c 55 bd a2 07 fc fb c3 b4 08 52 06 cd 13 07 72 ||U........R....r|
00000130 33 33 db 8a de 8b 46 0a 33 d2 83 e1 3f f7 f1 91 |33....F.3...?...|
00000140 97 8b 46 08 f7 f7 42 87 ca 3b da 72 17 43 f7 f3 |..F...B..;.r.C..|
00000150 8a f2 86 c5 d1 e8 d1 e8 0a c8 d0 cc d0 cc 0a f4 |................|
00000160 84 e4 74 02 b4 41 5b 8a d3 c3 0d 0a 4d 42 52 20 |..t..A[.....MBR |
00000170 45 72 72 6f 72 20 00 0d 0a 00 72 65 73 73 20 61 |Error ....ress a|
00000180 6e 79 20 6b 65 79 20 74 6f 20 62 6f 6f 74 20 66 |ny key to boot f|
00000190 72 6f 6d 20 66 6c 6f 70 70 79 2e 2e 2e 00 00 00 |rom floppy......|
000001a0 00 00 10 00 01 00 00 7c 00 00 00 00 00 00 00 00 |.......|........|
000001b0 00 00 00 00 00 f2 0e 00 d1 e4 45 8a 00 00 00 00 |..........E.....|
000001c0 21 02 07 08 b8 e3 00 08 00 00 00 58 f0 35 00 08 |!..........X.5..|
000001d0 b9 e3 07 c1 31 47 00 60 f0 35 00 f8 ff 18 00 c2 |....1G.`.5......|
000001e0 13 49 07 08 98 61 00 60 f0 4e 00 00 80 25 00 00 |.I...a.`.N...%..|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200

Unknown BootLoader on sda4

00000000 c8 c2 57 bc 32 e5 9a f1 80 61 4d 80 df b9 4b 14 |..W.2....aM...K.|
00000010 b9 20 93 9d a7 67 59 c9 48 0c 87 08 c2 58 e7 73 |. ...gY.H....X.s|
00000020 ed 6b 01 ac 0b 14 72 08 e0 2c 1e b5 40 d8 a6 f0 |.k....r..,..@...|
00000030 68 0c e3 b4 7a b3 de e4 17 e3 e1 0f 7e 04 26 aa |h...z.......~.&.|
00000040 31 71 c7 0c 8a 78 d5 19 b4 08 37 40 75 d2 34 89 |1q...x....7@u.4.|
00000050 5a d9 4f 17 f5 2a 3b 2e a7 8a cb 43 95 f6 fc 7a |Z.O..*;....C...z|
00000060 09 cc c3 35 cf a2 3e b4 c7 a9 27 c7 a0 b0 16 0f |...5..>...'.....|
00000070 f4 95 97 81 06 20 aa 7c 2f 52 a2 14 a1 10 4b e2 |..... .|/R....K.|
00000080 2c 4d 2c 60 7b a6 d9 c7 93 ff 3c e1 5d a3 aa e9 |,M,`{.....<.]...|
00000090 20 74 8e ef a7 78 53 3c 38 0e f2 63 e6 06 87 81 | t...xS<8..c....|
000000a0 e6 86 4d 1e f1 60 51 7b 19 53 d6 9f c9 db 66 e3 |..M..`Q{.S....f.|
000000b0 ed 0d 53 a7 0f ca d1 b3 76 5a 65 87 b3 d2 fe 8c |..S.....vZe.....|
000000c0 07 c4 3f d5 39 04 7c 22 02 54 a4 b4 80 46 06 ff |..?.9.|".T...F..|
000000d0 ec 86 99 0c 3c fb 35 3b be ae d1 1b 31 ca 0f 4c |....<.5;....1..L|
000000e0 19 20 30 a8 cf 0f ef d7 4f f4 b6 9c 23 ce 83 96 |. 0.....O...#...|
000000f0 c1 8a 5a c1 4b 34 98 d1 b2 ed 48 e5 21 a8 3a 38 |..Z.K4....H.!.:8|
00000100 27 83 89 24 50 0d 2a ce 0a ff c9 e6 a7 c9 20 48 |'..$P.*....... H|
00000110 10 61 31 32 19 25 68 a7 e3 20 2f c4 11 47 d9 f0 |.a12.%h.. /..G..|
00000120 46 7a 54 30 f0 9e ab 39 02 da 04 b7 3d ee b5 3f |FzT0...9....=..?|
00000130 8f 02 ea 62 34 70 9d 49 ca 29 9f 0c 87 18 57 e5 |...b4p.I.)....W.|
00000140 3f ce bf e8 89 59 c9 47 f2 12 25 04 59 78 5a a6 |?....Y.G..%.YxZ.|
00000150 c4 a6 ef 20 69 e0 88 36 07 60 f7 60 49 6c 56 21 |... i..6.`.`IlV!|
00000160 f3 4d 54 dd 24 65 bd 27 7f 5b 0e 28 9d e1 db 1a |.MT.$e.'.[.(....|
00000170 76 a1 b4 ad 1e 7f a6 00 1d 6e 8a f7 96 54 94 4e |v........n...T.N|
00000180 0a 66 43 35 4e 3a bd aa 2f 29 19 54 88 74 b3 84 |.fC5N:../).T.t..|
00000190 7b f4 50 97 12 21 cc e2 7b 31 e5 be 74 e5 85 98 |{.P..!..{1..t...|
000001a0 5f b8 38 9f 49 b7 b9 d7 07 52 ac 34 17 29 5d e4 |_.8.I....R.4.)].|
000001b0 37 bd f4 c0 19 6a 5f a1 01 af 2e 93 ec 0e 00 fe |7....j_.........|
000001c0 ff ff 82 fe ff ff 02 00 00 00 00 30 77 00 00 fe |...........0w...|
000001d0 ff ff 05 fe ff ff 02 30 77 00 00 88 7d 0f 00 00 |.......0w...}...|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200


=============================== StdErr Messages: ===============================

cat: /tmp/BootInfo-JsPdn5Kv/Tmp_Log: No such file or directory
cat: /tmp/BootInfo-JsPdn5Kv/Tmp_Log: No such file or directory
No volume groups found

User avatar
slipstick
Level 5
Level 5
Posts: 807
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Kernel Updates, is it advisable?

Post by slipstick » Thu Mar 29, 2018 11:19 pm

Thanks for the info. Just a quick glance shows that you have 2 grub.cfg files and you are obviously booting up on the one in sda1 which gets you into LM17.1 with the 3.13.0-37 kernel. The other one on sda2 has LM17.3 with the 4.0.4-116 kernel, but apparently that one isn't getting executed so you never see a menu for that. I'll need to look at this some more, but don't have time right now - it may be tomorrow before I can get back to you, but there is a lot of info. here. In the meantime, maybe someone with more experience will come up with the solution.
In theory, theory and practice are the same. In practice, they ain't.

andrewgouw
Level 3
Level 3
Posts: 153
Joined: Sat Nov 29, 2014 11:12 pm

Re: Kernel Updates, is it advisable?

Post by andrewgouw » Thu Mar 29, 2018 11:44 pm

I do appreciate all your help. I am so lost and am seriously considering reinstalling everything from scratch. My biggest problem is the Windows licensing which is a pain in the butt.
I have been using Linux mint for almost three years now but unfortunately I still need Windows for VBA programming. Wish I can find something similar so I can completely get rid of Windows.
I am sure I made this mess myself because of the lack of enough knowledge about mounting drives, but I tried to configure things like an expert which I am far from being one.
Take your time I am not in a real hurry. That I have learned to be when you are a novice. :(

User avatar
slipstick
Level 5
Level 5
Posts: 807
Joined: Sun Oct 21, 2012 9:56 pm
Location: Somewhere on the /LL0 scale

Re: Kernel Updates, is it advisable?

Post by slipstick » Fri Mar 30, 2018 4:30 pm

This still doesn't make much sense to me - it looks pretty mangled. Apparently your bootloader is using as a configuration file "/grub/grub.cfg" in sda1. The set root entries here don't look right, but if it uses the UUID's to find the operating systems, it will find Linux at sda2 and Windows at sdc1. The other configuration file is "/boot/grub/grub.cfg" in sda2 which apparently isn't getting used. Even on this one which was just updated or generated when you installed the 4.4.0-116 kernel the set root values look strange, but the UUID's are the same with Linux on sda2 and Windows on sdc1. I'm afraid my knowledge of GRUB is insufficient to make sense of this. So, all I have to suggest is:

1. Do nothing - in this case you are using a kernel that is not secure against Meltdown/Spectre exploits. If you try to upgrade the kernel to the latest in the 3.13 series, I expect you will get the same results as you did with the 4.4.0-116 kernel; i.e., it won't be used because it will appear in the unused configuration file.

2. Reinstall grub - this can break your system, so I would only try this as a last ditch attempt before reinstalling.
sudo grub-install --recheck /dev/sda

Sorry I can't give you a sure-to-work solution.
In theory, theory and practice are the same. In practice, they ain't.

andrewgouw
Level 3
Level 3
Posts: 153
Joined: Sat Nov 29, 2014 11:12 pm

Re: Kernel Updates, is it advisable?

Post by andrewgouw » Fri Mar 30, 2018 6:26 pm

Thanks again for your help. I don't know what I did to mess this up so badly. I will try your suggestions.

Reddog1
Level 3
Level 3
Posts: 143
Joined: Wed Jun 01, 2011 2:12 pm

Re: Kernel Updates, is it advisable?

Post by Reddog1 » Sun Apr 01, 2018 6:21 pm

Hmmm---looks like a job for the Boot Repair Utility. Seriously, boot-repair is excellent at sorting out boot configuration problems. I've used it with Mint and it is somewhat of a magical tool. There is a thread here:

viewtopic.php?f=46&t=207529

and read this and check out the links at the bottom:

https://help.ubuntu.com/community/Boot-Repair

andrewgouw
Level 3
Level 3
Posts: 153
Joined: Sat Nov 29, 2014 11:12 pm

Re: Kernel Updates, is it advisable?

Post by andrewgouw » Mon Apr 02, 2018 3:20 am

Thanks for the suggestion and links. I have downloaded boot-repair-cd from sourceforge.net and am preparing to do the necessary read up and try it out. Will let you know the result.

SysA-Punchcard-Oldie
Level 1
Level 1
Posts: 7
Joined: Sat Mar 31, 2018 3:06 pm

Re: Kernel Updates, is it advisable?

Post by SysA-Punchcard-Oldie » Mon Apr 02, 2018 4:23 am

Hi to whom it may concern ...
sysinfo M4300.png
Some experiences .... with Dell Precision M4300
* all Kernels up to Kernel 4.10. *** are fine
* Mint-Versions up to 18.3 are fine

Not operational with my machine:

* Kernel 4.11.***
* Kernel 4.12.***
* Kernel 4.13.***

Cheers SysA-Punchcard-Oldie

User avatar
Sir Charles
Level 7
Level 7
Posts: 1827
Joined: Thu Jan 04, 2018 1:00 pm

Re: Kernel Updates, is it advisable?

Post by Sir Charles » Mon Apr 02, 2018 5:32 am

SysA-Punchcard-Oldie wrote:
Mon Apr 02, 2018 4:23 am
* all Kernels up to Kernel 4.10. *** are fine
Hi,
For having the latest security patches against Meltdown/Spectre, you might want 4.4.0-116. The 4.10-kernels don't have those patches.
xenopeek wrote:
Wed Jan 10, 2018 6:24 am
In short, Linux Mint 18.x users should be using kernel 4.4.0-116 or 4.13.0-36 or newer and NOT continue to use any 4.8.x, 4.10.x or 4.11.x kernels (those are no longer updated and unsafe). Linux Mint 17.x users should be using kernel 3.13.0-142 or 4.4.0-116 and NOT continue to use any 3.16.x, 3.19.x or 4.2.x kernels (those are also no longer updated and unsafe).
I suppose that's one of the ironies of life, doing the wrong thing at the right moment -C.C.

SysA-Punchcard-Oldie
Level 1
Level 1
Posts: 7
Joined: Sat Mar 31, 2018 3:06 pm

Re: Kernel Updates, is it advisable?

Post by SysA-Punchcard-Oldie » Mon Apr 02, 2018 1:03 pm

THX for hints,

it took me some hours to check it out ... actually i managet to install/run Kernel 4.13.0-37 older kernels do report a crash with cinnamon.

BTW by using Mint actualisation services there are (sic!) no choices for update to Kernelversions for:

* Linux 4.14 Update https://www.heise.de/ct/artikel/Die-Neu ... 31941.html
* Linux 4.15 Update https://www.heise.de/ct/artikel/Die-Neu ... ?seite=all
* Linux 4.16 Update https://www.heise.de/ct/artikel/Die-Neu ... ?seite=all

in order to prevent failures and to prefer update systems there could be a need for improvements :mrgreen:


Best Tom aka SysA-Punchcard-Oldie
Attachments
sysinfo M4300 4 13.png

Cosmo.
Level 23
Level 23
Posts: 17823
Joined: Sat Dec 06, 2014 7:34 am

Re: Kernel Updates, is it advisable?

Post by Cosmo. » Mon Apr 02, 2018 2:53 pm

heise news report about the kernel, as released by the Linux kernel team. Mint as an Ubuntu based distro uses the kernel as maintained by the Ubuntu team.

User avatar
Pjotr
Level 20
Level 20
Posts: 11064
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Kernel Updates, is it advisable?

Post by Pjotr » Mon Apr 02, 2018 3:31 pm

Cosmo. wrote:
Mon Apr 02, 2018 2:53 pm
heise news report about the kernel, as released by the Linux kernel team. Mint as an Ubuntu based distro uses the kernel as maintained by the Ubuntu team.
Yes. And if you wish to compare the downstream Ubuntu/Mint kernel numbering with the upstream numbering at kernel.org:

Code: Select all

cat /proc/version_signature
The first part of the output shows the numbering by Canonical Kernel Team (Ubuntu), and the last part the upstream (kernel.org) kernel version that has been used by Canonical Kernel Team to create your kernel.
Tip: 10 things to do after installing Linux Mint 19 Tara
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

Mr_Reed
Level 3
Level 3
Posts: 190
Joined: Tue Dec 23, 2014 12:27 am

Re: Kernel Updates, is it advisable?

Post by Mr_Reed » Tue Apr 03, 2018 12:05 pm

I'm still pretty new to Linux, and all was going well for me for a time. I was enjoying the stability and ease of updates. Then along came spectre and meltdown, and I got confused about the kernels.

I ended up starting all over installing the latest Linux Mint 18.3 xfce, but I'm still getting asked to install kernel updates. I don't know if this is normal or not, but it feels like every few weeks or maybe once a month there is a kernel update, and I get the blue updates dot instead of the green check mark. I always had the impression that I was to leave the kernel alone if all was working well. Now the computer is controlling me and basically asking for new kernels as fast as they come out. I have since updated kernels many times after the spectre/meltdown scandal. I originally installed a LTS version, and now I'm concerned that the update manager has lead me astray out of a LTS. Can someone enlighten me on the kernels or what is going on. I have searched the forums and did not immediately see answers to my questions. Please advise. Thanks!

User avatar
Sir Charles
Level 7
Level 7
Posts: 1827
Joined: Thu Jan 04, 2018 1:00 pm

Re: Kernel Updates, is it advisable?

Post by Sir Charles » Tue Apr 03, 2018 12:11 pm

Mr_Reed wrote:
Tue Apr 03, 2018 12:05 pm
I have searched the forums and did not immediately see answers to my questions.
Here follows the recommendation for kernel updates in the wake of Meltdown/Spectre:
xenopeek wrote:
Wed Jan 10, 2018 6:24 am
In short, Linux Mint 18.x users should be using kernel 4.4.0-116 or 4.13.0-36 or newer and NOT continue to use any 4.8.x, 4.10.x or 4.11.x kernels (those are no longer updated and unsafe). Linux Mint 17.x users should be using kernel 3.13.0-142 or 4.4.0-116 and NOT continue to use any 3.16.x, 3.19.x or 4.2.x kernels (those are also no longer updated and unsafe).
(Please click on the arrow to read the whole post)
I suppose that's one of the ironies of life, doing the wrong thing at the right moment -C.C.

Cosmo.
Level 23
Level 23
Posts: 17823
Joined: Sat Dec 06, 2014 7:34 am

Re: Kernel Updates, is it advisable?

Post by Cosmo. » Tue Apr 03, 2018 2:45 pm

Mr_Reed wrote:
Tue Apr 03, 2018 12:05 pm
I don't know if this is normal or not
It is. Those updates - inside of a series) can fix a security leak, they can also fix a stability issue. If the maintainers provide an update, the update manager will find it after some time and consequently does offer it.

LTS does not mean, that the original packages will be good until the end of life of the Mint version; in the contrary. LTS means, that during this time updates will get made available. If the LTS time has reached its end, you will not get any updates offered; again this does not mean, that you are safe until the end of all days, but in the contrary: Nothing will get fixed.

Mr_Reed
Level 3
Level 3
Posts: 190
Joined: Tue Dec 23, 2014 12:27 am

Re: Kernel Updates, is it advisable?

Post by Mr_Reed » Tue Apr 03, 2018 9:24 pm

Cosmo. wrote:
Tue Apr 03, 2018 2:45 pm

It is. Those updates - inside of a series) can fix a security leak, they can also fix a stability issue. If the maintainers provide an update, the update manager will find it after some time and consequently does offer it.

LTS does not mean, that the original packages will be good until the end of life of the Mint version; in the contrary. LTS means, that during this time updates will get made available.
So if I originally installed LTS, that will not change based on me constantly updating the kernel. Just want to verify that I didn't inadvertently do away with the LTS.

User avatar
smurphos
Level 8
Level 8
Posts: 2255
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher...

Re: Kernel Updates, is it advisable?

Post by smurphos » Tue Apr 03, 2018 11:29 pm

Mr_Reed wrote:
Tue Apr 03, 2018 9:24 pm
So if I originally installed LTS, that will not change based on me constantly updating the kernel. Just want to verify that I didn't inadvertently do away with the LTS.
Mr_Reed,

A quick kernel 101 for you.

Mint 18.x releases are based on Ubuntu 16.04.x releases. Mint 18 and Ubuntu 16.04 were released back in mid 2016 with a 4.4.0-x kernel. 4.4.0-x was set by Ubuntu as the LTS kernel series and continues to receive security updates and bug fixes and will do so until April 2021. It's now on version 4.4.0-116.

Mint 18.1 and Ubuntu 16.04.1 also both shipped with the current 4.4.0-x kernel.

However Mint 18.2, 18.3 and the corresponding Ubuntu releases shipped with the newer 4.8.0-x and 4.10.0-x kernels respectively. Ubuntu call these HWE (Hardware Enablement) kernels because they add support for newer hardware. These kernels series are only supported for 9 months at a time so 4.8.0.x and 4.10.0-x are both already EOL (end of life) and no longer receiving security updates. However users should have been offered updates to 4.13.0.-x which is the currently supported HWE kernel. That will become EOL in August 18 and 4.15.0-x will take over as the supported HWE kernel until April 2021. Update Manager will take care of that transition.

So if you are running a fresh install of 18.3 unless you have specifically chosen to install a 4.4.0-x kernel you are not technically using a LTS kernel. But if you are on a 4.13.0-x kernel it is supported and if you follow Update Manager's recommendations you will eventually end up on 4.15.0-x and will be on a supported kernel for the lifetime of Mint 18.x

Although you should be suitably wary of kernel updates as they underpin the whole operation of your computer and updates can occasionally cause issues (although rarely across the board - normally for specific hardware combinations) you should not fear them or feel they are controlling your use of your computer.

If you have Timeshift set up to back up your system that makes it easy to recover from any bad update via a restore to an earlier backup.

Even without Timeshift for kernels it is a reasonably straightforward process to use the GRUB menu to reboot into an older kernel version and then use Update Manager to remove a problematic update.

Educate yourself on how both those processes work and you are good to go. If you are ever concerned about a specific update just hold off applying it for half a day or so and they do a forum search to see if there are widespread reports of issues.

Post Reply

Return to “Software & Applications”