[SOLVED] Updated recent intel microcode firmware through update manager, now cannot boot linux mint 18.3

hydrurga · 01-12-2018, 03:30 PM

Quote:

Originally Posted by Chripcikas

I did also try this 1-4 "recovering procedure" with no luck: http://metadata.ftp-master.debian.or..._README.Debian

Though I see the knowledgeable posters ruled this intel microcode issue out and focusing on the kernel issue.

Have you at any point successfully booted back up into your system after you upgraded the kernel? How about after you upgraded the microcode?

keefaz · 01-12-2018, 03:41 PM

Quote:

Originally Posted by Chripcikas

https://www.linuxquestions.org/quest...ro-4175608561/

In the thread above I've fixed the issue with my touchpad trough trail and error. I do not dare removing "splash quiet", because this might mess up my touchpad again. By the way i didn't get any error message, I just had a black scrsplash quieteen with a white cursor on the top left corner, no other messages were shown.

I doubt adding "splash quiet" resolved your touchpad issue, please see folowing post in your linked thread and read the link...

I was suggesting removing splash quiet at grub boot, that means it's temporary anyway. Just to see boot messages and errors.

Chripcikas · 01-12-2018, 03:47 PM

Quote:

Originally Posted by hydrurga

Have you at any point successfully booted back up into your system after you upgraded the kernel? How about after you upgraded the microcode?

I upgraded the microcode, rebooted, later on that day upgraded the kernel, rebooted, at the end of the day I shut down the laptop. Today I couldn't boot it up. I believe I should have gone through "shut down" and not "reboot" to properly check the status of the system after each of the upgrades.

Chripcikas · 01-12-2018, 04:02 PM

Quote:

Originally Posted by keefaz

I doubt adding "splash quiet" resolved your touchpad issue, please see folowing post in your linked thread and read the link...

I was suggesting removing splash quiet at grub boot, that means it's temporary anyway. Just to see boot messages and errors.

Alright, I went to GRUB, pressed e for edit and removed "quiet splash" from the linux code line and then ctrl+x to boot. No luck there. Or maybe I'm doing it wrong?

hydrurga · 01-12-2018, 04:12 PM

Quote:

Originally Posted by Chripcikas

I upgraded the microcode, rebooted, later on that day upgraded the kernel, rebooted, at the end of the day I shut down the laptop. Today I couldn't boot it up. I believe I should have gone through "shut down" and not "reboot" to properly check the status of the system after each of the upgrades.

Ok. Normally a reboot should be ok, unless you've read otherwise somewhere else. That does indicate however that it may not have been the kernel to blame in the end since you were able to successfully reboot after installing it.

So, perhaps we should chroot in anyway and take a look. Do you have a Linux boot disk/USB of some description?

In the meantime, however, I would try keefaz's suggestion of removing splash quiet first to see if that sheds any further light.

keefaz · 01-12-2018, 04:40 PM

Quote:

Originally Posted by Chripcikas

Alright, I went to GRUB, pressed e for edit and removed "quiet splash" from the linux code line and then ctrl+x to boot. No luck there. Or maybe I'm doing it wrong?

After removing quiet splash, press enter and "b" to boot

Chripcikas · 01-13-2018, 04:43 AM

Quote:

Originally Posted by keefaz

After removing quiet splash, press enter and "b" to boot

well, when I press enter, I jump to a new line. And "b" as in boot, doesn't respond. F10 or ctrl+X are shown to be used as boot. I hope we are talking about the same GRUB menu which has "advanced options" and all that.

Chripcikas · 01-13-2018, 04:48 AM

Quote:

Originally Posted by hydrurga

Ok. Normally a reboot should be ok, unless you've read otherwise somewhere else. That does indicate however that it may not have been the kernel to blame in the end since you were able to successfully reboot after installing it.

So, perhaps we should chroot in anyway and take a look. Do you have a Linux boot disk/USB of some description?

In the meantime, however, I would try keefaz's suggestion of removing splash quiet first to see if that sheds any further light.

Yes, I've created linux mint 18.3 kde boot disk now. How do I perform "chroot" in this particular case?

keefaz · 01-13-2018, 05:03 AM

Quote:

Originally Posted by Chripcikas

well, when I press enter, I jump to a new line. And "b" as in boot, doesn't respond. F10 or ctrl+X are shown to be used as boot. I hope we are talking about the same GRUB menu which has "advanced options" and all that.

Do you press enter twice? When you press "e" you're in edit mode, then you can use keyboard to edit the kernel boot line, adding or removing characters. When you finish, you press enter to quit this mode, then press "b"

hydrurga · 01-13-2018, 05:54 AM

Quote:

Originally Posted by Chripcikas

Yes, I've created linux mint 18.3 kde boot disk now. How do I perform "chroot" in this particular case?

Boot up to the desktop, open the terminal, and then enter

Code:

sudo fdisk -l

so that we can find out which partition contains your PC's root filesystem.

Chripcikas · 01-13-2018, 08:10 AM

Quote:

Originally Posted by hydrurga

Boot up to the desktop, open the terminal, and then enter

Code:

sudo fdisk -l

so that we can find out which partition contains your PC's root filesystem.

Code:

$ sudo fdisk -l
Disk /dev/loop0: 2 GiB, 2121834496 bytes, 4144208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4038462E-A2DC-4328-A76C-66F045357F23

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624   2050047    999424   488M Linux filesystem
/dev/sda3  2050048 500117503 498067456 237.5G Linux filesystem


Disk /dev/sdb: 3.8 GiB, 4009754624 bytes, 7831552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x003fb73e

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *     2048 7831551 7829504  3.8G  c W95 FAT32 (LBA)

hydrurga · 01-13-2018, 08:21 AM

Ok, assuming that /dev/sda3 is the root filesystem (taken from https://help.ubuntu.com/community/LiveCdRecovery):

Code:

sudo mount /dev/sda3 /mnt

sudo mount --bind /dev /mnt/dev

sudo mount --bind /proc /mnt/proc

sudo mount --bind /sys /mnt/sys

sudo chroot /mnt

This will allow you to run an update and see if that might solve the problem.

Tell me, would /dev/sda2 be a separate /boot partition?

Chripcikas · 01-13-2018, 08:32 AM

Quote:

Originally Posted by keefaz

Do you press enter twice? When you press "e" you're in edit mode, then you can use keyboard to edit the kernel boot line, adding or removing characters. When you finish, you press enter to quit this mode, then press "b"

I did press enter once. "Enter" does not quit this edit mode and "b" does nothing. I'm at the window that starts with "setparams 'Linux Mint 18.3 KDE 64-bit' " and words "quiet splash" are removed by me. At the bottom of the screen says: "Minimum Emacs-like screen editing is supported. TAB lists completions. Press ctrl-x or f10 to boot, ctrl-c or f2 for a command-line or ESC to discard edits and return to the grub menu." I press ctrl-x, type in encryption password and then is the same black screen with white crusor at the top of left corner.

Chripcikas · 01-13-2018, 08:46 AM

Quote:

Originally Posted by hydrurga

Ok, assuming that /dev/sda3 is the root filesystem (taken from https://help.ubuntu.com/community/LiveCdRecovery):

Code:

sudo mount /dev/sda3 /mnt

sudo mount --bind /dev /mnt/dev

sudo mount --bind /proc /mnt/proc

sudo mount --bind /sys /mnt/sys

sudo chroot /mnt

This will allow you to run an update and see if that might solve the problem.

Tell me, would /dev/sda2 be a separate /boot partition?

Code:

sudo mount /dev/sda3  /mnt
mount: unknown filesystem type 'crypto_LUKS'

This might be because my disk is encrypted?

I think /dev/sda2 partition was created when I encrypted the disk.

hydrurga · 01-13-2018, 09:06 AM

Ok, you might want to try the steps taken from https://feeding.cloud.geek.nz/posts/...oot-partition/ :

Code:

cryptsetup luksOpen /dev/sda3 sda3_crypt
vgchange -ay
mount /dev/mapper/ubuntu--vg-root /mnt
mount /dev/sda2 /mnt/boot
mount -t proc proc /mnt/proc
mount -o bind /dev /mnt/dev

chroot /mnt