Unable to boot after upgrade to 5.10.31

A complete newbie here. Was using Manjaro Linux KDE version with encrypted system.

I was using Kernel v 5.4.113 for quite some time. It sent notification for updates but I kept postponing it. Today, I decided to go for upgrade.

I used ‘Add Remove Software’. Went to Updates tab. And clicked on Upgrade. All packages were selected.

It informed me about removing some packages, etc. I accepted the suggestions.

After a massive 2.9GB update, it showed that everything went smoothly and update was successful.

When I restarted, in Advanced Option, it gave me an option of Kernel 5.10.31 and 5.4.113.

If I select 5.10.31, nothing happens. No messages, nothing. It just keeps showing my BIOS screen.

If I select 5.4.113, it shows FAILED to load kernel module.

What do I need to do to get the computer operational?

Seems something went wrong with the update. You may need to use one of our install medias and fix your system by chrooting into it.

1 Like

@philm Thanks Downloading the media. Will seek help after I boot the computer using USB stick.

@philm Sorry, could not get back here earlier. Was unwell. But back to normal now.

I have booted in my computer using the latest Manjaro KDE media. The partition manager shows a 300MB FAT32 partition (sda1) and an 8GB partition. I guess, it is SWAP (sda3). Then there is a large partition (sda2), I think it is /.

So, I will mount /dev/sda2 at /mnt.

Is sda1 boot partition or efi partition? What do I mount at /mnt/boot and at /mnt/boot/efi?

Try using manjaro-chroot. It should do that for you automatically:

manjaro-chroot -a

Once you’re chrooted, do a full upgrade sudo pacman -Syyu

@moson Thanks. This is much simpler. Tried it. It returned:

grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
==> ERROR: No Linux partitions detected!

Could it be because the system was encrypted?

Also, it is looking at sdb1 whereas the system in question is on the hard disk sda2. sdb1 is the USB drive from which I have booted.

Yes. If it’s encrypted you need to decrypt / open the encrypted volume first.

This might help you:

@moson Thanks. You may find this too basic. But please bear with me. I have used the KDE Partition Manager to unlock the encrypted partition and mounted the /dev/mapper/luks-xxx to /mnt. I have also mounted /dev/sda1 to /mnt/boot/efi and now will do manjaro-chroot /mnt.

This does not produce any error and produces a sh-5.1# prompt.

I don’t know your partition layout nor do I use encryption myself.
But that sounds correct what you did.


Yepp, then it seemed to work. Now try updating your system.

pacman -Syu

@moson Yes. All seems to be well so far. Doing sudo pacman -Syyu and keeping my fingers crossed.

@moson We are back to square one — exactly where it all started. If I choose to boot 5.10 kernel, it just keeps showing me BIOS screen. If I boot 5.4 kernel, instead, it shows ‘Failed to start load kernel modules’.

How do I fix this up?

We need some more information here.
Please post output of inxi -Fazy

chroot again and post output of journalctl -b 0

@moson inxi -Fazy produces:

  Kernel: 5.10.30-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC 
  misobasedir=manjaro misolabel=MANJARO_KDE_2102 quiet systemd.show_status=1 
  apparmor=1 security=apparmor driver=free nouveau.modeset=1 i915.modeset=1 
  Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
  Distro: Manjaro Linux base: Arch Linux 
  Type: Desktop Mobo: Gigabyte model: B85M-D3H v: x.x serial: <filter> 
  UEFI: American Megatrends v: F15 date: 08/20/2015 
  Info: Quad Core model: Intel Core i5-4670K bits: 64 type: MCP arch: Haswell 
  family: 6 model-id: 3C (60) stepping: 3 microcode: 28 cache: L2: 6 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 27137 
  Speed: 798 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 
  4: 798 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  Type: mds mitigation: Clear CPU buffers; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: disabled, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412 
  class-ID: 0300 
  Device-2: NVIDIA GK106 [GeForce GTX 650 Ti] vendor: ZOTAC driver: nouveau 
  v: kernel bus-ID: 01:00.0 chip-ID: 10de:11c6 class-ID: 0300 
  Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: 
  loaded: intel,nouveau unloaded: modesetting alternate: fbdev,nv,vesa 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: VGA-2 res: 1920x1080 hz: 60 dpi: 102 size: 476x267mm (18.7x10.5") 
  diag: 546mm (21.5") 
  OpenGL: renderer: NVE6 v: 4.3 Mesa 21.0.2 direct render: Yes 
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c 
  class-ID: 0403 
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 
  class-ID: 0403 
  Device-3: NVIDIA GK106 HDMI Audio vendor: ZOTAC driver: snd_hda_intel 
  v: kernel bus-ID: 01:00.1 chip-ID: 10de:0e0b class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.30-1-MANJARO running: yes 
  Sound Server-2: JACK v: 0.125.0 running: no 
  Sound Server-3: PulseAudio v: 14.2 running: yes 
  Sound Server-4: PipeWire v: 0.3.25 running: no 
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 
  chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp3s0 state: down mac: <filter> 
  Device-2: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee 
  v: kernel port: c000 bus-ID: 06:00.0 chip-ID: 10ec:8179 class-ID: 0280 
  IF: wlp6s0 state: up mac: <filter> 
  Local Storage: total: 946.1 GiB used: 0 KiB (0.0%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZRX-00L4HB0 
  size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: 1A01 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Blade 
  size: 14.59 GiB block-size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 1.00 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  Message: No partition data found. 
  Alert: No swap data was found. 
  System Temperatures: cpu: 58.0 C mobo: 27.8 C gpu: nouveau temp: 43.0 C 
  Fan Speeds (RPM): N/A 
  Processes: 185 Uptime: 6m wakeups: 0 Memory: 7.66 GiB used: 1.64 GiB (21.5%) 
  Init: systemd v: 247 tool: systemctl Compilers: gcc: N/A Packages: 
  pacman: 1217 lib: 326 flatpak: 0 Shell: Bash v: 5.1.0 running-in: konsole 
  inxi: 3.3.04

After chrooting, journalctl -b 0 produces no output:
– Journal begins at Sat 2020-12-05 15:13:52 IST, ends at Sat 2021-05-01 20:10:18 IST. –
– No entries –

I suspect it is something with the nvidia drivers.

Please run mhwd -li

@moson The output of mhwd -li after chrooting is:

> Installed PCI configs:
                  NAME               VERSION          FREEDRIVER           TYPE
     video-modesetting            2020.01.13                true            PCI
           video-linux            2018.05.04                true            PCI

Warning: No installed USB configs!

Without chrooting, it produces:

Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/catalyst/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-340xx-bumblebee/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-418xx-bumblebee/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-430xx-bumblebee/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-435xx-prime/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-440xx-prime/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/nvidia-340xx/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/nvidia-418xx/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/nvidia-430xx/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/nvidia-435xx/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/graphic_drivers/nvidia-440xx/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/network_drivers/r8168/MHWDCONFIG' is invalid!
Warning: config '/var/lib/mhwd/db/pci/network_drivers/rt3562sta/MHWDCONFIG' is invalid!
> Installed PCI configs:
                  NAME               VERSION          FREEDRIVER           TYPE
           video-linux            2018.05.04                true            PCI

You probably want to use the nvidia one.

chroot again, then mhwd -f -i pci video-nvidia

Maybe also reinstall linux54: pacman -S linux54

Then leave chroot and reboot. Check which kernel versions are shown in grub advanced tab. should be 5.10.32 and 5.4.114

This is producing an error:

> Installing video-nvidia...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/nvidia/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
:: Synchronizing package databases...
warning: downgrading package lib32-nvidia-utils (465.24.02-1 => 460.73.01-1)
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
resolving dependencies...
looking for conflicting packages...
:: nvidia-utils and nvidia-440xx-utils are in conflict (nvidia-libgl). Remove nvidia-440xx-utils? [y/N] error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)

:: nvidia-utils and nvidia-440xx-utils are in conflict
Error: pacman failed!
Error: script failed!

Should I remove the package that is conflicting?

Yes, 440 is long gone already. You last update must have been several months ago. :thinking:

@moson, Yes, indeed. I kept delaying the update. Lesson learnt. By the way, the removal is proving tricky. pacman -R nvidia-440xx-utils or pacman -Rs nvidia-440xx-utils causes:

checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-440xx-utils breaks dependency 'nvidia-utils' required by lib32-nvidia-utils
:: removing nvidia-440xx-utils breaks dependency 'nvidia-440xx-utils=440.100' required by linux54-nvidia-440xx
:: removing nvidia-440xx-utils breaks dependency 'nvidia-utils' required by nvidia-prime

Try removing linux54-nvidia-440xx first.
Then do sudo pacman -S nvidia-utils and replace if it asks.

afterwards run the mhwd command again.